Hello,
I own a Smart and Friendly CD Rocket 8020 CD burner (firmware v1.24, the latest). It works beautifully in DOS and Windows 98. However, when I boot into Windows 2000 Professional (SP1) the drive is not available. It does not show up at all on my system.
This was not always the case. On a recent clean installation of Windows 2000, the burner was visible for a short time. This had never happened before. There were two things that may have contributed to this:
1. I had a CD in the drive at boot time. This was the first time I had booted Win2k with a cd in the burner when reason 2 was in effect.
2. Since it was a clean installation of Win2k, there was no cd burning software on my system; specifically Easy CD Creator 5.
Easy CD Creator's documentation says it installs the latest ASPI layer onto the system. Before installation, I ran Adaptec's aspichk.exe program to check my ASPI layer. This program may or may not run correctly in Win2k, I'm not sure. The program reported no ASPI layer.
After installation of Easy CD Creator, I robooted my system. My CDR8020 drive was no longer visible, and aspichk.exe reported an updated ASPI layer. My suspicion is that before the EZCD installation, win2k saw the drive as a regular CD-ROM instead of a CDR.
My SCSI card is an Adaptec AVA-2906. I have worked with Adaptec's tech support on this problem, and as far as we could tell, the card is functioning properly. Smart & Friendly is out of business, so they can't help me.
The thing that triggere my post here, is the web page at: http://www.ntcompatible.com/old0100.shtml
This page lists the S&F 8020 as compatible with win2k and says to make sure you have the latest ASPI dlls. I have downloaded and installed the latest ASPI dlls from Adaptec's web site, but they have made no difference. Any ASPI dlls at all seem to make my burner cease to be visible from Win2k.
Under what configuration did you test the CDR 8020 in Win2k in order to get it working? What version of the ASPI dlls did you use? What version of the CDR firmware did you have? Do you have any thoughts as to why this may be occurring? Does anyone else have the same burner and similar configuration working under Windows 2000?
I'm really stumped on this one. Any help would be appreciated.
Thanks,
Dave