HP Computer and 98 Install 2

[jisoo22]

Hello all,

I have a strange problem. I recently tried to wipe and reload Windows 98SE on an old HP Pavilion 8275. The install with ok until it tried to start for the first time. The computer got as far as the Windows 98 splash screen and then kicked into DOS with an error message saying "C:\WINDOWS\SYSTEM\Vmm32.vxd missing/unable to load". I tried to replace this manually by copying that same file from another 98 machine and putting it into the system directory via DOS but no dice. Does anyone know of any issues with this?

Thanks,
Jisoo22

 

[Snickle]

Last time I saw that message was when there was a bad chip on a memory module. Win98 would install but not run, replaced the memory and it was then okay.

 

[Crustyoldbloke]

Hello Jisoo

Found in Windows 9x machines, VMM32.vxd is the virtual device driver library that contains virtual device driver files needed for system start up.

VMM32.vxd is different for every machine; therefore, if it gets corrupted, it cannot be copied from another computer; it'll need to be rebuilt.

Armed with that knowledge, you need to reinstall Win98SE and hopefully this file will be found when it starts firt time. For a more in depth view of this file, see the link below:

http://support.microsoft.com/default.aspx?scid=KB;en-us;q174018

Regards
Phil

 

[jisoo22]

Thanks for the info Phil, unfortunately I tried wiping and reloading twice already and no dice. The same error keeps popping up. Are there any suggestions? The last time I reloaded, I did get an error while installing. The mplayer.exe file didn't install properly (but I've used this cd before and never had a problem).

Thanks,
Jisoo22

 

[1zman]

I would look at the memory as previously mentioned. Is there any way you can use one stick or temp use some to try it out? Had this same problem on a machine. It had one bad ram stick. Replaced and the error went away. Of course I had to wipe and reload windows again.

Let us know what you find out.
Good Luck
Zman

 

[GeekBros]

Greetings Jisoo22,

I'm a former 3rd level tech for HP. I did a 6 month contract with them at the roll-out of Win 98 doing issue tracking. Anything that came in to the call center that wasn't already addressed, I was on the team that hunted down and resolved (or at least addressed) the issue. This one was HUGE. I'll try to 'nutshell' this as best as I can. Ready? Here we go...
When a drive is installed in any HP system, prior to loading the software bundle and OS, it is low-level "tatooed" with proprietary info that corresponds with the restore disks identifying itself as an HP drive which then allows the system to go ahead and proceed with installation. It's HP's way of protecting their software bundles which ship with their systems. Without the encoding anyone could use the accompanying disks to pirate the programs contained on them. Also in the 'tatoo' is the info related to the make-up of the system, its components, etc. This info can, (not always) corrupt an OS install when it is done via a retail version of Win 98 rather than using the oem disk that came with the system. As Phil mentioned, the VMM32.VXD file is built on a per-system basis. Each one is unique. When Windows setup is building this file, it looks for hardware info in several places including the BIOS of course. Many times this low-level 'tatoo' dupes the operating system into believing that it's the BIOS and can provide incorrect info about the system's makeup. If you are indeed using a retail version of Win 98 rather than the disk that came with your PC AND you've tried the other suggestions prior to mine, the next step is to low-level format your drive to wipe out the 'tatoo' thereby returning it to a normal, everyday, run-of-the-mill IDE drive. It's kinda like rescuing it and un-brainwashing it Every drive mfr. makes available for free d-load, a set of tools or utilities which performs the task of "low-level formatting' their drives. Simply d-load the utility, follow the instructions and voila. You will have a sqeuaky clean hard drive ready for any kind of formatting and FAT table you desire. If this doesn't work you've tried the ssuggestions set forth before mine, the problem, though extremely rare, most probably is originating within the memory bus on your board. I've seen this to be the case twice in 10 years of building/supporting systems. Good Luck and PLEASE let us know how you make out on this one.

Regards,
Steve McLean (Owner)
Geek Bros. Computers
steve@geekbros.biz

Side Note: The term 'low-level formatting' is not really what you're doing to the drive. However, it has become a term acknowledged industry-wide as the process of writing 0's to every sector of a hard drive.

 

[jisoo22]

Hi Steve,

That's extremely interesting information that you've revealed to me and would probably explain the problem that I've been having. I am indeed using a full retail version of Windows 98SE and after reloading it three times, swapping out all sticks of memory (reinstalling after each swap) and wasting more then several hours, I resolved the issue by physically removing the hard drive from the HP and placing it in my own custom box and reloaded that way. Installation went flawlessly and booted and detected all the parts in the HP computer. This would certainly validate your low-level tatoo format concept. I believe I'd had this issue before with a similar old Compaq computer, do you think they've implemented something like that also? At least now I know the short-cut to do it, a "low level format". Your explanation is very much appreciated by myself and I'm sure countless other frustrated at-home techies =)

Thanks a bunch!
Jisoo22

 

[GeekBros]

T'was my pleasure. I regret that I didn't read the thread earlier so as to have possibly saved you some time and a few gray hairs

As for the Compaq - yes indeedee! As well as Dell, IBM and especially eMachines, which requires a whole different line of combat to overcome this situation. But then you gotta remember, eMachines is the "Born again"...... dare I say it.... Okay, I'll just whisper it.... packard-bell!

Glad this was helpful to you.

Regards,

Steve