release the addon from the title, no cab inside. it directly integrates ASPI Layer into Windows source.
info:
http://www.adaptec.com/worldwide/support/d...exe&sess=no
download link:
ASPI Addon
size=133kb
md5 hash=C7B673DB50B9D854DEE6A4DE8D1208EB
Full Version: [Release] Adaptec ASPI Layer 4.71.2 True Addon
Hi,
I don't get it? Is it something to do with increased cd/dvd drive compatibility?
I currently use Nero's ASPI.
laze.
I don't get it? Is it something to do with increased cd/dvd drive compatibility?
I currently use Nero's ASPI.
laze.
QUOTE
ASPI for Win32 Overview
The architecture of SCSI makes it possible to access a wide variety of devices using a single bus linked to a host
computer with a SCSI host adapter. Support for peripheral devices in Windows (98, ME, NT, 2000 and Windows
XP (32-bit)) is normally achieved through device specific drivers layered on top of the operating systems’ native
SCSI support.
Because of the tremendous diversity of SCSI devices, no driver can support all SCSI peripherals. Instead,
separate drivers are needed for each major class of installed SCSI device. These drivers share the host adapter
hardware through the operating systems’ native SCSI support. The native SCSI layers are different between
Windows 98/ME and Windows NT/2000/XP (32-bit). In addition, development and debugging of VxDs or kernel
mode drivers can be very difficult. The need for a standard SCSI programming interface to simplify SCSI
application development and ease the porting of SCSI applications from one Win32 platform to another brought
ASPI for Win32 into existence.
The Advanced SCSI Programming Interface (ASPI) for Win32 was designed to increase compatibility and
simplify the connection of SCSI peripheral devices like tape, CD-ROM, WORM, magneto-optical, scanners, and
other devices. It defines a protocol for SCSI applications (called ASPI modules) to submit I/O requests to a
single operating system driver (called the ASPI manager). Access to the operating system driver is made
through a Dynamic Link Library named WNASPI32.DLL.
The architecture of SCSI makes it possible to access a wide variety of devices using a single bus linked to a host
computer with a SCSI host adapter. Support for peripheral devices in Windows (98, ME, NT, 2000 and Windows
XP (32-bit)) is normally achieved through device specific drivers layered on top of the operating systems’ native
SCSI support.
Because of the tremendous diversity of SCSI devices, no driver can support all SCSI peripherals. Instead,
separate drivers are needed for each major class of installed SCSI device. These drivers share the host adapter
hardware through the operating systems’ native SCSI support. The native SCSI layers are different between
Windows 98/ME and Windows NT/2000/XP (32-bit). In addition, development and debugging of VxDs or kernel
mode drivers can be very difficult. The need for a standard SCSI programming interface to simplify SCSI
application development and ease the porting of SCSI applications from one Win32 platform to another brought
ASPI for Win32 into existence.
The Advanced SCSI Programming Interface (ASPI) for Win32 was designed to increase compatibility and
simplify the connection of SCSI peripheral devices like tape, CD-ROM, WORM, magneto-optical, scanners, and
other devices. It defines a protocol for SCSI applications (called ASPI modules) to submit I/O requests to a
single operating system driver (called the ASPI manager). Access to the operating system driver is made
through a Dynamic Link Library named WNASPI32.DLL.
Apparently. That's from the aspi32.pdf included with the original installer. For the rest, all I know is that the Adaptec ASPI layer is as close to 'the standard' as you can get. I don't know how it compares to Nero's.
boooggy
I think you forgot to change the date in http://boooggyaddons.xable.net/ cause it still shows 11/25/2006
I think you forgot to change the date in http://boooggyaddons.xable.net/ cause it still shows 11/25/2006
download link updated and also fixed some typos in the inf...... 
as borat would say, vary nyce 
Can I use this on WinXP Pro x64?
Edit:
I found the original ASPI driver setup of adaptec, there are x64 drivers.
how can I edit the already integrated add on?
What file do I need to edit to change the 32bit to 64bit?
Edit2:
I edited DOSNET.INF, changed aspi32 to aspi64
also replaced the aspi32 files with aspi64 files.
Is this enough boooggy?
Edit:
I found the original ASPI driver setup of adaptec, there are x64 drivers.
how can I edit the already integrated add on?
What file do I need to edit to change the 32bit to 64bit?
Edit2:
I edited DOSNET.INF, changed aspi32 to aspi64
also replaced the aspi32 files with aspi64 files.
Is this enough boooggy?
dont know...please send me the download link for x64 aspi......
aspi_v471.exe
http://download.adaptec.com/software_pc/aspi/aspi_v471.exe
It's only for x64 itanium machines....
http://download.adaptec.com/software_pc/aspi/aspi_v471.exe
It's only for x64 itanium machines....
Hello,
Please, can you explain me what stepes i must do to make them integrated in the windows XP cd source ? Do i have to copy the files in I386, and that's all ? Do i have to put the cab in the addon nlite app ?
Thank you very much, i am a true BIGginer ^^
Please, can you explain me what stepes i must do to make them integrated in the windows XP cd source ? Do i have to copy the files in I386, and that's all ? Do i have to put the cab in the addon nlite app ?
Thank you very much, i am a true BIGginer ^^
Thank you, it works great on my xp sp2 Just have to put it in the addon nlite box
Just have to put it in the addon nlite box
I just tried integrating this via Integrator 1.5.1 and after installation I used ASPI check and it shows nothing installed.
Are others still using this Addon with 1.5.1?
Here is the order of integration:
RyanVM update only
WMP11 slipstream
WGAV and DX9
NR_IE7en_Addon_1.1.0
ASPI, dotNet All-in-One, and Java6
Each of these steps had its own /I386 directory and I just kept building upon each build so that I could go back at any point in the builds. I think I might just try adding ASPI addon all on its own in one of my builds and prior to the dotNET and Java stuff and see what happens.
If I have an application that requires looking for this ASPI layer, then how do I force one Addon to come before another AddOn?
Are others still using this Addon with 1.5.1?
Here is the order of integration:
RyanVM update only
WMP11 slipstream
WGAV and DX9
NR_IE7en_Addon_1.1.0
ASPI, dotNet All-in-One, and Java6
Each of these steps had its own /I386 directory and I just kept building upon each build so that I could go back at any point in the builds. I think I might just try adding ASPI addon all on its own in one of my builds and prior to the dotNET and Java stuff and see what happens.
If I have an application that requires looking for this ASPI layer, then how do I force one Addon to come before another AddOn?
please integrate this addon with nlite.
i didnt have any problems.....
i didnt have any problems.....
QUOTE (boooggy @ Apr 21 2008, 06:37 AM) 
please integrate this addon with nlite.
i didnt have any problems.....
i didnt have any problems.....
I got it to work with RyanVM, I believe I just did something wrong on my part because all I did was start over.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.