Comments on: Solved: “Bluebirds” installer on LG GH22NS50 DVD-RW

By: Bruce in ND

Bruce in ND — Mon, 01 Feb 2010 05:04:12 +0000

THANK YOU for the link. I actually had it under my mouse on the LG site, but was so pissed at the Bluebirds I didn’t even realize it was there until I revisited the site to conform that it is a most current version of the firmware update (it is).

I have two of the GH22NS50 drives I bought from TigerDirect.com in my most recent build. Using them to do anything other than play a DVD while Bluebirds was on them was about impossible. VISTA 64 doesn’t seem to like them much.

The updater lets you choose the drives from a list, and then when one is done it calls for a reboot. I started the program again and did the second drive, and THEN rebooted.

It looked like it was going well – the Bluebirds disappeared from both drives – and then the FUN began.

Everything started burping and churning, and then my video cards puked. My triple monitor set up went totally out the window, my desktop image went postage-stamp size, the monitors “lost” their place and got their order mixed up, and when I went to open the graphics card control program it ran around the three screens until sliding off the bottom of one and disappearing.

It took two cold restarts, but finally VISTA brought everything back into submission, the displays could be worked with and the monitor program could be worked with.

At $29 each, the price was pretty good for the burners. At $75 an hour or so for tech work, it could have cost some to straighten out.

But for FREE COLLEGE, it gave me a friggin Master’s Degree in Advanced Cursing.

I will be looking VERY CLOSELY at any other LG purchases I might consider.

Again, thank you folks for all the postings in this thread. It helped a LOT!!!

By: sim

sim — Wed, 06 Jan 2010 14:12:42 +0000

So basically, as a FreeBSD Unix user, I now have to *install* Windows just to get rid of this Bluebirds cack?? Nice one. >:-(

By: Alex

Alex — Sat, 05 Dec 2009 22:25:34 +0000

Forget about it guys, problem solved.

It was not a problem with the drive itself, but a bug on WinXP. Even when you do the right procedure of replacing hardware on your machine (Control Panel>Add or Remove hardware>fisically remove it), WinXP still retain info about the old drive on registry, thus creating a conflict between them.

So, if you use XP and decide to change your IDE burner with a SATA one, be sure to format and reinstall windows to prevent further headaches and money loss.

Cheers!!!

By: Alex

Alex — Sat, 05 Dec 2009 04:32:12 +0000

Hi all.

I know that this post is starting to get a gray beard, but ive recently purchased one of this drives (my previous was an LG GSA-H10A) and im almost doing a genocide at the store because of him.

When i first installed it, i burned a normal DVD-R disc with him like a charm, but when i tried to burn a DVD+R DL, the problems started, lost two disc, one at LeadIn process and the other one with 2% burned.

Went to the store, asked for a replacement and got another one…went back to home, installed it and…ZAP…same error.

Ive started googling for it and discovered that countless people had the same issue with this crap and i couldnt find any answer to the problem than i stumbled with this site in hope to find a light. So, if anyone can give any help, ill turn them as my personal heroes!!!

Already sent an email to LG asking about it, but 3 days and no response.

By: Chris

Chris — Sat, 14 Nov 2009 19:36:14 +0000

Hello there my friend and thank you for the link. I do the same job and can almost tell the same story but we have only started to stock the drives this week and I am the first one to buy one. When I saw the little Bluebirds thing I thought what the whets this and how do I get rid of it so thanks mate for saving me some time

By: NEW FOOL

NEW FOOL — Thu, 22 Oct 2009 08:05:35 +0000

I am on Ubuntu os so the link to the fix didn’t help me right off…however I found that by installing a feature called “linux crossover” I was finally able to get at the birds. The windows fix worked just fine. I don’t know why, but I had to flash the drive twice for it to take effect. That haneous piece of subterfuge is about the most underhanded thing I have seen, and it really caused me a lot of problems and cost me a lot of hours. I didn’t know I was dealing with something that was essentially a root kit. Now it all makes sense. I was running 3 machines on Windows and the only one that was getting “bombarded” by Trojans and viruses (and bears; oh my) was the one with the lg optical drive. Whoever did this is a terrorist within our borders. Hope I helped someone. As for the evil-doers; I’d love to see them turning on a spit.

By: Richard Werth

Richard Werth — Tue, 13 Oct 2009 20:40:10 +0000

This guy who programmed this should be fired as soon as possible.
After hours and hours of searching I don’t see any way to fix this problem in a linux box.

Never – never – never again LG

greetings R. Werth

Moege der Kerl der das zu verantworten hat moeglichst bald gefeuert werden.
Nach stundenlager Suche sehe ich keine wirkliche Moeglichkeit das Problem in einem Linuxsystem zu loesen.

Nie – nie – nie wieder LG

Schoenen Gruss
R. Werth

By: Frank3

Frank3 — Wed, 30 Sep 2009 10:01:40 +0000

Annoying…wtf would they include this crap if it will only mean my time is spent removing it???

Thanks for the update. Lesson learned…no more LG products for me.

By: Luc P

Luc P — Mon, 28 Sep 2009 03:24:07 +0000

I did the update, worked out great. Now try to get two of these units running in the same system… Good old error code 42… What to do? What to do? After uninstalling the device(s) it picked it back up after reboot. But sadly only one device appears, but the second is present in my bios… What to do? What to do? Sent an email to LG technical. Will wait and see.

By: falcongirl2u

falcongirl2u — Wed, 23 Sep 2009 14:27:26 +0000

Thank you for that post. We are a white box (oem) builder and usually use Lite-on with very success. However, Lite-ons weren’t available in the QTY I needed so I switched to the LG. Know we are going to have to fix this on all of those drives… Also thanks to the other guy who figured it out, but we’re glad you complained!