I have some zip files containing archives from the late lamented Zero magazine which every month had coverdisks that could play on either an Atari ST or an Amiga. A friend of mine is able to convert these zip files directly to a *.ST image for use with STEEM (Atari emulator) and I was wondering if something similar existed for conversion to an *.ADF file.
I did ask this question before and some bright spark said "Unzip it", clearly not having read my original post. The contents of the zip file are a *.PRG file and some *.TOS files which do not run under WinUAE, even using the virtual hard disk. Does anyone have any ideas? If I'm able to solve this dilemma, I can upload lots of demos and freeware which might be of interest to many of you. Thanks in advance.
Any idea how these files were created? AFAIK, ST disks were compatible with PC drives, so the odds are good that someone has just read the files straight from the ST sectors, zipped them, and binned the Amiga stuff, which their PC would have interpreted as blank, unformatted space at best.
If you don't got two floppydrives on your PC, you can't make use of the disk2fdi program. So unless you do actually got 2 floppydrives, here's what you could try instead, even though it may be a long-shot:
Create a blank ADF with WinUAE, unzip the archives with the program files and from within Workbench put them onto the blank ADF image.
After that you go to the menusystem in Workbench and access the "Execute Command..." launcher.
Now while the ADF is in DF0: drive, type this into the field of the Execute Command:
install df0:
Now a bootblock has been written to the disk and it should be rdy to use, given that the files and folders got the proper structure (eg. that there's a "s/startup-sequence" on the disk so it'll boot and launch the software that's on it).
That way you get the files from the zip archive, over to a bootable ADF image.
But as I said, it's a long-shot. I would've had to see for myself what files and folders that are in this zip archive and how they're supposed to execute.
But aside from the disk2fdi program, this is the only other way I could currently think of.