From: bharris@hfglobe.intel.com (Bennie Harris)
Subject: OS2SYS.ini file size. Possible Cause(s) !!! ??
Summary: OS2SYS.INI growing file size. Possible cause.
Keywords: OS2SYS.INI file size growing
Organization: Intel Corporation
Date: Thu, 19 Nov 1992 18:26:26 GMT


My findings are still PRELIMINARY, but last night after making
a few changes to my config.sys, my os2sys.ini file size did not
change. The findings are not conclusive since I have to go
back and redo the changes one at a time to determine what
condition(s) are responsible for causing the os2sys.ini file 
to grow.

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)

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 


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.

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.


My os2sys.ini did not grow even after I used my modem to dial-in,
transfer fax'es, change some notebook settings, edit files, 
format floppies and dualboot to native DOS. My machine was quiet
busy last night compared to previous nights where I have seen my 
os2sys.ini get bigger.

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.

I will post my what I find after I (hopefully) determine what is
causing the os2sys.ini file to grow.

I would like to hear from anyone else who has success with implementing
the above changes to their config.sys. There may be a common link with
our setup. I suggest that you make a backup copy of your config.sys 
before making any edits.


My system is a clone 386/25 with 8meg ram, 64k cache and AMI BIOS.
I'am using the standard VGA driver (640x480x16 Tseng) installed during the
installation. Video card is Orchid Pro IIs. Both drives are 213 Conner 
with FAT partitions.

-- Bennie Harris
Newsgroups: comp.os.os2.misc