[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Backing up 13 sector disks
- Subject: Re: Backing up 13 sector disks
- From: Rubywand <rubywand@swbell.net>
- Date: Wed, 27 Jun 2001 02:25:29 -0500
- Newsgroups: comp.emulators.apple2, comp.sys.apple2
- Organization: SBC Internet Services
- References: <eqilet0acjll0aiuh87cqphmogm33fuipu@4ax.com> <9ebs8k$n73$1@merope.saaf.se> <3B2D078A.C297626A@coli.uni-sb.de> <3B38A85F.EC8507E3@swbell.net> <9hakc6$pvh$1@merope.saaf.se>
- Xref: archiver1.google.com comp.emulators.apple2:1174 comp.sys.apple2:9547
Paul Schlyter writes ...
>
> In article <3B38A85F.EC8507E3@swbell.net>,
> Rubywand <rubywand@swbell.net> wrote:
>
> > A different approach would be to modify MUFFIN to operate something like
> > COPYA-- i.e. just copy 13-sector to 13-sector and not worry about
> > converting files for placement on a 16-sector disk.
>
> If you transferred Apple's old FID utility to a 13-sector DOS disk,
> it would happily copy files from 13-sector to 13-sector disks.
....
>
> Or you could run my little utility "DubbelDOS": run it on an
> unmodified version of Apple DOS 3.3: it will remove the FORMAT
> command, and then patch DOS 3.3 so it recognizes both 13-sector
> and 16-sector disks, switching automatically as needed. With
> DubbelDOS installed, you can use FID to copy files to/from 13/16
> disks in any combination (13==>13, 13==>16, 16==>13, 16==>16).
> With DubbelDOS you'll lose the ability to format floppies though.
>
> Below is DubbelDOS in Apple Monitor dump format - transfer the dump
> as a text file to a DOS 3.3 disk, then EXEC it to convert it to a
> binary file, and finally BRUN it.
>
>
> Dumping DUBBELDOS (start $0803, length $04C6)
> ==============================================================
> 0803: 20 58 FC A2 20 BD 84 0A DD 8E AE D0 2F CA 10 F5
> 0813: 20 20 0A 8D 8D 8D C4 D5 C2 C2 C5 CC C4 CF D3 A0
....
> 0CA3: 91 3E C8 A5 26 29 07 1D 99 BB 91 3E C8 A5 27 29
> 0CB3: 07 1D CC BB 91 3E C8 CA 10 B3 AD 99 BC 4A 4A 4A
> 0CC3: 0D FF BB 91 3E 60
>
> BSAVE DUBBELDOS,A$0803,L$04C6
....
Pretty neat!
Okay. On a PC, I copied just the code part-- i.e. ...
0803: 20 58 FC A2 20 BD 84 0A DD 8E AE D0 2F CA 10 F5
0813: 20 20 0A 8D 8D 8D C4 D5 C2 C2 C5 CC C4 CF D3 A0
0823: DB D2 A0 D2 C5 C4 C1 CE A0 C9 CE D3 D4 C1 CC CC
0833: C5 D2 C1 C4 8D 8D 8D 87 00 4C D3 03 A2 1C BD D0
... etc. through
0CC3: 0D FF BB 91 3E 60
including the following blank line.
This was pasted to a blank WordPad window and saved as a plain Text file.
The all-code Text file (call it "DDOSDMP.TXT") can be EXECed on an Apple
II so long as it does not have the 0D 0A line ender chars commonly used by
PC's. (On an Apple II, the line ender char needs to be just 0D.)
I used a PC Hex editor to replace all occurances of 0A 0D with 0D and
transferred the resulting file via regular Z-modem to the IIgs.
Another way is to transfer the unaltered PC Text file and, on the Apple
II, load it into Appleworks and save it as a Text file. Appleworks
automatically strips off the 0A. (Doing an ASCII or Text transfer from PC to
Apple II will usually get rid of the unwanted line ender char, too.)
Most likely, the transferred file will end up on a ProDOS disk or RAM
disk. Copy II Plus (v7.x or higher) can be used to copy the file to a DOS 3.3
diskette.
The DOS 3.3 disk with DDOSDMP.TXT was booted. To EXEC the file you can
enter ...
CALL -151
to get into the monitor; and, at the "*" monitor prompt, enter
EXEC DDOSDMP.TXT
This should result in a string of "*" prompts being displayed as the Text
file is read and 'typed in' by the EXEC command. After about 15 seconds, the
process is done. Pressing RETURN is a good idea to make sure the input buffer
is cleared.
While still in the monitor, the results can be checked by looking at the
end of the code via ...
CC3.CC8
This should show
0CC3- 0D FF BB 91 3E
0CC8- 60
To save the binary code, I entered
BSAVE DDOS.BIN,A$803,L$4C6
Doing a BRUN DDOS.BIN starts the program fine. What I'm wondering now is
what the directions (which seem to be in Swedish) mean?
Rubywand