|
P A G E T W O O F T W O |
P A G E T W O O F T W O |
|
An Alternate MethodYou can also install the latest Adaptec ASPI drivers *without* the requisite Adaptec hardware or software in your system, by 'virtually' installing an Adaptec 2940 SCSI adapter (even if you don't actually have one). Do this by opening your Install New Hardware wizard: Start >
Settings > Control Panel > Add/Remove Hardware. After you have 'virtually' installed the phantom Adaptec SCSI adapter,
you will be able to install the Adaptec ASPI layer.
Many people have reported using these Adaptec ASPI layer 4.60 drivers with a variety of operating systems, including Win98, WinME, Win2K, and WinXP .. all with NO PROBLEMS. I've heard many people say things like, "All my ripping and
burning problems disappeared once I updated my ASPI drivers to v4.60
(1021)." After installing/updating your ASPI layer drivers, you can then remove/delete the phantom (virtual) Adaptec hardware from your system (via your Device Manager). I forget where I learned this trick. Plextor support, perhaps. ForceASPI is easier & quicker, which is why I recommend that route. People who are uncomfortable using 'hacked' software [ForceASPI] might prefer this alternate method, even tho it's a bit more complicated. Another trick is to download and decompress Adaptec ASPI layer v4.71.2 [the executable decompresses to a default folder named "\adaptec\aspi"]. Rename WNASPIXP.DLL to WNASPI32.DLL and copy this renamed file to your \windows\system32 directory/folder. You should then be able to download and install Adaptec ASPI layer v4.60 without a qualifying Adaptec product installed in your system. This method has only been tested/verified with Windows XP. If anyone verifies that it works for Windows 2000, let me know. Note that there is also a file named WNASPI2K.DL_ that comes with the Adpatec ASPI drivers v4.71.2. I would expect this to be the one to use [renamed to WNASPI32.DLL .. but I could be wrong]. Burning & Ripping with Force ASPII regularly rip CD audio with Exact Audio Copy, and burn CDs using a variety of software programs: Nero Burning ROM, Fireburner, BlindWrite, Feurio, Jeff Arnold's CDRWin (Goldenhawk), Plextor's PlexTools, and CD Architect, Alcohol 120% .. and a few others - all with NO PROBLEMS. I use a Tekram DC-390U3W SCSI controller. Note that Adaptec ASPI drivers work fine with a non-Adaptec SCSI card. The SCSI standard is apparently well defined. If you still have problems ripping or burning after installing the latest Adaptec ASPI layer drivers, it's usually due to a problem with your burner or CD-ROM drive. It might be a good idea to try ripping with a program such as AudioCrusher, which doesn't require/use an ASPI layer. Perhaps you might try updating your drive's firmware. Or perhaps you installed a program that loads proprietary drivers for packet-writing software. For info on the kinds of problems this can cause, check out the FireBurner
FAQs. Scroll down about halfway & read the answer to the question:
Will Fireburner co-exist peacefully with other CD-R software? Plextor drives are generally considered the best rippers [DAE] & burners. See here for more info about -> [Ripping CD Audio with Exact Audio Copy]. Using Non-Adaptec ASPI DriversCompanies other than Adaptec (such as LSI Logic, for example) also write ASPI drivers. These other ASPI drivers *should* work fine .. but you don't have to use a PC for very long to know that things don't always work the way they should. =/ Can I get an amen, somebody? There is a chance that the particular burning or ripping program that
you use was developed [by program developers] using ASPI drivers
different from the ones you're currently using. If your ASPI
drivers are different from those used by the developer of your particular
burning or ripping software, there's a chance that your system may experience
quirky
compatibility problems. USB/Firewire devicesUpdate 15may2003: Dick Johnson writes to say:
If you have trouble downloading the file from Nero, I've mirrored it here: wnaspi32.dll [160-KB, v2.0.1.74]. Another reader wrote to say:
Fireburner ASPI with Windows XPI heard reports of problems with Fireburner when it is used in systems
running Windows XP. Fireburner
is apparently a front-end for ASPI, and Windows
XP won't let you access ASPI as a *User*. The solution is
to log in as an *Administrator*. The folks at Fireburner are reportedly
working on a fix, and may already have one.
You can download these files here
(199KB), compliments of Dusty. He even included a nifty .nfo
file containing quick-n-dirty instructions. [You can open his .nfo
file with any text editor, such as NotePad.] Windows Media PlayerYou can usually use Windows Media Player v6.4 by following these simple instructions:
From then on, all files you select will open with WMP v6.4. [Thx to SkyPilot for this tip.] More ASPI-related InfoLearn more about the wonderful world of ASPI at Bart's, .. Computall, .. Plextor,.. Terry Burke's,.. Chicken Systems and Mike Richter's. For your hypertext convenience, this ASPI guide can be found at any of these fine Radified URLs: It has become surprisingly popular since search engines discovered
it. Try searching for ASPI in either Google
or Yahoo,
and you'll see what I mean. Before closing, I want to mention <shameless plug> a few other Radified guides you might find helpful. For example:
If I did a good job explaining the ASPI mojo, you shouldn't have any further questions. But if you do, I started a thread in the Rad forums, where you can post your ASPI-related queries or share insights I might've overlooked. The end. Happy ripping & burning.
|