Hello,
I'm trying to create a DOS 3.3 disk for my FloppyEmu through CiderPress II or AppleCommander, but it doesnt seem to work. Simply putting the files into an image and using the Emu gives me an error of "File Not Found." I assume the process isnt as easy as just placing files in the .DO disk, so what am I doing wrong?
You have to run INIT to write RWTS to boot sectors.
Thanks! However, when I tried this (Booting DOS 3.3, ejecting it, then using INIT HELLO on a new inserted disk) the FloppyEmu says Write Error, Saved Trk 00 in 497
I don't know what that means. I would probably reach out to the FloppyEmu author for support.
I usually start with a .dsk image of a blank formatted floppy and then you can write files to it with whatever utility you find convenient on your modern computer and then just copy it onto your Micro SD card and put it in your FloppyEmu and mount and save to it and otherwise use like a normal floppy.
Thanks! I also found my problem, I was trying to format .DO files and the FloppyEmu manual says it recommends .WOZ files for formatting (which work). My next question, how would I be able to boot into a basic program? I know some floppies have a modified HELLO file that RUN or BRUN a basic program, but there's this disk I'd like to reverse engineer for learning purposes and it doesn't have a HELLO file. How is this possible?
(For those curious, it's an emulation of the infamous IIC earthquake program from the Bond Movie)
When you initialise a disk, the defacto standard is to:
INIT HELLO
but this is only a standard. "HELLO" can be any valid name of your choosing.
For example, if you:
INIT GOODBYE
the BASIC program GOODBYE would be run.
Hope this helps.
Cheers,
Mike
There's no real need to "format" a disk image. You can great the disk image in Ciderpress, add relevant files to is using Ciderpress and it ought to work in your floppy emu.
If you're using DOS 3.3 disk images, it's probably more reliable to use the .dsk suffix.
Ciderpress usually wants to create a .do suffix when making a DOS-ordered disk image, but changing it aftwerwarrds to .dsk has helped me avoidn issues over the years.
ProDOS-ordered images, or .PO usually present no issues to the Floppy Emu.
I am a reluctant adopter to the .WOZ format, especially for self-made disk images, for which I find the increased file size irrelevant. I rewlly only use .woz images if I really want to preserve metadata on a disk image created from a physical floppy that has some significance. (which is almost never)
Alright! I think I understand now. This was helpful! Thanks guys.