| Click here to select a new forum. |
| FloppyEMU HD20.dsk issues on SE |
Posted by: jj9999 on 2020-12-09 19:29:11 I have a new FloppyEMU rev C board updated with latest firmware.
Unfortunately, after downloading the linked HD20.dsk from https://www.savagetaylor.com/downloads/downloads-macintosh/ and copying it to it’s own subdirectory on the SD card, when I select it in floppy emu I get a “file not contiguous” vs FloppyEMU saying that the “startup disk has been saved” as it does with the default HD20.dsk supplied on the FloppyEMU SD card.
The dsk file opens up fine under mini Vmac emulator.
Any ideas?
|
Posted by: jj9999 on 2020-12-09 23:01:37 Update:
The error is implying a disk fragmentation error. All files were copied to SD card today, so I doubt that.
Tried formatting the card and copying files again to defragment- no luck.
Copying the HD20.dsk on its own to the root of the SD seems to work but kinda defies the purpose.
Any clues?
|
Posted by: Skate323k137 on 2022-03-14 06:59:48 Ran into this issue myself with my rev C on my SE, never had the issue with my rev B. It originally started with a read state error.
Reformatted the SD, re-copied just the one disk image, still got a "file not contiguous" error. The only other spare micro SD's I had laying around are cheapo's that the floppyEMU doesn't like, or massive 128GB microSD sandisks. I may try a sandisk out of morbid curiosity at this point, but last night I ended up setting the floppyemu back to floppy mode, and figuring out how to mount the SD from my extra SCSI2SD in Basilisk.
Edit: found a spare 16GB sandisk, copied the 2GB disk image to that, and the floppyEMU is happy again. Definitely be careful your brands of SD cards, as always nowadays.
Another edit: I spoke too soon, now I'm getting "READ STATE CHANGED 2" on the FloppyEMU :/ MacOS offers to format the disk and then is unable to.
I've emailed BMOW at this point, I cannot get this thing working in hard disk mode again, but I'm sure that BMOW will come through. |
Posted by: Skate323k137 on 2022-03-14 09:22:58 Ok, so I think I've narrowed this down to having something to do with the micromac accelerator.
If I boot with extensions off, effectively disabling the micromac, the FloppyEMU works in HD20 mode again. If I reboot with the accelerator enabled, I get the read state changed errors.
I let Steve/BMOW know... this happens with both Rev B and Rev C on the newest firmware. Hopefully there can be a fix, or someone else can try to reproduce this?
I have read that SE/30 may not support HD20 in which case that might explain this, seeing as the processor/FPU on my accelerator are that of an SE/30 for all intents and purposes. |
Posted by: cheesestraws on 2022-03-14 10:32:49
seeing as the processor/FPU on my accelerator are that of an SE/30 for all intents and purposes.
The processor and FPU don't matter here. The SE/30 doesn't support the HD20 because the driver for the HD20 isn't in the SE/30 ROM. If your accelerator uses the SE ROM, the driver should be there (though it might be broken by the accelerator in other ways, I suppose) |
Posted by: mg.man on 2022-03-14 11:50:20
Ok, so I think I've narrowed this down to having something to do with the micromac accelerator. If your accelerator uses the SE ROM, the driver should be there (though it might be broken by the accelerator in other ways, I suppose) Well... FWIW, I also get this READ STATE CHANGED 2 error when trying to use my FloppyEMU (also Rev.C) in my SE with my Total Systems Mercury 030 "on". If I disable or don't load the TS Mercury Extension, I can boot from the FloppyEMU in HD20 mode. |
Posted by: Skate323k137 on 2022-03-14 11:53:40
Well... FWIW, I also get this READ STATE CHANGED 2 error when trying to use my FloppyEMU (also Rev.C) in my SE with my Total Systems Mercury 030 "on". If I disable or don't load the TS Mercury Extension, I can boot from the FloppyEMU in HD20 mode.
Thanks for that info, it definitely helps!
No worries here as I have my scsi2sd transport set up just fine but it would be interesting to see if it could be made to work. Probably more effort than it's worth for myself.
Also the rev B does the same with the accelerator, now that I did more testing. Not a surprise though as they both have the newest/same firmware. |
Posted by: mg.man on 2022-08-03 02:09:21 Just to cross-post in case anyone else hits this ...
Does anyone know of there is some of programmer switch procedure to disable a Mac SE Radius '020 accelerator on boot? My Floppy Emu doesn't work in HD mode with the accelerator, it would be nice to be able to disable the accelerator so I can copy from my Floppy Emu in HD mode to the SE internal...
68kmla.org
It looks like "Accelerators" do not play nice with the Floppy EMU's HD20 mode. Does anyone know if Steve from BMoW is still active here? Anyone know his ID? |
Posted by: oldmacuser on 2023-06-26 08:51:43 Formatting the SD card with the "SD Card Formatter" app fixed the issue for me. |
Posted by: marinelayer on 2023-07-08 10:21:56 Also chiming and confirming that Accelerators seem to be an issue in HD20 mode. I've got a Mac SE with a Radius Accelerator SE with a 68020 and I get the same "READ STATE CHANGED 2" error. Reformatting and copying back does not help. I've tried multiple images. |
Posted by: LazarusNine on 2023-09-03 02:23:55
Formatting the SD card with the "SD Card Formatter" app fixed the issue for me. Thank you so much for this recommendation. 👏 The 'file not contiguous' error was so infuriating. This solution worked! |
Posted by: oldmacuser on 2023-09-06 14:55:06
Thank you so much for this recommendation. 👏 The 'file not contiguous' error was so infuriating. This solution worked! Glad to hear it worked out! |
Posted by: theirongiant on 2025-01-27 21:47:12 FloppyEmu owner here, reporting in with the same "Read State Changed 2" error on a Macintosh SE FDHD that has an accelerator card installed. It's not an original MicroMac, but rather a new reproduction PDS card made by MacEffects that is emulating a 68030 @ 25MHz.
I can boot the SE FDHD and use the FloppyEmu in HD20 emulation mode if the accelerator's extension is disabled. I don't actually have to remove the card to use the FloppyEMU.
I wonder if it's the extension itself that is causing issues for FloppyEmu. |
| 1 |