Error Message 00192
February 24, 2007 3:53 AM Subscribe
My IBM Thinkpad 600 (Pentium 2) has crashed. Whenever I start it up, I get error message 00192. I'd like to avoid going to a technician if possible. What do I do now?
Obviously, I've already tried google-ing this, but the results I got were either inconsistent or too technical for me to understand.
This computer:
- runs Windows XP
- is around 8 years old (approximately)
- hard drive is brand-spanking-new
- runs pentium 2, 266 MHz
the different results i got were that it could be the fan, the battery, or another complicated one (see below). on a different site i checked, a user who had gotten the same error message mentioned that he took out his battery and the error message stayed, so the problem probably wasn't the battery.
the third option i got for what was wrong was as follows:
snacc 00192: ERROR (0xC0): ACC card id number is out of expected range. Minimum possible id number: < #>. Maximum possible id number: < #>.
Explanation:
The SNA/ACC is hard coded to expect the card number range to be between zero to 63, inclusively.
Action:
Execute the xsnapadmin utility to make sure the configured card number is not out of the required range. Fix the card id and restart the SNA/ACC link.
Help!
Obviously, I've already tried google-ing this, but the results I got were either inconsistent or too technical for me to understand.
This computer:
- runs Windows XP
- is around 8 years old (approximately)
- hard drive is brand-spanking-new
- runs pentium 2, 266 MHz
the different results i got were that it could be the fan, the battery, or another complicated one (see below). on a different site i checked, a user who had gotten the same error message mentioned that he took out his battery and the error message stayed, so the problem probably wasn't the battery.
the third option i got for what was wrong was as follows:
snacc 00192: ERROR (0xC0): ACC card id number is out of expected range. Minimum possible id number: < #>. Maximum possible id number: < #>.
Explanation:
The SNA/ACC is hard coded to expect the card number range to be between zero to 63, inclusively.
Action:
Execute the xsnapadmin utility to make sure the configured card number is not out of the required range. Fix the card id and restart the SNA/ACC link.
Help!
It's been awhile, but I think that particular code is telling you the cmos battery is bad.
posted by pjern at 4:48 AM on February 24, 2007
posted by pjern at 4:48 AM on February 24, 2007
First, the SNA/xsnapadmin stuff you found is a total red herring. It has nothing to do with your ThinkPad. Googling for "FRU 3810" will be more fruitful. FRU means Field Replaceable Unit and is IBM jargon for a part.
If you can't figure it out that way, ask on the ThinkPad mailing list.
posted by grouse at 4:53 AM on February 24, 2007
If you can't figure it out that way, ask on the ThinkPad mailing list.
posted by grouse at 4:53 AM on February 24, 2007
Best answer: You need to go here.
http://www-307.ibm.com/pc/support/site.wss/product.do?brandind=10&familyind=50083&operatingsystemind=49979&template=%2Fproductselection%2Flandingpages%2FonlinePublicationsLandingPage.vm&validate=true
It's the link for IBM Thinkpad 600s. Check the back of the unit to see if its a 600E or 600X. In the back of the .pdf user manual is a list of all error codes.
PS - These machines function much better when converted to Linux (choose your distro). They are the last of a quality generation.
posted by Funmonkey1 at 5:09 AM on February 24, 2007
http://www-307.ibm.com/pc/support/site.wss/product.do?brandind=10&familyind=50083&operatingsystemind=49979&template=%2Fproductselection%2Flandingpages%2FonlinePublicationsLandingPage.vm&validate=true
It's the link for IBM Thinkpad 600s. Check the back of the unit to see if its a 600E or 600X. In the back of the .pdf user manual is a list of all error codes.
PS - These machines function much better when converted to Linux (choose your distro). They are the last of a quality generation.
posted by Funmonkey1 at 5:09 AM on February 24, 2007
Response by poster: thanks! the problem was indeed the battery; i took it out and the computer works great, except now i can't disconnect it from the power cable.
as well, i'm going to install linux on it. i'm thinking ubuntu just because it's the only kind i'm familiar with, unless anyone has a better suggestion?
thansk for the help!
posted by alon at 6:00 AM on February 24, 2007
as well, i'm going to install linux on it. i'm thinking ubuntu just because it's the only kind i'm familiar with, unless anyone has a better suggestion?
thansk for the help!
posted by alon at 6:00 AM on February 24, 2007
Just to be clear, the CMOS battery referred to in solopsist's answer isn't the same thing as the laptop battery that you run your computer from. It's a tiny internal battery that you'd have to crack the case to replace.
It sounds as though the laptop battery and not the CMOS battery is what went bad (no surprise: an 5+ year old laptop battery is not going to work well), but in case you have further problems that are in fact related to the CMOS battery it'd be a good idea to know the distinction.
As to Linux distribution choice, I'd suggest considering xubuntu for your slow, elderly hardware. It's still Ubuntu so it should work well if you're familiar with Debian-like distributions, but is more lightweight than the GNOME- or KDE-based derivatives.
If by "familiar with" you don't actually mean you know Ubuntu itself but that you know GNOME as an end user, well, then my advice doesn't apply.
posted by majick at 7:10 AM on February 24, 2007
It sounds as though the laptop battery and not the CMOS battery is what went bad (no surprise: an 5+ year old laptop battery is not going to work well), but in case you have further problems that are in fact related to the CMOS battery it'd be a good idea to know the distinction.
As to Linux distribution choice, I'd suggest considering xubuntu for your slow, elderly hardware. It's still Ubuntu so it should work well if you're familiar with Debian-like distributions, but is more lightweight than the GNOME- or KDE-based derivatives.
If by "familiar with" you don't actually mean you know Ubuntu itself but that you know GNOME as an end user, well, then my advice doesn't apply.
posted by majick at 7:10 AM on February 24, 2007
Second the xubuntu recommendation. It's snappy once you load up. It'll make your P2 feel like it's running DOS again (except, prettier interface). Just super-fast.
posted by Civil_Disobedient at 3:57 PM on February 24, 2007
posted by Civil_Disobedient at 3:57 PM on February 24, 2007
How funny, I have four of these at work, three of which were 'dead'. I was able to resurrect two of them by installing ubuntu. Yesterday.
The other one is suffering from a very similar problem described here, hopefully Funmonkey1's link will let me get that last one up and running as well.
posted by quin at 5:22 PM on February 24, 2007
The other one is suffering from a very similar problem described here, hopefully Funmonkey1's link will let me get that last one up and running as well.
posted by quin at 5:22 PM on February 24, 2007
Thirding Xubuntu. I put it onto an old 600MHz Celeron, and it's as responsive as my Dual G5 Mac or my office XP P4. It takes a while to open programs and windows sometimes (you don't forget what machine you're on, let's not exaggerate too much), but once things open and load, it feels snappy enough. Stock Ubuntu/Gnome on it was unbearable.
posted by Kadin2048 at 1:31 AM on February 25, 2007
posted by Kadin2048 at 1:31 AM on February 25, 2007
« Older How can I find counseling with no money to spare? | Gift for an 85 yeard old Freemason Newer »
This thread is closed to new comments.
I just ran a SystemBoard test, and after that i got an x by the SystemBoard icon, and beneath it the cryptic message:
DEV 001
ERR 96
FRU 3810
posted by alon at 4:02 AM on February 24, 2007