First post, by alfiehicks
- Rank
- Newbie
Hi, I've recently swapped the motherboard and CPU in one of my machines (It's now an AOpen MX3S with a 1GHz PIII) and doing so caused a whole variety of issues that I wasn't prepared for. I've sorted most of them out now, but this one currently has me stumped. Quake - and only Quake - has this weird issue where it'll run completely fine, but when I go to exit, it goes back to DOS and prints the usual text screen, but doesn't give me a prompt. The machine isn't locked up, I can still press ctrl+alt+del to restart, and repeatedly pressing any other key eventually causes busy beeps, but they sound more like soft clicks rather than the usual loud beeps. If I do the same thing with Scourge of Armagon (Expansion Pack 2 for Quake) then the results are the same, except it also shows a blinking cursor, but still no prompt.
The results are the same across multiple installs of Quake: this one (which is v1.08), another identical install on a separate drive partition, and on an install of v1.01 that I backed up to a CD. If I run the game in Windows 98 instead, I can still exit the program via closing the window and it quits gracefully with no issues. I'm booting DOS from a floppy disk and Windows from a CF card. I've installed all of the Windows 98 drivers for the board, but DOS doesn't need those, it should just work. I read on another post on here that disabling EMM386 fixed this issue in another person's case, but I'm relying on EMM386 to run the SB16 emulation driver for a Sound Blaster Live.
Another thing : Windows 98 takes absolutely forever to load now that I've swapped out the board and CPU. After the typical boot splash, it abruptly goes back to the BIOS screen (where it verified the DMI Pool Data) but overlays it with a blinking cursor in the top left (overlapping the previous graphics without overwriting them) and just sits there seemingly idling for another ~30 seconds. The HDD light doesn't blink at all during this, so I fail to see what it could be doing. It did not do this before with the older hardware configuration.
I'm beginning to think the board and/or CPU might just have ghosts in it, but this really feels like two separate software issues, so I'm hoping that's the case. Any help would be greatly appreciated.