TDK VeloCD and Firmware

[forouza1]

I'm trying to upgrad to Firmware 1.07 and having no luck on my VeloCD 12x10x32x. I've been getting the same problem as other posts. I run Firmware update, I get the hour glass thing on my mouse cursor and then Explorer gives an error with the application not responding. I've read all the previous posts and it seems to be a problem with ASPI layer. Don't know what ASPI layer means. I'm running WinME. DMA is not an option to enable in my Device Manager but I have the jumper set on the drive and ViaIDE Tool confirms it's in DMA mode2(ATA33). I tried flashing without jumper on and it didn't work either. Anyhelp would be much appreciated.
I'm using Nero5.0 and InCD.

 

[Crizza]

check out the forums at cdrinfo under hardware to get more help there.

(there may even be a guide there, but I'm too lazy to look )

just a thought - do you have a 98 machine that you could install it in to do the upgrade under that?

good luck!!

post thought: Just bought one yesterday, it came with 1.05 but 1.07 update on a floppy. Updated fine. Give it a shot on a 98 machine.

[edit: who knew links were so tough ]

 

[MrChicken]

Did you look here?
Firmware update page.
It was written for that big Iomega deal, but the TDK is the same drive.

 

[forouza1]

Thanks Mr. Chicken, this gives me another lead.

I looked into it a little more. I did an check on my ASPI files with aspichk.exe (got from Adaptec Website) and found that ASPIENUM.VXD is missing. Also got a error message saying that my ASPI files are incorrectly installed and that one or more files are using an older version. Now Adaptec says in their tech pages that WinME has a different setup than Win9x so may that's why I get the error message. If anyone else has any tried and failed upgrading firmware 1.07 but finally had success please reply.

Thanks...

 

[MrChicken]

This probably wont help, but.... I updated the FW on my Iomega under ME.
I had EZCDcreator 3.5c under 95 when I upgraded to me.
Installed the EZCD that came with the Iomega (4.2d I think), then flashed the firmware from within ME.
I'm speculating that if I had any problems with the ASPI drivers, it got fixed by the new install of EZCD.

Search the archives for the Hot Deals forum for the Iomega deal from just a just a couple of weeks back. there is a HUGE thread about the deal and the firmware updates including failure then successes.

 

[billyjak]

I have the TDK and flashed it with no problems.
I beleive I got it in the beta state, it wasen't on the 12x10x32x at the time just on the 8x burnner and I flashed it not realising I did this, but it flashed with no problems.

 

[forouza1]

See I think the problem I'm running into is some conflict with WinME. Everyone I've talked to hasn't complained of problems updating using Win2K or Win98

 

[John C]

I've had the exact same problems with my tdk 12/10/32 in Win98SE. I've tried the suggestions so far with no luck. Still looking for answers.

 

[John C]

Figured it out!

Here's what worked in my case:

First I downloaded aspichk.exe and found that my ASPI layer was not up to date.

Then I updated my ASPI files using a hack called ForceACPIv1.7 since I didn't have any Adaptec products installed on my machine (although I do own a sccsi card) (if you have one of their products you can use adaptec's updater instead "aspi32.exe" found on their site).

After running ForceASPI as instructed here, I rebooted and suddenly the firmware upgrade flashed perfectly!! Now I finally have 1.07.

Upon restarting a second time windows informs me that my ASPI is older than the version installed by windows98se and that I can go to setup to fix it. However, since the adaptec aspi's are actually newer versions I chose to ignore this. I have also heard that some burning software requires the newer aspi layer. So we'll see if this causes me problems or helps me later. P.S. I'm not sure if this is an illegal program or what but I think TDK or Microsoft owes us a similar fix.