AUI Cover Disks larger ADF sizes?

[FerociousAmiga]

So I was browsing thru the FTP and found the collection of Amiga User International disks. Noticed that a bunch of the ADFs are larger than standard size.

eg:
Amiga User International Superdisk #089.zip 826K
Amiga User International Superdisk #090 [Ext].zip 936K

And are denoted by [Ext]. I tried using GoADF but doesn't like the ADF image. How do you write these larger images? What witchcraft is this?! ?

EDIT
I have a bunch of the AUI disk and noticed that #90 for example shows in my A500 WB 3.2.1 as NDOS or something like that but #89 is fine.

[Dan]

They have a custom format so that it fits more data than a normal disk.

It is called disksparse, and usually the disk before is the bootdisk.

Boot from the #89 then you should be able to access the files from the #90 normally.

If you want to make an adf, you can by booting from the #89 and use the dms, transadf or other tool on the (this is from memory: ) sd0: device instead of df0:

[FerociousAmiga]

Thanks Dan!

Great, Fudge me!!! I thought I had defective AUI floppies and formated about 20 of the 90 disks. Started suspecting something when every other disk was not reading.

[mark_k]

The package that allows you to read/write/format those disks is DiskSpare.

Once you have mounted one of the DiskSpare-format floppies, you could use some disk image creation program (one that isn't limited to normal floppy disks) to create plain disk image files of them.

[andy2004]

if i remember AUI on the diskspare in the mountlist used DS0:
low 0 high 79
blockpertrack 12

each disk was max 983kb in size.. instead of FFS 880k
the first disk of the AUI.. gets extracted into RAM.. and the mountlist is mounted from there.. and it tells you all you need to know to set it up..
they used Unlzx to extract the c.lzx file.. from the first disk..

basically copy c:unlzx ram:
copy c:*.lzx ram
unlzx x c.lzx ram:
^ containing all files required by the diskspare.. so that when the 2nd disc was put in, the system would automatically be able to see the files.

I have the same information in my winuae setup.
so i can mount the images but i use statram.device or fms.device
statram is ramdrive.. reason for 81 that would be the max setting for diskspare.
not used by AUI... they used the same settings in the FF0: below.

SD0: Device = statram.device
Unit = 0
BlocksPerTrack = 12
HighCyl = 81
BufMemType = 1
DosType = 0x444F5303
Flags = 3
Surfaces = 2
Reserved = 2
Interleave = 0
LowCyl = 0
Buffers = 5
StackSize = 600
Priority = 5
Mount = 1
#

FF0: Device = fmsdisk.device
Unit = 0
Flags = 1
Surfaces = 2
BlocksPerTrack = 12
Reserved = 2
Interleave = 0
LowCyl = 0
HighCyl = 79
Buffers = 2
BufMemType = 0

[chip]

EXT means extended ADF, longer than standard ADF of 880KB