I think this could be some in-built goofyness in Windows.  I have seen
this behavior with other Windows apps, specifically in Outlook 98. If
I ever access the A drive from Outlook, i.e. to attach a file to email
or save to floppy, every time I bring up the "file locator" dialog it
will grind my A drive.  The only thing that stops this is if I kill
Outlook and restart it.

--------------------------------------------------------------
Matt Cleland                            mcleland AT msiinet DOT com
Matt Cleland                            mcleland AT msiinet DOT com
IBM Certified Specialist - ADSM
Midland Systems, Inc.                   (618) 345-0864
St. Louis, MO                           (618) 346-1779 FAX


> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> Andrew Raibeck
> Sent: Wednesday, August 26, 1998 10:30 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
> >
>