Now, power back on, srart, and no need to touch anything else. It will start back in where it left off.

"When all else fails", read the setupnotes... on the cd.
That is what I did. I have no mouse, most likely beacause I lack the driver for an optical usb connector style mouse.. and this board has only one ps2, which is being used for the keyboard. Mouseless system up and running.

Went into safe mode and noticed in device manager that an unknown mouse was in device manager, confirming that it really was getting hung up on msmouse.vxd driver.

I renamed the msmouse.vxd => msmouse.old. Tried to reboot, but then it hung saying windows looking to load msmouse.vxd but could not install it.

I went into system.ini and removed msmouse.vxd from the mouse driver line, which left it with I believe only msmouse=*vmouse, or something like that.

I then booted successfully into windows, although I had to reset my video settings as it went back to the big old 640x480? setting.

fyi, I have connected the labtec optic mouse, and probably won't get a labtech again, as I've had other problems with it as well.

Hope this helps someone, as this board has been very helpful to me.

From: Perry on 03/26/2005
I have a Win98 machine having the same problem - boot step-by-step and machine hangs at msmouse.vxd loading - whether I select Y or N.

I then started in safe mode, went into the folder C:\Windows\Systems and rename the msmouse.vxd file. Rebooted Normal, system.ini couldn't find msmouse.vxd and I continue with the start up. Everything OK, it seemed. Checked the PS/2 serial port mouse functions; everything normal.

That said something:
1. msmouse.vxd is not essential for mouse operation, at least on my machine.
2. still not sure whether it's a driver associated with msmouse.vxd or not which might be corrupt.

I am tempted to modify the system.ini to read at the mouse line:

mouse=*vmouse

instead of its current:

mouse=*vmouse, msmouse.vsd

But anyway here IS the issue...

After making a copy of the new bios onto the floppy they said to install the floppy in the drive and reboot. it didn't. it wont. I mean it wont boot to the floppy, not in XP. XP doesn't like autoexec.bat files on bootup?. Tell me if i'm wrong but i think it hates them? i got a system boot disc error so to clarify the instructions or at least what i did to achieve the same results...

I did everything you said here---> http://support.gateway.com/support/drivers/ or ftp://ftp.gateway.com/pub/hardware_support/bios/amd/7511677.txt');

BUT i also made a window XP system disc and used it to boot to DOS A: prompt, then i swapped it out with the new bios disc and ran the autoexec.bat from drive A: waa laa. brand new bios. thanks for all the confusion Gateway! now if it only stops the dang hangup! also FYI... This hangup only occurs from a cold boot. which makes it a very very time consuming issue to troubleshoot from a techs standpoint. if anyone out there can verify the exact time it takes for a coldboot? i'v read 4-5 mins. but thats is NOT enough for this system. seems closer to 8-10. but idunno.

Maybe someday Windows will add a "lock" for a cold boot option or something, after all Mr Gates is a "control phreak" lol. :D

Ok, I tried the solution for the Win98 version, which was to:
1. bootup in SafeMode
2. run RegEdit
3. export All files to MyDocuments/newfile
4. delete Enum from HKEY_LOCAL_MACHINE
5. restart

As I restarted, the system would prompt a warning window stating my display configurations are not appropriate and press OK to get the Hardware Installation Wizard to fix problem. I pressed OK, and the system would boot nicely into SafeMode.

Now, how the heck do I get out of SafeMode, and allow for the system to bootup Normally?

I try to shutdown from SafeMode, and the screen will get to the black screen with orange font stating "your computer will now shut down", but the screen just sits there with no other actual indication of actually shutting down. At one time, I left the shut down screen and it seemed like it did not shut down properly because the keyboard number key was still lit, it seemed to have just stopped running. I usually have to reset the on/off (I/O) switch at the back of my tower. The reset will allow the fan to startup the boot, but the buttons at the front for power on and reboot do not work, until I have reset the I/O switch at the back. What do I do now?

The machine failed to boot again even without msmouse.vxd. So that confirmed that it's not a driver associated with msmouse.vxd. Browsing all the posts here, I suspected it was most likely a problem caused by corrupt hardware drivers listed in the Registry. I followed TekWar's suggestion posted on 9/24/03:

The Enum entry contains all of the hardware driver info and drivers are loaded from there. Get rid of the Enum entry and the drivers can't load:

1. Boot to Safe Mode (if possible) and run RegEdit.
2. Before you do anything else, export the registry to a backup file. Make sure you choose to export all and not just a key!
3. Open HKEY_LOCAL_MACHINE.
4. Select and DELETE the Enum entry.
5. Reboot and let the OS re-detect the hardware.

The machine started up with no more glitches any more. Indeed, as Tekwar forewarned, the sacrifice to pay was to load all my hardware device drivers back. Fortunately, my machine was an IBM Thinkpad which detected on start-up the hardware without drivers and loaded them from the Drivers directory. I had to load a couple of drivers manually though - my modem and wireless network card - so it's essential you have your CDs for those critical drivers for reloading.

Epilogue: The machine loaded fine, but a new problem arose. The video card driver had a conflict and the monitor defaulted to 640x480 VGA 16 color only. I tried to reinstall driver and there was always an installation error so that the installation always aborted. Apparently, the new Enum entries pointed to drivers which might still be faulty. I finally had to replace the new Enum entry with my old one (I hadn't deleted it, just renamed it), booted machine up with no glitch, before I reinstalled the video card driver successfully to get back into 11024x768 24-bit color.

I then started in safe mode, went into the folder C:\Windows\Systems and rename the msmouse.vxd file. Rebooted Normal, system.ini couldn't find msmouse.vxd and I continue with the start up. Everything OK, it seemed. Checked the PS/2 serial port mouse functions; everything normal.

That said something:
1. msmouse.vxd is not essential for mouse operation, at least on my machine.
2. still not sure whether it's a driver associated with msmouse.vxd or not which might be corrupt.

I am tempted to modify the system.ini to read at the mouse line:

mouse=*vmouse

instead of its current:

mouse=*vmouse, msmouse.vsd

Should I do that to bypass the msmouse.vsd loading in future?

But using scanreg /restore with a 2 day old registry solved the problem anyway :-)

The problem occurred after installing and trying to launche egoboo, a free 3d dungeon game - possibly some OpenGL call failure.

Thanks for all contributing to this forum thread - I was having the same problem and tried that idea where you delete the ENUM registry key and it worked. You saved me a lot of time and sweat - thank you very much.

My Win98 computer was working until I tried to install a wireless network card. The tech support people told me that the card wasn't working because win98 was corrupted and to reinstall win98.
So I tried to reinstall, and at 62% in, my tiny hard drive ran out of memory. So I tried booting up again, and now it's telling me that vmouse.vxd is missing.

From your suggestions, I tried:
-scanreg/restore
-bootdisk doesn't seem to work
-moving my soundcard to a different slot
-it won't even start in Safe Mode
-tried the PNP tweak, but there's no option to turn off/on OS on my blue screen

-To be clear, I am only a tinkerer, so there's a chance I screwed up on some of your instructions!

I would just chuck the damn thing out but it's got some music files that I recorded, so I'm freaking out trying to get it to work.
Any suggestions? Anything worth trying again?

Another possibility?? I was wondering if I set up my new hard drive to run windows 98 as the master, would I be able to just set up the old hard drive as the slave and access my music files?

Had this problem, even with no NICs, PCI cards or anything else attached. Updated BIOS, problem solved.

I've made it after 3 f. hours.
Try this:

- Install Microsoft Patch for USB (240075up.exe);
- Disable USB 2.0 support from my BIOS;
- delete everything on USB from Devices and reinstall them (Refresh);

This worked for me. Good luck.

Wasted the better part of a day trying to get windoze to load after reformatting C - kept hanging in the places where it calls for a restart - trick was to power down after the bios message comes up and do a cold boot.

I Read all the replies and started trying all the different fixes. Turned out I caused the problem when I bumped one of the memory cards. The BIOS would tell me if a single memory cell was faulty, but wouldn't tell me the whole card was bad, The BIOS just saw it as no card installed. Reseating the memory card fixed it.

I had it and now I don't. How'd I fix it you ask?
Take memory sticks out of their USB readers before
restarting the machine.

I believe that the problem is caused by corrupt hardware drivers which are listed in the Registry. The Enum entry contains all of the hardware driver info and drivers are loaded from there. Get rid of the Enum entry and the drivers can't load.

Also, you may have to go into the Control Panel on some machines and start the Add New Hardware Wizard to get your devices back. I had an IBM Aptiva that didn't detect on start-up and I had to do it manually.

Here is one thing you can try in this situation. Make sure you have all of your driver disks handy tho...

1. Boot to Safe Mode (if possible) and run RegEdit.
2. Before you do anything else, export the registry to a backup file. Make sure you choose to export all and not just a key!
3. Open HKEY_LOCAL_MACHINE.
4. Select and DELETE the Enum entry.
5. Reboot and let the OS re-detect the hardware.

Keep in mind that this may not be the fix for all situations that have this symptom, but it has fixed a few in the past in my shop.

How do I fix it..
--------------

PS/2 Compatible Mouse Port
Mouse
This Device Has a Problem: Code=28 (0x1C)
The drivers for this device are not installed correctly. To install the driver
for this device, click the Driver tab, and then click Update Driver.
Registry Key:    HKEY_LOCAL_MACHINE\enum\BIOS\*PNP0F13\0D
Alloc resources:    Logical Configuration 0
IRQ:    12 Mask: x0000
Forced resources:    None
Boot resources:    Logical Configuration 0
IRQ:    12 Mask: x0000
Filtered resources:    None
Basic resources:    Logical Configuration 0
IRQ:    0 Mask: x1000
Driver:    Mouse\0000
Driver Date:    5-11-1998
Driver:    msmouse.vxd
   File Size: 15809 (0x3DC1)
   File Date: 5/11/1998 8:1 AM
   Company Name: Microsoft Corporation
   File Version: 4.10.1998
Driver:    mouse.drv
   File Size: 7712 (0x1E20)
   File Date: 5/11/1998 8:1 AM
   Company Name: Microsoft Corporation
   File Version: 9.01.0.000

----------------------

Thank you

Mucho troubleshooting, including changing Files, Buffers, Stacks settings per Microsoft "knowledge" base...their words, not mine, toggling the PnP OS on and off in the BIOS, and analyzing the BOOTLOG (never was able to figure out how to keep from overwriting the file when booting up in Safe Mode after the unsuccessful boot in normal mode).

Finally got the machine to boot normally after disabling the wireless network card, so from all previous postings deduced that it's a PnP issue with the PCI slot and/or the wireless card.

Switched the card from one slot to another and PROBLEM SOLVED! Normal boot, no errors.

Thought someone out there might be reading this and like to know!

Tnx,

cheers

I tried installing 3 different distro's of linux, they all hung on install ( they all worked on my old pc, which was the exact same model,same bios).

The mobo in question is a "systemboard pc/100" (thats original!) made by pcchips, 433Mhz Celery

After spending a ridiculous amount of time on it i had to give it back to the customer with USB not working and recommend that they get a mobo upgrade.

How did we come up with the solution?
We used a Bootlog Analyzer (free tool) that gave us the minutes between the last thing loaded and the next thing... when we found it took over a minute to go from this device to the next one, we disabled it and it worked.

PROBLEM 2:
When trying to install everything goes well until after you re-boot the PC, then the PC is registering a hardware conflict. This could be something like "FDC Failure" or it would lock up while trying to load 'msmouse.vxd'. It will freeze and it is hung in a hang. Locked up. No IRQ conflicts in Device Manager. It did not bring up the Add Hardware Wizard when the card was inserted.

CAUSE:
BIOS PnP is set to No for the PCI slot that you put the card in.

SOLUTION:
You must enable Plug'n'Play in the BIOS for the PCI slot that the ES/PCI card is in. Power up the PC and go into the BIOS SETUP. Usually you will press the Del key right after power-up. Here is is listing of some of the key combinations used to enter the BIOS setup on startup. You must do this during the first few seconds after you turn on power. If you see the Windows startup, it's too late.

Award Bios=Ctrl-Alt-Esc
AMI Bios and Award Bios and others=Del (most common)
Compaq=F10
Dell=Ctrl-Alt-Enter
Dell=Reset(Twice)
HP Pavillion= Esc then F1
NEC=F2
Phoenix Bios=Ctrl-Alt-S
Phoenix Bios=Ctrl-Alt-Ins
PS/2=Ctrl-Alt-?
PS/2=Ins
Toshiba=Esc
Toshiba=F1

With the Award BIOS you will go to PNP/PCI CONFIGURATION and set PnP OS Installed to Yes.