8603 pointing device error

Модератор: Stelt

Вернуться в Компьютеры и периферия

Кто сейчас на форуме

Сейчас этот форум просматривают: нет зарегистрированных пользователей и гости: 4

How To I Fix The 8603-Pointing Device Error

We have collected for you the most relevant information on How To I Fix The 8603-Pointing Device Error, as well as possible solutions to this problem. Take a look at the links provided and find the solution that works. Other people have encountered How To I Fix The 8603-Pointing Device Error before you, so use the ready-made solutions.

8603 pointing device error + other misc problems

https://discussions.virtualdr.com/showthread.php?161848-8603-pointing-device-error-other-misc-problems

Apr 20, 2004 · Ok, I went over to this person’s house to check the computer out. It had viruses. 7 viruses to be exact. I tried deleting all the registry keys, installing and running Norton but everything I undone the virii put back even after Norton wiped out 52 infected files. It was the adware virii. Anyways, I bring the computer back to my house to take care of this problem, I plug it in boot it up and .

301 keyboard error,8603 pointing device error? Mend .

https://howtomendit.com/answers.php?id=112151

301 keyboard error,8603 pointing device error? my computer was working as normal.i shut it and when i started it after a few minutes,a message appeared in bios screen:post setup errors-301 keyboard errors-8603 pointing device errors my keyboard then stopped working and i am stuck to the screen,i tried 2 other keyboards but to no use

8603. PS/2 Pointing device error or not connected Tom’s .

https://forums.tomshardware.com/threads/8603-ps-2-pointing-device-error-or-not-connected.1073203/

Apr 01, 2005 · Archived from groups: microsoft.public.windowsxp.hardware (More info?) When I boot XP pro, I get this error message just before the XP start up screen.

Post Startup Error — 8603 Pointing Device Error. How can I .

https://answers.yahoo.com/question/index?qid=20070909103023AApDGxc

Sep 09, 2007 · When I choose «Restore settings» from configuration/Setup Uitility, my computer worked. Problem is I have to do this every time I turn on my computer.

IBM 300gl 8603 pointing device error? Mend Notebooks .

https://howtomendit.com/answers.php?id=176054

Download the Hardware Maintenance Manual from www.lenovo.com and work your way through the diagnostics. If you do not find the fault quite quickly or it needs a …

8603. PS/2 Pointing device error or not connected — XP .

http://forums.techarena.in/xp-hardware/50625.htm

Jan 04, 2005 · Since you are using USB mouse and PS2 port is emplty, it is your mobo?s BIOS notifying you that there’s nothing plugged in to the PS/2 mouse port.

I have an 8603 pointing device error on my pc.? Yahoo .

https://ca.answers.yahoo.com/question/index?qid=20090706142030AANYCS7

Jul 06, 2009 · Looking for an electric scooter that is powerful enough to climb the steepest hill (boat launch the hill) but doesn’t go fast is under $1000?

PS/2 pointing device error Tech Support Guy

https://forums.techguy.org/threads/ps-2-pointing-device-error.230529/

May 27, 2004 · Thanks for helpful keyboard keys link. She says after following the instructions, -after reboot, no mouse is recongnized ( no mouse icon) and still getting » 8603 pointing device error» after reboot. When in the device manager, that part says she has mouse, but in the utilities part it says the mouse is uninstalled.

POST error codes — Netfinity 5000 — IBM

https://www.ibm.com/support/home/entry/portal/docdisplay?lndocid=ddse-43unpt#!

8603 (Pointing Device Error) 1. Pointing Device 2. System Board: 0001200 (Machine check architecture error) 1. Processor 2. Optional Processor: 000120P0, 000120P1, 000120P2, 000120PF (Processor cache error) 1. Failing Processor: 01295085 (ECC checking hardware test error) 1. Processor: I9990301 (Fixed boot sector error, no operating system .

POST error codes — IBM IntelliStation M Pro (Type 6233, 6850)

https://www.ibm.com/support/home/entry/portal/docdisplay?lndocid=migr-45754#!

2462 (Video memory configuration error) Video adapter (if installed) System board; 5962 (IDE CD-ROM configuration error) Run Configuration/Setup; CD-ROM drive; CD-ROM power cable; IDE cable; System board; Battery; 8603 (Pointing device error) Pointing device; System board; 00012000 (Processor machine check) Update BIOS; Replace microprocessor

How To I Fix The 8603-Pointing Device Error Fixes & Solutions

We are confident that the above descriptions of How To I Fix The 8603-Pointing Device Error and how to fix it will be useful to you. If you have another solution to How To I Fix The 8603-Pointing Device Error or some notes on the existing ways to solve it, then please drop us an email.

Источник

8603. PS/2 Pointing device error or not connected

Distinguished

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

When I boot XP pro, I get this error message just before the XP start up
screen,

8603. PS/2 Pointing device error or not connected

I press OK and the computer boots normally and the mouse works fine.

My mouse is a Logitech MouseMan wheel , it’s plugged in USB.
I got the latest drivers and software for the mouse.
In the Hardware Manager of the system properties, in the mouse and pointing
devices section, it only lists:

HID-compliant MouseMan Wheel

I know for sure it used to show a second mouse, named PS/2 Compatible
Pointing Device or something like that. That is before I update the
mouseware. however, I was still getting this 8603 error at startup with the
older mouseware.

specs:
Aptiva — Pentium III 550MHz
128MB RAM
Windows XP pro

sunny

Distinguished

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

> When I boot XP pro, I get this error message just before the XP start up
> screen,
>
> 8603. PS/2 Pointing device error or not connected

That’s your motherboard’s BIOS telling you there’s nothing plugged in to
the PS/2 mouse port. Since you are using a USB mouse, this message is of
no concern, but probably cannot be supressed. You’ll just have to ignore it.

> I press OK and the computer boots normally and the mouse works fine.
>
> My mouse is a Logitech MouseMan wheel , it’s plugged in USB.
> I got the latest drivers and software for the mouse.
> In the Hardware Manager of the system properties, in the mouse and pointing
> devices section, it only lists:
>
> HID-compliant MouseMan Wheel
>
> I know for sure it used to show a second mouse, named PS/2 Compatible
> Pointing Device or something like that. That is before I update the
> mouseware. however, I was still getting this 8603 error at startup with the
> older mouseware.
>
>
> specs:
> Aptiva — Pentium III 550MHz
> 128MB RAM
> Windows XP pro
>
>
> Thanks.

Источник

Thread: 8603 pointing device error + other misc problems

Thread Tools

Search Thread

Display

8603 pointing device error + other misc problems

Ok, I went over to this person’s house to check the computer out. It had viruses. 7 viruses to be exact. I tried deleting all the registry keys, installing and running Norton but everything I undone the virii put back even after Norton wiped out 52 infected files. It was the adware virii.

Anyways, I bring the computer back to my house to take care of this problem, I plug it in boot it up and the first thing it tells me is 8603 Pointing device error. And yes there’s a mouse plugged in. I try to continue and exit setup and it comes up 1962 no operating system found. This computer was just running at the person’s house and I get it home and it won’t work. It won’t even boot with a floppy in it! None of the cables have been unhooked, and nothing else out of the ordinary either. It’s like it doesn’t want me to fix it..lol I don’t think the virus could have done this, it was only an adware virus, Adware.ADTOMI + other; favoriteman, clearsearch..etc.

This system is a P2 350, 128mb ram 4g hd win98

Just when you think you’ve seen it all.

Just moving a computer a small distance runs a chance of something coming loose inside the case. Of course, a lot depends how the computer is handled..kept upright, laid down,
thrown around..etc.
Getting inside the case and pushing all cables, boards, memory, etc., firmly into place would be my first choice to pin it down.
Good luck and let us know.

If you get the boot problem fixed (safe mode?), try CWShredder.
Scroll down

Read below if you want to but as I was writing this, I was messing around with the bios setup. found this option that said «Disketteless operation» which was checkmarked «disabled», for craps and giggles I enabled it and the computer booted. I cannot figure how that option got changed unless it was the virii. really weird. Thanx for reading and thanx for replying!!

Ok, here’s an update. I checked all the cables over and over and come up with nothing. Everything is seated properly, all cables are hooked up properly. Even though the Pointing Device Error is coming up the computer should still boot. When I first boot the computer it comes up with it’s IBM screen tells me there’s a pointing device error, goes to blank screen then beeps twice. 2 short beeps then asks if I want to continue into setup or exit setup. If I continue it goes directly to a screen that shows a floppy drive (DOS) with an arrow pointing to the drive and says 1962 No operating system found. I try inserting a floppy hit F1 like it directs, it access the floppy and goes right back to the same screen. I’m using a boot floppy I use for every computer I’ve ever worked on and it won’t boot.

I go into the system configuration and into devices and i/o ports and get into IDE drives setup. once in there I go to IDE hard disk drive 0 which is the main, hit enter on that and it comes up with the size as being 4224 MB which is the correct information for the hard disk. it even shows it in the system summary.

Источник

POST error codes — IBM eServer xSeries 235

Troubleshooting

Problem

This document is intended for trained servicers who are familiar with IBM Personal Computer products. Use this document along with advanced diagnostic tests to troubleshoot problems effectively.

Resolving The Problem

This document is intended for trained servicers who are familiar with IBM Personal Computer products. Use this document along with advanced diagnostic tests to troubleshoot problems effectively. Before servicing an IBM product, be sure to review the safety information. Click here to review safety information.

In the following error codes, X can be any number or letter.

Note: See «System» on page 156 in the Hardware Maintenance Manual (HMM) to determine which components should be replaced by a field service technician.

062 (Three consecutive startup failures using the default configuration.)

1. Run the Configuration/Setup Utility program
2. Battery
3. System board
4. Microprocessor

101, 102 (System and processor error)

1. System board

106 (System and processor error)

1. System board

111 (Channel check error)

1. Memory DIMM
2. System board

114 (Adapter read-only memory error)

1. Failing adapter
2. Run diagnostics

129 (Internal cache error)

1. Microprocessor
2. Optional microprocessor (if installed)

151 (Real time clock error)

1. Run diagnostics
2. Battery
3. System board

161 (Real time clock battery error)

1. Run the Configuration/Setup Utility program
2. Battery
3. System board

162 (Device configuration error)
NOTE: Be sure to load the default settings and any additional desired settings; then, save the configuration.

1. Run the Configuration/Setup Utility program
2. Battery
3. Failing device
4. System board

163 (Real-time clock error)

1. Run the Configuration/Setup Utility program
2. Battery
3. System board

164 (Memory configuration changed.)

1. Run the Configuration/Setup Utility program
2. DIMM
3. System board

175 (Hardware error)

1. System board

176 (Computer cover or cable cover was removed without a key being used)

1. Run the Configuration/Setup Utility program
2. System board

177, 178 (Security hardware error)

1. Run the Configuration/Setup Utility program
2. System board

184 (Power-on password damaged)

1. Run the Configuration/Setup Utility program
2. System board

185 (Drive startup sequence information corrupted)

1. Run the Configuration/Setup Utility program
2. System board

186 (Security hardware control logic failed)

1. Run the Configuration/Setup Utility program
2. System board

187 (VPD serial number not set.)

1. Set serial number in the Configuration/Setup Utility program
2. System board

188 (Bad EEPROM CRC #2)

1. Run the Configuration/Setup Utility program
2. System board

189 (An attempt was made to access the server with invalid passwords)

1. Run the Configuration/Setup Utility program, and type the administrator password

201 (Memory test error.) If the server does not have the latest level of BIOS installed, update the BIOS to the latest level and run the diagnostic program again.

1. DIMM
2. System board

229 (Cache error)

1. Microprocessor
2. Optional microprocessor (if installed)

262 (DRAM parity configuration error)

1. Run the Configuration/Setup Utility program
2. Battery
3. System board

289 (DIMM disabled by POST or user)

1. Run the Configuration/Setup Utility program, if the DIMM was disabled by the user
2. Disabled DIMM, if not disabled by user

301 (Keyboard or keyboard controller error)

1. Keyboard
2. System board

303 (Keyboard controller error)

1. System board

602 (Invalid diskette boot record)

1. Diskette
2. Diskette drive
3. Cable
4. System board

604 (Diskette drive error)

1. Run the Configuration/Setup Utility program and diagnostics
2. Diskette drive
3. Drive cable
4. System board

605 (Unlock failure)

1. Diskette drive
2. Drive cable
3. System board

662 (Diskette drive configuration error)

1. Run the Configuration/Setup Utility program and diagnostics
2. Diskette drive
3. Drive cable
4. System board

762 (Coprocessor configuration error)

1. Run the Configuration/Setup Utility program
2. Battery
3. Microprocessor

962 (Parallel port error)

1. Disconnect the external cable on the parallel port
2. Run the Configuration/Setup Utility program
3. System board

11XX (System board serial port 1 or 2 error)

1. Disconnect the external cable on the serial port
2. Run the Configuration/Setup Utility program
3. System board

1301 (I2C cable to front panel not found)

1. Cable
2. Front panel
3. Power switch assembly
4. System board

1302 (I2C cable from system board to power on and reset switches not found)

1. Cable
2. Power switch assembly
3. System board

1303 (I2C cable from system board to power backplane not found)

1. Cable
2. Power cage assembly, if installed
3. System board

1304 (I2C cable to diagnostic LED board not found)

1. Power switch assembly
2. System board

1600
(The system management processor is not functioning) Do the following before replacing a FRU:

1. Ensure that a jumper is not installed on J34.
2. Remove the ac power to the server, wait 20 seconds; then, reconnect the ac power. Wait 30 seconds; then, turn on the server.

1. System board

1601
(The system is able to communicate to the system management processor, but the system management processor failed to respond at the start of POST.) Do the following before replacing a FRU:

1. Remove the ac power to the server, wait 20 seconds; then, reconnect the ac power. Wait 30 seconds; then, turn on the server.
2. Flash update the system management processor.

1. Remote Supervisor Adapter, if installed
2. System board

1602
(Cable for optional service processor adapter not installed)

1. Disconnect all server and option power cords from server, wait 30 seconds, reconnect, and retry

1762 (Hard disk configuration error)

1. Hard disk drive
2. Hard disk cables
3. Run the Configuration/Setup Utility program
4. Hard disk adapter
5. SCSI backplane
6. System board

178X (Fixed disk error)

1. Hard disk cables
2. Run diagnostics
3. Hard disk adapter
4. Hard disk drive
5. System board

1800 (No more hardware interrupt available for PCI adapter)

1. Run the Configuration/Setup Utility program
2. Failing adapter
3. System board

1962 (Drive does not contain a valid boot sector)

1. Verify that a startable operating system is installed
2. Run diagnostics
3. Hard disk drive
4. SCSI backplane
5. Cable
6. System board

2400 (Video controller test failure)

1. Video adapter (if installed)
2. System board

2462 (Video memory configuration error)

1. Video adapter (if installed)
2. System board

5962 (IDE CD-ROM drive configuration error)

1. Run the Configuration/Setup Utility program
2. CD-ROM drive
3. CD-ROM power cable
4. IDE cable
5. System board
6. Battery

8603 (Pointing-device error)

1. Pointing device
2. System board

0001200 (Machine check architecture error)

1. Microprocessor 1
2. Optional microprocessor 2

00012000 (Microprocessor machine check)

1. Microprocessor
2. System board

00019501 (Microprocessor 1 is not functioning — check VRM and microprocessor LEDs)

1. VRM 1
2. Microprocessor 1
3. System board

00019502 (Microprocessor 2 is not functioning — check VRM and microprocessor LEDs)

1. VRM 2
2. Microprocessor 2

00019701 (Microprocessor 1 failed)

1. Microprocessor 1
2. System board

00019702 (Microprocessor 2 failed)

1. Microprocessor 2
2. System board

00180100 (A PCI adapter has requested memory resources that are not available.)

1. Reorder the adapters in the PCI slots. It is important that your startup device is positioned early in the startup-device order so that it is run by POST
2. Ensure that the PCI adapter and all other adapters are set correctly in the Configuration/Setup Utility program Utility program. If the memory resource settings are not correct, change the settings
3. If all memory resources are being used, you might need to remove an adapter to make memory available to the PCI adapter. Disabling the adapter BIOS on the adapter might correct the error. (See the documentation provided with the adapter)

00180200 (No more I/O space available for PCI adapter)

1. Run the Configuration/Setup Utility program
2. Failing adapter
3. System board

00180300 (No more memory (above 1MB for PCI adapter))

1. Run the Configuration/Setup Utility program
2. Failing adapter
3. System board

00180400 (No more memory (below 1MB for PCI adapter))

1. Run the Configuration/Setup Utility program
2. Move the failing adapter to slot 1
3. Failing adapter
4. System board

00180500 (PCI option ROM checksum error)

1. Remove failing PCI card
2. System board

00180600 (PCI to PCI bridge error)

1. Run the Configuration/Setup Utility program
2. Move the failing adapter to slot 1
3. Failing adapter
4. System board

00180700, 00180800 (General PCI error)

1. System board
2. PCI card

00181000 (PCI error)

1. Adapter
2. System board

01295085 (ECC checking hardware test error)

1. System board
2. Microprocessor

01298001 (System BIOS installed on this server does not support level of processor)

1. Ensure all microprocessors have the same cache size.
2. Microprocessor 1.

01298002 (System BIOS installed on this server does not support level of processor)

1. Ensure all microprocessors have the same cache size.
2. Microprocessor 2.

01298101 (System BIOS installed on this server does not support level of processor)

1. Ensure all microprocessors have the same cache size.
2. Microprocessor 1.

01298102 (System BIOS installed on this server does not support level of processor)

Источник

Problem

This document is intended for trained servicers who are familiar with IBM Personal Computer products. Use this document along with advanced diagnostic tests to troubleshoot problems effectively.

Resolving The Problem

This document is intended for trained servicers who are familiar with IBM Personal Computer products. Use this document along with advanced diagnostic tests to troubleshoot problems effectively. Before servicing an IBM product, be sure to review the safety information. Click here to review safety information.

In the following error codes, X can be any number or letter.

Note: See «System» on page 156 in the Hardware Maintenance Manual (HMM) to determine which components should be replaced by a field service technician.