SCOUG-HELP Mailing List Archives

Return to [ 21 | August | 2000 ]

<< Previous Message <<


Date: Mon, 21 Aug 2000 22:48:51 PDT
From: "Steven Levine" <steve53@earthlink.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: TRAP0003

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

In <200008220516.WAA01598@snipe.prod.itd.earthlink.net>, on 08/21/00
at 10:16 PM, "Gary Granat" said:

>Nope. Get the same TRAP0003.

OK. Sure sounds like you something changed in the Thinkpad configuration.
Alt-F1 boots from \os2\boot\config.x which, since most folks don't know
about arcinst, is very different from config.sys.

>>>As far as the xWorkplace stuff is concerned, I'm tending to discount it

OK. I've never run it, so I'm not aware of how it installs.

>Good idea, although I'm not quite sure where to start the process. Time
>wise, this is a daunting task since I have to boot from the utility
>diskette set each time I do a restart (a 2-3 minute process). I did some

Yes, it is. That's why I always arrange to have one or more of my data
partitions bootable by BOOTOS2. It's about a 3MB footprint and well worth
it at times like this. Some folks dedicate an entire partition to a
maintenace boot. I can see not good reason for this.

To speed up the process in your case, use the divide and conquer
technique. REM out everything you can live without. Assuming the 1st
reboot does not trap, add 1/2 back each reboot. Before each edit, save a
copy of config.sys. If you trap, you can restore config.sys and un-REM
the other half. When REM-ing out statements mark them so you can tell
them from the existing REM statements. I use lower case rem for the
temporaries and upper case REM for the existing REM's.

>investigation today, comparing the dates on files between the two
>systems, and the results are bizarre. As best I can tell, I have a mix
>of Fixpak 11 and Fixpak 12 dates in D:\OS2\BOOT. I'm tempted to copy

This is probably not the case. Remember that FP11 was the last FP that
included all the device drivers. FP12 contains a few drivers, but rest
are in Device Driver FP01. Why do you think this could be the case?

>files between the two systems, but I'm not confident that I'm going to do
>more than to just confuse the issue. Steve Schiffman suggested that I do
>a reinstall over the top of the existing system (preserves my apps, with
>any kind of luck) and then reapply Fixpak 12. That is beginning to look
>more attractive :-)

It might preserve your desktop somewhat, but you wll still have a lot of
work to do restoring the private parts of the .ini setting.

I'd take a real close look at the drivers. These are the most likely
sources of your problems.

>Speaking of Fixpaks, the June SCOUG CD has 12, 13, and 14 on it. I have
>been well satisfied with the stability of Fixpak 12. Any information
>concerning stability of 13 and 14? If I'm going to go the reinstall
>route, I have the option of applying a later Fixpak.

FP14 has long term advantages because it changes over to the WSeB
uniprocessor kernel. However, this is a big change and it's still shaking
out. Lot's of folks are running FP14 without problems. Others have
problems.

I'll be updating my boxes to FP14 as soon as time permits.

Steven

--
----------------------------------------------------------------
"Steven Levine" MR2/ICE 2.19zk #10183 Warp4/FP11
www.scoug.com irc.webbnet.org #scoug (Wed 7pm PST)
----------------------------------------------------------------

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================


<< Previous Message <<

Return to [ 21 | August | 2000 ]