Megalextoria
Retro computing and gaming, sci-fi books, tv and movies and other geeky stuff.

Home » Archive » net.micro.ti » fried TI portable PC
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Switch to threaded view of this topic Create a new topic Submit Reply
fried TI portable PC [message #128024] Mon, 05 August 1985 22:17 Go to next message
lindley is currently offline  lindley
Messages: 22
Registered: September 2013
Karma: 0
Junior Member
Article-I.D.: ut-ngp.2207
Posted: Mon Aug  5 22:17:23 1985
Date-Received: Wed, 7-Aug-85 03:22:05 EDT
Distribution: net
Organization: U.Texas Physics Department; Austin, Texas
Lines: 23

I have two TI Proffesional Portable Computers under my care, and both
seem to be victims of power surges.  One of them seems completely dead,
at least as far as the system board; the power supply and crt seem ok.

The second one I'm a little more hopefull about getting repaired soon.
It attempts to boot when you turn it on, but displays the message:
'SYSTEM ERROR: 0005', and then locks up.  As a side note, the problem
started when I left it on overnight so a program could finish running.
When I came in the next day, the screen had the message 'SYSTEM ERROR
1041 SYSTEM HALTED', or something like that.

It's my suspicion that 0005 is the number of some unit in the machine,
hopefully one that can be replaced.  But we don't have the technical
manual for this pc, nor is it likely we can get one very soon.  So, is
there anyone out there who can tell me what these two error messages
might mean?  Please respond by mail, as I don't reguraly read this
group.
-- 

~~ John L. Templer,  University of Texas at Austin
~~ {allegra,gatech,seismo!ut-sally,vortex}!ut-ngp!lindley

      You can't talk in your sleep if you can't sleep.
Re: fried TI portable PC [message #128027 is a reply to message #128024] Tue, 13 August 1985 17:38 Go to previous message
haddock is currently offline  haddock
Messages: 21
Registered: July 2013
Karma: 0
Junior Member
Article-I.D.: waltz.31900009
Posted: Tue Aug 13 17:38:00 1985
Date-Received: Sun, 18-Aug-85 04:37:37 EDT
References: <2207@ut-ngp.UTEXAS>
Lines: 35
Nf-ID: #R:ut-ngp.UTEXAS:-220700:waltz:31900009:000:1495
Nf-From: waltz!haddock    Aug 13 16:38:00 1985


	/* ---------- "fried TI portable PC" ---------- */
			      [edited]
	It attempts to boot when you turn it on, but displays the message:
	'SYSTEM ERROR: 0005', and then locks up.  As a side note, the problem
	started when I left it on overnight so a program could finish running.
	When I came in the next day, the screen had the message 'SYSTEM ERROR
	1041 SYSTEM HALTED', or something like that.

	It's my suspicion that 0005 is the number of some unit in the machine,
	hopefully one that can be replaced.  But we don't have the technical
	reference manual.

Nope, no such luck.  The error message numbers are basically indicators
of what area within the TIP[P]C could be causing the problems and will
not ALWAYS point to the real culprit of the problem.   Also, I don't believe
that the Tech. Ref. Manual has all (or any) of the system error codes.

The 0005 is an indication that there is a problem with the system
(mother) board RAM when the system is booted.

The 1041 is telling you about a RAM parity error that was detected
during normal operation.

Insufficient cooling could be your problem also.

================================================================
                           _____
        -Rusty-         |\/   o \    o
                        |   (  -<  O o     Where's the fish?
                        |/\__V__/

ARPA:   Haddock%TI-CSL.csnet@CSNet-Relay.arpa   or  Rusty@Maryland
CSNet:  Haddock@TI-CSL
USENET: {ut-sally, convex!smu, texsun, rice} ! waltz ! haddock
  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: Free Toronto TURING PC Compiler on Floppies
Next Topic: TIPC memory price quote
Goto Forum:
  

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Thu Apr 25 11:19:57 EDT 2024

Total time taken to generate the page: 0.08389 seconds