First post, by bamdad
- Rank
- Newbie
hey everyone,
i've been around these forums for years now but always found answers to my questions and i guess i enjoy reading what others have to say so i kept quiet. however, the problem i'm facing is really bugging me so.. here we go.
so i have an old machine that used to have an AMD 486DX4-100 until recently, then i found a 100mhz IBM (cyrix) 5x86 lying around and thought i'd give it a go. after jumpering and building a homebrew cooler for the better part of the night and discovering that it can go up to 120mhz with a 40mhz bus i was thrilled.. aside from the fact the new ISA bus speed killed my already wonky intel etherexpress pro card's eeprom - but that is another story.
of course i went ahead and fired up duke3d that was quite laggy running on my old 486 CPU. the demo behind the main menu was silky smooth, no palette problems or artifacts.. and then i started a new game and found that my serial mouse is dead. this baffled the frak out of me since it was working perfectly in norton commander so i tried it in blood and the same thing happened. then shadow warrior. even rise of the triad. however, and this is the weirdest part, in older games like doom or sim city 2000 it's working perfectly. it even works in duke's build.exe. not to mention windows 3.11. this rules out any IRQ conflicts and dos4gw incompatibilities, so i tried
- lots of microsoft mouse drivers and the newest ctmouse
- lowering ISA bus speeds
- un-overclocking the CPU
- removing cyrix optimisations (5x86.exe stuff)
- patching duke3d.exe with 'buildmfx'
- checking whether duke3d is using COM1 for a serial game (although i don't think that affects single player and it was working with the 486 before but just in case)
..to no avail.
so is my cyrix processor on a crusade against 3d realms or am i doing something horribly wrong? xD
best,
bamdad