You can download sad to dsk and dsk to sad converter source code from ftp.nvg, and use it if you want to. Or you can just look there for more information on handling sad files and what is "next" in the header ;-)
8 in last byte of header means 512 bytes per sector. It's 64*8=512. All values from 1-255 are supported, so you can theoretically have 64-16320 bytes per sector. > Sounds to me like we can and should use sad.gz for most disks because > of its simplicity, and only use sdf when we have to? Generally, SAD supports everything which is not copy-protected. SDF supports absolutely everything. At least I think..... ----- Original Message ----- From: "Stuart Brady" <[EMAIL PROTECTED]> To: <sam-users@nvg.ntnu.no> Sent: Thursday, March 08, 2001 6:09 PM Subject: RE: Disk image formats > On Thu, 8 Mar 2001, Simon Owen wrote: > > >SAD files have a 22 bytes header, which contains a rather large text > >signature and some geometry information. You can specify the number of > >sides, number of tracks per side, number of sectors per track and the bytes > >per sector. > > So "Aley's disk backup", char sides (2), char tracks (80), char sectors > (10)... and then what? All of my disks seem to have 8 as the last byte in > the header, so is this just multiplied by 64? > > [snip SDF info] > > Sounds to me like we can and should use sad.gz for most disks because > of its simplicity, and only use sdf when we have to? > -- > Stuart Brady >
