WINDOWS
NT DEVICE SETTINGS
Before you being burning stuff using NT (which,
in my opinion, is the best OS to burn under with CDRWin), you have to turn off that damned
"Auto Insert Notification". (By the way, you
should do this anyways becuase of certain viruses that will use the AIN it its advantage
to automatically install itself without your knowledge!) Anyway, you can
disable it by changing the following value in the system registry...
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/
Cdrom/Autorun=0
Now, you'll also need to make sure you've got
up-to-date ASPI drivers, which you don't if you've got NT4SP3 running (unless your CD-R
came with certain software that has already installed these - but most of the time this is
not the case).
If you have an Adaptec SCSI card and are unable
to run CDRWin under Windows NT, then download and install the latest drivers from
Adaptec's FTP site...
ftp://ftp.adaptec.com/pub/BBS/winnt/aspi32.exe
If you do NOT own an Adaptec SCSI card or wish to use an IDE CDROM drive or recorder, then
you can get the required ASPI drivers from the following FTP site...
ftp://grc.com/aspi_me.exe
The following files will be installed/updated on your system...
WINNT40\SYSTEM\WINASPI.DLL
WINNT40\SYSTEM\WOWPOST.EXE
WINNT40\SYSTEM32\WNASPI32.DLL
WINNT40\SYSTEM32\DRIVERS\ASPI32.SYS
You must also make sure that you have the proper ATAPI device driver and that is is being
started on your system at bootup...
1) Open the "Control Panel" folder and click on the "Devices" icon.
2) Find the ATAPI entry in the device driver list.
3) If the status is NOT set to "Started", then highlight the ATAPI entry and
click on the "Startup..." button. Select either the "Boot",
"System", or "Automatic" option.
WARNING: The ATAPI.SYS driver under NT 4.0 Service Pack 3 has a bug that prevents our
software from operating correctly with ATAPI CDROM devices. The fixed driver can be found
at...
http://www.goldenhawk.com/support/bmnt4.zip
Copy the new ATAPI.SYS driver into the WINNT\SYSTEM32\DRIVERS directory. Note: Service
Packs 4 and later do not have this problem.
Credits: this is an edited version of a
message originally posted on Goldenhawk's site at http://www.goldenhawk.com/support/setup.txt.
|
