ghost
commented
5 years ago Hi,
I'll just throw in some troubleshooting tips. Telling us about your Kickstart version and some information about your directory structure would help here. AFAIK FS-UAE is involving in some extra AmigaOS side wizardry when directly booting WHDLoad archives. With a real Amiga or another variant of uae, you don't have the assign command from your kickstart rom and the CD command is in there from Kickstart 2.0x onwards. You might want to have a copy of them in the C folder or at the root of your boot drive. This applies to all bootable disks you want to use.
If you already have this sorted out, you might want to check the early startup boot menu for your drives. Reboot with both mouse buttons pressed and you should be able to see your drives listed on a new screen if they're mounted properly. If you can't get to this screen, try switching to a slower config. If you're already at early startup but don't see the drives listed and that you're sure they're shown as mounted in the hard drive configuration screen in uae4all2, then please walk us through the issue with screenshots and the contents of your configuration file.
Switch does have a permissions issue regarding the archive bit of files in other scenarios. I didn't have this issue with uae4all2 but you can try deselecting "file is ready for archiving" option for all files and folders from the root down (Windows).
Best.
HoraceAndTheSpider
Hi
Just started really digging into this emulator. Looks very nice from what I’ve seen so far.
I am having trouble however with HDs mounted from folders.
I’ve set up some WHDLoad games with very simple startups; cd into a game folder, and launch the WHDLoad slave ... nothing major in there, all simple enough stuff.
I’ve tested the self-contained files in Fs-uae on OSX and there are no issues.
I’ve moved the files over to my Vita via FTP and I mount the drive, reset to boot and everything seems to start in dos.
I am then hit with errors such as “cd failed return code 20”
Sadly I also seem to have a similar issues when using other folders (such as my AMOS coding setup) , although this returns “assign: file is not executable”
In each case the failure is the first command of startup-sequence
From my time using Amiberry on the Pi, is there perhaps a permissions issue here to do with file transfer? Is there a requirement for the files to be located somewhere else where there are the appropriate rights? It does seem strange that ADFs in the folder at ok, but perhaps that simply confirms that the files can be read ok, just not executed on the Amiga side.
I appreciate that HDFs might solve the problem, but they are not really practical for me when I tend to share files (saves etc) between systems , or like to test programs I’m writing on multiple difference emulators.... plus the time consuming element of converting everything.
As an aside, It would also be nice if “save Config for game” was able to detect that my game comes from the HD and not DF0: as this doesn’t seem to give a notification when used this way .
Any thoughts welcomed. Thanks