Re: [fuse-emulator-devel] Next release of fuse

[Miroslav A. <mir...@gm...>]

Hi

Alfi you say?
That's just 2x steppers and a pen hooked up to parallel port. Have its box
still in my drawer.

;)




Any new ideas can be documented in the official sourceforge project. Feel
free to open a ticket there.


If the provided file format is a snapshot file that is to be just loaded
into speccy memory, that is not that hard. Done that already.
If on other hand it needs emulating hw and loading that file into it, that
is more work.
And there is also the problem that additional hw might not be accepted into
the base fuse app. Especially if it is a local hw, not used widely.
In such a case it can be made available only within a fork.. just like i
made one in github.


Anyway i think this discussion is now off the original question ;)



Miro


Dňa ut 11. 2. 2025, 22:05 Tomáš <to...@vo...> napísal(a):

> D40 is emulated for many years. The first version, with WD2797 controller.
>
> I am looking for some further development too. For example low level
> microdrive cartridge format, like ZEsarUX has. LEC and Sinsoft memory
> extensions. Plotter device (Alfi).
>
> I can provide the technical docs to developers, but I am not enough
> experienced in Fuse internal structure to code it by myself.
>
> Here is the description of ZEsarUX  .mdv file format for example-
>
> The first 256 bytes is a header:
>
> offset Description
> 0 “RAWMDV” 6 bytes
> 6 -Version. byte. current: 0
> 7 -Creator: 30 bytes. String ended with 0 byte (0 final optional).
> Example “ZEsarUX 11.1-SN”
> 37 -Machine: What machine uses this microdrive. String ended with 0 byte
> (0 final optional). 20 bytes: examples:
>          “Spectrum”
>          “QL”
> 57 19 bytes.
>          -Date: 19 bytes. String ended with 0 byte (0 final optional)
>          “DD/MM/AAAA HH:MM:SS”
>
> 76-79 Usage counter, times the microdrive has been full read (times the
> header position has passed position 0). Unsigned integer 32 bits, little
> endian
> 80-255 Reserved. Set to 0
>
> After the header comes the data and then the type of all data. For
> example, for a 90 KB raw microdrive, here it comes:
>
> 90 KB of data: just the raw data
> 90 KB of type for all the data: every position of data can be: gap or data.
> And also, every position can be marked as "bad position" (emulating a
> microdrive with sections of data that can't be written or read).
> Every one of this data type is a mask of bits, currently only bits 0 and
> 1 are used:
>
> Bit 0: Data or Gap. If set bit, it's a data. If not, it's a gap
> Bit 1: Bad position. If set, it's a bad position. If not, it's a "good"
> position
>
> For example if the first 5 bytes of data are: Gap, Gap, Data, Data,
> Data+Bad, the data types will be:
>
> 00, 00, 01, 01, 03
>
> Following the same 90 KB example, the total size of the RMD file will
> be: 256+92160+92160=184576 bytes
>
> Omikron
>
>
> Dne 11.02.2025 v 8:09 Miroslav Arki napsal(a):
>
> > If interested I have a fork on github, look for arki55. Unmerged stuff
> > is only around Didaktik 128k with floppy D40 thou. I've created github
> > workflows for auto building multiple versions within PRs, also created
> > workflow for nightly builds. Limited to win32 packages only thou.
>
> --
> Tento e-mail byl antivirovým softwarem AVG zkontrolován na viry.
> www.avg.com
>