fjk61011
Veteran Member
I've bought a USB to serial cable, waiting on a null modem and will try that. Slight problem, modern pc downstairs and 5150 5160 upstairs.Reading that link.
I've bought a USB to serial cable, waiting on a null modem and will try that. Slight problem, modern pc downstairs and 5150 5160 upstairs.Reading that link.
This setup worked before but doesn't now. I'm beginning to think there is something wrong about the design of the XT-FDC. I'll trudge on and see what I can do.Summary of work so far.
IBM XT 5160 motherboard, V-20, 8087, Super XT BIOS.
AT PSU
CGA with composite out.
Memory card
XT-IDE with DOM
XT-FDC with Gotek
EtherLink II NIC
DOS 6.22, mTCP
I'll post addresses and IRQs later
Maybe try a different AT28C64.Is it possible that an address conflict damages the XT-FDC BIOS?
I can't get the XT-IDE and the XT-FDC to work together.
The press F2 appears and dissappear between boots
Was this with the XT-IDE/XUB installed or not installed ?But on the question of 'damage' to the Multi-Floppy BIOS, I have been meaning to get back to some experimentation that I did earlier. From memory, earlier, when adding a second drive to the Multi-Floppy BIOS, it was possible for me to create a conflict there. The "Press F2 to run ..." would not appear, and a BIOS re-flash was the only remedy. Something like that.
Modem7 said to refer to. It as an ISa controller and serial card. Works now in combination with xt-ide. Here is an observation. I can change the dip switches on Xt-ide without using xtidecfg an it still works. My at28 c64 b have arrivedIt's been many years since i last used Sergey's FDC BIOS on a regular basis, Back then i used the FDC BIOS in a ROM Board, Or i used a spare Rev 1 XT-IDE PCB as a ROM board, Because i never did order the parts to build the FDC i bought from Sergey over 10 years ago.
Back then i built and kept several different FDC BIOS's to cater for different floppy drive setups, If i swapped floppy drives i just re-flashed the EEprom with the correct BIOS setup for the Floppy drives i was using, Because the F2 setup option of the BIOS did not work with the EEprom my ROM boards use and when using the XUB it clobbered the F2 setup of the FDC bios when using the FDC BIOS in the AT28C64 it was written to work with.
Clever. Was thinking the same about xtide messing with xtfdc biosIt's been many years since i last used Sergey's FDC BIOS on a regular basis, Back then i used the FDC BIOS in a ROM Board, Or i used a spare Rev 1 XT-IDE PCB as a ROM board, Because i never did order the parts to build the FDC i bought from Sergey over 10 years ago.
Back then i built and kept several different FDC BIOS's to cater for different floppy drive setups, If i swapped floppy drives i just re-flashed the EEprom with the correct BIOS setup for the Floppy drives i was using, Because the F2 setup option of the BIOS did not work with the EEprom my ROM boards use and when using the XUB it clobbered the F2 setup of the FDC bios when using the FDC BIOS in the AT28C64 it was written to work with.
Using new xtfdc. xt-ide and xt-fdc together.What XT-FDC are you using ?, Your original Sergey's FDC or the NEW Sergey's FDC or is it the same issue with both FDC's ?.
Was this with the XT-IDE/XUB installed or not installed ?
But on the question of 'damage' to the Multi-Floppy BIOS, I have been meaning to get back to some experimentation that I did earlier. From memory, earlier, when adding a second drive to the Multi-Floppy BIOS, it was possible for me to create a conflict there. The "Press F2 to run ..." would not appear, and a BIOS re-flash was the only remedy. Something like that.
Not installed. 'Bare bones' configuration.Was this with the XT-IDE/XUB installed or not installed ?
Sorry to hear about your sister, My little Niece was recently diagnosed with stage 4 cancer, Life can be so challenging at times. Can you not try flashing the AT28C64 in situ using XTIDECFG.COM ?I'll be missing for awhile. My sister is very ill. I tried my gq-4×4 to flash a AT28C64 but when I read it it was all FF