robertmo3wrote on 2025-04-04, 08:24:you have to
disable "Windows Hypervisor Platfrom" from windows components and reboot
https://winsides.com/wp-content/uploads/20 […] Show full quote
robertmo3wrote on 2025-04-04, 09:37:one more thing to check
this is also some cpu virtualization feature that has to be enabled in bios […] Show full quote
one more thing to check
this is also some cpu virtualization feature that has to be enabled in bios
then i don't know
make sure neither vmware nor virtualbox, nor rready is running in the bacground
try turning it on, reboot, check what qemu says and turn it off again, reboot and check qemu
Virtualization is already turned on, I turn it on after every bios update and I can definitely run vmware.
robertmo3wrote on 2025-04-04, 09:37:one more thing to check
this is also some cpu virtualization feature that has to be enabled in bios […] Show full quote
one more thing to check
this is also some cpu virtualization feature that has to be enabled in bios
then i don't know
make sure neither vmware nor virtualbox, nor rready is running in the bacground
try turning it on, reboot, check what qemu says and turn it off again, reboot and check qemu
Virtualization is already turned on, I turn it on after every bios update and I can definitely run vmware.
robertmo3wrote on 2025-04-04, 09:37:one more thing to check
this is also some cpu virtualization feature that has to be enabled in bios […] Show full quote
one more thing to check
this is also some cpu virtualization feature that has to be enabled in bios
then i don't know
make sure neither vmware nor virtualbox, nor rready is running in the bacground
try turning it on, reboot, check what qemu says and turn it off again, reboot and check qemu
Virtualization is already turned on, I turn it on after every bios update and I can definitely run vmware.
I'll try it on a different machine.
Nope, the Intel haxm mode doesn't work on an i7 2600. Microsoft Defender repeatedly scans the app on both machines. There's no way to disable it, it turns back on. That might be why it's not working.
I am trying to set my wheel's paddles as the shift up / down keys for IndyCar Racing II. Pressing ctrl + f1, the usual keymapper prompt, just causes the game to freeze. I then have to alt+ctrl+delete to get out of the game.
What is the keyboard shortcut for the keymapper? Or, why does dosbox freeze when I select ctrl+f1?
Ctrl+F1 invokes dosbox settings, since it's not speedy3d mode, it can work in background while you see in game frame.
If you want use ctrl+F1 as in game key? Use different keys for now, maybe it will be fixed to enable those keys too, by having option to disable them for instance dosbox.
If I am not wrong with it.
I am trying to set my wheel's paddles as the shift up / down keys for IndyCar Racing II. Pressing ctrl + f1, the usual keymapper prompt, just causes the game to freeze. I then have to alt+ctrl+delete to get out of the game.
What is the keyboard shortcut for the keymapper? Or, why does dosbox freeze when I select ctrl+f1?
Thank you.
Thanks @Raven-05.
If you followed @gplaps guide :
1)In the dos tab of rlauncher, click "dosbox settings"
2) dosbox-rendition.conf should open in notepad. At the bottom of this file there should be the line
1 IndyCar.Exe > filename
Filename is a name of a temporary file.
Add a rem and a space before that line., so it says
1 Rem indycar.Exe>filename
3) Save this file and run dosbox. You should be able to run press [ctrl+F1] when dosbox starts and configure the mapping.
4) Once this is configured, you should be able to click "dosbox settings" and remove the rem, save the file and restart dosbox. Icr2 should autorun again with the mapping enabled.
Alternatively you should be able to [ALT +TAB] to the dosbox console and press [CTRL+F1] while the game is running, map your keys and then [ALT +TAB] back to the game window. This should also work. There are two dosbox console windows, you need to pick the one that says c:\indycar.exe > filename.dmpicr2 has logged its memory usage (in KB) to.
Last edited by sharangad on 2025-04-05, 04:30. Edited 1 time in total.
https://github.com/intel/haxm :
"HAXM runs as a kernel-mode driver on the host operating system, and provides a KVM-like interface to user space, thereby enabling applications like QEMU to utilize the hardware virtualization capabilities built into modern Intel CPUs, namely Intel Virtualization Technology."
check if it is enabled in task manager -> performance tab -> cpu -> Virtualization
and also try the tool they recommend in previous link: https://www.intel.com/content/www/us/en/suppo … processors.html
"You can use the Intel® Processor Identification Utility to verify if your system is capable of Intel® Virtualization Technology.
Using the tool, Select the CPU Technologies tab. See if the Intel® Virtualization Technology options are checked or not."
Last edited by robertmo3 on 2025-04-05, 07:20. Edited 1 time in total.
https://github.com/intel/haxm :
"HAXM runs as a kernel-mode driver on the host operating system, and provides a KVM-like interface to user space, thereby enabling applications like QEMU to utilize the hardware virtualization capabilities built into modern Intel CPUs, namely Intel Virtualization Technology."
check it it is enabled in task manager -> performance tab -> cpu -> Virtualization
and also try the tool they recommend in previous link: https://www.intel.com/content/www/us/en/suppo … processors.html
"You can use the Intel® Processor Identification Utility to verify if your system is capable of Intel® Virtualization Technology.
Using the tool, Select the CPU Technologies tab. See if the Intel® Virtualization Technology options are checked or not."
I've already checked, it's enabled in the bios and hyper-v should be disabled. But I'll recheck in a bit.