Aspi Layer Links
PLEASE CONSIDER FOR STICKY
I've been seeing some issues crop up on other forums concerning issues with newer versions of software that are installing newer ASPI layers, causing problems with our older favorite app.'s like CloneCD and Primo/RNM. I've still got links for downloading different ASPI layers and fixes in my favorites folder, so I'd thought I'd throw them up here in case anyone needs to go back to the 4.6 series or get away from the buggy 4.70 layer.
Most of the latest stuff is available here, including ASPICheck, ForceASPI 1.7 (ASPI 4.61 Layer), etc.:
Look in the last two sections at the bottom of the page for stuff about ASPI.
If you have v4.70 ASPI, the ASPICheck utilitiy will probably bug out--v4.70 has some known bugs. You can try updating to one of the newer versions available at that link to see if it resolves any issues you may be having with your software. If one of the newer versions still doesn't work, try going back to a v4.6 series driver. V4.60 is the preferred one for CloneCD. The ForceASPI v1.7 listed there will install version 4.61. Here is a direct link to v4.60 from Adaptec.
Please read the warnings carefully. If that link eventually gets killed, you can get it from a german posting here as well:
If the lack of an Adaptec product prevents you from installing, use ForceASPIv4.6. I got mine originally from here, the link appears to be working still:
If that fails to download, there was some info on an alternate method to get around the Adaptec requirements to install their 4.6 ASPI directly listed here:
This basically involves manually installing a fake Adaptic SCSI controller to fool the installer into thinking you have one.
There have been some reports of issues with Win2000 and Me I think, but for the most part they work on just about all OS after Win95 from what Ive read. It is recommended to do a restore point for XP before monkeying with your ASPI Layer, but the ForceASPI programs should conduct a backup of your existing layers for other OS's.
I'm running the 4.60 (1021) layer with 98SE still, and use Primo (2.0.749) with engine 342 to support my 104 Burner for DVD Games/Movies, and CloneCD for my CD games (the 104 doesn't support RAW-DAO, but I have a compliant CD Burner). Ulead DVD Movie Factory and Magix Movies to DVD/CD work flawlessly with this layer--haven't got Nero or DiskJuggler though--and CDRWIN worked well with my burner on my MBoard controller (wouldn't recognize burners on my Promise PCI IDE).
I am considering purchasing Instant copy or CloneDVD when it gets released. CloneDVD will probably be built off the 4.60 ASPI just like it's little brother CloneCD. These 2 proggies look like they'll be the Schizit in DVD Movie backups. CloneDVD may even be an alternative to Primo/RNM and Nero for an automated PS2 backup process....still waiting for some info on it. Elby is being very tight-lipped about it, but it should be worth the wait--they've been tinkering with this idea for nearly 2 years now, waiting for the standards war to stabilize before working issuing any releases.
Hope the links help some of you guys out there who are having trouble with your app.'s--I saw one post where a guy constantly uninstalls/reinstalls Nero/RNM each time he uses them!? Maybe the 4.6 layer will resolve these conflicts.
For me best aspi is 4.60.
Work in all windows 98,me,xp,nt,2000
This one is good too. Force Aspi. And no, it as nothing to do with Star Wars.
Alcohol 120% is best proggy around now, dont' bother with cloneXXX any more.
if you're encounter aspi problem with nforce2 chipset, try http://www.frogaspi.org/
this is supposed to be the most current one, clicking the aspi.bat file will do it for you, update, and all. aspi is the way that pre-nt windows (9x) communicated with the cd drives, the aspi layer for nt or xp just makes the old programs that talked to the cd drives work on the new systems.
EDITED: In response to the post below, here are a couple more versions I had around, in case they get scarce...........
Compaitbility issues are a state-of-the-art money maker for Microsuck, they have invested MILLIONS in ways to make us pay. I currently run Vista x64 Ultimate, which features an unsigned driver filter that will not accept an unsigned driver unless you start it in disable unsigned driver mode, (for developers) and every time you start, if you want the app with the unsigned driver to continue to work. There is no real danger, really, in installing an unsigned driver, usually, "signing" is Microsucks extortion of software companies to make them pay money or their software won't work, and it squeezes the little fish (who also make all the really cool, and free type software I most appreciate) out of contention. A TALENTED user can get around that (if by starting it delibberately in that mode, every time: Vista x64), but that would be maybe 1 or 2% of users, to limit that market, the other 98% are defeated by the first Windows popup, and out of the reach of any software company that doesn't hand over the share of their profits to Microsuck. And they spend an aweful lot deliberately designing this kind of shit, to control the market. I can see that they clearly contradict every anti-trust law we have to protect us from that sort of thing, and flagrantly, at that, but a company that big just does the same, they fork over a share to the gov, somewhere, somehow, cut them in, to let them get away with it. Welcome to America, this epitomizes the capitolist mantra: "For the money, and by the money", you know? The poeple can suck wind, and pay for it all, in the end. Shit, O.J. showed us that if you got the dough-ray-me, you can literally get away with murder in this country. Why not let one company corner the market on computer software?
I do Windows diagnostics, all the time, and other than user errors, 99.99% of Windows issues were deliberately designed into Windows, to make money for Microsuck. Don't you just love knowing that? Like CSS on DVD's, for those who use old VCR's as a video signal to RF coverter... sorry, you can't watch DVD's, no matter what you paid for them, but the IMPORTANT thing is that you can't copy or tape a DVD, either, right? As long as we don't loose money, we don't mind srewing you out of yours, and did that one to you, deliberately. I went through that one with someone, once who just would not believe it until I brought over an unscrabled DVD to prove that there was really nothing else wrong with her set, escept that CSS made everything else unplayable.. until she bought a new TV. Pay, and pay, and pay, and pay, the American way.
im from solace too
Originally Posted by RAISTLIN