Re: ADT with a Laser 128

[Rubywand <rubywand@swbell.net>]

Ed Eastman writes ...
> 
> It seems you have done some homework.  Personally I never had any
> compatability issues with the laser128 I had.  I'll have to try the
> memory address continuation thing in the monitor program.  Currently I
> have a version 4.2 (Thankx Roy) and (gasp) it too fails the continue
> entering numbers test.  You are not alone.
> 
> Thankfully you have the answer to the initial problem, include the
> memory addresses in each line of ADT.DMP.  (Catch that Jeff?)
> 
> I will simply have to try the Laser128 and see for myself about
> transferring disk images via ADT.  It should be compatible...  Of course
> I don't use any term software for the initial transfer, I just
> null-modem connect and have the TP Type the file to the port. (Type
> adt.txt >com1)
> 

 ....

> >
> > The fix is to include the memory addresses for each line in ADT.DMP; I
> > whipped up a quick Perl script to add them and everything is happy.
> > Strangely, I can only find that one other report of such an issue. Is it a
> > known problem with the Laser's monitor routines?
> >
> > Anyway, as Calthaer reports, the Laser 128's serial port is not compatible
> > enough with a SSC for ADT to do its trick. Damnit!
> >
 ....


     Don't know much about the Laser 128. If sending an address at the start of
each line helps, sending ADT_ss.dmp (included with Paul Schlyter's ADTcc stuff)
may work. It's supposed to be ADT for SSC interfaces and it does send the
addresses.

     Or, just going to ADTcc (for non-SSC interfaces) may work. ADT_cc.dmp also
includes the addresses. 

     Both .dmp files have the usual PC LF chars in the end-of-line code; so,
you may want to tell Hyperterm or whatever to filter those out.

     Have reorganized ADT stuff a bit on GS WorldView. Now, practically
everything-- Windows and MS-DOS PC programs plus ADT, ADTcc, and ADTgs is
included in ADT_2004.zip at http://apple2.org.za/gswv/a2zine/Utils/ .



Rubywand