Windows 3.1 / MS-DOS Lag on new ASUS TUF Gaming laptop.
Re: Windows 3.1 / MS-DOS Lag on new ASUS TUF Gaming laptop.
What is the status of this? here is the bug report ticket again.... : https://www.virtualbox.org/ticket/21613
Last edited by eg1 on 6. Aug 2023, 14:27, edited 1 time in total.
Re: Windows 3.1 / MS-DOS Lag on new ASUS TUF Gaming laptop.
Could you look through the source code yourself?
Re: Windows 3.1 / MS-DOS Lag on new ASUS TUF Gaming laptop.
Nobody seems to care. It worked fine on my old laptop. I STILL don't know what is causing nested paging to slow down my machine when I run Windows 3.1.
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Windows 3.1 / MS-DOS Lag on new ASUS TUF Gaming laptop.
I won't go so far as to say that nobody cares, there have been DOS hobbyists on the devteam before. But as I already mentioned above - neither DOS and Windows 3.1 are supported. That means that nobody is obliged to jump to attention when you report a problem using them. In addition to which, bug report tickets with no attached logs are pretty much guaranteed to get no response even if the guest is supported.
Re: Windows 3.1 / MS-DOS Lag on new ASUS TUF Gaming laptop.
OK. I will upload some logs later today.
Re: Windows 3.1 / MS-DOS Lag on new ASUS TUF Gaming laptop.
MS=DOS VM Logs. August 6 2023 1.00 PM New York Time.
- Attachments
-
- Logs08062023WithNestedPagingEnabled.zip
- (61.16 KiB) Downloaded 117 times
Re: Windows 3.1 / MS-DOS Lag on new ASUS TUF Gaming laptop.
Please look through the logs carefully. BTW Malwarebytes does not cause this.
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Windows 3.1 / MS-DOS Lag on new ASUS TUF Gaming laptop.
The heardening log shows exit code 0, so no hardening problems.
The VM log only runs for 25 seconds. Did the behavior demonstrate in this half minute?
You must keep aware of the circumstances around here. We on the forum are volunteer fellow Virtualbox users (not Oracle employees), who do this because we like to. We will be happy to help where we can. Some of us are deep in the source code. Some, like me, are very much not.
You are a fellow Virtualbox user, who needs help. You do not have an Oracle support contract, which you would definitely remember having purchased, considering how much one costs.
So you are entitled to zero (0) support, unless you ask nicely here on the forums and we can help if we can understand the problem.
However, we will not tolerate being bumped constantly. Once a week for a month, then you might as well let it go, since it will mean that no one here knows what the problem is.
BTW, do all VMs do this or only the 3.1 VM?
Also, of it was working on the new laptop but stopped, whatever happened at that time still needs to be tracked down.
The VM log only runs for 25 seconds. Did the behavior demonstrate in this half minute?
Ticket 21613, on 8/6/2023 wrote:by eg1, 8 weeks ago
Attachment: Logs.zipadded
Windows 3.1 Dos Logs
To the ticket, my good person, to the ticket. The devs don't come here. These are user forums.
You must keep aware of the circumstances around here. We on the forum are volunteer fellow Virtualbox users (not Oracle employees), who do this because we like to. We will be happy to help where we can. Some of us are deep in the source code. Some, like me, are very much not.
You are a fellow Virtualbox user, who needs help. You do not have an Oracle support contract, which you would definitely remember having purchased, considering how much one costs.
So you are entitled to zero (0) support, unless you ask nicely here on the forums and we can help if we can understand the problem.
However, we will not tolerate being bumped constantly. Once a week for a month, then you might as well let it go, since it will mean that no one here knows what the problem is.
BTW, do all VMs do this or only the 3.1 VM?
Also, of it was working on the new laptop but stopped, whatever happened at that time still needs to be tracked down.
Re: Windows 3.1 / MS-DOS Lag on new ASUS TUF Gaming laptop.
But the bug report ticket never got any replys. Should I redo the logs? If so I will do it now and come back to you.
Last edited by eg1 on 7. Aug 2023, 00:47, edited 1 time in total.
Re: Windows 3.1 / MS-DOS Lag on new ASUS TUF Gaming laptop.
New log files
- Attachments
-
- Logs08 06 2023 2 19 39 PM EST Nested Paging Disabled.zip
- (63.31 KiB) Downloaded 122 times
-
- Logs08 06 2023 2 06 30 PM EST Nested Paging Enabled.zip
- (80.25 KiB) Downloaded 127 times
Last edited by eg1 on 7. Aug 2023, 01:46, edited 2 times in total.
Re: Windows 3.1 / MS-DOS Lag on new ASUS TUF Gaming laptop.
Yes, this happens with nested paging enabled, and on all VMs, I created about 50 VMs.
Please share this bug ticket online: https://www.virtualbox.org/ticket/21613
Please share this bug ticket online: https://www.virtualbox.org/ticket/21613
Last edited by eg1 on 7. Aug 2023, 00:33, edited 1 time in total.
-
- Volunteer
- Posts: 5678
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Windows 3.1 / MS-DOS Lag on new ASUS TUF Gaming laptop.
I have a few unrelated remarks:
In the Bugtracker ticket, you provided links to video screen captures that were meant to show the lag, but they cannot be accessed without using a Google account. I'd suggest to either provide them unconditionally, or to describe what "lags the hosts framerate a bit" really means.
Additionally, you changed the ticket status to "awaitsfeedback", which is normally used by a VirtualBox developer to ask the bug reporter for additional information. In consequence, it could happen that no VirtualBox developer will look at the ticket, even if they were interested. I'd suggest to change the status back.
Your newest log files seem to show more differences than you've been talking about: The VM with Nested Paging disabled booted from the virtual hard disk image. The VM with Nested Paging enabled booted from several floppy disk images, had Nested VT-x/AMD-V enabled (why?) and complained about an unsigned software called ExplorerPatcher trying to invade the VirtualBoxVM memory address space.
In the Bugtracker ticket, you provided links to video screen captures that were meant to show the lag, but they cannot be accessed without using a Google account. I'd suggest to either provide them unconditionally, or to describe what "lags the hosts framerate a bit" really means.
Additionally, you changed the ticket status to "awaitsfeedback", which is normally used by a VirtualBox developer to ask the bug reporter for additional information. In consequence, it could happen that no VirtualBox developer will look at the ticket, even if they were interested. I'd suggest to change the status back.
Your newest log files seem to show more differences than you've been talking about: The VM with Nested Paging disabled booted from the virtual hard disk image. The VM with Nested Paging enabled booted from several floppy disk images, had Nested VT-x/AMD-V enabled (why?) and complained about an unsigned software called ExplorerPatcher trying to invade the VirtualBoxVM memory address space.
Re: Windows 3.1 / MS-DOS Lag on new ASUS TUF Gaming laptop.
Uninstalling ExplorerPatcher does not fix this, bug report video capture files: https://easyupload.io/m/wr3pju
Last edited by eg1 on 7. Aug 2023, 00:43, edited 2 times in total.
Re: Windows 3.1 / MS-DOS Lag on new ASUS TUF Gaming laptop.
No matter if it runs Windows 3.1 or MS-DOS it still lags. Even if VT and PAE/NX are disabled.
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Windows 3.1 / MS-DOS Lag on new ASUS TUF Gaming laptop.
Are all your VMs 3.1 & MSDOS?
Also, you "reported" this post of yours viewtopic.php?p=539240#p539240 as off-topic. Was that a mistake, or does that post have incorrect information?
Also, you "reported" this post of yours viewtopic.php?p=539240#p539240 as off-topic. Was that a mistake, or does that post have incorrect information?