> Honest opinion, I agree with this. I am a hobby programmer and don't want to waste my time learning to write a driver. The problem is that no one offers a free download or some kind of GNU license of such a driver for non commercial use. I don't want to refer people to download demos of certain products just to use their ASPI driver. <
This is a valid point.
So we need either:
1. A freeware ASPI Layer for Windows NT/2000, which works fine and stable
2. A freeware alternative to soemthing like ElbyCDIO
Both have their pro- and cons:
1. A really complete replacement of the Adaptec ASPI is a Nightmare, because it MUST open the controllers directly. The reason is simple: NT(2000, XP, ...) has devided its peripherals into "Device Classes", like Scanners, CD-ROMs (this includes DVD-ROMS and Writers), Harddisks, etc.
ASPI is per design a "Bus" Interface (hence the name Advanced SCSI Programmer's Interface), so old Applications designed using ASPI may try to send commands to Scanners, Harddisks, CD-ROMs, ... via the Interface.
SPTI on the contrary works on Device Classes, in fact all SPTI commands must be directed through the devices class driver.
So, when designing an ASPI->SPTI converter, you must somehow enumerate the devices. Which classes do you include? Only CD-ROM class? (Well, someone who uses ASPI to write Scanner Software may really recommend Adaptec ASPI )
AFAIK ASPI has some strange notification methods from the Windows 3.1 days, which are still supported. (I believe Adaptec ASPI still supports 16 Bit Applications?)
The question is - how much effort must go into a "free ASPI Layer". If you only support a small subset of the original ASPI and restrict yourself to a specific device class like CD-ROM, this is pretty easy to do.
2. Well, having a "good I/O layer" for free without the old compatibility burden from the past would be indeed a good thing, but here you have the problem of writing at least a 9x driver.
BTW, ElbyCDIO only offers access to CD-ROM class devices (hence the name), so the security problems aren't as bad as I first thought in one of my previous posts.
Conclusion: A free ASPI layer would be nice, but would encourage peaople to use this ancient interface. It would probably be not as compatible to all applications as the Adaptec ASPI.
A freeware "modern" I/O layer for all Windows platforms would be better, but is much work, and who is willing to do that?