Skip to main content
Retrocomputing

Return to Answer

added 6 characters in body
Source Link
Ziagl
Ziagl
  • 298
  • 1
  • 8

I recently had the exact same problem with Win98SE on VirtualBox on an AMD CPU. There the solution was to run

vBoxManage.exe modifyvm "Win98" --cpu-profile "Intel Core i5-3570"

vBoxManage.exe modifyvm "Win98" --cpu-profile "Intel Core i5-3570"

I think there is a similar option in Hyper-V to change used CPU profile.

I recently had the same problem with Win98SE on VirtualBox on an AMD CPU. There the solution was to run

vBoxManage.exe modifyvm "Win98" --cpu-profile "Intel Core i5-3570"

I think there is a similar option in Hyper-V to change used CPU profile.

I recently had the exact same problem with Win98SE on VirtualBox on an AMD CPU. There the solution was to run

vBoxManage.exe modifyvm "Win98" --cpu-profile "Intel Core i5-3570"

I think there is a similar option in Hyper-V to change used CPU profile.

Source Link
Ziagl
Ziagl
  • 298
  • 1
  • 8

I recently had the same problem with Win98SE on VirtualBox on an AMD CPU. There the solution was to run

vBoxManage.exe modifyvm "Win98" --cpu-profile "Intel Core i5-3570"

I think there is a similar option in Hyper-V to change used CPU profile.