Windows 98 Virtual Machine Problems

[Faraday3]

Good afternoon,

I am having some problems with my recently purchased version of VMware Workstation 7.1.1. I am running a Windows 98 Virtual Machine that was original installed in VMware Workstation 4.0. I upgraded the *.vmx file by going to VM -> Upgrade or Change Version and choosing the Hardware Compatibility to be "Windows 6.5-7.x." I then chose "power on this virtual machine."

After that, it started up. However, it says that it is searching for PCI-to-PCI Bridge. After hitting cancel 32 times, it asks for PCI System Peripheral, then PCI Universal Serial Bus, then PCI Ethernet Controller, then PCI Multimedia Audio Device, then PCI Universal Serial Bus again. After hitting cancel for all of these, the Windows 98 Virtual Machine starts and runs smoothly. I am able to work and do everything that I need to do within the Virtual Machine.

The major problem comes when I shut down the virtual machine. By going to Start -> Shutdown, I close the Windows 98 Virtual Machine. At this point, if I try to power the Virtual Machine back on it comes up with an error message that says "snapshots are not available for this virtual machine." If I look inside the contents of my *.vmx file, it is wiped completely empty and all the settings are lost. Luckily I have a backup of my *.vmx file. But going through all of this is a huge hassle every time I need to use VMware.

Please help,

Faraday

[Faraday3]

I should also include some *.vmx files. First, here is the original VMware 4.0 vmx file:

config.version = "7"

virtualHW.version = "3"

memsize = "192"

ide0:0.present = "TRUE"

ide0:0.fileName = "Windows 98.vmdk"

ide1:0.present = "TRUE"

ide1:0.fileName = "auto detect"

ide1:0.deviceType = "cdrom-raw"

floppy0.fileName = "A:"

Ethernet0.present = "TRUE"

Ethernet0.connectionType = "hostonly"

sound.present = "TRUE"

sound.virtualDev = "es1371"

sound.fileName = "-1"

displayName = "Windows 98"

guestOS = "win98"

priority.grabbed = "normal"

priority.ungrabbed = "normal"

uuid.location = "56 4d 40 db a2 1e c6 35-32 e3 01 e2 bf 53 b0 19"

ethernet0.addressType = "generated"

ethernet0.generatedAddress = "00:0c:29:53:b0:19"

ethernet0.generatedAddressOffset = "0"

tools.remindInstall = "FALSE"

uuid.bios = "56 4d 40 db a2 1e c6 35-32 e3 01 e2 bf 53 b0 19"

parallel0.present = "TRUE"

parallel0.fileName = "LPT1"

ide1:0.startConnected = "TRUE"

tools.syncTime = "FALSE"

undopoints.seqNum = "0"

ide0:0.mode = "persistent"

ide0:0.redo = ".\Windows 98.vmdk.REDO_a02704"

undopoint.restoreFromCheckpoint = "FALSE"

undopoint.checkpointedOnline = "FALSE"

undopoint.protected = "FALSE"

[Faraday3]

And here is the vmx file after I upgrade it to 7.1.1

<br>

.encoding = "windows-1252"

config.version = "8"

virtualHW.version = "7"

memsize = "192"

ide0:0.present = "TRUE"

ide0:0.fileName = "Windows 98.vmdk"

ide1:0.present = "TRUE"

ide1:0.fileName = "auto detect"

ide1:0.deviceType = "cdrom-raw"

floppy0.fileName = "A:"

Ethernet0.present = "TRUE"

Ethernet0.connectionType = "hostonly"

sound.present = "TRUE"

sound.virtualDev = "es1371"

sound.fileName = "-1"

displayName = "Windows 98"

guestOS = "win98"

priority.grabbed = "normal"

priority.ungrabbed = "normal"

uuid.location = "56 4d 40 db a2 1e c6 35-32 e3 01 e2 bf 53 b0 19"

ethernet0.addressType = "generated"

ethernet0.generatedAddress = "00:0c:29:53:b0:19"

ethernet0.generatedAddressOffset = "0"

tools.remindInstall = "FALSE"

uuid.bios = "56 4d 40 db a2 1e c6 35-32 e3 01 e2 bf 53 b0 19"

parallel0.present = "TRUE"

parallel0.fileName = "LPT1"

ide1:0.startConnected = "TRUE"

tools.syncTime = "FALSE"

undopoints.seqNum = "0"

ide0:0.mode = "persistent"

ide0:0.redo = ".\Windows 98.vmdk.REDO_a02704"

undopoint.restoreFromCheckpoint = "FALSE"

undopoint.checkpointedOnline = "FALSE"

undopoint.protected = "FALSE"

ide1:0.autodetect = "TRUE"

usb.present = "TRUE"

sound.autodetect = "TRUE"

virtualHW.productCompatibility = "hosted"

pciBridge0.present = "TRUE"

ehci.present = "TRUE"

pciBridge4.present = "TRUE"

pciBridge4.virtualDev = "pcieRootPort"

pciBridge4.pciSlotNumber = "21"

pciBridge4.functions = "8"

pciBridge5.present = "TRUE"

pciBridge5.virtualDev = "pcieRootPort"

pciBridge5.pciSlotNumber = "22"

pciBridge5.functions = "8"

pciBridge6.present = "TRUE"

pciBridge6.virtualDev = "pcieRootPort"

pciBridge6.pciSlotNumber = "23"

pciBridge6.functions = "8"

pciBridge7.present = "TRUE"

pciBridge7.virtualDev = "pcieRootPort"

pciBridge7.pciSlotNumber = "24"

pciBridge7.functions = "8"

vmci0.present = "TRUE"

[continuum]

I would recommend NOT to upgrade virtual machines with Win 9x to version 7.

IMHO Win98 VMs should not use virtualhardware higher then version 6




_________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

[Faraday3]

I was forced to upgrade my operating system from Windows XP to Windows 7 and VMware Workstation 4.0 is not compatible with Windows 7.

[continuum]

yes - I know - but this does not change a bit on my last reply




_________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

[Faraday3]

You are right, it is certainly not desirable to run the Windows 98 VM in VMware 7.0, but this is something I must work out.

[continuum]

I think you missunderstand.

Run WS 7 - no problem with that.

But in case of Win98 VMs do NOT use virtualhardware 7 - instead leave it at version 6.

Version 7 introduces a bunch of pci-bridges and other stuff that is not nice to have in a Win98 VM.

By the way - your wiped vmx-file.

This has nothing todo with the win98 issue.

This can also happen with any other guests in case the VM crashes in an unlucky moment.

To help yourself when this hapens again always keep your old vmware.logs as they can be used to recreate the vmx-file in case it is necessary.

See http://sanbarrow.com/vmdk-howtos.html#restorevmx




_________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

[Faraday3]

I think I got it to a point where I'm happy. I got the support staff to direct me to the VMware vCenter Converter Stand Alone Client. In that I converted my 4.0 vmx file to a 7.0 vmx file, clicked through all the PCI-to-PCI bridge errors. Additionally, I set my snapshots manager to "Take a New Snapshot" each time I shut down. While it can amass a large amount of snapshot files, it seems to work. Do you see a problem with this option?

[continuum]

Additionally, I set my snapshots manager to "Take a New Snapshot" each time I shut down.

Oh dear - this means asking for trouble.

This stupid dangerous option should have never been added to Workstation IMHO.

Please , please for your own good - only take snapshots in this conditions:

- you are not under the influence of alcohol or drugs or an angry husband

- you really plan to do something next that can go wrong [ eg windows update ...

The less snapshots you have tyhe faster and more stable is your VM

By the way - the advice from support was a bad one IMHO

I would have disabled all the pcibridges and would only use virtual hardware mark 6

But who am I to argue against support

_________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

[Faraday3]

Haha. Ok. I tried doing what you suggested. Upgraded it to VMware 6.0 and it still corrupts the vmx file after powering on and shutting down. Do you see anything suspicious in my vmx file that I posted above?

[continuum]

yes - this line needs special care

ide0:0.redo = ".\Windows 98.vmdk.REDO_a02704"

I am in a hurry right now - will check back later.

I am curious about the wiped vmx-files ...

Ulli




_________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

[Faraday3]

My question has been answered and it seems to be my fault and something a lot smaller than I originally thought.

My virtual machine folder was placed in a shared folder across a network with my company.  If I right-click the destination of this folder, it's not necessarily on my C:\ drive but rather on a net work //drive type thing.  For some reason, this presented major problems to VMware.  When I transferred all the files to a local C:\ folder, everything worked great.

Thanks for everybody's suggestion.  Hopefully this is something that VMware could tackle for a future update.

[meatngreenz]

the pci to pci bridge appears to be in a loop when you are installing but it actually installs about 20-25 pci to pci bridge devices.

Just kkep hitting the install button

I also upgraded a a windows 98 vm and a windows nt4. this is what i encountered with both devices

[continuum]

If necessary you can remove those devices by editing the vmx-file