-
Notifications
You must be signed in to change notification settings - Fork 80
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
Can Not Install on Windows 10 Professional 64Bit. #101
Comments
Hi, Do you get a dialog asking "Do you want to install WOW32 (Win16 application) support?" prior to the error message? Did you check your Antivirus program if it eliminated the ldntvdm.dll loaders? Unfortunately, the 32bit loader is always detected as a Virus false-positive and therefore Windows Defender etc. tend to remove it or even deny access to the loader .dll files. Copy I recommend using the latest loaders from this repository, as I recently fixed a bad handle leak bug. Run To install the AppInit hooks for the loader. |
Leecher1337,
I actually shut-off Avast (my anti-virus) during the install. I will print
this message out and see if these steps work.
Thanks for your quick response and help,
John Riley
…On Tue, Aug 4, 2020 at 1:51 PM leecher1337 ***@***.***> wrote:
Hi,
Do you get a dialog asking "Do you want to install WOW32 (Win16
application) support?" prior to the error message?
WOW32 support is not needed for DOS-only applications, just 16bit Windows
applications (where WineVDM is a better choice anyway).
Did you check your Antivirus program if it eliminated the ldntvdm.dll
loaders? Unfortunately, the 32bit loader is always detected as a Virus
false-positive and therefore Windows Defender etc. tend to remove it or
even deny access to the loader .dll files.
To check, if the loaders are present or install them manually:
Copy
ntvdmpatch\release\ldntvdm\syswow64\10.0\ldntvdm.dll -> C:\windows\syswow64
ntvdmpatch\release\ldntvdm\system32\10.0\ldntvdm.dll ->
C:\windows\system32\
I recommend using the latest loaders from this repository, as I recently
fixed a bad handle leak bug.
If antivirus cries, ensure to tell it to leave the loader alone and
permanently accept the files on the system.
Then also ensure that the loader is installed in AppInit and that AppInit
is allowed.
Run
ntvdmpatch\release\reg\appinit.reg
ntvdmpatch\release\reg\ldntvdm.reg
To install the AppInit hooks for the loader.
This in short describes the manual loader installation process in case the
rest of the installation process for installing the ntvdm-files in your
System32 and Syswow64 directories worked.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#101 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIUCSF467N42TSXWU5FA23DR7BKDRANCNFSM4PUSNFFQ>
.
|
Leecher1337, Using the files you said to use fixed my issue! Thanks again, for your time and effort! John Riley |
So, I've installed using the binary files found here: http://www.columbia.edu/~em36/ntvdmx64.html
I installed once or twice and was getting this error:
Then it would give me this:
After it still didn't work I reached out to a friend in California, who has it working, on nearly the same laptop that I have. We tried together 3 times. I own ProBoard Bulletin Board System software, and was going to test the latest version in a Windows 64Bit environment, but every time I go to run PROCFG.EXE of the ProBoard BBS software, I was getting this:
Here is my system and OS Information:
SLASHTOP - CPU-Z HTML report file.pdf
Please help me. I've been a Computer Tech Hardware guy for 30 years... This is a first one for me. But again, I'm not a programmer, I have a great team that does that work for me. All donating their time. Thanks again, for your time and what you've done for the community. This should have been including with Windows 64Bit to begin with. Thanks again.
John Riley
The text was updated successfully, but these errors were encountered: