Re: Re[2]: Win 95 Scheduler
1998-09-09 19:41:01
I can tell you that version 3 does not solve this problem. We have
recently upgraded to 3 and I have Win95 on my PC. Anthony is right! It
is a nightmare. I have one of the only 2 servers using Win95 that are
being backed up by ADSM. My PC is being backed up during the day rather
than at night because I am here and have the manual scheduler running at
that time. For security reasons I do not go home and leave my PC up and
running. Also, this is why I have been scheduled for an 'upgrade' to
NT. Yippee!
Sandye J. Jackson
> -----Original Message-----
> From: Anthony Jones [SMTP:Jones4A AT KOCHIND DOT COM]
> Sent: Tuesday, September 08, 1998 12:13 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Re[2]: Win 95 Scheduler
>
> I second that! I work in an environment that has over 1500 Win95/NT
> desktops. I have denied the Win95 users from using ADSM for this very
> reason. It is a nightmare trying to support a user group with the way
> ADSM
> runs on 95.
>
> I have configured the Microsoft System Agent to kick off the scheduler
> 30
> minutes before the nightly backup, just in case the user closes it.
> This
> seems to work ok, if the user leaves the pc up at night.
>
> --- Anthony Jones
>
> > -----Original Message-----
> > From: Matt Cleland [SMTP:adsmrus AT STLNET DOT COM]
> > Sent: Tuesday, September 08, 1998 12:55 PM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: Re[2]: Win 95 Scheduler
> >
> > I think you hit the nail on the head - the ADSM scheduler in Win95
> is
> > *NOT*
> > a Windows friendly app. It runs in a Dos box, as a command line
> app.
> > Windows doesn't know what's running in that DOS session, so it will
> not
> > kill
> > it without asking the user.
> >
> > My wish for the Win95 client is for it to run as a true windows app,
> and
> > reside in the tray, not on the task bar. My laptop has at least 5
> or 6
> > little things running in the tray, and they are not obtrusive. My
> > personal
> > opinion is that having the ADSM scheduler sit as a button on the
> task bar
> > is
> > wrong, and leaves it exposed to having the user mess with it.
> >
> >
> >
> > --------------------------------------------------------------
> > 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
> > > Eric LEWIS
> > > Sent: Tuesday, September 08, 1998 1:33 PM
> > > To: ADSM-L AT VM.MARIST DOT EDU
> > > Subject: Re[2]: Win 95 Scheduler
> > >
> > >
> > > Well, not quite so fast. Most Windows friendly applications
> talk
> > to
> > > Windows during the shutdown process. For example, my Word
> '97 will
> > > gracefully close files, prompt me for save of updated and
> open
> > files,
> > > then shut down, all from a single Windows shutdown command.
> > >
> > > Microsoft put the hooks there for application programmers to
> use if
> > > they want to. I recall this particular hook in one of the
> earliest
> > > versions of the Windows SDK. This is one of those ADSM rough
> > edges.
> > >
> > > There are (V2 at least) similar rough edges on the Macintosh
> > client,
> > > the close window box on the Mac client actually shuts down
> the
> > > application. Frustrating to Mac users who think they are
> > > just putting
> > > the window into the background and then don't get a backup.
> We
> > > reported this particular grievance to IBM - and a fix was
> > > possible for
> > > v3. I haven't checked yet.
> > >
> > > Eric Lewis U of Wis-Madison
> > >
> > >
> > >
> > >
> > >
> > >
> > > ______________________________ Reply Separator
> > > _________________________________
> > > Subject: Re: Win 95 Scheduler
> > > Author: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> at
> IPNET
> > > Date: 9/8/98 9:56 AM
> > >
> > >
> > > ADSM like any other program on WIN 95 is a started task. If you
> shut
> > down
> > > Win 95 without shutting down running programs, you will get the
> same
> > > problem. It is a function of the operating system not ADSM.
> > > The solution
> > > is to go to Windows NT, where ADSM runs as a service in the
> background.
> > >
> > > Dave Larimer
> > > State Farm Insurance
> > > David.Larimer.HNJ9 AT StateFarm DOT com
> > >
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- Win 95 Scheduler, Mark R Lines
- Re: Win 95 Scheduler, Dave Larimer
- Re: Re[2]: Win 95 Scheduler, Matt Cleland
- Re[2]: Win 95 Scheduler, Eric LEWIS
- Re: Re[2]: Win 95 Scheduler, Anthony Jones
- Re: Re[2]: Win 95 Scheduler, Robinson, Cris
- Re: Re[2]: Win 95 Scheduler, Laszlo Nemeth
- Re: Re[2]: Win 95 Scheduler, Robinson, Cris
- Re: Re[2]: Win 95 Scheduler,
Jackson, Sandye <=
|
|
|