Mike Chambers
Veteran Member
- Joined
- Sep 2, 2006
- Messages
- 2,621
I've got a 10 MHz XT clone board with a V20, not sure of the brand. It's a later model that seems to be more integrated than most, and it's not very large.
Anyway, lately it's got a strange issue where it always throws a KB error on post, yet the keyboard works fine. It happens with any keyboard I connect.
I also recently booted it up (XT-IDE + CF card), loaded a packet driver and tried to run a program. It just hangs. I've tried multiple NICs, not sure if it's even related to the networking or not. The KB error makes me feel like there's a more general issue somewhere with part of the chipset. The same program works fine on any other XT-style system.
This is a clean MS-DOS 6.22 boot, F5 to load without config.sys/autoexec.
Any thoughts on this one?
EDIT: Well the program lockup turned out to be a silly issue. The CF card is formatted with a different CHS layout than what the XT-IDE is picking it up as, so some things will read the wrong sectors when loading!! At least MSD reports something different than the image I flashed onto it, so I'll see if that resolves it.
Still bugged by the keyboard error on POST though.
Anyway, lately it's got a strange issue where it always throws a KB error on post, yet the keyboard works fine. It happens with any keyboard I connect.
I also recently booted it up (XT-IDE + CF card), loaded a packet driver and tried to run a program. It just hangs. I've tried multiple NICs, not sure if it's even related to the networking or not. The KB error makes me feel like there's a more general issue somewhere with part of the chipset. The same program works fine on any other XT-style system.
This is a clean MS-DOS 6.22 boot, F5 to load without config.sys/autoexec.
Any thoughts on this one?
EDIT: Well the program lockup turned out to be a silly issue. The CF card is formatted with a different CHS layout than what the XT-IDE is picking it up as, so some things will read the wrong sectors when loading!! At least MSD reports something different than the image I flashed onto it, so I'll see if that resolves it.
Still bugged by the keyboard error on POST though.
Last edited: