SCOUG-HELP Mailing List Archives

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

Date:	Sat, 1 Apr 2006 12:55:59 PST8
From:	sshapiro@ucsd.edu (Sandy Shapiro)
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: boot problems

In , on 04/01/06
at 12:48 PM, "Steven Levine" said:

>In <200604011843.k31IhYCl193080@pimout7-ext.prodigy.net>, on 04/01/06
> at 10:43 AM, sshapiro@ucsd.edu (Sandy Shapiro) said:

>>>Sounds like a memory error, I would start swapping memory chips.

>>That's a good thought.

>>Memtest-86 shows no errors on two passes.

>>I swapped the two RAM modules, and on the last reboot I got an error
>>message: Sys3175 -- Tcpstart access violation at SOMU.DLL.

>Can you live with running with just one chip for a day or so? This might
>allow you to determine if the problem is one of the chips or if it's a MB
>issue.

>Another thing to try is to drop the BIOS back to the the low performance
>settings.

The error is not predictable -- I could easily go a day or two without
getting one.

I can certainly change the BIOS in the meantime. And I am not adverse to
getting new RAM chips and putting these into another computer.

I am glad this does not seem to point to an OS/2 Warp problem. I worry
that after all these years of use it might be getting unstable. I do run
Unimaint regularly. (Checkini and Cleanini just won't work.)

Thanks,
Sandy

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

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
"postmaster@scoug.com".

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

Return to [ 01 | April | 2006 ]

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.