Subject: Re: ADT
Path: lobby!newstf02.news.aol.com!portc01.blue.aol.com!newsfeed.direct.ca!newsfeed.berkeley.edu!cyclone.swbell.net!nnrp1.rcsntx.swbell.net.POSTED!not-for-mail
Message-ID: <38659FC1.BE83DA4B@swbell.net>
From: Rubywand <rubywand@swbell.net>
Reply-To: rubywand@swbell.net
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: comp.emulators.apple2
References: <3864f026$0$4969@news.voyager.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 59
Date: Sat, 25 Dec 1999 22:55:29 -0600
NNTP-Posting-Host: 207.193.227.181
X-Complaints-To: abuse@swbell.net
X-Trace: nnrp1.rcsntx.swbell.net 946184145 207.193.227.181 (Sat, 25 Dec 1999 22:55:45 CST)
NNTP-Posting-Date: Sat, 25 Dec 1999 22:55:45 CST
Organization: SBC Internet Services



Ian Primus writes ...
> 
> I was able to get the Apple Disk Transfer working... sorta.
> When trying to send the adt.dmp to the apple, I get a BEEP! "Syntax
> Error" after every line of stuff. Anything else I should try?
 ....

    "SYNTAX ERROR" sounds like you are still in BASIC (which should not be).

     Once you set up the Apple for getting input from Slot 2 and start sending
the text of adt.dmp from the PC, the first instructions which are 'typed in'
(via the text being sent) are ...

3D0G  (3 D zero G)
NEW
CALL-151


     Evidently, the 3D0G is there in case the Apple is in monitor mode when you
start-- it should put you into BASIC. if you are not in monitor mode, it just
enters a nonsense BASIC line: 3 D0G  (By the way, this line does not get caught
as a syntax error when it is entered.)

     The NEW and CALL-151 should clear any current BASIC program and put you in
the monitor ready to have the program 'typed in':

803:4C 03 08 ...  etc.


     If you are getting a bunch of syntax errors it means the commands that put
you in the monitor are not being executed. The fault could be on the Send or
Receive side or both.

     The ADT directions tell how to place get the Apple II going with the SSC
set to 300 baud. They are likely to be correct because lots of users have
followed them with success.

     A more likely place for a problem is on the Send side. If you are using
HyperTerm, the following details may help:

Set up a New Connection profile. Name it something like adt300.ht, select
"Direct to COM 1" (or whatever COM port you use), and follow the remaing
prompts for the setup. Configure for 8 bits, No Parity, 1 Stop bit, 300 baud.
Set Flow Control to "None". Other settings- Emulation can be TTY and, in ASCII
Setup, nothing should be checked in the "ASCII Sending" area. I have just "Wrap
lines that exceed terminal width" checked in ASCII Receiving. Set Line Delay to
about 400 ms.

The file to send is adt.dmp.  To send it under HyperTerm, use the "Send Text
File" option, select "Browse", and pick adt.dmp-- you may need to set the
"files of type" box to "all files" to see adt.dmp.

(Once you have the 300 baud connection profile setup and saved, you can use it
for future tries at sending text at 300 baud. When you start HyperTerm you just
skip creating a new profile and "Open" adt300.ht.)



Rubywand