Yes, the path is one place. For example, if the application has its own
WINSOCK.DLL, WSOCK32.DLL, or other TCP/IP library that duplicates the Windows
functions, in its own directory, but that directory appears first in the PATH
variable, then that might cause this problem (hopefully the application didn't
*replace* the WINSOCK.DLL that comes with Windows.).
If you can't locate the problem, you might contact the vendor of the software
application and ask if they install their own winsock support (this would be my
suspicion).
Regards,
Andy
Andy Raibeck
IBM Storage Systems Division
ADSM Client Development
e-mail: storman AT us.ibm DOT com
ADSM-L AT VM.MARIST DOT EDU on 08/26/98 08:59:21 AM
Please respond to ADSM-L AT VM.MARIST DOT EDU
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: Querying the A Drive
Andy,
We have that problem with a Win95 client - opening the client lauches an
internet mail application.
I had no idea where to look to turn it off.
Can you tell me how to "go back to the normal stack?" Is it the windows
PATH variable you are referring to?
> ----------
> From: Andrew Raibeck[SMTP:storman AT us.ibm DOT com]
> Sent: Wednesday, August 26, 1998 11:29 AM
> To: ADSM-L AT vm.marist DOT edu
> Subject: Re: Querying the A Drive
>
> The latest V3 Win32 client GUI (version 3.1.0.5, which was just refreshed
> yesterday) has a backup tree that displays "Local", "Network", and
> "Removable"
> file systems. If you just work with the "Local" drives, I'm pretty sure
> that we
> don't look at the floppy since it is a removable drive.
>
> About the second problem: I vaguely recall similar issues in the Windows
> 3.1x
> environment. In those cases, launching ADSM caused internet applications
> (like
> a web browser, or something like that) to be launched. This was because
> installation of the internet application caused a new TCP/IP stack for
> that
> application to get installed (I think it got installed in a separate path
> from
> the normal TCP/IP stack, but the path configuration caused the new stack
> to be
> used by default). Going back to the normal stack resolved the problem. My
> memory is a bit fuzzy on the details (it's been a few years since I've
> seen
> this), but I think I got the gist of it right.
>
> Anyway, maybe something like this is happening in your user's case?
>
> Best regards,
>
> Andy
>
> Andy Raibeck
> IBM Storage Systems Division
> ADSM Client Development
> e-mail: storman AT us.ibm DOT com
>
> > Don't ask me why, but I have a customer who would prefer it if ADSM
> didn't
> > check the A: drive when the GUI is first initiated. I think they don't
> > like
> > the noise it makes and since they won't ever be backing anything up from
> > the
> > A: drive they don't want to listen to it. Anyway, being the good
> support
> > person I strive to be, I thought I'd ask if anybody knows a way to have
> it
> > stop doing that? We tried DOMAIN C: D: in the options file, but it
> still
> > goes to check the A: drive. We're a version 2 Windows 94 32-bit Intel
> > client
> > and version 2 VM server.
> >
> > This person also has another problem - When the ADSM GUI is initiated a
> > product they're using on their workstation called, Midrange Workspace
> > launches and attempts to connect to an AS400 machine. Has anybody every
> > heard of this or have any thoughts on what might be going on?
> >
> > Thanks in advance for your help.
> >
> > Betsy
> >
>
|
