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

[Rubywand <rubywand@swbell.net>]

Dunk writes ...
> 
> On Mon, 22 May 2000 12:34:25 GMT, "Paul R. Santa-Maria"
> <paulrsm@ameritech.net> wrote:
> 
> >Have you tried to strip the last line from the MS-DOS file and type it in
> >by hand after transferring the rest?  Where is the DOS33.DMP (or whatever)
> >so I can take a look at it?
> 
> Got it from:
> 
> http://www.grin.net/~cturley/gsezine/GS.WorldView/v2000/Mar/index.html
> 
> The file doesnt seem corrupt in any way.  I tried leaving the last
> line off and typing it in manually but same result :(
 ....

     Tried out downloading the file from GSWV and transferring it to our II+
(instead of to the IIgs).

     Our II+ has 64k RAM and a decent general purpose serial card (not an SSC).
The cables used were the same as for tests with the IIgs except that the A2
cable plugged into the NULL modem adaptor was a plain 12-ft 25:25 cable running
across the room and connecting to the serial interface card.

     The 300 baud Text transfer went fine (took about 20 minutes) and ended
with the expected Applesoft prompt on the screen. However, unlike with the
transfer to the IIgs, I did not have keyboard control at the II+! Don't know
what the explanation for this is. (Perhaps some interfaces recognize and deal
with an 'end of send' code correctly and others do not.)

     The cure was to enter IN#0 (letters in caps, the "0" is a zero) from the
PC keyboard. The "IN#0" appeared on the II+ screen and the command was
executed. This returned input to the II+ keyboard and the INITHELLO could be
entered to create a bootable DOS 3.3 diskette. (This info has been added to the
GSWV March 2000 article and info file inside dos33dmp.zip.)

     BTW, before doing the IN#0 I tried entering the INITHELLO from the PC.
This worked fine, too-- the disk was INITed on the II+.

     It may be that the above does not relate directly to your situation; but,
it does show that different interfaces may behave differently. For instance, if
the final 9D84G is not being executed because of the way your interface handles
its input buffer, entering Return from the PC keyboard (perhaps more than once)
after the transfer may do the trick.

     Something else to try is to enter INITHELLO (in caps) from the PC
keyboard. Or, you could try entering IN#0 to give keyboard control back to the
Apple II+.

     As long as Hyperterm is set up to _not_ "send line ends with line feeds"
(i.e. this option is not checked), you should not be getting a corrupted send.
(The text should show on the II+ screen as though it is being typed in.) 
Really, you should be fairly close to getting the transfer to work.

     There is one more thing to make sure of: your II+ needs to have at least
48K of RAM installed. The transferred DOS 3.3 will not work on machines with
less than 48K.



Rubywand