THE WELCH COMPANY
440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700
S U M M A R Y
DIARY: January 9, 1996 09:06 AM Tuesday;
Rod Welch
Created new Os2 Ini file to fix desktop crash.
1...Summary/Objective
2...Frequent Desktop Crashes - Memory leaks??
3...Corrupt Ini
4...Fixing Ini
5...Memory Leaks
6...Newsreader/2
..............
Click here to comment!
CONTACTS
0201 - IBM OS/2 407 443 2000
020101 - Mr. Jesus Rodriguez
020102 - Dep: 6F8A (ZIP 1024) DOS App "Debug" Specialist =407 443 0452
020103 - Technical Support =800 992 4777 fax 407 443 6940 407 994 5544
SUBJECTS
CPU #8, 586, Software, OS2, Installation
OS2 Crashed, White Desktop
White, Icons at top of screen
32115x,442 number assigned to 0387x,psh oa
Restoring After Crash
OS2 Crashed, Desktop Folders will not open
Memory Management, OS2 Desktop Fails
Why Operating Systems Fail
Memory Management, RAM Leaks
Desktop, Make.ini
1312 - ..
1313 - Summary/Objective
1314 -
131401 - Followed up work at ref SDS 17 line 55, ref SDS 16 line 50,
131402 - line 32, ref SDS 14 line 30.
131403 -
131404 - The new ini file created today does not seem to correct the problem;
131405 - was unable to obtain utilities or information from internet. Submitted
131406 - question on obtaining ini utilities.
131407 -
131408 -
1315 -
1316 -
1317 - Progress
1318 -
131801 - Frequent Desktop Crashes - Memory leaks??
131802 -
131803 - We have continued and more frequent occurrances of desktop failures
131804 - the past two months. Fortunately we have been able to recover using
131805 - the Alt F1 routine to restore the desktop. Today I am going to try
131806 - re-building the os2.ini file because it may be corrupt, per
131807 - understandings from an article in the 960103 issue of Microtimes on
131808 - page 74 entitled: Solutions. It says in the last paragraph:
131809 -
131810 - It is also a good idea to use a utility such as UniMaint to clean
131811 - and fix the .INI files on a regular basis (to avoid restores) or
131812 - prior to backups (to avoid backing up .INI files cluttered with
131813 - obsolete information). N
131814 -
131815 - What is unclear is whether building a new ini file using the Os2
131816 - method will accomplish the same thing. It is also unclear whether
131817 - re-building the ini files will improve the problem we are having of
131818 - constant desktop crashes. I have been unable to get information from
131819 - the Internet or from IBM on the cause of the desktop crashes, for
131820 - example whether they are caused by memory leaks reported at ref SDS 16
131821 - line 83; except, a report received via internet indicated that one
131822 - type of memory leak in os2 may be related to using DOS applications
131823 - with custom icons, which we are doing on CPU #8, ref SDS 17 line 169.
131824 -
131825 -
131826 - Corrupt Ini
131827 -
131828 - Possibly a slightly corrupt ini file may accelerate the time period
131829 - for memory leaks to impact the desktop. However, there is no direct
131830 - evidence for this conclusion, nor support from IBM or any published
131831 - material I have encountered.
131832 -
131833 - Instructions for re-building the os2 ini files are at ref SDS 1 line
131834 - 113.
131835 -
131836 -
131837 -
1319 -
1320 -
1321 - 1004 called Junaid at IBM 407 443 6557
1322 -
132201 - I called Junaid following up our discussion last year at ref SDS 7
132202 - line 76.
132203 -
132204 - I related the continuous problem we are having with desktop crashes.
132205 - Junaid repeated his position that he has not encountered this problem
132206 - from any other customer or any other source, ref SDS 7 line 76.
132207 -
132208 - [See follow up on evaluation by IBM, ref SDS 19 line 67.]
132209 -
132210 - Fixing Ini
132211 -
132212 - He feels the problem may be a corrupt ini file; seemed to feel the
132213 - cause is less likely to be memory leaks reported at ref SDS 17 line
132214 - 169. Junaid indicated the some DOS applications can corrupt the os2
132215 - ini files. The DOS app we use the most is Medit, and it has not
132216 - corrupted the ini files in os2 on CPU #7 which is still using os2 2.1.
132217 - Does not seem to have done this on CPU #3 which is using os2 3.0,
132218 - although in both cases, these systems are used very much.
132219 -
132220 -
132221 - Memory Leaks
132222 -
132223 - Junaid said that rebuilding the ini files with makini.rc may or may
132224 - not remove any corruption in the ini files. He said various
132225 - applications can cause corruption in the ini files. He seeme to say a
132226 - lot of things about memory leaks, but generally feels these do not
132227 - cause our desktop problem.
132228 -
132229 - Junaid said we can get utilities from the IBM BBS at:
132230 -
132231 - 919 517 0001
132232 -
132233 - ...or access it via Internet at:
132234 -
132235 - http://pccbbs.raleigh.ibm.com
132236 -
132237 - The utilities he uses to clean up his ini files are:
132238 -
132239 - checkini
132240 - inimaint
132241 -
132242 - Another Web site he suggests is:
132243 -
132244 - ftp://ps.boulder.ibm.com/ps
132245 -
132246 - Tried this and got message the http site was closed. Could not
132247 - find the files at the ftp site.
132248 -
132249 -
132250 - Newsreader/2
132251 -
132252 - I asked about locating Internet user groups that deal with the Os2
132253 - program. He suggested accessing:
132254 -
132255 - Newsgroups
132256 -
132257 - ...and then doing a search for os2.
132258 -
132259 - I was finally able to figure out that Junaid was really trying to say
132260 - we should try the Newsreader/2 program. I found a topic under alt
132261 - something os2, and it had a lot of discussion about os2 and W95. I
132262 - put a question about solving the desktop crash and memory leak issue.
132263 - No one ever responded.
132264 -
132265 -
132266 -
132267 -
132268 -
1323 -
1324 -
1325 - 1248 OS2 INI Files
1326 -
132601 - Tried to use the instructions at ref SDS 1 line 119. This caused the
132602 - desktop to come up in VGA mode. The Matrox video configuration was
132603 - lost. I have to install it again.
132604 -
132605 - Got instructions at ref SDS 4 line 82. However, actually had to use
132606 - the instructions to create the Matrox drivers using an os2 prompt at,
132607 - ref SDS 4 line 72.
132608 -
132609 -
132610 -
132611 -
1327 -
1328 -
1329 - 2223 Submitted Query
1330 -
133001 - Logged onto the Web and then IBM Home page.
133002 -
133003 - Submitted question to IBM Webmaster seeking site to download the os2
133004 - ini file maintenance programs.
133005 -
133006 - [See follow up at ref SDS 18 line 79.]
133007 -
133008 -
133009 -
1331 -
Distribution. . . . See "CONTACTS"