*** Original Author: ADSM-L @ MARIST - ** Remote User **; 12/07/94 16:38
>Received: from VM.MARIST.EDU by AUDUCADM.DUC.AUBURN.EDU (IBM MVS SMTP V2R2.1)
> with TCP; Wed, 07 Dec 94 16:38:39 CST
>Received: from VM.MARIST.EDU by VM.MARIST.EDU (IBM VM SMTP V2R2)
> with BSMTP id 1029; Wed, 07 Dec 94 16:14:21 EST
>Received: from VM.MARIST.EDU (NJE origin LISTSERV@MARIST) by VM.MARIST.EDU
> (LMail V1.2a/1.8a) with BSMTP id 8057; Wed, 7 Dec 1994 16:14:19 -0500
>Date: Wed, 7 Dec 1994 16:15:55 -0500
>Reply-To: "Dist. Stor. Manager(ADSM) List" <ADSM-L AT VM.MARIST DOT EDU>
>Sender: "Dist. Stor. Manager(ADSM) List" <ADSM-L AT VM.MARIST DOT EDU>
>From: Donald Coleman <coleman AT POST.QUEENSU DOT CA>
>Subject: Re: IP20259 Available for Fault Problem with Windows Client.
>X-To: "Dist. Stor. Manager(ADSM) List"
> <ADSM-L%MARIST.BITNET AT QUCDN.QUEENSU DOT CA>
>To: Multiple recipients of list ADSM-L <ADSM-L AT VM.MARIST DOT EDU>
>
>I've placed the diskette image file for the ADSM Windows client at V1 R2 L5
>(PTF IP20259) on index.storsys.ibm.com. Via anonymous ftp, the files are in:
>
> /adsm/fixes/v1r2/windows/
>
>This PTF includes the fix for APAR IC08731 (general protection fault when
>running the backup/archive and the scheduler client simultaneously).
>
I have installed the above files and it appears to have corrected the GPF
problem.
However, when I tried to install this version on a machine running Windows
For Workgroups and the Microsoft TCP/IP stack, it hung (it appeared to loop
before it interrogated the local drive structure and bfore it connected to
the host). <alt><ctl><del> gave the message that dsm.exe was not responding.
Neither the scheduler or dsm.exe would run.
I installed 1.2.4 on the same machine and it ran O.K. (except for the GPF
problem).
-----------------------------------------------------------
Don Coleman,
Queen's University Computing & Communications Services
Kingston, Ont. Canada K7L 3N6
Tel: (613) 545-2034 Email: Don.Coleman AT QueensU DOT CA
*** Comments from STEWAJM - Stewart, Mike; 12/08/94 10:19am:
Hm. Interesting. I've never gotten any version of ADSM to work
with Windows for Workgroups and Microsoft TCP/IP for WfW.
Every version I've tried hangs for awhile (maybe, several minutes)
then comes back with a TCP/IP failure message. Every other TCP/IP
application I've used with this setup works, though, including
Mosaic. I have an open problem, and the response so far is
"currently unsupported environment."
|