re: mup.sys : Tell us about your system
Tuesday, March 1, 2005 at 6:01 am
Windows XP Annoyances Discussion Forum
Posted by Art Jenkins
(3 messages posted)
Mike:
I take it that the APIX must be a hardware configuration in the actual chipset of
the mainboard.
I'm using a Fujitsu-Siemens board and using winXP, and when I finally got things
sort of straightened out, I checked and found that I had 22 interrupts divied out
to the devices (mostly to USB handlers and devices).
Even with everything apparently working, and all the root hubs and everything all
working properly and no usb devices plugged in, I still have a problem with it looking
for one usb controller that I have no reason for and have to leave it as a Question
mark in device manager. It doesn't bother me unless I delete it out again and as
soon as I boot up it wants a driver for it!
Oh well - I guess with PC's nothing is perfect!!!
Thanks for pointing to that interesting and enlightening article on interrupts!
Art.
On Tuesday, March 1, 2005 at 1:39 am, Mike wrote:
>Windows is picky because it is virtually plug-n-play. Instead of assigning interrupt
>requests manually like the good old days, XP is supposed to be extremely user friendly-to
>a fault. Unfortunately, hardware conflicts arise and XP will not boot. USB is notorious
>for being IRQ hogs. Mup.sys seems to be a precursor to the loading of the HAL, which
>is a mystery to me. I've had this problem simply from disconnecting a hard drive
>to move it to another IDE slot. I am lazy and I've skimmed over this article, but
>I fixed my system before I finished it. To avoid paraphrasing more qualified data,
>see:
>
>http://www.microsoft.com/whdc/system/sysperf/apic.mspx.
>
>Please feel free to correct me, I'm not in the IT field, so some layman explanation
>to this phenomenon would be helpful.
>
>
|
All messages in this thread [show all]
 |  | | | | |  | re: mup.sys : Tell us about your system (Art Jenkins: Tue, Mar 1, 2005, 6:01 am) |
| |
| |
Return to the Windows XP Discussion Forum
|
|
