Re: does adt.dmp work with prodos?

[Rubywand <rubywand@swbell.net>]

wabrown@my-deja.com writes ...
> 
> i've loaded adt.dmp (from adt122.zip) on a laser 128
> running prodos.  the readme.txt indicates adt.dmp is
> used with dos3.3.  is adt.dmp binary supposed to run
> properly when the boot disk is prodos?

     No. It is a machine language program which expects to hook into DOS 3.3.

 
> when i brun adt and select the "send" option, i get
> the message "testing disk format" and then an immediate
> "brk:$03DB" (it never accesses the drive).  is RWTS not
> at $3D9 in prodos?

     A jump at $3D9 exists as a standard R/W Track-Sector connection point for
DOS 3.3 but this is not the case for ProDOS. In a for-ProDOS version of ADT you
would probably want to use the Machine Language Interface routines which read
and write 512-byte blocks.

> 
> if adt.dmp doesn't work with prodos, is there another
> adt---.zip that will work with prodos?
 ....

     ADT transfers can transfer 5.25" ProDOS disks; but, it does not run under
ProDOS.

     If you do not have a way to boot DOS 3.3, you can email a regular poster
to the newsgroup and offer to pay mailing and materials costs to get a bootable
DOS 3.3 diskette.

     Byron suggested that, perhaps, your concern with using ProDOS might be
that you want to transfer ProDOS disks. As he points out, ADT does not care
whether the 5.25" disk it transfers is a ProDOS or DOS 3.3 disk.

     ADT reads and writes sectors; and, both DOS's use the same basic 16-sector
format for 5.25" disks. (ProDOS uses two sectors to come up with a 512-byte
block-- equals 8 blocks per track-- on 5.25" disks.)

     So, you can use a ProDOS version of Copy II Plus (e.g. v7.4) to copy the
ADT file from the ProDOS diskette onto a bootable DOS 3.3 diskette. (Or, you
could boot DOS 3.3 and re-transfer adt.dmp to a DOS 3.3 diskette.)


     One thing that may be confusing at first is the talk about "sector
ordering" in the ADT docs.

     The sectors on the 5.25" diskette are physically laid out in consecutive
numerical sequence. The name of each sector (e.g. "0", ..., "15") is coded onto
the diskette.

     Using this 'hard' ordering would slow down reads and writes because files
usually exist on consecutively numbered sectors and (at least at 1MHz) there is
not always time to gulp a sector of stuff and be ready to get the very next
sector which passes beneath the R/W head. Things would be slow because you'd
have to wait for another revolution of the disk to read the next sector in a
file.

     Both DOS 3.3 and ProDOS 'rename' the sectors via translation tables so
that, say, the sector called "Sector 4" does not physically (on the diskette)
immediately follow "Sector 5". This makes it possible to often take in two or
three sectors of a file in a single revolution.

     Naturally, DOS 3.3 and ProDOS 'rename' the sectors differently. Since ADT
runs under DOS 3.3, it uses DOS 3.3 names for the sectors and creates images in
which data is consecutively stored in terms of DOS 3.3 naming. By generally
accepted convention, these are ".dsk" 5.15" disk images. (An alternative
naming, ".do" for "DOS 3.3 order" is hardly ever used.)

     Since ADT uses the same ordering for creating disks from disk images,
everything works out okay for transfers in either direction whether the content
is DOS 3.3 or ProDOS. (And, emulator programs just care about being able to
detect the ordering used for an image. They do not care whether the content is
ProDOS or DOS 3.3.)
     
     The place where you can hit a snag is in transferring disk images created
by some utility which uses ProDOS naming for the sectors. (For example, NuLib
can create disk images from .sdk files created by 8-bit ShrinkIt; the images
will use ProDOS sector naming.)  These images are supposed to have names ending
with ".po" (for "ProDOS order").

     ADT will transfer a .po disk image and create a diskette; but, most of the
sectors will end up at the wrong physical locations on each track. Whether the
stuff in the disk image is DOS 3.3 or ProDOS does not matter. When you boot
such a diskette it will crash because the contents of files is all swapped
around.

     If you run ADT under DOS 3.3 and stick with transferring DOS 3.3 order
(.dsk and .do) disk images to your Apple II, your disks should work fine.




Rubywand