This is most confusing. THe Keybaord and touch pad stopped responding, put in a USB mouse, and that works. It crashes when you try to shut down, and holding down the on/off switch does nothing (the whole keypad has died, but lights still work).
Remove battery, and reboot, F2 works to get into BIOS. Alt F10 does nothing on bootup so i can return to factory defaults.
Press F8 and boots into safe mode, keyboard and mouse work fine. Reboot into normal mode, keyboard and mouse no longer work (mouse works if you moce it as windows starts to load, then it just stops). Have to remove battery to reboot.
Complety removed all partitions and formatted, then tried to restore with my backup disks made long ago, but as soon as windows boots, same problem.
Alt F10 still no longer works on bootup, although it is enabled in the BIOS.
It is an Acer Travelmate 2310, anyone got any ideas?
I have even tried to install a new version of XP, from a standard disk, but half way through install, keyboard stops working.
The fact it works in safe mode tells me it's cant be dodgy wiring, whcich usually means driver problems, but the fact ti does it with restore or new install is very confusing.
Anyone got any ideas, however daft or stupid?
Cheers
Remove battery, and reboot, F2 works to get into BIOS. Alt F10 does nothing on bootup so i can return to factory defaults.
Press F8 and boots into safe mode, keyboard and mouse work fine. Reboot into normal mode, keyboard and mouse no longer work (mouse works if you moce it as windows starts to load, then it just stops). Have to remove battery to reboot.
Complety removed all partitions and formatted, then tried to restore with my backup disks made long ago, but as soon as windows boots, same problem.
Alt F10 still no longer works on bootup, although it is enabled in the BIOS.
It is an Acer Travelmate 2310, anyone got any ideas?
I have even tried to install a new version of XP, from a standard disk, but half way through install, keyboard stops working.
The fact it works in safe mode tells me it's cant be dodgy wiring, whcich usually means driver problems, but the fact ti does it with restore or new install is very confusing.
Anyone got any ideas, however daft or stupid?
Cheers







