re: Mup.sys? Hangs but not? Wha's happening?
Tuesday, July 22, 2003 at 1:51 am
Windows XP Annoyances Discussion Forum
Posted by ddd
(1 messages posted)
OK - I'm coming in well into this, but i found this thread when i, too, attempted
to boot into
safe-mode only to discover a 'hang' at the moment after MUP.SYS loaded.
But I had some pretty severe symptoms that led me here as well -
1. my floppy couldn't recognize a disk with known-good data - it
reported messages saying any disk was 'not formatted', and even then
i couldn't even get it to complete a format on a blank fresh floppy.
2. my CDROM could play music but not show me the track.cdda file list in an
'explorer' window and my DVD-ROM couldn't do anything.
3. my networking was inoperative. IPCONFIG wouldn't run at all.
4. event-viewer said the 'null', 'beep', 'ipsec', and a variety of other services
had failed to start because the related drivers were 'invalid'
5. my device-manager reported my floppy disk with a yellow exclam point,
my 'microcode updated device' (a system device) also with a yellow exclam.
6. i had already tried 'uninstalling' the floppy disk and 'reinstalling' it - with
no luck
so today i started looking at these drivers (mup.sys, flpydisk.sys, fs_rec.sys, etc.
tcpip.sys, and some others) in my Windows/system32/drivers folder.
lo and behold, when i ran the mouse over 'em, some of the drivers in the
folder clearly gave little balloon messages what they were, while the ones
named above only showed the 'date created' and no name or function info
in the balloon. i concluded those must the the 'invalid' ones.
happily i had a copy of XP drivers from another XP computer
I had partly backed up and started locating 'invalid' drivers on the one XP computer
and replacing them with copies from the other (good) XP computer. BINGO!
within minutes I had my networking back (by replacing the tcpip.sys),
then i kept going and now i have my floppy, cdrom, and everything else.
btw, refreshing MUP.SYS made the device-manager 'microcode update device'
error mark disappear. turns out the floppy really needed fs_rec.sys (filesystem
recognizer driver) refreshed, and that also made the CDROM come back.
i wound up refreshing null.sys, beep.sys, and a bunch of others and that
made the event-viewer stop reporting all those errors on bootup. no more
'invalid drivers' causing various services to not start when needed.
i don't suggest doing this willy-nilly. i was careful to match byte-counts and
original 'date-created' on each one and only refreshed ones that 'appeared'
invalid by the lack of function/name in the balloon indicators. a little tedious,
but the computer is back to 100%.
i hope this helps you all get to the bottom of this.
btw, MUP.SYS is the 'multiple UNC' driver, but it is reflected in your device-manager
as 'Microcode UPdate Device' - which makes more sense. not that i know what this
thing *does*, but I bet it is the thing that updates WinXP when you add a hard
drive or ram to your computer.
i haven't tried again to boot into safe mode, but i bet it won't hang after
MUP.SYS now :)
Good luck, folks - hope you succeed in fixing your systems.
DDD
On Monday, July 21, 2003 at 9:39 pm, sean wrote:
>well. tried hooking my new hd up to my old computer.
|
All messages in this thread [show all]
 |  | | | |  | re: Mup.sys? Hangs but not? Wha's happening? (ddd: Tue, Jul 22, 2003, 1:51 am) |
| |
