Hi,
It shouldn't.
How about providing some log? Like attaching vmware.log that you can find in the virtual machine folder.
Please do not copy&paste log contents into a post here as it makes the thread very difficult to navigate and read. You can find an attach link at the bottom right area when posting. Note that this is only available in the discussion thread, not in the inbox.
--
Wil
Hi,
The log says Windows 8.0 and VMware Workstation 6.0.5.
The CPU isn't even recognized, but your host name suggests that you are running off a GA-Z270X-UD5 (rev. 1.0) | Motherboard - GIGABYTE
If you enabled hardware virtualization in the BIOS then did you also powercycle (eg. unplug the power to make that setting active) ?
Besides that.. Windows 8.0 is not supported anymore by MS AFAIK and Workstation 6.0.5 has been retired for almost 6 years (http://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/support/product-lifecycle-matrix.pd... ), but you are running of recent hardware.
So my suggestions to getting this to work properly is to:
- update your Windows 8.x until you are current
- then install VMware Workstation 12.5.7
If it then still does not work, attach the vmware.log while at that stage again and it will normally have better information on what went wrong.
But I would expect that it will work after the above updates.
--
Wil
Hi,
I am running windows 10
That's the problem with an old product as Workstation 6.0.5, it might misreport on whole range of OS calls, it said "host version is 6.2.9200" which equals to Windows 8.0 and that's not because of problems in the code of Workstation 6.x, but because the Windows API for retrieving host OS version has changed
That is just one of the things in Windows that changed.
Running Workstation 6.x on Windows 10 most certainly is not supported as WS6 was retired years before Windows 10 was released.
As for the "Windows 98 is not supported on Workstation 12.5" you have to realize that that is just the official statement.
VMware will try to keep that to work, but they stopped doing extensive tests on that platform to guarantuee that it works.
A VMware employee worded it a bit better as I did, but I can't find his quote in a search.
If an update breaks things then you can either go back a revision or tweak some settings.
As virtualization is very tightly coupled with the host OS, you really need to keep up to date with VMware Workstation if you want to run it on a current host OS and hardware platform.
If you don't want to do that, then you really are "on your own".
--
Wil
Ok.
I think the old VM with 1GB RAM might have a bit too much RAM. That wasn't a common configuration at Win98 time.
Max RAM supported by Windows 98?? | [H]ard|Forum
For testing I would not go beyond the 512MB RAM.
That doesn't explain why your other VM with 256MB RAM has the same problem though.
Please recheck that Intel Virtualization Technology is enabled in your EFI/BIOS.
Did you power cycle already?
The above is the most common reason for this particular error!
If you are sure that VT-x is enabled and you did power cycle the machine then can you try with guest OS set to "Other" and see if that helps?
If that still doesn't help, but the guest OS back to Win98 and try "Binary Translation" mode for the hypervisor instead of automatic.
--
Wil