-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better explaination what chk and fre modes means and how to enable HAXM on Intel. #289
Comments
The difference between checked and free is documented in the HAXM is documented here: Do NOT use original HAXM driver, you need the one shipped with NTVDMx64, as it requires a special build. |
Thanks, Same with HAXM, because i searched for it too and not found any details in mail readme.. Because i would not expect that i have to uninstall intel HAXM, maybe some check if HAXM already instatel and hint to uninstall it in console would be more fail proof too. Question is if i uninstall Intel HAXM package and install yours, would other SW as Qemu on Windows what are using Intel HAXM still work? Im not sure what HAXM is now active. I have install package installed over it ntvdmx64. |
Ahem.. Are you kidding me? The first 2 lines of the readme.txt point you right to the autobuild.txt which contains the description for CHK and FRE builds and build instructions. There can't be a more prominent place to link to it. And you said, you didn't find them? Sorry, but that's ridiculous! autobuild.txt also clearly states:
It also states:
So what does it tell us? It means that you don't have to uninstall the original IntelHaxm driver, it means that NTVDMx64 brings its own driver and upon launching NTVDM, it may stop the original IntelHAXM driver (in case it is named "IntelHaxm", otherwise you would have to stop it using "net stop or via Services.msc") in order to load its own. So, yes, they should be able to coexist on the same system, but can NOT run at the same time (so using qemu and NTVDMx64 concurrently at the same time wouldn't work). The HAXM shipped with NTVDMx64 is not a drop-in replacement to the original Intel HAXM driver, it listenes to another device name which gets only used by the NTVDMx64. |
It depends what readme do you mean, i mean this: Its wall of text, i not expected that there are some "links" to other files. Compiler hints was good enough to not need for search for info in quite a long readme.. Haxm, i would bet, that i tried to find it too and it wasnt there, could be wrong some typo, or i searched hax-m, or something like that, or readme was updated meanwhile, im sorry. Thanks for HAXM explanation i still think that it would be nice to check if haxm is already installed and print 1 more line, how it use together. |
I tried to search what is difference between autobuild-ccpu-chk.cmd and autobuild-ccpu-fre.cmd, but here on github descript i did not found these keyboards, neither i found some readme within downloaded github code.
So i have to search and ask chatgpt that got info that chk is more for debuggin and fre shoul be lighter version. Its this right.
About HAXM i know that is HAXM, i have used with Qemu on Windows in the past.. but its long time. Im unsure what to do enabled it, again and how to test that is really enabled.
I far i remember you have to install HAXM intel package, its not available on AMD cups and disable through bcd Hyper-V... But its enough or some other steps are needed?
The text was updated successfully, but these errors were encountered: