Deacon Blue writes ...
> 
> Hi!
> 
> I have setup the ADT v. 091 on a IIGS (ROM01) using a null-modem connection
> to the built-in Mini-DIN8 connector.  'ADT.EXE' is running as a DOS-job
> under Win ME.
> 
> I've experience from before with ADT v.122 running on a IIC-system <--->
> Windows-DOS mode,  where the transfers functions flawlessly at 9600 bps.
> speed rate.
> 
> My question is related to the performance of the "GS-port" of the software.
> As with v. 122 I got a "OK" confirmation in the MS-DOS dialog and a progress
> bar during the writing  process.
> 
> This is not the case with GS-version.  No information is received to confirm
> write on the DOS-side.  When trying to make a directory listing of available
> images, this takes effect only after the second/third attempt.
> 
> Aside from this quirky behaviour the programme is able to read/transfer
> DSK-images onto the IIGS-floppy.
> 
> Even though the programme works I'm not sure if the source-transfer through
> 'Win Hyperterminal' was successfull at 300 bps, as there appeared some
> garbage text after the save-process had finished.  Should this be expected?
> 
> --->  Is there available a finished DSK-image containing the latest ADT for
> GS, as with the other  v.1.22?  I might try this solution to get a 100%
> correct version, if available.
> 
 ....


     Almost certainly, your difficulties are on the PC side and stem from
running adt.exe as a DOS job under Win ME instead of under plain DOS. (ADT does
not run well in a Win 95 DOS window, either.)  Try restarting your computer in
DOS and running ADT that way.


     For a way to check your version of ADT-GS, see the info below ...


>From "ADTCK (ADT Transfer Checker) July 2000 Update"

 ....

     Type in the program listed below and save it as
ADTCK on the same disk as the ADT you've transferred. Then, 
RUN ADTCK and check the numbers you get against the checksums
listed after the program. (The program displays intermediate
sums and a final sum.)

Note: Changing the saved default parameters of ADT via an 
ADTConfig program, etc. will change the checksum and render
the checksum test invalid.


ADTCK for ....  ADTGS (v.90), ADTgs (v.91)

 10  TEXT : HOME
 20  PRINT  CHR$ (4)"BLOAD ADT,A$4000"
 40  FOR I = 0 TO 2579
 50 Z = Z +  PEEK (16384 + I)
 55  IF I / 500 =  INT (I / 500) THEN  PRINT "CURRENT SUM= ";Z
 60  NEXT I
 70  PRINT "CHECKSUM= ";Z


Checksums

 ....

ADTGS (v.90)     ADTgs (v.91)   for Apple IIgs
76               76
39865            48588
89559            97886
142200           151354
206728           201728
289377           284376
295079           290904  <-- final sums

 ....



Rubywand