Because you're using EmuTOS, I assume that you don't use HD driver on the ACSI disk. I tried on Linux EmuTOS 0.9.7 with Hatari 2.0 & latest Mercurial versions using 8MB, 16MB and 200MB ACSI images. All worked fine. So the crash could be something OSX port specific.

I also run MacOS (OS X) version of Hatari. I was able to use the sample 80MB ACSI image provided on the Hatari website along with the 512K version of EmuTOS 0.9.7. I am also running MacOS Sierra (10.12.1).

Have you tried the sample image to see if that works for you with Hatari 2.0?

Honestly, I am running out of ideas. I have no problems using the hd80mb.img file. In fact, that is my normal Hatari HD image since only a few of my games are HD compatible. I would suggest moving the hatari.cfg file out of ~/Library/Application Support/Hatari. This will force Hatari to start with its default options. It will boot up with EmuTOS (probably the 192K version) and you can add the sample 80MB ACSI image from there and reboot Hatari.

Yes, your image also crashes my Hatari. However, I created a 400 MB image and formatted it using AHDI. I was able to successfully boot the disk image using the 512K EmuTOS. Since even the sample 80MB image does not boot for you, I would eliminate your disk images as the problem for now.

Have you tried the sample 80 MB image on your old Macbook running 10.6.8? Right now, I cannot say there is a problem for everyone using the OS X version of Hatari when booting ACSI images. Unfortunately, I do not know why the problem is happening for you.

When I run Hatari from the Terminal, I see the following message along with other Hatari diagnostic messages:Mounting hard drive image '/Users/bobc/Downloads/400MB_image_easymint_68k_ext2.img'Abort trap: 6

At that point, Hatari crashes. I have no idea what the Abort trap message means.

I was able to mount the test 400 MB image that I formatted with AHDI 5 (boot program was AHDI 6) without a problem.

You may need to subscribe to the Hatari developers list to get more technical help with this problem.

My OSX 10.6.8 Computer: I generate with the HDUtil Program a 900MB MSDOS FAT Image and partition it with HDDriver under EmuTOS. These works all fine. But my old Images I can not use because Hatari 2.0 crash. But I can use these Images with Hatari 1.9 or 1.7 without a Problem. Why ?

Hatari 2.0 crash with the 900MB Image to from the OSX 10.6 Computer under macOS Sierra ...

- My TEST Image has a BGM and a LNX Partition for the MiNT ext2 Filesystem -

You do not have the required permissions to view the files attached to this post.

Frank, I just made a 15 minute analysis of the Hatari code involving ACSI images and found a bug that could be the reason for your crash. Can you please test if the image loads, if the file name of the hard drive image is really short? I.e. instead of having /Applications/Atari_ST_Emulatoren/Hatari/900MB_TEST.IMG, could you load for example in /tmp/900MB_TEST.IMG (assuming there is /tmp on MacOSX)?

I just tried Christian's suggestion and I was able to load your image. I did not see the problem because my images are saved in ~/Documents/Hatari/Disks so the pathname was smaller. Since your pathname is 41 characters, you only have 6 characters to work around the problem if you leave your images in the same path. I am not sure when a new executable may be released with this fix. Is there a way you could move your images to another directory with a shorter pathname?

Christian,

As macOS is derived from FreeBSD, it does have a /tmp directory. However, it is normally hidden. The easiest way for Frank to find it in the Finder is by selecting Go to Folder in the Go menu. At that dialog box, simply type "/tmp" to get to /tmp. Actually, /tmp is a link to /private/tmp on macOS.

I have uploaded an updated Hatari binary to my Dropbox account. Please note it will probably only run on your macOS Sierra Mac. This is a 64-bit only binary. The official binary runs on more systems. However, this should resolve your problem with the long image names.

This binary also includes any other changes that were made since Hatari 2.0 was released about three weeks ago. Since this is a development version, it has not been heavily tested. However, I am optimistic that the changes that have been made will not affect you.

Glad I found this thread. I was having the exact same issue with my Hatari install on my Hackintosh. I am running El Capt.

I moved the directories to a separate drive and just name them on the root level, everything fine. Annoying.. but fine.

I want to have both an ASCI imge and Gemdos to transfer files. I dont have older version experience, but when I setup a 1gb.img as my asci, then a directory called Gemdos with subdirectories F G - I get them to show up.. but also get c: lowercase cartridge show up.. why?

Also showinfo does not report the Hatari setup correct. Is that common? I am running a MegaSTE 4MB @16mhz (emu my real hardware)

There's an option for GEMDOS HD to skip other drives, but it relies on Hatari interpreting the HD images partition tables in the same way as the HD driver you're use. If those don't match, there's a command line option to specify which drive GEMDOS HD should use.

As to the cartridge stuff...

Hatari builtin cartridge image has some native code needed by GEMDOS HD emulation (to create basepage for the started program with TOS, so that TOS can see/use it). Cartridges can have a file system, and the Hatari one does include a one. You can see the cartridge file system only with real TOS, with EmuTOS it's missing as EmuTOS doesn't (and apparently won't) support cartridge file systems.

That cartridge file system is harmless, it doesn't override anything, although it has a C: drive designation.