then three blank lines... then the next line. I'll try the inter-character delay...also, upon completion, it doesn't go back to the ]-prompt. it just has an asterisk on the line. that makes me think that these inverted letters are corrupting the uploading of the operating system.
the way i'm starting this is by booting the system using the system utilities disk. then i choose #9 from the list and exit out of the utilities. this gives me a ]-prompt. i then type in#2 and then send the file from the pc. that all seems to be working properly... until about 5-8 minutes into the procedure when the inverted letters show up.
i also noticed some differences between the documentation and the //c. for instance, the dos33dump docs say to type PR#6 but that's not a valid call on the //c. is that a critical step? and the first line in the dump is CALL 151. is that the correct call for the //c?
Peter Ibbotson wrote:
The last few lines look like this: :06 04 02 0F DD C6 B4 F0 08 C9 :BB D0 04 A0 1D A2 00 4C FF B1 :B7 00 00 00 8D 63 AA 8D 70 AA :8D 71 AA 60 20 5B A7 8C B7 AA :60 20 7E AE AE 9B B3 9A 20 16 :A3 BA 8E 9B B3 A9 09 4C 85 B3 : 3D0:4C BF 9D 4C 84 9D 3F2:BF 9D 38 4C 58 FF 3F8:4C 65 FF 4C 65 FF 65 FF 9D84G The last 4 lines put the jump vectors back in then call the DOS cold start routine. $3DO - jmp to dos cold start, jmp to dos warm start $3F2 - Reset handler, checksum, Applesoft & handler $3F8 - Jmp-Ctrl-Y,NMI and IRQ If this is isn't what you're seeing on screen then I can only presume you have some sort of comms problem, it might be worth trying a small inter character delay. The inverted L and P sound like that might be the problem.