Message authorized by:
    : thughes AT POBOX.HARVARD DOT EDU@INTERNET at #EMAIL
     Same here exactly. Thought it was security software, it wasn't.
If I remove ftp stuff from the autoexec.bat temporarily it will come up and of
course not be able to connect, so there's something. but what?

FTP's PC/TCP for windows say's 3.1 on the icons, supposed to work with adsm v2
according to the doco.

Waiting

______________________________ Reply Separator _________________________________
Subject: V2 Windows 3.1 Client Problems
Author:  ADSM-L AT VM.MARIST DOT EDU@INTERNET at #EMAIL
Date:    3/15/96 10:27 am


X-Sender: thughes AT pobox.harvard DOT edu (Unverified)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

Hello...

I'm running into a couple of problems with the install of
the version 2 Windows 3.1 client across a few machines.

These machines have either PCTCP 2.2 or 2.3 software
installed. I've done the the winsock.ddl and the
'minimumcopyspace' corrections, but still am having
difficulty.

The problems I'm seeing:

  * On one machine (486/33 16MB), any attempt to start the
    ADSM client results in getting thrown back to the dos
    c: prompt, with windows ending. This is with no other
    application present (except for I think Micosoft Office)


  * On several other machines the ADSM client installs and
    functions as advertised. However, when not running a backup
    or schedule, the parm for 'minimumcopyspace' in the windows.ini
    file has to be set back to 12 or 18 from the recommended 32,
    for any other combination of software to run.

    The customers get very annoyed at having to switch this
    configuration to get a backup done and then have to remember
    to set it back to run other software.

    My gut tells me there is something obvious that I'm missing, but
    can't quite put my finger on it.

Any help would be appreciated. Thanks

...Tom Hughes
   Technical Consultant
   Harvard University - OIT