SCOUG-HELP Mailing List Archives

<< Previous Message << >> Next Message >>

Date:	Wed, 31 Jul 2002 12:31:49 PST7
From:	"J. R. Fox" <jr_fox@pacbell.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: Light @ the end of the Trap E tunnel (?)

Content Type: text/plain

=====================================================
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.
=====================================================

Steven replied to me:

> Starting here is a good idea. Unfortunately, it appears the answer may be
> elsewhere. :-)

Or maybe not, after all. (Don't want to ruin the ending, though.)

> >someone like Scott G. or Irv S. -- in another context -- write something
> >like "If CSLIM=ffffffff, then the whole trap screen is probably useless."
>
> Not at all. It just means the the trap did not occur within a 16-bit
> driver. The cslim is a handy way of determining which driver trapped,
> when it works.
>
> When cslim is all ones, you have to use different methods to determine
> which code is trapping.
>
> These numbers are the least useful for trap analysis. cs:eip and ss:esp
> are much more important. The numbers are your reporting are for where the
> kernel halted and are essentially generic. The kernel halts at the same
> place for a wide variety of traps.

I'll make a note of that.

> Get:
>
> http://home.earthlink.net/~steve53/os2diags/DumpTrapScreen.zip
>
> and adjust config.sys as directed. Then use the provided tool extract the
> trap screens for you. Saves a lot of writing.

O.K., will do. I hope this is not one of those that writes a GIGANTIC file, and you have to take
preventive measures to keep it from overwriting a partition . . . . Some messages on the
newsgroups mentioned a method that writes a dump to one or two diskettes.

> >I have the last version, 2.52, and think I picked up that driver. I'll
> >double-check on the driver.
>
> I'm pretty sure, you can't even boot without the beta driver,

Actually, you can and I did, for a couple weeks. How stable it all was, we may clearly have reason
to doubt.

In this Trap E culprit sweepstakes, we may (at last) have a Winnah ! As luck would have it, I had
downloaded that beta driver shortly after it was released, but had lost track of whether I ever
actually plugged it in. Evidently not. Makes sense, because I never took W4 beyond FP-9, and WSEB
never did have C-A-D installed, so I never really needed this. eCS has only had C-A-D Cmdr.
installed for perhaps 10 days. A couple other things got installed on the same day, and I
_suspected_ that the troubles dated from then. The beta KBDBASE.SYS driver replacement for C-A-D
must have been overlooked.

> but since I don't run CAD Cmdr, I'm not entirely sure how the failure shows up.

I think we can make a wild guess. ;-) I'm still not clear on how a kbd driver springs the Trap
when I click on a DOS or eCS session *with the Mouse*, but maybe it's just a few paces down the
road, hardware-wise.

Anyway, I substituted in the beta KBDBASE.SYS yesterday, and have not seen a Trap E since in eCS,
despite repeatedly trying to trigger one. I'm not going to celebrate just yet, though, as many of
the Trap E newsgroup respondents mentioned them coming back a while later, after a seeming cure.

> Uninstall the SDD drivers, using the supplied tool. This should
> revert you to VGAGRADD which is the default for MCP/eCS installs. Test
> with this. If it still traps, run \os2\setvga.cmd. This should revert to
> pure VGA. Test with this. If it still traps, I would do a Selective
> Install of DOS VDM support and reapply the MCP2 FP.

SDD is long gone at this point, and I assume the rest is no longer necessary.

> PC only replaced the keyboard driver. It overrode doscalls.dll.
>
> >We're talking about KBDBASE.SYS here, aren't we ?

> Yes. That's the base keyboard driver that PC replaces. I've always
> assumed the CAD does the same. If that's not the case, you'll have to
> supply me with the details.

I thought they were more different than that, but maybe not. I sort of miss WatchCat, and was fully
prepared to switch back to that instead, had this situation not turned the corner.

> >whether or not C-A-D is supposed to be compatible with eCS
>
> Commenting out the CAD entries will not restore the IBM driver since
> KBDBASE.SYS does not have a CONFIG.SYS entry.

A very good reason I was unable to find one.

btw, your instructions for redoing the Mozilla install worked perfectly. I replaced 1.1a with the
just released 1.1b. Not really being a Mozilla user yet, I decided to keep rolling the dice.

Now I should be able to get back to building up this eCS partition. Thanks for all your help.

Jordan

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

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".

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

Return to [ 31 | July | 2002 ]

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.