drcrunch

I have to admit it, I will probably go with 7 soon. All of my laptops are on it and it seems to be surprisingly stable for a relatively new MS product. Networking sharing seems a little buggy at times but I am not sure if that's just a Norton "Feature" or if MS is the cause. I am a slow converter by history, I still have rock solid SCO Unix 505 P1s running for specialized apps at work. The first laptop that I set up with MS 7pro 64 bit hurt $$$ wise as all of my video and publishing apps had to be upgraded.

to ianymaty Thanks for the leads. I have been to the manufacturers websites multiple times and the firmware was not listed in their docs, only through the utilities so I missed it. Oh, well. I had the LG maxed out on the firmware already but the LiteOn was new and likely had to do with their internal identification issues, though whatever their fix was it seems to have worked. I had to install the update in safe mode. Is this a typical behavior? The LG updated during a normal session. I also reduced my memory by 2gigs as XP apparently only does 4gigs max and according to some opinions has problems when it has too much. I also increased the virtual memory page size but I doubt this had any effect as I was messing with another piece of software (old DVD shrink with the "out of memory error." Didn't help that app either. Regardless, I just had a successful burn and verify with the units and they worked. I will run ImgBurn through it paces tomorrow and see if the fix holds up. to LIGHTNING UK! I read that you have a bunch of optical drives in your various machines, have you run into the issue with XP and identical optical drives not being properly addressed and recognized (SATA)? http://www.computing.net/answers/windows-xp/two-new-dvd-drives-will-not-work-code-42/192082.html Also, when reading the hardware info, I read that I have a lot of loaded legacy drivers. I have never examined the guts of XP in that detail, is that normal? To mmalves, thanks for the hardware info link. It led to the update.

I included the info that was gleaned from the log in my first comments as it looked very clean to me. I may be mistaken as I do little hardware debugging and could miss something. I understand fully that the problem is on my end but need some guidance on a start point. Here is the most recent part of the log. ImgBurn-brief.log There are much older entries as I have been using the app for quite a while and the hardware has changed but these show the recent behavior. The first entry shows a successful burn but the verify froze. This was a new change in behavior as the previous freezes were before the burn started. The third entry shows the freeze at the set book type, the log records the speed being set. It has done this several times but he log only shows the one incident. The last is a successful burn with one of the drives disconnected. The only item that I changed in the time between the burn freeze and the verify freeze was to retire some old shares that referenced the drive letter now occupied by the second optical drive and I am unsure of the relationship if any to the acute problem. If this is a hardware problem or a driver issue but it is not showing itself elsewhere, any advice on where to begin the hunt?

Ah, a cogent bit of advice. Thank you. See attached.Hardware.html

It's a joy that all of you are measuring your hardware with each other, but is this as useful as help gets?

With firmware and drivers up to date, do you have any advice how to fix the problem?

XP 2 Twin BluRay drives LG WH10LS30 LiteOn iHBS212 If either drive is installed separately they work just fine when burning. When both are installed if an attempt to burn is made with either unit the burn freezes at Change Book Type commands after reporting a successful setting of speed. The process can be aborted but the unit remains frozen and even notepad wont respond to any command when the freeze happens (I was trying to log observations). The ImgBurn log only shows the successful speed set then the abort command. The application will not close and it has been necessary to hard reboot as the shutdown commands won't proceed. Also noted is that Nero can use either drive to record and does not seize up but once the freeze has happened Nero cannot access the affected drive either.