[ngw] High Utilization on GW Server

David Calhoun mailinglists at jam.rr.com
Fri Dec 14 15:55:14 UTC 2001


Here's a reference to WININIT.  It's oriented towards programmers,
though.

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q140570


David

Mary Van Engelen wrote:
> 
> Thanks, David!  We were actually investigating using WININIT but couldn't
> find info on the sequence of events.  Also, we had the syntax backward.
> 
> Can you point me to a source for more information on using WININIT?
> 
> Thanks again,
> Mary
> 
> At 12/14/01 03:29 AM, David Calhoun wrote:
> >Mary,
> >
> >Here's how install programs do it:
> >
> >Create a text file named WININIT.INI in C:\WINDOWS with the contents
> >
> >[rename}
> >C:\WINDOWS\SYSTEM\NWWS2NDS.BAK=C:\WINDOWS\SYSTEM\NWWS2NDS.DLL
> >
> >Reboot your system.
> >If the file already exists, reboot before doing the above.
> >If you wanted to delete the file, you could replace the first filename
> >with NUL
> >
> >The syntax is DestinationFileName=SourceFileName
> >You must use only local files and short (8.3) names.
> >You can have multiple lines with one deletion or rename per line.
> >
> >When you start up, WININIT.EXE processes WININIT.INI if it exists and
> >renames it WININIT.BAK.  You'll see the "Please wait while Windows
> >updates your system files" messages to let you know it found something
> >to do.  There are no error messages I'm aware of, so if a file is
> >missing
> >or the name is misspelled, you won't know about it.
> >
> >If you want to copy these files to workstations in a login script, you
> >want to check for an existing WININIT.INI so you don't step on an
> >install's finish.
> >
> >This works only with Win9X.  I'm not aware of anything like this for
> >NT/Win2K.  They seem to require a program to call an API function.
> >
> >I hope this is helpful.  I have at times used WININIT.BAK to see
> >what the last install program replaced so I could roll back changes.
> >
> >
> >David Calhoun
> >Mary Van Engelen wrote:
> > >
> > > What I'm trying to do is rename the dll to bak. I don't want to push down a
> > > beta dll.  I created a simple bat file to rename the dll, as follows:
> > >       ren c:\windows\system\nwws2nds.dll c:\windows\system\nwws2nds.bak
> > >
> > > I'm trying to figure out how to run that bat file using NAL or, more to the
> > > point, to push down a renaming of the file. I've tried running the bat
> > > through the login script, but the dll is already loaded by the time the bat
> > > file runs and the same thing is happening when I push it down using NAL.
> > >
> > > Is there another approach?
> > >
> > > Mary
> > >
> > > At 12/13/2001 08:29 AM, you wrote:
> > > >Just make the NAL object to copy in the new file, mark distribution as
> > > >'reboot if needed' (which it will), and it should take care of the rest.
> > > >
> > > > >>> maryve1 at starpower.net 12/13/01 07:32AM >>>
> > > >Can the reboot to DOS be done using NAL?  If so, how?
> > > >
> > > >Thanx,
> > > >Mary
> > > >
> > > >At 12/11/01 09:52 AM, Ray Diers wrote:
> > > > >The file is one of those system files that is in use as soon as you
> > start
> > > > >Windows.  We reboot into DOS to make the change.
> > > > >
> > > > >Ray
> > > > >
> > > > > >>> maryve1 at starpower.net 12/10/01 05:22PM >>>
> > > > >I tried several times to rename this DLL on my Win98 workstation and
> > I got
> >
> > > > >a sharing violation.  I even tried it after a reboot.  I was hoping
> > I would
> > > > >be able to apply the fix using NAL,  Is it possible?
> > > > >
> > > > >At 12/10/01 11:23 AM, you wrote:
> > > > > >Thanks for the response.  I couldn't agree more about beta
> > software.  I'll
> > > > > >add beta only as a last resort.
> > > > > >
> > > > > >Betty
> > > > > >
> > > > > > >>> RADiers at wausaucoated.com 12/10/01 10:57AM >>>
> > > > > >We just renamed the file, and noticed the immediate improvement.  It's
> > > > > >hard enough getting release software working right.  Just don't
> > want to
> > > > > >add beta software to the mix.
> > > > > >
> > > > > >I just noticed that the latest NetWare client for NT/2000 (4.81) has a
> > > > > >much newer  NWWS2NDS.DLL file. May of 2001 vers Jan of 2001.
> > > > > >
> > > > > >Ray
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > >>> tcwatsb at tcc.vccs.edu 12/10/01 09:44AM >>>
> > > > > >I found the TID.  What specifically was done to the
> > workstations?  Did you
> > > > > >apply the FTF mentioned, or simply rename NWWS2NDS.DLL as a
> > > > > >workaround?  I've just renamed this file on my Win98 workstation,
> > and have
> > > > > >noticed a much quicker response time.
> > > > > >
> > > > > >Thanks.
> > > > > >Betty
> > > > > >
> > > > > > >>> EMAIL at co.pierce.wa.us 12/07/01 05:55PM >>>
> > > > > >It's not a GroupWise specific TID, so if you have narrowed your search
> > > > > >down by checking "GroupWare" on the knowledgebase search screen,
> > you have
> > > > > >to remove that check mark.
> > > > > >
> > > > > >Been there, done that.
> > > > > >
> > > > > >Rochelle A. Adsitt
> > > > > >Pierce County Information Services
> > > > > >
> > > > > > >>> tcwatsb at tcc.vccs.edu 12/7/2001 2:36:51 pm >>>
> > > > > >I came up empty on a search for this TID#.
> > > > > >
> > > > > > >>> RADiers at wausaucoated.com 12/07/01 04:59PM >>>
> > > > > >Have a look at Novell TID # 10057998.  We applied the TID and
> > utilization
> > > > > >dropped immediately.  Client workstations noticed an improvement in
> > > > > >response.  If we rebuild a PC and forget to make this change
> > utilization
> > > > > >jumps up again.
> > > > > >
> > > > > >Ray
> >



More information about the ngw mailing list