Re: Problems transferring DOS3.3 from PC to IIe :(

[Rubywand <rubywand@swbell.net>]

dunk@ecosse.net writes ...
> 
> Hi All,
> 
> I just got my hands on a lovely IIe with SSC which I've been trying to
> transfer DOS3.3 over to from a Win PC.
> 
> I turn on the IIe, do Control-Reset to drop into Basic, a IN�2 (british
> keyboard??? cant get the # symbol??)

     According to the //e Technical Reference, even though an English pound
symbol is shown, the correct ASCII code for # is sent when you type Shift-3.


> and start the trasfer from the PC
> with Hyperterminal.
> 
> Everything is going fine until right at the end.  The last line that is
> shown on the IIe screen is
> *9D84G
> 
> Then the IIe just hangs.  According to the DOS33.dmp file instructions,
> I should be returned to a basic prompt?  Anyone got any ideas?
> 
> My SSC is set to 300bps, 8-N-1 with CTS.  Goes great until the end
> (even at 19200!).
 ....

     It sounds like you may be getting a corrupted send. So, when the 9D84G
(i.e. go to $9D84 and start executing code there) is sent, your system crashes.

     A common cause of corruption is using HyperTerm without the correct
settings. There are two ways this can happen:

1- The settings for the setup used are wrong.

     The Text file included with the DOS 3.3 dump file (in dos33dmp.zip)
describes a good 300 baud setup for HyperTerm which you can create and save as
A2at300.ht .


2- After HyperTerm is started, the user forgets to load the setup.

     After starting the HyperTerm program, you need to go to the Files menu and
Open your 300 baud setup-- i.e. the setup you created and saved under some name
like like "A2at300.ht". (It's easy to overlook this step. If you just start
HyperTerm and do not load a setup you want, you will get the default setup.)



     If you would rather not mess with HyperTerm, you can do a plain Text send
under MS-DOS.  As suggested by Delfs, you can use the "mode" command to set
up the com port and the "type" command to send a dump file (such as
dos33.dmp).

Under Windows95, 98, etc., open a DOS window. (Or, you can restart in DOS
mode or just boot MS-DOS.)  Change Dir to get to the directory containing
dos33.dmp.

Enter the following:

mode comX: baud=300 data=8 parity=n

In the above, replace "X" with the com port# for the com port connected
to the Apple II. For example, if the connection is to COM2,
you would enter ...

mode com2: baud=300 data=8 parity=n

Note: The PC should respond by echoing an abbreviated version of your mode
command on the screen. If you get an error message, it could mean that the
COM port you want to use is committed to some background task. For example,
if you have started a telecom program under Windows and it uses COM2, then,
the mode command will probably not work for COM2 until you shut down the 
telecom program.

When you are ready to start the transfer, enter the "type" command to start
the transfer. For example, taking COM2 as the port connected to the Apple II,
you would enter 

type dos33.dmp >com2:


     Since there is no error checking during the send, it is best to stick with
a low baud rate. Especially when sending via the MS-DOS mode command, baud rate
should be 300 (for both the PC and Apple II).



Rubywand