Oh, I can try and convert them, but mind that I recovered those images waaaaay back, using a DOS disc utility and later the real disc emulation on RealSpectrum emulator. I'm still amazed that it actually worked!
Fuse 1.5.3 released
Re: Fuse 1.5.3 released
Re: Fuse 1.5.3 released
just played with an emulator. I choose Didaktik 80 and load demo. There are no AY sound(
How to enable it ?
How to enable it ?
Re: Fuse 1.5.3 released
Hello !
Keep in mind the .MGT uses an interlaced tracks pattern. Each 10 sectors, it swaps sides and the next 10 sectors actually contain the same track from the second side rather than the following track of the same side.
In fact, floppy disks are written that way to minimize disk head moves and accelerate both writing and reading files.
Since it's the natural way data are organized on the real disk, I don't think the emulator should mess with the order the data are organized provided it would still read the tracks stored into the image file in sequence, even if the image has been created from a single side floppy disk.
However, I don't have first hand knowledge of how a single sided floppy disk is converted into a .MGT file. Does it store an empty track once every two tracks, or does it just store the existing data in sequence, the way the floppy disk drives transmits them to the computer ?
On the other hand, it seems like there's another file format for MGT disk images, the .IMG format. And this ones stores all the tracks from the first side in sequence, then goes on with the second side ones, restarting from track #0 !
As a result, loading a .IMG (I'm talking about the data internal organization) file that would for instance be renamed into .MGT (if the emulator would only manage .MGT files, maybe) would result in missing once every two tracks because they're actually stored 80 (or 40, in the case of a single density floppy source) tracks away !
The other way around would probably also fool the emulator (and as pointed, it's probably impossible to tell the difference between a double sided 40 tracks image and a single side 80 tracks image because they're the same size - though I don't think single side double density 3"1/2 floppies were that popular at the time : most single sided floppies were from the 5"1/4 single density era, where you used to punch a second hole in the sleeve to be able to use the second side)... :p
Well, what I mean is a half or quarter size image file should probably be automatically assumed by the emulator it's about a 40 tracks floppy, and if it's the quarter of the usual size, then of course it should be treated as a single sized one.
Anyway, maybe the first thing would to check the actual way your data is stored into the image file, check if the file is named accordingly to its actual format, and in the case the emulator can't mount one of them and it's unfortunately the one you've got, write a simple program to swap tracks as expected inside the file before renaming it accordingly ?
Keep in mind the .MGT uses an interlaced tracks pattern. Each 10 sectors, it swaps sides and the next 10 sectors actually contain the same track from the second side rather than the following track of the same side.
In fact, floppy disks are written that way to minimize disk head moves and accelerate both writing and reading files.
Since it's the natural way data are organized on the real disk, I don't think the emulator should mess with the order the data are organized provided it would still read the tracks stored into the image file in sequence, even if the image has been created from a single side floppy disk.
However, I don't have first hand knowledge of how a single sided floppy disk is converted into a .MGT file. Does it store an empty track once every two tracks, or does it just store the existing data in sequence, the way the floppy disk drives transmits them to the computer ?
On the other hand, it seems like there's another file format for MGT disk images, the .IMG format. And this ones stores all the tracks from the first side in sequence, then goes on with the second side ones, restarting from track #0 !
As a result, loading a .IMG (I'm talking about the data internal organization) file that would for instance be renamed into .MGT (if the emulator would only manage .MGT files, maybe) would result in missing once every two tracks because they're actually stored 80 (or 40, in the case of a single density floppy source) tracks away !
The other way around would probably also fool the emulator (and as pointed, it's probably impossible to tell the difference between a double sided 40 tracks image and a single side 80 tracks image because they're the same size - though I don't think single side double density 3"1/2 floppies were that popular at the time : most single sided floppies were from the 5"1/4 single density era, where you used to punch a second hole in the sleeve to be able to use the second side)... :p
Well, what I mean is a half or quarter size image file should probably be automatically assumed by the emulator it's about a 40 tracks floppy, and if it's the quarter of the usual size, then of course it should be treated as a single sized one.
Anyway, maybe the first thing would to check the actual way your data is stored into the image file, check if the file is named accordingly to its actual format, and in the case the emulator can't mount one of them and it's unfortunately the one you've got, write a simple program to swap tracks as expected inside the file before renaming it accordingly ?