home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!paladin.american.edu!gatech!destroyer!cs.ubc.ca!unixg.ubc.ca!ochealth
- From: ochealth@unixg.ubc.ca (ochealth)
- Newsgroups: comp.os.os2.misc
- Subject: Re: cause of growing ini problem - SOLVED!!
- Date: 24 Dec 1992 09:30:03 GMT
- Organization: University of British Columbia, Vancouver, B.C., Canada
- Lines: 40
- Message-ID: <1hbvurINNfh0@iskut.ucs.ubc.ca>
- References: <92358.223504COP80196@UCF1VM.BITNET>
- NNTP-Posting-Host: unixg.ubc.ca
-
- In article <92358.223504COP80196@UCF1VM.BITNET> Bill Laird <COP80196@UCF1VM.BITNET> writes:
- :I have been able to (finally) recreate situations that cause the ini
- :files to fill up with garbage. I hope IBM is listening here.
- :
- :To recreate the problem:
- : 1) Make a copy of a program object that is stored in a subdirectory
- : to the desktop. I was using a 200 K .exe in this case
- :
- : 2) Drag and drop the the newly copied object on the desktop to
- : the shredder and delete.
- :
- : 3) os2sys.ini file will grow (34 K in this case)
- :
- : Sounds like a WPS problem to me...
-
- It definitely is a WPS. Your method is interesting, but seems consistent
- with the way I got os2sys.ini to grow (same size increment, I think)
-
- I can get os2sys.ini to grow if I open up the Settings menu tab on an object
- (but only if Settings... hasn't been opened for that object before).
-
- Since you used WPS to drag/copy an object, WPS must automatically look
- at or copy the settings info, causing the same growth as opening
- up the settings menu manually.
-
- :
- :
- :Bill Laird -------------------------------------
- :University of Central Florida ║" 640 K is all the memory you will ║
- :cop80196@ucf1vm.cc.ucf.edu ║ ever need"... Bill Gates ║
- :ci$ : 71753,130 -------------------------------------
- :
- :
-
-
- --
- ______________________________________________________________________________
- ochealth@unixg.ubc.ca
-
-
-