Windows ASPI Package
Adaptec has it's own downloadable ASPI layer pack.
9x/Me/NT4/2k/XP/2003/Vista/2008/7/8/10 (plus all
64-bit versions). If you use Wine, it should also
run on Linux and other x86-based Unixes
"Some software may attempt to access optical drives
using SPTI (SCSI Pass-Through Interface). This
programming interface was created by Microsoft to allow
direct access to hardware like optical drives.
Unfortunately, the implementation in NT 4.0 is very poor
and unstable. Attempting to access hardware through SPTI
may result in STOP or Dr. Watson errors. If the option
is available, use ASPI access instead."
Burning at 1,800KB/s under NT
I had tried using a 3.36 / 4.70 Buslogic BT646S
to drive a Plextor PX-W124TSi, but all it would do upon
starting to write is fill up the device buffer, and then
the device buffer would drain. Once drained, the burn
terminated. This may be an issue with the BusLogic
I then installed a Corvette with a wide cable, a
Plextor PX-W124TSi (term disabled), 50 to 68 pin
converter, and left the heatshrinked active terminator
at the end of the F/W cable intact. I used the Adaptec
4.71 ASPI package (includes Win2k version) which
installs version 4.60 (correct for NT 4.0). I used
IMGBurn. Fired the Plextor PX-W124TSi up, waffled
through the IMGburn screens, and waa-laa, we have a
successful burn taking place.
Corvette on 95-Y/NT4/Nero 5.10
I did have to install the Adaptec ASPI layer, ForceASPI could not successfully complete the install. Nero tech support, trying to be helpfull, eventually advised me to enable DMA on the drives, like I was using W9x/XP or other kiddie OS. Hint: there is NO setting under NT to enable DMA. If you run NT Diagnostics, it reports DMA is not being used by the system. Yet Nero Infotool reports DMA... Go figure.
Burning with Nero 4.0 and WfW
One Possible CD Burning
CD and DVD Musings
The data stream required for a 4x burning process is about 500Kbps, which can be done with a reasonably configured 486DX33 / 16MB and a sufficiently fast HD subsystem already. But the lot of the fat software packages require Win 9x / ME or even XP - were the latter two are often too big for older machines.
The difference between CD-R and CD-RW burner is mainly just a firmware issue - and a slightly modified laser control. Since CD-RW includes burning CD-R already the manufacturers opted to drop sole CD-R burners in favor of lower-priced CD-RW units. I can see no problem with it. I would always prefer a CD-RW capable burner over one that does only CD-R.
Far better however is a multiformat burner that also does DVD in its various manifestations (DVD-R, DVD+R, DVD-RW, DVD+RW and DVD-RAM ... and Double Layer) ... plus the CD-R / CD-RW stuff. Would be a bit more expensive but more versatile as well. Win98SE is sufficient to run e.g. MyDVD software for creating home-made DVDs My PC300GL 6561 with 333MHz P-II and 128MB does fine here - and it is far from being a "modern" system.
Controller and Device Issues
Odd challenge is with a wide hard drive and burner on the same controller. I suppose that having a F/W drive talking to a burner is overkill, since the HD will be sitting around, waiting for the CD burner to come up for air. I had tried to separate HD and burner onto separate controllers.
A kicker is a Wide drive and CD burner on a F/W. I had a 20x Plextor (with the HPDB68 port) that refused to run on a Corvette until I disabled wide messages. Perhaps running the burner and a dedicated HD on the same Buslogic BT-646 would then be the best setup.
Lack of ASPI Layer
Bootable CD on PS/2
I have probably found out why Server 95 doesn't want to boot from CDs, except from the ServerGuide CD (thanks Peter!) and a few others.
The key is the first sector, a kind of "Boot Sector". Not a real one, of course. It is described in the original El Torito (Boot CD) specification, but seems to be forgotten in the CD layout description and marked as "not necessary". And since El Torito is a specification by Phoenix and IBM, IBM CDs do work - they knew how to do it. The ServerGuide CD has this "Boot Sector". And others, who implemented El Torito based on the specification, just skipped this part.
Writing an utility would be a bit difficult, but not impossible, because it would need to analyze the disk image if it already has this boot catalog. If not, it would need to generate a new one. And if it has, it could copy it to sector 0, and subtract the negative offset to calculate the new relative addresses. But I'm not sure if I can program all these things ... or better: I'm sure I can't program all these things. Maybe someone other wants to try it? *g*
Here are the specs, the boot catalog can be found at section 2: HERE