Post by SimonOf course someone may jump in and solve your problem, but I think you'll
have more luck by posting to emulation newsgroups.
You know, I think I have the answer.. and I'm pretty sure it's not
even emulation specific. The real problem here is that hard-drives
these days are so so much bigger than in the "Amiga days" that the
amount of free space reported is probably a bigger number than the
program knows how to handle (the one reporting the free space.) It's
checking to see if you have enough space to do something, and getting
some massive number back, and depending on the actual result of the
(overflowed) number it gets, it's quite likely to get a number that's
interpreted as a *negative* value. So any 'nice' program that checks
for free space before copying files ends up behaving badly. :|
Basically, what this person should really do is make the main
hard-drive an image-file. (Just a nice little 40MB or whatever
hard-drive image .. the exact size you want will depend a lot on what
you're doing .. I have lots of images: a 17MB PAL Workbench, a 50MB
Picasso96 Workbench, a 400MB Games partition, and a 220MB 'other stuff'
partition.) Image files end up having a whole lot less problems than
windows directories. (I also have a windows directory as my scratch:
drive.. and Directory Opus is always reporting (falsly) that there
might not be enough space to copy the files into it. Fortunately with
DOpus I can just get it to copy anyway. Other program aren't always so
flexible.)
If you really really wanna be working with just a Windows directory,
install the Workbench onto a normal disk-image file, then copy that to
a Windows directory. Just don't be suprised if you find there are
problems down the line again with disk-space or file-names. The
Windows directory tricks UAE does are pretty good, but still not
perfect.
(sometimes windows-illegal filenames get mangled, and expect the free
space to always be reported wrongly ..most people don't use windows
directories as drives, so these problems might never be fixed.)
My recommendation is still an image file though. The Amiga Operating
System is pretty simple. If you run out of space on an image you can
just make a new, larger image and copy the files over to that. So long
as you have a good file-manager like DiskMaster or DirectoryOpus,
nothing will ever get screwed up when copying files to a new image. (I
like FileMaster too, but recently noticed that it can't handle zero
block files, and I have a few of those on my drives.)
Okay, that's all I have to suggest. Good luck with it.
Nathan.
PS: Actually, I even remember having this with some 'old' Amiga
programs on the A4000 with a nice huge 4GB HDD. Some of the free-space
values would always show up with some crazy negative value. A sure
sign the programmer never considered such huge numbers would be
encountered.