3
  1. Create the Gen 1 machine with less than 512MiB Ram (above requires you to put MaxFileCache=524288 and MaxPhysPage=40000 in the system.ini later).
  2. Add either a virtual or physical IDE drive (physical requires you to go to Disk Management and right-click on the drive and click offline to be detected and doesn't need to be IDE itself).
  3. Add a CD ROM drive from your bootable Windows 98SE iso image.
  4. Boot it, you might either install right away or run a prompt entering setup /is to skip disk check.
  5. Your keyboard should work as long as you don't click inside the window when the setup starts, else your keyboard and mouse get mounted and unusable, so only click the hyper-v title bar, or you might think the window froze which it did not.
  6. You can go trough the whole progress with only your keyboard and without mouse, or you can close and start over from step 4.
  7. When the installation is done you can reboot.
  8. You will be greeted with the fresh new message: enter image description here
  9. So how do you get past this error?

The funny part is that it doesn't happen at the setup, only at start-up (finishing the installation).

I just wanted to share this, because I've not seen anybody else post about it.

4

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.

| improve this answer | |
  • 1
    First startup is likely actually finishing setup I suspect. Try again with say 64 ram and no network card or interface . You can easily re enable that once it is alive. – AndyF Jan 14 at 20:06
  • 1
    Good idea, I tried, but it didn't change much. – Kevin Crans Jan 15 at 9:49
  • 1
    Sorry it did not work. Try disabling all non essential hardware i.e. Sound etc . Then keep doing the F8 thing to get it to start in safe mode. It will complain eventually you cannot completel setup in safe mode however letting it boot cycle then restarting in normal mode may help. Cannot immediately think of anything else sorry. – AndyF Jan 15 at 11:18
  • 1
    I don't know your requirements, but is using another hypervisor like VirtualBox an option? – Ziagl Jan 15 at 11:29
  • 1
    It does (or did) work in Virtual Box although if memory serves the vbox addins disc was not terribly keen on 9x . May require something like vbox 6x or 5x but hopefully you won't have to go that far. – AndyF Jan 15 at 12:09

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.