which adf creator

I've still not got any ADF creators working with workbench/kickstart 1.3.

Can anyone recommend one, and say for sure that it will work in 1.3?

I'll need it to compress from non-dos (i.e. games) disks and be able to span multiple floppies.

Ta

[T_hairy_bootson]

Tracktool works great in WB1.3.

http://members.tripod.com/whdloadrules/utilities.html

Not sure what you mean by span multiple floppies though.

Thanks for the tip-of. TrackTool runs perfectly. HOWEVER...

If I make an image of a single floppy disk (game), with the destination path df1:filename.adf, it starts running but stops after reading 74 blocks, saying the destination disk is full. So the image doesn't fit on a completely formatted floppy disk. It's bigger than the disk it came from! I can't save it into RAM and compress it either, as I've only got 1 meg.

This is what I meant by needing to span multiple disks (I'm thinking of things like winzip that lets you save a file bigger than one floppy, onto a sequence of floppies.)

Is there any adf creator that:
EITHER compresses 'on the fly'
OR lets you write to a sequence of floppy disks?

Cheers,

T

[scaf]

You can try this compilation of utilities : http://nebulus.fr.nf/~scaf/adfdump/
It's a WB 1.3 disk, designed to work with KS1.3

[Rick Dangerous]

On this site (english & german):
http://adfsender.stoeggl.com/index.html
there's too a description how to use transdisk and transwarp on the Amiga.
Both programs do the same: creating an ADF anywhere.
Try it.

Cheers,
Rick

[LocalH]

For compression on-the-fly, you can use a DMS tool - I know there are some potential disks that DMS won't be able to handle, but for most ADOS disks and non-protected NDOS disks, you shouldn't have a problem (although I would test the DMS after making it by rewriting it to a disk). Alternately, you can use transdisk with command line arguments - by default, it copies the whole disk, but you can give two parameters that denote the starting and ending track. So, you can do the disk in two or four passes, depending on how much RAM you have (4 passes for 512KB and 2 passes for 1MB). Then, you just have to read out each section of the disk separately, to combine them when writing back to disk (whether it be a real or emulated disk). If you're converting Amiga disks to ADF, then you should just be able to join the files in their proper order (using any suitable program on your OS of choice), as ADF doesn't add a header to the disk image. If you're converting ADFs to Amiga disks, then you'll have to write them back out to a disk.

For four passes, using RAM as a placeholder (be sure to copy each part to another medium before doing the next part):
transdisk >RAM:disk-00-19.adf -s 0 -e 19
transdisk >RAM:disk-20-39.adf -s 20 -e 39
transdisk >RAM:disk-40-59.adf -s 40 -e 59
transdisk >RAM:disk-60-79.adf -s 60 -e 79

To write each piece back to a disk (in case you're transferring disks to an A500), replace the > in each line with -w and a space, and either copy your pieces to RAM: as you're writing the disk, or change the path to where you've already got the pieces. This will cause transdisk to write the parts back to disk.

If you have 1MB, then do the same thing as before, except changing the tracks to copy:
transdisk >RAM:disk00-39.adf -s 0 -e 39
transdisk >RAM:disk40-79.adf -s 40 -e 79

This should work for all standard disks. If you have a disk that happens to use the few tracks above 79, this will not work (and as I haven't used transdisk to transfer such a disk, I don't know how high transdisk can read and write).

Edit: Bah, forget all this, Tracktool allows you to do exactly what you want. From the docs:

Originally Posted by Tracktool

You can specify the number of tracks to read with the LOW and HIGH arguments. To read tracks 40-69 only:

TrackTool READ Games:Lemmings.ADF LOW 40 HIGH 69