Jump to content
  • Who's Online   0 Members, 0 Anonymous, 29 Guests (See full list)

    There are no registered users currently online

rhanners

E80041927: Trackwriter Error - Aspi Failure

Recommended Posts

I'm using win98SE, have Plextor 708 burner, and Easy Creator 5.3.5.10v. Up until a few days ago, burning CD's was no problem at all. All of a sudden I get errors when I try to burn a data disc on to a CD-R disc. These are the same discs I've always used. So I thought the Plextor might have bitten the dust but when I perform a self diagnostic test, the burner passes.

 

So I took an AOpen DVD burner out of my other machine (same software in it). I just burned a disc with this computer and drive 5 days ago, so I know the drive is good. I substitued in this drive and when I try to burn a CD-R (same data by the way), I get the same error message. I then put the drive back in the old machine - works like a charm.

 

So it isn't the burner and I have not installed any new programs or done any other thing to the computer for several months. So does anyone know why I get the E80041927 - ASPI failure message?? Everything else seems to work just fine.

Share this post


Link to post
Share on other sites

Hello,

 

It seems that something has disturbed the ASPI layer in your machine. ASPI is the Advanced SCSI Programming Interface used by optical drives, and it is layered between the drive and Windows.

 

I seem to remember that Adaptec had a utility to check this, called ASPICHK. It can be found in many places, and here's one of them

here (click)

 

If your ASPI layer is disrupted it may pay to reinstall it. Check on the web for Adaptec's ASPI 4.60, and use something like FORCEASPI to reinstall it. (Version 4.7 is the latest, but 4.6 is considered the most stable)

 

Forceaspi can be found here (click)

Share this post


Link to post
Share on other sites

I found Force ASPI and the ASPI check program. The check program said that the layer was not right as I had a mix of versions. So I used Force ASPI to install version 4.60 on to the machine. Running Easy Creator 5 again, yielded the same error message and yet another coaster. Before doing all of this, I also followed a Roxio support item that said to rename various ASPI related files to ".old". I did that and it also did nothing. Got the same error message and another coaster. I find it strange that this should be happening. Again, I took a known good burner and used it in this machine, only to get the same error messge. So is it Roxio that is screwed or support files? The whole thing really makes no sense.

Share this post


Link to post
Share on other sites
I found Force ASPI and the ASPI check program. The check program said that the layer was not right as I had a mix of versions. So I used Force ASPI to install version 4.60 on to the machine. Running Easy Creator 5 again, yielded the same error message and yet another coaster. Before doing all of this, I also followed a Roxio support item that said to rename various ASPI related files to ".old". I did that and it also did nothing. Got the same error message and another coaster. I find it strange that this should be happening. Again, I took a known good burner and used it in this machine, only to get the same error messge. So is it Roxio that is screwed or support files? The whole thing really makes no sense.

Leaving the main question to Brendon, I'd suggest getting a CD-RW or two to play with, so you don't keep making coasters. If the CD-RW doesn't turn out well, erase and reuse.

 

Lynn

Share this post


Link to post
Share on other sites

It's not a hardware issue, so swapping your burner won't affect it. It's the driver layer between Windows and your burner drive.

 

Did Aspichk say you had a good installation of the ASPI layer after you ran Forceaspi? If it didn't, you should completely uninstall your ASPI layer before running Forceaspi, so you get a good clean install.

 

Leaving the main question to Brendon, I'd suggest getting a CD-RW or two to play with, so you don't keep making coasters. If the CD-RW doesn't turn out well, erase and reuse.

 

Lynn

 

If you're being persuaded to use CDRWs, you should read this, written by Guru Lynn.

 

CD-RWs are a fine tool, but not a long-term tool. The same quality that enables them to be re-written will cause them to fade to blank over time. They can still be re-used, but eventually not even an ISO based program will retrieve them. There is no hard-and-fast rule as to how long they will last, but the more critical the situation the more you should worry about this.

 

There are three kinds of CD-RW media

standard (1-4x)

"high-speed" (4-10x or 4-12x)

"ultra-speed" (10x or 12x and up)

There is different technology behind each of the three forms of CD-RW, and they are not compatable. If your burner's middle number is 4x or lower, it will only use standard; up to 10 or 12, it can use standard and "high-speed" RW's higher than that, it can use "high-speed" and "ultra-speed", and possibly standard.

 

(To check what your burner can use, open any project, like MusicProject or DataProject, click on "Tools", click on "CD Drive Properties", click on the drive you want to check, and there is a drop-down box for "supported media". It will list CD-RW, CD-RW (High Speed), and CD-RW (Ultra Speed) seperately.)

Share this post


Link to post
Share on other sites
I found Force ASPI and the ASPI check program. The check program said that the layer was not right as I had a mix of versions. So I used Force ASPI to install version 4.60 on to the machine. Running Easy Creator 5 again, yielded the same error message and yet another coaster. Before doing all of this, I also followed a Roxio support item that said to rename various ASPI related files to ".old". I did that and it also did nothing. Got the same error message and another coaster. I find it strange that this should be happening. Again, I took a known good burner and used it in this machine, only to get the same error messge. So is it Roxio that is screwed or support files? The whole thing really makes no sense.

As Brendon said, it's a software issue. But, ECDC 5 is supposed to provide it's own ASPI layer, and not use whatever might be installed. I would definitely suggest trying to uninstall ECDC 5, run Roxizap (disable GoBack first if you're running that) and then reinstall. I would guess that somewhere along the line, one of the ECDC files that it uses for the ASPI interface has been corrupted or overwritten.

Share this post


Link to post
Share on other sites

Yes, I got a good ASPI check after using Force ASPI. I first saved the current files, then killed the files, then installed the new files, rebooted and checked. I kind of figured I was going to have to uninstall Roxio as the next move. If Roxio provides it own ASPI layer, will it overwrite the 4.60 version I just installed, or does it install it as something seperate? Just curious. I'll have to look to see if I can find Roxizap on the site. Thanks for the help.

Share this post


Link to post
Share on other sites
Yes, I got a good ASPI check after using Force ASPI. I first saved the current files, then killed the files, then installed the new files, rebooted and checked. I kind of figured I was going to have to uninstall Roxio as the next move. If Roxio provides it own ASPI layer, will it overwrite the 4.60 version I just installed, or does it install it as something seperate? Just curious. I'll have to look to see if I can find Roxizap on the site. Thanks for the help.

The URL for roxizap - and a lot of other information - is in the FREQUENT ANSWERS post pinned to the top of the board.

 

Lynn

Share this post


Link to post
Share on other sites
Yes, I got a good ASPI check after using Force ASPI. I first saved the current files, then killed the files, then installed the new files, rebooted and checked. I kind of figured I was going to have to uninstall Roxio as the next move. If Roxio provides it own ASPI layer, will it overwrite the 4.60 version I just installed, or does it install it as something seperate? Just curious. I'll have to look to see if I can find Roxizap on the site. Thanks for the help.

It doesn't "install" an ASPI layer, just provides it's own when it is loaded (that is, when you go to run it, not when you install it). So, your 4.60 ASPI layer should remain untouched.

Edited by d_deweywright

Share this post


Link to post
Share on other sites

Well, I just totally uninstalled all of Roxio 5, ran Roxio zap and then did a total reinstall plus updates to get to 5.3.5.10v again. I also ran ASPI check and got the green box and everything is at 4.60 level. So figured that this might work. Nope, I still get a "Trackwriter error - ASPI failure (T7121)." So I'm really at a loss as to what this might be causing this. As I said before, the system was working fine, I didn't install any software or updates and this just started to happen.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×