lite-on 411 firmware problem (nimrod)

[nordic bro]

Hi -

I just bought a Lite-on 411s (says so on box and chassis). After reading posts I grabbed the *F revision firmware but can't write it to the drive (drive properties says revision is *5 or something).

I'm using Win98SE (I don't ordinarily use Windows) and tried executing the extracted icon and it says "Error - no drives found." I tried running the executable from a dos prompt and after booting with the win98 emergency disk but it won't run. Is there some step I'm missing? I found a post here about removing the drive from a device mgr so I tried that but get the same error ("no drives").

Currently it's set up as ide1:slave. I tried it as master - doesn't help. I can use the drive just fine to read (Windows) and write (Linux). Windows explorer shows it just fine. It seems the only thing that can't find it is the firmware from the Lite-on site.

Mike

[RJW]

Might me a mislabeled 451S. You could try the 451S firmware update.
451S is the newer version of the 401S. Design has changed so that it's cheaper to make.

[dhc014]

Use Nero InfoTool or DISCInfo to see the model and firmware. Don't just guess that it's "*5 or something"

[nordic bro]

Use Nero InfoTool or DISCInfo to see the model and firmware. Don't just guess that it's "*5 or something"

Thanks.

I never said or intimated I "guessed" at it. I was making the point that it unquestionably needed updating ahead of someone here telling me not to worry about updating it because it may already have current firmware. Since it was clearly not *F, therefore according to everyone requiring updating, there's no point in being more precise on which rev firmware it had OOB.

FYI (problem's fixed), I had already tried 451 firmware thinking maybe the chassis label was incorrect (since the problem was that the drive was fully usable except by the firmware patch). But I got an obtuse error and thought maybe the patch knew it was not a 451 and refused to run.

But after the first reply here I reran 451 patch and took a second look at the error. It was something to do with ASPI. So I started some DVD software and saw a wnaspi32* error and started looking around. Apparently some DVD software I had installed had at some point overwritten system *aspi* files (kind of a kooky software system allowing something like that to happen). I found a tip by someone of using something called "sfc" and was able to reload three CD-related system files.

After rebooting (don't Windows ppl ever get sick of incessant rebooting?) I tried the firmware patch and it finally completed. So the problem was an application overwriting system files. All seems to work Ok now.

Thanks for the help...

Mike

PS Since this entire mess and waste of time was due to some ill-behaved app's installation, is there some way to mask system files from app installations to prevent this sort of thing?