BTW, the original error was because of a change in hardware, it looks like a mouse was changed and the configuration file was not.
Just as a quick point. The reason why Windows survives all of these hardware swaps is that Windows has almost every single driver for every single piece of generic hardware built into it. The upside of this is that it can tolerate random hardware swaps. The downside is that it takes up huge amounts of space and can easily result in conflicts that are hard to diagnose.
Linux, on the other hand, typically installs only the hardware drivers you need. If you change the hardware, particularly if it's a quasi embedded system, then you need to update both the config files and install drivers for the new hardware. The errors you were seeing were related to missing hardware for either the keyboard or the mouse, or perhaps a change in the mouse hardware (keyboards are pretty much all the same). It looks like there might have been a serial mouse attached at one point, which is no longer attached...
Another thing to keep in mind is that some hardware is tied to specific ports on the PC (like specific serial or even USB ports) and if you move stuff around, it can break the configuration. This is esp. true with embedded systems that you are not supposed to change. Also, change the BIOS can also affect the 'locations' of hardware on the computer, resulting in issues.
HTH,
Chris.


LinkBack URL
About LinkBacks




Anyway-the saga continues-the good news is that Ajax checked out the sandisk hardrive and reader and they are both OK-the bad news is that the sandisk hardrive and reader are OK.... Was really hoping this would be the problem, replace them and "Bob's your Uncle"...so back to square one. I must admit that Drew at Ajax has been very patient and helpful in trying to get this mess all sorted out. The next step is again a process of elimination. Again-the computer boots up perfectly from the original hard drive in windows. I had then disconnected the hard drive (ribbon & power) and so the computer would be forced to boot automatically from the sandisk and would only get to the kernal panic stage. So then the sent the sandisk and reader to Ajax to be checked out. So what Ajax would like me to do is send them the new motherboard and they will see if they can get it to boot up with my sandisk and reader... At his point not sure what else to do.....
Tom
I got this message from Drew from Ajax:
