Conference 7.286::atarist

I frequently use Whack at 19,200 baud both through DECserver and
directly connected to a DZV terminal line.  I also have used
Uniterm/KERMIT this way.  It's easier than using a modem.  You follow
the same instructions, but skip the part about dialing the modem, etc. 
You use any standard DEC null modem cable, such as you would use for
connecting a VT220 or other terminal.  The one on my desk is a
BC22D-10.

To be really simplistic:

- Make sure EMULATOR.ACC and CONTROL.ACC are loaded on the ST.  They
came with mine - I think they all have it.

- Connect to the system with a null modem cable as you would any random
terminal.

- Call down the VT52 emulator desk accessory.

- Set baud rate for 9600

- Go back to the emulator and log in as you would a VT52.

If you can get that far, you should be able to extrapolate for running
Whack or Uniterm, and even for using KERMIT and STRANSF, by following
the same instructions the modem users follow.

    If you have access to a 3100 then i found this to be the easiest way:

            1)  Format a floppy on the atari for 720k (double sided - normal 
                format. No special TWISTER format etc.)

            2)  Using a public domain program called IBMFMT, format
    		the same disk on the atari. Thus you have formatted the
    		one disk twice.
    
    Now you have a disk that has been formatted for the ST and IBM/3100 etc.
    
    Now from the Vax end :

            3)  copy pcdisk.exe disk:[directory]*
    
    If you want the pcdisk.exe then i'll copy you one. Also set up these 
    logicals, i have them in a file called PCDISK.COM, but it is only 
    these 3 lines :

            4)  $define sys$share disk:[directory],sys$library
                $define sys$help disk:[directory],sys$sysroot:[syshlp]
                $pcdisk == "$disk:[directory]pcdisk"

    Now from VMS invoke the PCDISK utitlity.

            5)  $pcdisk
            
    At the pcdisk prompt type the following :

            6)  PCDISK> use b: madala$dua2: /write

    Replace madala$dua2: for your VMS device name for the floppy. Note 
    the prompt has now changed. Now import the file onto the floppy disk.

            7)   B:\> import [directory]filename.txt b:
    
    Exit.

            8)  B:\> exit

    Just to be sure, go back into PCDISK and check the contents of the floppy :

            9)  $pcdisk
                PCDISK> use b: madala$dua2: /write
                B:\> dir b:
                       .
                       .
                       .
                B:\> exit

    I think that if you check the contents of the floppy inbetween steps 7 
    and 8 then it remembers what you have put there, instead of actually 
    doing a directory of the floppy.

    Now all you need do is take the floppy home, and read it from your ST!
    
    Cheers,

                               Lewis.
                     

        Is this double formating or formating on a MS-DOS machine always
        required?  I understand that TOS V1.4 fixed this problem.

    re .3
    
    Lewis,
    
    I did everything exactly how you described in your reply.
    the result is the following:
    
    When I do the IMPORT (even with the /LOG qualifier) PCDISK says
    
    %PCDISK-I-IPD, file.dat imported to A:\file.dat
    
    and a DIR command verifies that message. The file is shown in the
    directory of the floppy. But when you EXIT from PCDISK and start
    it again and USE the same floppy again it is completely empty.
    
    During this procedure it is strange that the USE command takes a little
    time, but the IMPORT command return immediate with the prompt and the
    message.                                                       
    
    Any Ideas
    Joachim

    
    Have a look in notes 730.* ,730.30 and following.
    Perhaps part of your pb.
    					Jean-claude.
    

    Hi
    	I am trying to get a copy of pcdisk but oldtmr don't exist anymore
    can somebody help me ?
    
    P.K.

msbcs::disk_wallace_r:[wallace_r.public]pcdisk*.*

There a two .exe files and a .hlb (help library) file.

	Ray

    The files are also supplied by pathworks, you can extract them from the
    distribution save sets. They work without a license. 
    
    Regards, 
    
      Peter.

    re last two
    
    Thank you Itried it and it worked great...Look out internet here I
    come. 8^).
    
    p.k.