[FS-UAE] Boot a real compact flash card on OSX ?

[gibs]

Is it possible de boot on a real compact flash on OSX ?

Foul can do it on linux.


In my configuration file I did:
hard_drive_0=/dev/disk5
hard_drive_0_label=DH0

Logs:
hfd open: '/dev/disk5'
HDF '/dev/disk5' opened, size=0K mode=3 empty=0
Internal error; file src/od-fs/hardfile_host.cpp, line 390

Thanks

[FrodeSolheim]

Originally Posted by gibs

Is it possible de boot on a real compact flash on OSX ?

Foul can do it on linux.

In my configuration file I did:
hard_drive_0=/dev/disk5
hard_drive_0_label=DH0

Logs:
hfd open: '/dev/disk5'
HDF '/dev/disk5' opened, size=0K mode=3 empty=0
Internal error; file src/od-fs/hardfile_host.cpp, line 390

Thanks

The access to the block device is probably restricted by default. You can check the permissions with:

ls -l /dev/disk5

Make sure you have read (and write) permission for the file -and then try again

[nexusle]

A little bit another question, but is it also possible to set a real CDROM/DVD drive in FS-UAE for OSX??

[gibs]

Frode,

This is what I did

I tried again now, same result (except that the disk is assigned to disk6 today)

hfd open: '/dev/disk6'
HDF '/dev/disk6' opened, size=0K mode=3 empty=0
Internal error; file src/od-fs/hardfile_host.cpp, line 390

Why hardfile_host.cpp ? it's not a hardfile :/

[FrodeSolheim]

Originally Posted by nexusle

A little bit another question, but is it also possible to set a real CDROM/DVD drive in FS-UAE for OSX??

No, sorry. I have not made any effort to use native CD-ROM drives and and this has also a low priority for me, among other things because of the amount of work involved in supporting all platforms.

Originally Posted by gibs

Frode,

This is what I did

I tried again now, same result (except that the disk is assigned to disk6 today)

hfd open: '/dev/disk6'
HDF '/dev/disk6' opened, size=0K mode=3 empty=0
Internal error; file src/od-fs/hardfile_host.cpp, line 390

Why hardfile_host.cpp ? it's not a hardfile :/

Well, it sort of is a hardfile Or rather, FS-UAE only implements support for hardfiles (disk image files), not physical devices. But due to the everything-is-a-file nature of Linux/Unix, block devices, including hard drives, can be opened as files, and disk images files are just 1:1 byte copies of block devices anyway... So that's why foul can use /dev/something instead of /path/to/hdf on Linux -using the hardfile support. I suppose the same could work on Mac OS X.

Now, to debug your problem: It is important that you use a recent development version of FS-UAE to get support for large drives.

Also, you should attach FS-UAE.log to provide more debug information, but first you should make the log file a bit more useful.

Please set a specific environment variable in a console and run fs-uae from there -this will enable a bit extra relevant information in the log file:

export FS_DEBUG_HDF=1
fs-uae <parameters>

[nexusle]

It was just a question. No needness about this

[gibs]

@Frode

Here is the complete report (screenshots/logs) :

https://dl.dropbox.com/u/1566495/Amiga/FSUAE.zip

[FrodeSolheim]

Thank you for a very thorough and good report It looks you have done everything correctly

The problem is that the detected size of the device/file is 0 bytes. The hardfile code detects the size by opening the file (device in this case), seeking to the end and checking the file position. It is possibly that this is not supported for block devices on Mac OS X, and that one needs to use ioctls to get the size of the device. I haven't got a device to test with right now (and I'm not going to try to open the root partition ;-)).

[ascp]

Hello Frode! Linuxman as I am, tried mounting an empty sdcard as desribed:

hard_drive_0=/dev/MYSDDEVICE
hard_drive_0_label=DH0

and verified that permissions were rw for the device.
FS-Uae-lancher just frozee though. It it so that this only works for already partioned media?

[amigafreak68k]

Originally Posted by jonathan

FS-Uae-lancher just frozee though.

That's normal I think. On OSX I have the same behavior. I seems, that FS-UAE (Launcher) try to scan the media.

Just wait a little bit and don't close the Launcher when it seems frozen.