Supercomputer
Posted: Sun Nov 16, 2003 10:33 am
I have a couple of old computers lying around that I infrequently use to test 'this' or 'that'. I am very interested in using these computers to make a supercomputer. My idea is to use the floppy drive "ports" on each mother boad to connect the two motherboards together for a "communication" channel.
I had two other older computers (66Mhz and 133Mhz) connected in this manner and surprisingly they would both boot and recognize the floppy controller (from an old 5" floppy drive, guts taken out). The ribbon cable went from one floppy connection on the motherboard to the floppy controller (middle connector on cable) then to the other motherboard.
There were other complexities that kept me from moving forward with the experiment and I gave it up. Until I realized that those problems might be solved from the BIOS.
I would rather do away with the floppy as a "pass through" device and just have the ribbon cable from one motherboard to the other. Then, in the BIOS, to verify that it was indeed working, I could write some kind of communication protocol to identify each motherboard to the other. Basically output to the terminal a message.
For instance: Extend the BIOS of computer A and B to include some communication verification code. Once the normal BIOS code finished and the new extended code is entered, A sends a "message" to B using the floppy "port" (I think it is called an interrupt). B recognizes the message, processes it (prints it to the screen) then sends a reply. A recognizes the reply, processes it (screen again) and the test is done.
This test would do one of two things. If it didn't work (or you know it can't be done) it would help me to put closure on this crazy idea. OR, if it did work (possible with 'xyz' adjustments) it would motivate me to continue and spend endless hours and countless dollars working to improve it.
I have Assembly language knowledge and can write software. I have some training in electronics but not in depth enough to move forward (as you might be able to tell already). I am just looking for anyone willing to offer input, ideas and suggestions.
Thanks!
Andrew
I had two other older computers (66Mhz and 133Mhz) connected in this manner and surprisingly they would both boot and recognize the floppy controller (from an old 5" floppy drive, guts taken out). The ribbon cable went from one floppy connection on the motherboard to the floppy controller (middle connector on cable) then to the other motherboard.
There were other complexities that kept me from moving forward with the experiment and I gave it up. Until I realized that those problems might be solved from the BIOS.
I would rather do away with the floppy as a "pass through" device and just have the ribbon cable from one motherboard to the other. Then, in the BIOS, to verify that it was indeed working, I could write some kind of communication protocol to identify each motherboard to the other. Basically output to the terminal a message.
For instance: Extend the BIOS of computer A and B to include some communication verification code. Once the normal BIOS code finished and the new extended code is entered, A sends a "message" to B using the floppy "port" (I think it is called an interrupt). B recognizes the message, processes it (prints it to the screen) then sends a reply. A recognizes the reply, processes it (screen again) and the test is done.
This test would do one of two things. If it didn't work (or you know it can't be done) it would help me to put closure on this crazy idea. OR, if it did work (possible with 'xyz' adjustments) it would motivate me to continue and spend endless hours and countless dollars working to improve it.
I have Assembly language knowledge and can write software. I have some training in electronics but not in depth enough to move forward (as you might be able to tell already). I am just looking for anyone willing to offer input, ideas and suggestions.
Thanks!
Andrew