ntvdmx64
ntvdmx64 copied to clipboard
leecher1337
Can't uninstall ntvdmx64 and reinstall
Ntvdmx64 was removed from the program list using windows uninstall. but there are remants still there somewhere. When I try to reinstall, it get error. " it seems you have ntvdmx64 already on your system". What file I have to manually delete so that I may reinstall ntvdmx64?
also I thought you made additional updates past aug 2022, but that seems to be the latest
https://github.com/leecher1337/ntvdmx64/issues/159#issuecomment-1399428458
i spent 2 days trying to get ntvdmx64 uninstalled. Part of the problem was that good old win 11 file explorer was not finding all the files on my system. I could literally go to the folder and see the file, but search would not find it. I wound up deleting a bunch of files in multiple directories and then re-installed ntvdmx64. but I had to manually point to the directory that several files were in to get it to install. Lastly , when I tried to run it, apparently something went wrong as I got the standard win 11 error, can't run this program on win 11. That was yesterday. So i will try again to uninstall.
I am going to attempt to compile your most recent updates. But I haven't compiled any software in decades so my skills are kaput. So I am not too optimistic. I find I now need step by step instructions to get it right.
This has actually taken me longer to get up and running than buying a new dell workstation that still supports legacy 32 bit and installing win 7 32 bit.
Finally I still find your ntvdm to be the best option over any dos emulator that will allow working with windows programs and dos programs at the same time on a new pc that will only run 64 bit os. If I had lots of money and time, I would just convert all my dbase over to windows. But what fun would that be to give in to the microsoft gods?
You are doing a great job.
Thanks for all your help.
At 08:18 AM 1/31/2023, you wrote:
https://github.com/leecher1337/ntvdmx64/issues/159#issuecomment-1399428458#159 (comment)
Reply to this email directly, https://github.com/leecher1337/ntvdmx64/issues/214#issuecomment-1410674502view it on GitHub, or https://github.com/notifications/unsubscribe-auth/AWPXDHQQMEDVGT7EGG55KATWVE3NVANCNFSM6AAAAAAT6JG23Qunsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
-- This email has been checked for viruses by AVG antivirus software. www.avg.com
I still wonder what caused the uninstallation to fail in a way that it was unable to remove ntvdm.exe and a bunch of files, I never had such a constellation in my test runs. As said, normally it doesn't hurt if you have the files except ntvdm.exe in your Windows-directory sticking around as a new installation will overwrite or keep them anyway, so removing ntvdm.exe should be enough for reinstallation. The crucial part is the loader ldntvdm.dll, it is the only component that can interfere with your system on a failed uninstallation and if it doesn't load properly, it's also the component that is crucial to be able to start up the NTVDM on 16 bit applications. It's also cannot hurt to remove the following registry paths, if they exist, in order to force the loader to update the symbols: HKEY_LOCAL_MACHINE\Software\ldntvdm HKEY_LOCAL_MACHINE\Software\Wow6432Node\ldntvdm HKEY_CURRENT_USER\Software\ldntvdm HKEY_CURRENT_USER\Software\Wow6432Node\ldntvdm
Don't worry about compiling, most stuff should work automatically, if you have all necessary files in your build directory, the autobuild-script should take care of most stuff.
Of course, 32bit Windows with native NTVDM is preferred over NTVDMx64, if it's possible for the user, as you have real V86 mode performance.
If you are able to find out why your uninstall failed are have a scenario on how to reproduce it, I would be interested in the cause, because I never heard of such a case yet where files stayed on the system.
I finally got ntvdmx64 working and was able to install and uninstall the normal way. I got fed up with avg so I deleted it temporarily. that was causing the install problem. it kept putting ldntvdm in quarantine and failing the install with errors and preventing un install.
I installed ccpu version, tested dbase and dcom. they work , slow as a snail.
I uninstalled ccpu and installed haxm. it said installed,but when i ran dbase, error " haxm not installed" . I tried uninstalling and in stalling,. same result. i installed ccpu again and it works ok. i will try your suggestions of earlier emails to net start IntelHaxmNtvdm
I have word 2.0 installed, but now that has failed to open. That's a win 3.1 program so it should work , but it doesn't. it did work before when I installed the old ntvdmx64. when running dbase and other 16 bit s/w i run into the problem of the quick edit function not staying set. I set it the fist time I open the program. Then when I close and reopen it, the quick edit is unchecked. This is what it looks like on win 7 32 bit, similar on win 11 64 bit.
Emacs!
However I can only get At 09:41 AM 1/31/2023, you wrote:
I still wonder what caused the uninstallation to fail in a way that it was unable to remove ntvdm.exe and a bunch of files, I never had such a constellation in my test runs. As said, normally it doesn't hurt if you have the files except ntvdm.exe in your Windows-directory sticking around as a new installation will overwrite or keep them anyway, so removing ntvdm.exe should be enough for reinstallation. The crucial part is the loader ldntvdm.dll, it is the only component that can interfere with your system on a failed uninstallation and if it doesn't load properly, it's also the component that is crucial to be able to start up the NTVDM on 16 bit applications. It's also cannot hurt to remove the following registry paths, if they exist, in order to force the loader to update the symbols: HKEY_LOCAL_MACHINE\Software\ldntvdm HKEY_LOCAL_MACHINE\Software\Wow6432Node\ldntvdm HKEY_CURRENT_USER\Software\ldntvdm HKEY_CURRENT_USER\Software\Wow6432Node\ldntvdm
Don't worry about compiling, most stuff should work automatically, if you have all necessary files in your build directory, the autobuild-script should take care of most stuff.
Of course, 32bit Windows with native NTVDM is preferred over NTVDMx64, if it's possible for the user, as you have real V86 mode performance.
If you are able to find out why your uninstall failed are have a scenario on how to reproduce it, I would be interested in the cause, because I never heard of such a case yet where files stayed on the system.
Reply to this email directly, https://github.com/leecher1337/ntvdmx64/issues/214#issuecomment-1410802963view it on GitHub, or https://github.com/notifications/unsubscribe-auth/AWPXDHQ4VLINZBGOLIPB4V3WVFFDVANCNFSM6AAAAAAT6JG23Qunsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
-- This email has been checked for viruses by AVG antivirus software. www.avg.com
Yeah, Antivirus Software is a real pest. No idea why so many ppl are using snakeoil, it just slows down the system to a crawl and often is worthless against new threats, thus vendors implemented plain stupid heuristics to detect new threats which in turn is affecting legitimate targets like NTVDMx64. I guess there is no solution to this dilemma.
Hm, regarding Word 2.0 for Windows, I wonder if you really opened it with NTVDMx64, because HAXM build currently doesn't support WOW16, only CCPU build does and you were using HAXM build for performance Reasons because of DBASE. So maybe you had installed WineVDM for running Win16 applications? This constellation should work.
Regarding quiclkedit, maybe you are affected by this patch? https://github.com/leecher1337/ntvdmx64/commit/60a71f222702671a862ca85da701441bb4ac2c4b But it has been made already in 2020, did you use such an old version? Quickedit default normally can be specified in .pif file for given application.