| Author | Message |
|
|---|
kicken
Joined: 21 Feb 2009
Florida | | I just recently found an old copy of Disk speed I had, and decided to give it a try on my new system to see what numbers I get. I downloaded the latest copy first since I knew mine was old, and when I try and run it I get an error:
Windows - Drive Not Ready
Exception Processing Message 0xc00000a3 Parameters:
0x000007FEFE387240 0x0000000000000004 0x000007FEFE387240 0x000007FEFE387240
(screen shot: http://aoeex.com/extras/DiskSpeedError.jpg)
I'm wondering if this is because I am running with 64-bit or not.
System Info: http://aoeex.com/extras/SystemInfo.jpg
|
|
Roadkil
Joined: 28 Mar 2008
South Australia | | hi there... thanks for the info... i developed the app on a vista 64 box so im sure it should work. Are you the admin user? and do you have User Accss control enabled (those annoying popups which say are you sure you want to do this all the time)
Cheers
|
|
kicken
Joined: 21 Feb 2009
Florida | | Hi,
My account is part of the administrators group. I do have UAC enabled normally. Since you brought it up I disabled it and tried to run it, but ended up with the same results.
Thanks, Keith |
|
Roadkil
Joined: 28 Mar 2008
South Australia | | Strange! Ill try booting up a 32 bit vista and do some testing and get an update done as soon as i can!
Thanks for the info |
|
youlikethaaaat
Joined: 17 May 2009
Wales | | I also have been getting a similar error.
I'm running Windows XP Proffessional.
[img]http://i42.tinypic.com/2ns0v87.jpg[/img]
I usually get this exact same error when trying to boot a virtual machine in VMware with a floppy drive configured. I think this is because my computer hasn't got a floppy drive.
|
|
Roadkil
Joined: 28 Mar 2008
South Australia | | Just had another message from another user with the same issue. Ill look into this one and put an update up shortly.
Cheers! |
|
Mario
Joined: 31 Dec 2009
Netherlands | | I had the same error. But I know for sure it is because the application is looking at the first drive A:
I disabled my floppy-drive in the BIOS and the error was gone!
I suggest that the application looks primarily at the current drive. The same error was found in the first version. I never experienced it because I normally have my floppy drive disabled.
Happy New Year! |
|
|
|---|
