First post, by NooNaN
- Rank
- Member
Hi Guys - I have a retro PC that I just set back up after a move. I happen to boot it up without the mouse attached as the cord wasn't long enough for the new placement. Everything was good...my AWE 64 was assigned the correct addresses, midi out to my external devices was fine, everything.
Then, I plugged the mouse in and rebooted to do some more testing. Now, my AWE64 went a mess. It tried to assign weird IRQs and the MPU wouldn't work at all. SB diagnosis reported errors and I could not manually assign everything back to normal. I unplugged the mouse, rebooted and all was fine again.
I'm at a loss...no idea why any mouse system resources would throw the AWE64 for a loop like that. Would appreciate any and all help!
I'm running the following (not sure more is relevant, but if so, please ask):
AMD K6-IIII 450
AWE64 Gold ISA
CuteMouse Driver with a Microsoft, standard PS/2 mouse
DOS 6.22
Thanks!