From: shurr@cbnews.cb.att.com (larry.a.shurr)
Subject: Re: OS2SYS.ini file size. Possible Cause(s) !!! ??
Organization: AT&T Bell Laboratories, Columbus, OH
Date: Fri, 20 Nov 1992 16:10:33 GMT
Keywords: OS2SYS.INI file size growing

In article <Bxz783.2Jn@hfglobe.intel.com> bharris@hfglobe.intel.com (Bennie Harris) writes:
}
}My findings are still PRELIMINARY, but last night [he made changes
}to his CONFIG.SYS which appear to have stopped the growth of OS2SYS.INI].

}I made the following changes to my config.sys file.

}1. Moved the SET VIO_SVGA=DEVICE(BVHVGA,BVHSVGA) from the bottom
}   of my config.sys to after the SET VIO_VGA=DEVICE(BVHVGA,BVHSVGA).
}   This statement (SET VIO_SVGA=) was placed in my config.sys during
}   the SP installation.
}   These two statements now appear as :
}                 .
}                 .
}                 .
}
}   SET VIDEO_DEVICES=VIO_SVGA
}   SET VIO_VGA=DEVICE(BVHVGA,BVHSVGA)
}   SET VIO_SVGA=DEVICE(BVHVGA,BVHSVGA)

I made this change, too, though I did it because I thought it
"looked" better.  All I really meant to do was keep my local 
settings at the end of CONFIG.SYS.

}2. MOVED THE DEVINFO=SCR,VGA,C:\OS2\VIOTBL.DCP from the bottom of
}   my config.sys file to after the DEVICE=KBD,US,C:\OS2\KEYBOARD.DCP
}   statement. This line was also put into my config.sys during the
}   SP installation.
}   The  statements now appear as :
}                 .
}                 .
}                 .
}
}   DEVINFO=KBD,US,C:\OS2\KEYBOARD.DCP
}   DEVINFO=SCR,VGA,C:\OS2\VIOTBL.DCP 

I don't recall seeing this setting.  It may be in my CONFIG.SYS,
but it wasn't at the end of CONFIG.SYS either before or after I
installed the SP so I wouldn't have paid it much attention.

}3. REM'ed out the CALL=C:\OS2\CME.EXE /C MKDIR K:\TEMP statement
}   I put in to create a temp directory on my ramdrive.
}   This change may seem minor but I want to list it anyway.

I've never done this -- i.e., I never put anything like it in,
so I've never taken it out, either.

}4. Removed (REM'ed out) 4OS2.exe and put CMD.exe back in
}   the SET OS2_SHELL= and SET COMSPEC= statements.
}   I was using 4OS2 before the SP installation and experienced
}   no problems with it. In fact like it so much that I even sent 
}   in my registration for 4OS2 and 4DOS.

}   I also converted my command prompts back to use CMD.EXE with
}   using the * (default setting) for the program path\name settings.

I'm using 4DOS and 4OS2 and I have not converted back to CMD.  I 
agree that they are really good and I am registering.

}[His OS2SYS.INI doesn't grow in circumstances where it did previously].

As far as I can tell, I've never had any problems with the Incredible
Expanding .INI File.  My OS2SYS.INI file is at about 55K right now --
I don't know if that represents any abnormal growth, though it is 
certainly not the MegaByte Monstor that others are reporting.

}Although the results seen are not conclusive I want to share what I
}have seen so far with anyone who is having problems with their
}os2sys.ini file growing and find something common between our setups.
}I will be undoing the changes one at a time I made to pinpoint what  
}is responsible for the problem.

Good luck,
Larry
-- 
Larry A. Shurr (las@cbnmva.att.com or att!cbnmva!las) speaking only for myself.
EOR (end-of-ramble)
Newsgroups: comp.os.os2.misc