milirobot.blogg.se - january 2023

WINDOWS 98 VIRTUALBOX DRIVERS
WINDOWS 98 VIRTUALBOX DRIVER

So I installed the Hyper-V role on my laptop and attached the XP drive to a new VM and it came right up. I had been running 98 in VMWare Workstation, but when I needed to load up that XP drive, it turned out to be a bear to get VMWare to do anything with a VHD. In order to hold on to the files and configurations on it, I virtualized the drive and the first/easiest/freest option I found was to convert it to a VHD. Long answer: When I finally let go of my WinXP box, it had an IDE hard drive that I couldn't attach to a newer computer. If it can run on an iPhone, then there's got to be a way to run it in Hyper-V. I'm simply fixated on getting it running in Hyper-V. I am not interested in alternative hypervisors to getting a Win98 vm running, I know about alternatives and can implement them when I need to.

Microsoft Windows 98 Second Edition star 4.5.

Microsoft Corporation Windows 8.1 Pro star 4.

I could use VMWare for 98, but I virtualized my old XP box into Hyper-V and Hyper-V and VMWare don't play nice in the same sandbox. Many of my favorite games won't run on an NT kernel. Now if you really want to know why, I have a thing for old games. Or other ideas on what might be causing the problem and how I can work around it. I'm looking for any advice or help on hacking the VM hardware, possibly to remove/disable the PS/2 controller entirely.

WINDOWS 98 VIRTUALBOX DRIVER

When I run a logged boot, the last driver to load is VPD (vpd.vxd - a "virtual printer driver"), which loads successfully. (This might be an intentional fault, since MS no longer supports older MS operating systems on Hyper-V.)

I suspect that there's a fault in Microsoft's emulated PS/2 controller. Windows 98 should be glowing on that (virtual) hardware. Generation 1 virtual hardware emulates an Intel 440bx chipset with PS/2 keyboard and mouse.

WINDOWS 98 VIRTUALBOX DRIVERS

I've also tested a DOS VM (DOS 6.22 runs fine in Hyper-V - go figure) and determined that almost any mouse drivers will cause mouse and keyboard input to fail completely. If I only used the keyboard and didn't touch the mouse (not even moving the cursor) then I would be able to complete setup. I was able to determine, almost by accident, that the mouse was the underlying issue. Given that the hardware is virtual (and the physical hardware is good), this is almost definitely a driver problem.ĭuring Windows Setup, one of the problems I encountered was that the keyboard and mouse would not respond. I've been able to complete setup successfully (with some finagling), but I run into a "Windows Protection Error" when Windows attempts to start for the first time. I'm trying to hack Windows 98 SE to run inside Hyper-V client on Windows 8.1.