VirtualBox

Opened 15 years ago

Closed 12 years ago

#2865 closed defect (wontfix)

Unable to start DOS 6.22 or Windows 98 when VT-x is enabled

Reported by: Iker Owned by:
Component: VMM/HWACCM Version: VirtualBox 3.1.6
Keywords: Windows 98 MS-DOS 6.22 Cc:
Guest type: other Host type: Windows

Description (last modified by Frank Mehnert)

It is not possible to start DOS 6.22 or Windows 98 virtual machines when VT-X is enabled. DOS operating system hangs in the startup message (starting ms-dos...) and Windows 98 hangs after some seconds with the splash screen.

Attachments (4)

VBox.log (43.1 KB ) - added by Iker 15 years ago.
MS-DOS 6.22 VM log file
Windows 98-2010-05-03-23-21-11.log (39.3 KB ) - added by Technologov 14 years ago.
Windows 98 on VirtualBox 3.2.0-BETA1.
Win98 VMX-2011-03-17-03-11-44.log (42.2 KB ) - added by Technologov 13 years ago.
Win98 + Unrestricted VMX stucks during OS install. VBox 4.0.4.
Win98-basic-VMX-2011-03-17-03-14-55.log (42.5 KB ) - added by Technologov 13 years ago.
Using basic VMX. VBox 4.0.4. Win98 setup.

Download all attachments as: .zip

Change History (22)

by Iker, 15 years ago

Attachment: VBox.log added

MS-DOS 6.22 VM log file

comment:1 by Sander van Leeuwen, 15 years ago

Summary: Unable to start DOS 6.22 or Windows 98 when VT-x is enabledUnable to start DOS 6.22 or Windows 98 when VT-x is enabled -> retry with 2.1.2

Try again with 2.1.2 please.

comment:2 by Frank Mehnert, 15 years ago

Resolution: fixed
Status: newclosed

Please reopen if this problem persists with 2.1.4.

comment:3 by Ryan Novosielski, 15 years ago

Resolution: fixed
Status: closedreopened

I have this problem with Windows 98 on 2.2.2.

comment:4 by Ryan Novosielski, 15 years ago

I'm sorry, I run 2.2.4 -- my mistake -- same problem there.

comment:5 by Technologov, 15 years ago

This bug looks similar to bug #3317 and bug #5407

-Technologov

comment:6 by Frank Mehnert, 15 years ago

Summary: Unable to start DOS 6.22 or Windows 98 when VT-x is enabled -> retry with 2.1.2Unable to start DOS 6.22 or Windows 98 when VT-x is enabled
Version: VirtualBox 2.1.0VirtualBox 2.2.4

in reply to:  6 comment:7 by frankk74, 14 years ago

Replying to frank: Same problem exists in 3.1.2:

Please update (I know it is old but it should be a simple fix) the win98 template in the following ways:

1) un-enable VT-x 2) un-enable PAE extension

Thanks Guys for a great product!!!!!!!!!!

comment:8 by Iker, 14 years ago

I think the problem happens when 16-bit code has to be emulated. I don't know why, but any OS using 16 bit code has many failures in Virtualbox (MSDOS, WIN95,98,Me). Indeed, I've installed Windows NT 3.51 and works rock solid when using 32-bit apps, but when a 16-bit program is installed on it, it usually fails with memory errors (for example, using IE for NT 3.51, which is a 16-bit browser). However, those OS can run perfectly in Microsoft's Virtul PC (which uses hardware virtualization by default).

I hope somebody finds the error.

Cheers!

comment:9 by Technologov, 14 years ago

Problem still exists in VirtualBox 3.2.0-BETA1.

by Technologov, 14 years ago

Windows 98 on VirtualBox 3.2.0-BETA1.

comment:10 by Sander van Leeuwen, 14 years ago

Component: otherVMM/HWACCM

#3317 marked as a duplicate.

comment:11 by Sander van Leeuwen, 14 years ago

Version: VirtualBox 2.2.4VirtualBox 3.1.6

comment:12 by Technologov, 14 years ago

Two new duplicates found: #6597 and #6686

-Technologov

comment:13 by Frank Mehnert, 14 years ago

Still relevant? Might be fixed with VBox 3.2.10.

comment:14 by Frank Mehnert, 13 years ago

Resolution: fixed
Status: reopenedclosed

No response, closing.

comment:15 by Technologov, 13 years ago

Resolution: fixed
Status: closedreopened

Unfortunately still relevant for v4.0.4, even with "Unrestricted VMX", it fails.

-Technologov

by Technologov, 13 years ago

Win98 + Unrestricted VMX stucks during OS install. VBox 4.0.4.

by Technologov, 13 years ago

Using basic VMX. VBox 4.0.4. Win98 setup.

comment:16 by Technologov, 13 years ago

The two failures are not equal, however, as basic VMX actually proceeds *further*, while "Unrestricted VMX" VM stops very soon in the setup process.

comment:17 by trlkly, 12 years ago

While I still have this problem with Windows 95, I was able to run both DOS 6.22 and Windows 98SE with VT-x and nested paging enabled. DOS worked out of the box. Windows 98SE did crash during the first time I tried to install it, so I booted the bootable CD, but chose to go to a command prompt, then ran D:\SETUP.EXE /ie /im /is and Windows 98SE installed without a hitch.

I don't know if Windows 98 just recovered after the crash, or if those options helped. My guess would be that /im, which disables the conventional (<1024K) memory check, is the one that fixed it. If so, that implies that VirtualBox has a problem dealing with conventional memory.

All of these were the U.S. English version.

I know for sure /is wasn't the problem, as that disables Scandisk, which worked perfectly well in my first install. And I can't see why /ie, which disables the prompt to create a boot floppy, would have had anything to do with it, as that doesn't affect the install until later.

comment:18 by Frank Mehnert, 12 years ago

Description: modified (diff)
Resolution: wontfix
Status: reopenedclosed

You might try to check if this works with VBox 4.1.22 or 4.2.0. Even if this does not work there is not much we can do because Windows 9x fails on modern CPUs due to timing problems.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use