Amiga.org
The "Not Quite Amiga but still computer related category" => Amiga Emulation => Topic started by: mgerics on January 20, 2008, 09:08:07 PM
-
Under WINUAE I am using windows directories, not a real hd or hardfile...all of the sudden I get work: is not validated!!
What gives? If I run nearly anything, I get the not validated requeter thrre times, then it continues.
Any ideas? Nothing new on the windows side (anti-virus, etc).
-
Which version of WinUAE ?
Which version of Windows ?
Which file system (FAT32 / NTFS) ?
-
i didnt think this was possible but you have borked up the hardfile, hehehe... you must validate the hd, but how i dunno when it comes to emulated stuff.
-
It doesnt sound like he has done anything with intention, could this be a bug?
-
HopperJF wrote:
It doesnt sound like he has done anything with intention, could this be a bug?
I'm using winUAE 1.4.5 and I haven't experienced this problem. I have 5 different configurations from OS 1.3 to 3.5 with DH0 and DH1 being Windows folders. So far so good.
Fester
-
The dreaded "Volume work is not Validated" requester... haven`t seen that in a long, long time, thank God!!
-
@Thomas regrets, I should know to supply all possible info.
@1260 - I am not using a hardfile, only native windows directories..
xp pro fully updated
ntfs
winuae 1430
OS 3.9 with both boing bags
This system was working fine - I was forced to crash the pc itself when I thought an animation creation had locked up the emulation. Subsequent reboot shows nothing wrong with the hard drive, e.g. no errors reported, scandisk was run manually - usual pc recovery done after a forced power off.
-
mgerics wrote:
I was forced to crash the pc itself when I thought an animation creation had locked up the emulation.
A crash is a crash - emulated or not. ;-)
-
DOH! Ignore the n00b!
I was using a shortcut pointing to a configuration that referenced an >emabarrased face< HARDFILE!
When I began investigating, I was opening winuae then opening a *different* config to see what was up - hence I saw a windows directory referenced, not a hardfile. When I finally just ran the one I loaded manually and DIDN'T get the errors, I knew something was up. A little PROPER digging and I fixed it.
Sorry for all the hassle, and thanks to all who were trying to help - I'll buy your next beer when you are in town.
-
I was helping by keeping my yap shut :-D
:pint: