Saved Bookmarks
| 1. |
Solve : If motherboard on DOS computer dies, can I caddy from another?? |
|
Answer» Hi The ROV has a direct comms link using RS232 on a serial port to this AWS unit which gives us feedback on the screen in its DOS program when it goes over something metallic. It is also useful to know that Dos comms software is traditionally configured to access a definite com port - and it must be using the same port address and IRQ that the original HARDWARE is set up with, or reconfigured with the port/IRQ on the replacement machine. What happens when you boot the machine you have? Is there a screen that displays text? Or does it beep in a sequence of short or long beeps? Where are the four red lights? It's possible that the machine's CMOS battery has passed away and the BIOS settings need to be reconfigured. At least that is a common fault, and your machine is obviously many years old - was the battery changed?Hey, thanks for the replies. FIRSTLY, is there any chance you could quickly bullet point how to install this HDD as a primary HDD on a normal computer? In answer to the other questions. Originally the computer booted fine, tested and worked great. Next time i went to turn it on I got an error message after the memory test saying 'Verifying DMI Pool Data' then 'Insert system disk and press any key'. Finally, after removing all the connectors and CLEANING them down thinking it could be communication to the HDD, I now boot and nothing on screen but instead 4 red lights which are right on the back of the motherboard in the top right hand corner. The beep code is one 1 second beep, every 3 seconds or so. I can't actually work out what the red lights are indicated. They just stay on constant and there is nothing on the motherboard i can see (from an awkward angle) to describe what they are. Could this be as simple as the CMOS? The HDD was replaced before it was donated to us but doubt a CMOS would be... but I should still get something on screen surely? Quote from: RPMNautical on July 26, 2015, 03:44:20 PM turn it on I got an error message after the memory test saying 'Verifying DMI Pool Data' then 'Insert system disk and press any key' That looks like a CMOS battery problem with the BIOS settings at default and it just doesn't know which boot device to use - and in some very old machines you needed to enter the cylinders/heads/sector values in the hard drive settings in the BIOS. Quote The beep code is one 1 second beep, every 3 seconds or so. But that one seems like a RAM error, if the BIOS is AMI. The first test to try and solve the RAM error is to remove and reseat the ram modules, as the connections may be a bit tarnished. Code: [Select] | 18. What do the AMI BIOS Beep codes mean ? | +--------------------------------------------+ Except for beep code #8, these codes are always fatal. 1 beep Refresh failure 2 beeps Parity error 3 beeps Base 64K memory failure 4 beeps Timer not operational 5 beeps Processor error 6 beeps 8042 - gate A20 failure 7 beeps Processor exception interrupt error 8 beeps Display memory read/write failure 9 beeps ROM checksum error 10 beeps CMOS SHUTDOWN register read/write error 11 beeps Cache memory bad If the machine then boots and the first error is back, replace the battery. It is still fails, then you can look at replacing the RAM module if you can find an old one. Having said that - you may be able to use any machine with a COM port and only transplant the actual software directory, inside of which may be a configuration file where the com port address and IRQ number can be changed to match the settings in the new machine. When booting the new machine and entering the BIOS you will see the com port settings with address and IRQ, and can even change them to match what is already in the config file. It's possible that the program will run under Windows. This assumes a few things - if you want better advice and you can zip up and post a link to the software folder then it may be clearer what steps to take. |
|