InCD 4.0.1.0 disabled my cdrom drive

[edsonh]

Summary:

I have 2 CD drives; one LG CD-ROM CRD-8480C and one HL-DT-ST CD-RW GCE-8520B (also LG). I installed InCD 4.0.1.0 and the system crashed shortly after every windows boot. Now the system is stable, but no longer recognises my cd-rom drive.

===============

LONG version:

I just installed InCD 4.0.1.0 and after rebooting Win98SE presented me a BSOD mentioning "voltrack.vxd".

Then I chose windows safe mode and uninstalled the new InCD and put the 3.5.24.0 version back.

In the system properties both drives were appearing TWICE, both were assigned the D and E letters. I removed one of each to match the config prior to the incident.

Now the BIOS startup isn't able to see my cd-rom drive !!
I still can see it in windows safe mode, but both cd drives are disabled then (what i assume is normal)


?? What has the new InCD done to my computer ??


I had InCD 3.5.24.0, InCD EasyWrite Reader (installation file: 750.220 bytes) and Nero Express 5.5.10.20 bundled -- all installed and no problems at all. Both drives were working and even were used by Nero.

My CDRW drive is new and I had nothing but Ahead's software installed. It came bundled with Nero Express 5.5.9.9 and InCD 3.39.0 (which I never succeded installing - had to download a newer version from the website).

I have a VIA chipset motherboard (don't ask me which ) and the "4in1 435v" drivers installed. It worked fine. I chose that drivers version after reading the following note at http://www.viaarena.com/?PageID=300#old

"**Note: Win95/98/98SE are now relatively old operating systems, and drivers are no longer optimized for those operating systems. Many users of VIA chipsets who run Win95/98/98SE report that using an older version, such as VIA 4in1 version 4.35, they experience a more responsive system."


Suggestions on how to make my computer, BIOS, whatever, detect my CDROM drive once again??? Anyone? Please?

By the way, I'm sorry if I made any mistakes or was impolite. I'm a newbie to this forum and am quite distressed by this whole unnecessary mess.

==========================

Below, parts of a CONFIGSAFE log of changes after InCD 4010 installation. CONFIGSAFE came with the IBM Aptiva computer I own.

I installed the new InCD on 20/06/03.


-> means the file that IS now
<- means the file that WAS then
+ means the file has been added
- means the file has been deleted


ConfigSafe System Changes Report
--------------------------------

Changes Starting : 19/06/03 00:00:26 System Snapshot
Changes Ending : 21/06/03 14:14:30 Now

System Information

19/06/03 00:00:26 21/06/03 14:06:00
Coprocessor: Yes Yes
Base Memory: 163264K 163264K
Windows Version: 4.10 4.10
Processor Vendor: AuthenticAMD AuthenticAMD
Processor Type: AMD-K6(tm) 3D processo AMD-K6(tm) 3D processo

Drive Information

19/06/03 00:00:26 21/06/03 14:06:00
A: Present Present Removable
C: 2177644 Kb 2034184 Kb Fixed
- D: 0 Kb Not Present CDROM
E: 0 Kb 0 Kb CDROM

============= notice the absent cdrom drive

WINDOWS\SYSTEM changes:

CatRoot
{F750E6C3-38EE-11D1-85E5-00C04FC295EE}
<- CATMAST.cbd 16/04/03 03:14:12, 11374
-> CATMAST.cbd 20/06/03 22:17:32, 12994
<- CATMAST.cbk 16/04/03 03:14:12, 168
-> CATMAST.cbk 20/06/03 22:17:32, 192
<- HASHMAST.cbd 16/04/03 03:14:12, 54466
-> HASHMAST.cbd 20/06/03 22:17:32, 56194
<- HASHMAST.cbk 16/04/03 03:14:12, 4536
-> HASHMAST.cbk 20/06/03 22:17:32, 4680

WINDOWS\IOSUBSYS changes:

<- bsudfrdr.vxd 27/04/03 01:17:24, 114367
-> bsudfrdr.vxd 21/06/03 14:03:16, 114367
+ incdfs.vxd 23/05/03 14:57:34, 678681
+ incdpass.vxd 23/05/03 14:58:02, 153844
<- incdrm.VXD 27/04/03 01:17:24, 23715
-> incdrm.VXD 21/06/03 14:03:16, 23715



THEN I uninstalled both InCD 3.5.24.0 and InCD EasyWrite Reader and installed the InCD 4010. The changes were:

SYSTEM
CatRoot
{F750E6C3-38EE-11D1-85E5-00C04FC295EE}
<- CATMAST.cbd 16/04/03 03:14:12, 11374
-> CATMAST.cbd 20/06/03 22:17:32, 12994
<- CATMAST.cbk 16/04/03 03:14:12, 168
-> CATMAST.cbk 20/06/03 22:17:32, 192
<- HASHMAST.cbd 16/04/03 03:14:12, 54466
-> HASHMAST.cbd 20/06/03 22:17:32, 56194
<- HASHMAST.cbk 16/04/03 03:14:12, 4536
-> HASHMAST.cbk 20/06/03 22:17:32, 4680

IOSUBSYS
<- bsudf.vxd 05/03/03 15:38:22, 131784
-> bsudf.vxd 23/05/03 14:43:26, 8952
+ bsudf.vxd [new incd version].bak 23/05/03 14:43:26, 8952
- bsudfrdr.vxd 27/04/03 01:17:24, 114367
- CDRBSVSD.vxd 28/10/02 15:53:02, 14105
+ incdfs.vxd 23/05/03 14:57:34, 678681
+ incdpass.vxd 23/05/03 14:58:02, 153844
- incdrm.VXD 27/04/03 01:17:24, 23715

WINDOWS
- BsUDF.tbl 04/03/03 05:24:00, 381466
- UNMRW.cfg 27/04/03 01:17:22, 27458

===========================

If needed I may provide some more information (e.g. modified registry information)

[Inertia]

I suggest that you first read the thread at EasyWrite Reader on W98SE: BSOD (Exception w/ voltrack), which had the same blue screen "voltrack.vxd" error.

There apparently may be a connection with this error and an incompatible version of the EasyWrite Reader. As noted in the linked thread, different versions of EasyWrite Reader must be installed for InCD 4.0.1.0 and InCD 3.52.40.

I would start by uninstalling the EasyWrite Reader. InCD 4.0.1.0 is buggy and I would not recommend using it until it is stable. Since you report that the system BIOS is not detecting the CD-ROM, I would check to make sure that the "D" drive was not somehow disabled in the BIOS.

If the drive is properly set up in the BIOS, I would completely uninstall the "D" drive in safe mode and physically disconnect the power and IDE cables from the drive and reboot. Power down, reconnect the cables (check the motherboard connection for proper seating while you're at it) and hopefully the drive should be redetected upon startup.

[KCK]

edsonh:

In addition to Inertia's advice, I may note that sometimes it helps to clean up ghosts for other controllers in Safe Mode; see S14 in the InCD 3.x troubleshooting guide:

http://www.cdrlabs.com/phpBB/viewtopic.php?t=9597

I'm a bit confused by your CONFIGSAFE logs. If I understood correctly, right now you have InCD 3.52.40 and EasyWriteReader 3.3.2.0. To check for possible remnants of InCD 4.0.1.0, please post the Nero InfoTool report, and the contents of your C:\Windows\System\Iosubsys directory, as indicated in Q11 and S11.1 of the InCD guide. It would help if you could annotate at least some drivers, just as Traveller did in his post:

http://www.cdrlabs.com/phpBB/viewtopic.php?t=11305

[edsonh]

Thank you all for your attention and suggestions, but what I feared the most came to be true. My cdrom drive is permanently damaged and is no longer functioning (I tested it in other 2 computer I have). It's likely the BSOD were way too much for it. That explains why the BIOS didn't see it.

Thank you Ahead Software. I really appreciate your regard to your customers.
Next time, test your releases a bit further to save us an unnecessary headache and material ($$$) losses.

Inertia and KCK , I'm really grateful for the rapid replies you posted. Had the problem been something else I'm sure you'd have gotten the solution.

[KCK]

Sorry to hear that your CD-ROM drive is dead. I don't think a single BSOD caused by InCD 4.0.1.0 could kill a healthy drive, but it might have been the final straw in your case. Well, I sympathize with you, but most likely the drive would have failed soon anyway, and I would hesitate before blaming Ahead for what might have been a coincidence.

Anyway, if you still need help in cleaning up your Iosubsys directory, just give us the necessary information.

[Inertia]

KCK,

Ordinarily, I would agree with your statement above. However, I am much more skeptical after the experience found in the Incompatibility problem between Nero and Sony laptop docking thread.

It was actually determined that a Nero install was corrupting the firmware of the Sony laptop docking station, leaving it inoperable. I am not saying that this is the case with edsonh's experience, but that it can't be considered impossible.

[KCK]

Inertia:

Well, I was only referring to the BSOD mentioned by edsonh as the likely culprit.

On the other hand, there is something strange in edsonh's story. I don't know if he rebooted after uninstalling InCD 4.0.1.0, and again after installing InCD 3.52.40, but the double appearance of both drives in the system properties (Device Manager?) does sound weird.

Anyway, if we assume that InCD's installer has somehow corrupted the CD-ROM firmware, maybe the drive could be reflashed. The "Download search" for CRD-8480C at

http://forum.firmware-flash.com/

finds firmware v1.01, but the link seems to be broken.

[dburg]

The firmware of a device is flash through manufacturer proprietary, specific and confidential commands, hence, InCD which does not include any flashing command is totally unable to damage a firmware. Maybe Windows installation was corrupted???

[cfitz]

The firmware of a device is flash through manufacturer proprietary, specific and confidential commands, hence, InCD which does not include any flashing command is totally unable to damage a firmware.

I don't know what went wrong with edsonh's drive, and agree that it is unlikely that InCD directly caused the problem, but InCD does interact with the drive at an intimate level, so it shouldn't be summarily dismissed as a possible culprit. And since we have been down this path before, I would be a little hesitant to so quickly make as bold a statement as "totally unable to damage a firmware":

Does anyone know why would Nero be capable to damage the firmware of the Sony laptop docking station?

Ahead Software sent me an email about this and they said its total BS.

As to Nero changing or modifying any recorders firmware, this feat is simply technically impossible as anyone in the industry who has done any repair on recorders can verify. It would take a firmware upgrade utility to even create the potential for such an occurence.

with Chris O'Brien's help at sony, we were able to set up a test system and duplicate this error, and help to narrow down the causes and when its caused ... It is caused by our Installer program ... with the Sony Vaio Docking station attached, it is somehow corrupting the Docking stations firmware.

(All from the thread Inertia referenced above)

Déjà vu all over again?

cfitz

[dodecahedron]

Déjà vu all over again?

exactly!

[CCampbell]

It is true that with Sony and Ahead working together, we were able to determine that versions of Nero 5.5.72. thru 5.5.82 did cause the firmware on the Sony Docking station to become damaged. But if you had the latest firmware for that docking station installed then Nero 5.5.7.2 thru 5.5.8.2 would not cause this damage to the firmware to occur. And it only occured when using our installer, not when you installed manually. So, to be fair, the blame must be carried by both Ahead and Sony. Sony was never able to provide a sample docking stataion with this older firmware to our Engineers in Germany, so we were never able to get to the bottom of the issue to find the true cause.

And the likely hood that InCD 4 caused this damage to the recorder is very small, but again to be honest and fair, we can not rule this out 100%.

Of course, if Edsonh can re-flash the firmware and if the drive then begins to work again, this would suggest that InCD 4 in fact did cause this to occur. If the recorder still does not function, or can not be re-flashed even though attempted, then this suggest the drive was indeed on the way out. Which is not the first time for any model recorder.

So at this point, only 'edsonh' can help us all come to a better understanding as to the possible cause by attempting to re-flash the upgrade. Otherwise it remains an unknown, and we would not create a bug report or have or Q&A team and the recorder MFG test this for us.

Best Regards,

Craig

[cfitz]

Well and fairly said, Craig. I wish you were around here more often.

Now, could we entreat you to comment on the Nero 6 versus Nero 6 Ultra issues?

http://www.cdrlabs.com/phpBB/viewtopic.php?t=11348

Thanks,

cfitz

[dburg]

Astonishing this firmware flashing, as flashing a firewire requires to upload data to the device with dedicated command, then unlock the protection, initiate the rom flashing...

Too bad that we haven't the docking station, I would enjoy to see this with my own eyes (and an bus scanning tool ) But ok, this one was with Nero and Nero is not my department .

[dodecahedron]

yes, astonishing is the right word...

[edsonh]

KCK:

Sorry to hear that your CD-ROM drive is dead. I don't think a single BSOD caused by InCD 4.0.1.0 could kill a healthy drive, but it might have been the final straw in your case. Well, I sympathize with you, but most likely the drive would have failed soon anyway, and I would hesitate before blaming Ahead for what might have been a coincidence.

I also find it very unlikely a single BSOD could fry a healthy cd drive. However, they were a few. I rebooted a few times while altering a couple of things (eg uninstalling; installing the old InCD; removing the twin drives in the Device Manager).

It's possible the drive was on the verge of failing. However, what I cannot put up with is the fact the whole computer was fine until the very moment I installed the new InCD and it was unstable from then on. The computer froze rightaway.

After the reboot, it froze once again. I went into safe mode to uninstall it and install the old InCD. Windows kicked in, I opened the browser to visit Ahead's troubleshooting and Eudora to send them an email. BSOD.

Chose safe mode and then I realized there were two devices for each actual drive in the Device Manager. I removed the extras and rebooted.
Finally win98 was stable but the cdrom drive did not respond. Then I went on to tweak the bios and windows trying to make it come back to life.

What I blame Ahead for is not directly damaging my drive, but not testing their releases thoroughly and thus exposing their customers to crashes which may have material consequences. Besides, that causes a lot of unnecessary stress to whoever goes thru such an experience.

Enough of reading? yeap.

[KCK]

Thanks for the feedback, edsonh!

I agree with your general assessment of the situation.

I'm still puzzled why you had two devices for each actual drive in Device Manager after uninstalling InCD 4.0.1.0 and then installing InCD 3.52.40.

InCD 4.0.1.0 made a lot registry changes on my XP box. I didn't have time to look at them more closely, but at least some of them seem to touch rather low-level settings. Further, in contrast to InCD 3.5x, InCD 4.0.1.0 makes Explorer report additional properties for CD-ROM drives (e.g., whether they can read MRW discs). I don't know if this carries over to 98SE, but maybe a possibly unclean uninstallation of InCD 4.0.1.0 could be related to the doubling of devices which you saw.

Did you try to reflash your drive? You could ask the guys at the Firmware forum about the broken link.

[Inertia]

edsonh,

I hope that your LG CRD-8480C is still under the one year warranty and can be replaced.

If not, have you tried reflashing the drive firmware? If the drive is not replaceable under warranty, there is nothing to lose at this point. Even if it is replaceable, LG may authorize the reflashing before replacing it. Normally LG won't replace a drive failure due to a bad flash, but may allow it if the drive has already failed. You may want to check with LG to see what they will do for you.

If you decide to try reflashing the drive, you can get the LG CRD-8480C - Firmware version: 1.01 and carefully follow the procedure. Note in the readme.doc file that the drive MUST be connected as Master on the secondary IDE cable alone.

I can assure you that readers of this thread are curious whether reflashing the LG CD-ROM CRD-8480C may restore the drive to operation or not.

[dodecahedron]

I can assure you that readers of this thread are curious whether reflashing the LG CD-ROM CRD-8480C may restore the drive to operation or not.

VERY!

[dburg]

Further, in contrast to InCD 3.5x, InCD 4.0.1.0 makes Explorer report additional properties for CD-ROM drives (e.g., whether they can read MRW discs). I don't know if this carries over to 98SE...

Yes, the additionnal tab in the device properties is available under all OSes supported by InCD 4. It is a shell extension (an extension of the Windows Explorer), like the Load, Format and Erase entries in the context menu. The registration into Windows of this shell extension is done through a standard call to regsvr32 /s /c (that is, we do not modify this part of registry directly but ask Windows to do it for us). I expect that Windows does modify registry key for the user interface of its Explorer (HKLM\Software\Microsoft\Windows\CurrentVersion\Explorer\...), which should not be related to driver registry keys (HKLM\System\CurrentControlSet\...)

I've just asked to the installer author who confirmed that the InCD 4 shell extension is well de-registered during uninstallation.