Page 1 of 1

FS-UAE mounting shareable drive 3.9 <> 4.1

Posted: Thu Nov 03, 2016 3:34 pm
by karynroberts
I have AmigaOS 4.1 Classic PPC installed on my Arch Linux system running FS-UAE - I'm trying to create a 'shareable' drive to transfer files between my AmigaOS 3.9 installation and AmigaOS 4.1.

I figured out how to mount an .adf file - issues with the 'save file' - but I'm unsuccessful creating a useable .HDF etc to transfer files.

Is there an FAQ, if only general in scope, to assist me?

Cheers.

Re: FS-UAE mounting shareable drive 3.9 <> 4.1

Posted: Thu Nov 03, 2016 6:06 pm
by thomasrapp
Should be trivial. Both OSes can read each other's files. Just mount both at the same time. Or duplicate one, format it and use it as shared drive.

Re: FS-UAE mounting shareable drive 3.9 <> 4.1

Posted: Thu Nov 03, 2016 11:07 pm
by tonyw
Can OS3.9 read a disk formatted by MTB?

Re: FS-UAE mounting shareable drive 3.9 <> 4.1

Posted: Fri Nov 04, 2016 4:22 pm
by karynroberts
I have tried every possible configuration - 3.9 won't read 4.1 disks, 4.1 won't read 3.9 disks. Initially the reason I joined the forum was for this same issue except with the .adf image. I would create a 3.9 blank, copy some files on it, mount it under 4.1 and my files would be gone. 'This' at least turns out to be the save image copy it creates - so I mount the save image - feeling I had found the solution I tried the same with HD image but no. I've tried .vhd, .vdi, .hdf, RDB, FFS you name it. The only way I could get my 4.1 useful was to copy over the net driver via the save image .adf.

I must admit I'm a bit confused - also, I'm not sure how much of what I may be experiencing is with FS-UAE.

But --- any help appreciated ...

Cheers,
Karyn

Re: FS-UAE mounting shareable drive 3.9 <> 4.1

Posted: Fri Nov 04, 2016 4:28 pm
by karynroberts
thomasrapp wrote:Should be trivial. Both OSes can read each other's files. Just mount both at the same time. Or duplicate one, format it and use it as shared drive.
When I add both the 4.1OS and blank .hdf (.vdi, .vhd) it won't boot. I've entered the boot ROM and made sure the scsi id is not set to bootable and set boot priorty, and held both mouse buttons down and chose dh0: - it still wants to boot from the 'blank' disk, thus does not boot the OS.

FYI, I'm not experiencing this with 3.9, 3.1 or any other combination of OS's and drives.

Karyn