GoADF! - a new tool for your Amiga

[Nightshft]

Originally Posted by Vojo

A new version is coming (in a few weeks), with support for ADZ, DMS and HFE files

That's very useful! Especially if you can mount .dms files. (Because AFAIK dms only allows to extract to trackdisk.device and not to hdd-folders (like un-adf)).

[Vojo]

Originally Posted by Nightshft

That's very useful! Especially if you can mount .dms files. (Because AFAIK dms only allows to extract to trackdisk.device and not to hdd-folders (like un-adf)).

In the new GoADF version, DMS/ADZ/HFE files can be mounted like ADF. But you'll need more RAM for this, minimum 2 MB (FAST recommended)

[jvidia]

Originally Posted by Vojo

In the new GoADF version, DMS/ADZ/HFE files can be mounted like ADF. But you'll need more RAM for this, minimum 2 MB (FAST recommended)

GOOD WORK!

2mb is not the problem for people like me who have an ACA500Plus .... the compatibility with the MC68SEC000 is

PLEASE think about this issue

[utri007]

Originally Posted by Vojo

In the new GoADF version, DMS/ADZ/HFE files can be mounted like ADF. But you'll need more RAM for this, minimum 2 MB (FAST recommended)

Just registered it. Asked DMS support and got it. Thanks.

For me DMS is much more valuable than ADF

[jvidia]

Originally Posted by utri007

Just registered it. Asked DMS support and got it. Thanks.

For me DMS is much more valuable than ADF

Great to see Vojo listening to us

[utri007]

Originally Posted by Vojo

In the new GoADF version, DMS/ADZ/HFE files can be mounted like ADF. But you'll need more RAM for this, minimum 2 MB (FAST recommended)

Just wondering is "new GoADF" version current 1.2.1 build 1730 or future version?

[Vojo]

Originally Posted by utri007

Just wondering is "new GoADF" version current 1.2.1 build 1730 or future version?

Look at post #79

I'm finish it, new version for registered users will be avaible really soon

[jurassicman]

Yeah! I can't wait!

[BippyM]

Not tried this yet, but I must say.. It looks quality!

[Alpha One]

Hi, may I ask what kind of font you are using? It looks amazing.

Originally Posted by Vojo

thank you, I've already sent the key to you



PS. A new version is coming (in a few weeks), with support for ADZ, DMS and HFE files - first for registered users, as thanks for their support

[Vojo]

Originally Posted by Alpha One

Hi, may I ask what kind of font you are using? It looks amazing.

Look at post #57

[mr.spiv]

Slightly unrelated question.. any of these "friendly" formats support 16 byte "Sector Label Area" that is available for OFS/FFS trackdisk device?

[Jope]

Originally Posted by mr.spiv

Slightly unrelated question.. any of these "friendly" formats support 16 byte "Sector Label Area" that is available for OFS/FFS trackdisk device?

HFE and extended ADF and other MFM formats will support that, but ADF, DMS and similar cooked sector dump formats will not contain that.

[Toni Wilen]

In theory ADF could easily support sector headers because ADF is only supposed to support up to 82 tracks.

80 tracks including sector headers would become (80 * 11 * 2 * (512 + 16)) = 929280 bytes. 82 track standard adf is only 923648 bytes. Misdetection is not possible.

HD ADFs won't also cause problem, they are far bigger.

[Jope]

I guess if you make it so, then it will be the new standard. Somehow I feel it might be a better idea to just leave .adf alone and invent a new extension for these? Loads of people using old tools will get confused once these images start showing up. :-)

[Toni Wilen]

HD disk ADF or extended adf (which uses same extension) probably already breaks them. Data in sector header is also almost useless, creating yet another format/extension isn't worth the trouble.

Only remaining question, where to put extra sector header data:

Interleaved 1 (header, data, header data..)

Interleaved 2 (data, header, data, header)

Not interleaved (data, data, ... data, header, header.. header). This is too stupid way, manual hex-editing/checking would be really annoying but it also would be compatible with existing software, at least partly.

Interleaved 2 would be my choice.

[mr.spiv]

I am kinda tempted to use that extra 27.5KB but if none of the widely used "standard" formats use it, then it does not exists in practise.

[Jope]

Originally Posted by Toni Wilen

Only remaining question, where to put extra sector header data:

Interleaved 2 would be my choice.

Not interleaving it would make it easiest to strip it out for old tools, no new code needed, only dd or some other method for truncating the file.

I hope people would't include this data unless it is really needed, so images like this would probably be an exception rather than the norm. In reality I'm sure we'll start seeing these images even when it's not useful, because more data must be better.. :-)

Interleaved 2 sounds like the easiest way, you can easily ignore it from the end of a track buffer if it is not interesting in some particular application. Writing a label stripper is also a programming 101 level task.

[Toni Wilen]

"16 byte sector headers + 512 byte data" interleaved format support added. Only enabled if ADF file size is exactly (80 to 82) * (512 + 16) * (11 or 22) * 2. GUI "new disk" option won't be added!

[Vojo]

Originally Posted by Toni Wilen

"16 byte sector headers + 512 byte data" interleaved format support added. Only enabled if ADF file size is exactly (80 to 82) * (512 + 16) * (11 or 22) * 2. GUI "new disk" option won't be added!

GoADF will support this.