Take a look at the following:

Unistall 100% Ez CD Creator from Win2k (note that the plain words comes from
Most times the drivers of EasyCD and Nero can cause conflicts.

(This is typically caused by lower level system drivers associated with
writing UDF. If everybody is following the rules as defined by Microsoft,
this should not be the case).

Unistalling Ez CD Creator is one solution however the Ez CD Creator
unistaller leaves behind several files which still causes problems to Nero
(delete all following files, if present)

(In ECDC 4.xx releases there are separate installs for ECDC and DirectCD. If
you uninstall ECDC in anything before ECDC 5.0, you will not uninstall
DirectCD. This is a separate uninstall process which explains why you see
the files listed below and still listed in the registry. This would be the
case for any Roxio application that is still left installed (i.e Take Two or
DirectCD) :

- CDR4VSD.SYS (Used by ECDC and DirectCD in Windows NT4)
- CDR4_2K.SYS (Used by ECDC and DirectCD in Windows W2K)
- CDRALVSD.SYS (Used by ECDC and DirectCD in Windows NT4 (older versions)
- CDRALW2k.SYS (Used by ECDC and DirectCD in Windows W2K)
- CDRALWNT.SYS (Used by ECDC and DirectCD in Windows NT4)
- CDRALVSD.SYS (duplicate)
- CDUDFRW.SYS (This does not exist in NT4/W2K. There is only a CDUDFRW.VxD
used by DirectCD in 9x)
- CDUDF.SYS (Used by DirectCD in Windows NT4/W2K)
- CDRPWD.SYS (Used by DirectCD in Windows NT4/W2K)

which rested in the directory C:\WINNT\SYSTEM32\DRIVERS and the file
CDR4VSD.DLL in the directory C:\WinNT\System32 and restart Windows.

Additional: When the Adaptec software is uninstalled the registry is not
reverted to use the Windows "cdrom.sys". You have to edit the registry to
stop the Adaptec driver after uninstall. The critical keys that the software
leaves behind after being uninstalled are in:
E-BFC1-0 87002BE10318}

In this section you will find two keys called "UpperFilters" &
"LowerFilters" and you will need to delete both of these keys and reboot to
restore Win2K to the default CD driver. You should also search for other
keys containing "cdralw2k" and "cdr4_2K" and delete these then delete these
two files AFTER the reboot. Note you cannot delete the references to these
in "ENUM" as they are generated from the class driver, but they will not be
there after the reboot.

(This is the same issue as described above. It would be dangerous to delete
the whole upper and lower filter keys if somebody else had their drivers
installed in this location. In W2K it is not a good idea to only delete the
upper and lower filter keys. You must also delete the Service registry
entries and the drivers themselves. Again, this will be handled if ALL of
the Roxio applications are uninstalled (i.e ECDC, DCD, and Take Two).

In addition there is an article in the MS knowledge base about this..




----- Original Message -----
Sent: Saturday, March 15, 2003 3:23 AM
Subject: [PEDA] Roxio, Nero, Virii and crashes

> HELP!!! In attempting to uninstall DirectCD, I've gotten my system into a
> state where it won't boot! Sorry if I'm off-topic, but I'm desperate and
> these lists are the best resource I've found for help. Others may save
> themselves much grief by learning from my experience. I'm cross-posting to
> the DXP list as well.
> My recent queries on the web encouraged me to buy Ahead Nero to replace
> Roxio's DirectCD. Thus far, that advice still seems to have been good -
> is far superior to DirectCD, and far more stable.
> I had them both installed and peacefully coexisting. On advice that I
> not have two CD burner packages installed, and the realization that I'd
> use DirectCD again, I uninstalled DirectCD. I've since learned that
> DirectCD is in and of itself the worst virus infection I've ever seen. It
> won't uninstall cleanly, their "tech support" is no help, and now my
> won't boot. When I boot into Windows 2000 Pro, it appears to boot
> In searching the web I've found that many others have come to similar
> but no solutions to my specific problem. First sign of trouble is that
> my auto-start apps are still getting settled in, a box appears saying
> "Preparing to install...." with no appname. Its cancel button does
> About ten seconds later, the box goes away - and then comes back. Total of
> about 6 times or so, and then the system does a normal shutdown and
> Again, and again, and again.
> I've killed almost a full day on this so far, with no end in sight.
> Spelunking in the registry finds many hundreds of entries sprinkled all
> the place, referring to Roxio, DirectCD, etc. I spent a couple hours
> absolutely every registry entry which looked remotely related. This was
> a "crippleware" version of DirectCD that could just barely write a data
> any other operation took me automatically to Roxio's website to buy the
> version. Thus I'm not only pretty ticked at Roxio, but also at Dell. Dell
> preinstalled this on the machine, and the sales pitch implied I was
> the full version. Thus I consider this to be bait-and-switch, plain and
> simple. So Dell is now on my blacklist too (it wouldn't have taken much
> their fiasco with proprietary power supplies, but that's another whole
> I've tried unplugging the CD drive and rebooting, unplugging all the USB
> peripherals on the theory that something there is trying to install, etc.,
> all to no avail. I've already run the Win2K Repair from the CD; no joy
> either. So I'm getting ready to reinstall Win2K, and cringing at the
> of all the drivers etc. that I'll need to set up again.
> There is a slim chance that this might have been precipitated by a virus
> other than Roxio, because one of my clients had a particularly nasty virus
> infection last week. But I haven't downloaded any executables from them,
> I'm well-guarded against other forms such as macros. And the problem
> up right after I ran Ahead's driver clean utility.
> My best guess at present is that Roxio left something around which now
> detects that the rest isn't installed, and it's trying to repair the
> installation. But that's only a guess.
> I can get to the Windows recovery console, and also to Safe mode. but
> had any luck repairing things that way. Any and all tips gratefully
> Steve Hendrix

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* To post a message: mailto:[EMAIL PROTECTED]
* To leave this list visit:
* http://www.techservinc.com/protelusers/leave.html
* Contact the list manager:
* Forum Guidelines Rules:
* http://www.techservinc.com/protelusers/forumrules.html
* Browse or Search previous postings:
* http://www.mail-archive.com/[EMAIL PROTECTED]
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Reply via email to