KW> The fundamental problem is that I've got a SCSI CD-ROM and an
 KW> Adaptec SCSI controller. To run MSCDEX I must run ASPICD.SYS.
 KW> To run ASPICD.SYS in DOS I need to load the ASPIxDOS.SYS device
 KW> driver. Well, since OS/2 has control of the SCSI board, there
 KW> seemed to be no way to get ASPI7DOS to load. (My attempts to do
 KW> so all failed in a variety of interesting ways.)
 KW> It turns out that the answer is _quite_ simple. The ability to
 KW> load ASPICD in a DOS session is built in to OS/2 v4! They have
 KW> provided an "ASPISTUB.SYS" to be loaded in your DOS session that
 KW> allows the DOS ASPICD.SYS driver to communicate with the OS/2
 KW> OS2ASPI.DMD. Once ASPICD is loaded, MSCDEX loads without a
 KW> problem and my program runs!
hummm... i run a SB16/SCSI-II card... i believe that it uses Adaptec chips 
also... as the SB drivers may handle this in my case, i thought i'd look for 
any similarities to your stuff...
on my system, ASPISTUB.SYS is located in my \OS2\MDOS directory. taking a 
look at it turns up the following text...
  SCSIMGR$
STUBDD:  OS/2 ASPI Driver, ASPI Specification Version 2.0, installed.
 4 SYS0664: VASPI.SYS is required for STUBDD on OS/2.
 5 SYS0667: STUBDD requires OS/2 Version 2.0 or above.
 VASPI
looking for VASPI turned up VASPI.SYS in the same directory...
inspecting VASPI.SYS turns up only SCSIMGR, ASPI and VASPI which are assumed 
to be simple driver calls...
my system is running Warp Connect without the networking installed...
ASPISTUB.SYS       386 10/03/1994 14:43
VASPI   .SYS      8928 12/01/1994 12:45
 KW> Now, can anyone tell me where ASPISTUB.SYS is documented? Or even
 KW> that what I've done is provided? I searched through every .INF
the above info may point you in additional directions... i've found that i 
generally need to research several references before finding something 
related to my interest...
)\/(ark
---------------