Closed ghost closed 2 years ago
Hi, no issues here so far, updated to mentioned verison without issues:
Are you sure that you are using the most recent loaders (see https://github.com/leecher1337/ntvdmx64/issues/167 )? Amy CPU related errors were fixed in latest update that could cause problems like those you mentioned
Regarding installation of symbols for all DOS/WIN16 applications, installation is not necessarily needed for operation, it's just if you want to debug NTVDM. Not sure, why comm.sym didn't get built when you compiled, maybe check logfiles that get produced before the final keypress when autobuild finishes. Maybe you did a FREE-build, not a checked build where there are no usable debug symbols available (for debugging the ntvdm and components, always use the checked build)
I've used a old already-compiled copy (free thing I guess), however I don't remember how to compile the new version... I've made a video when skype closes, this happen with vmware, vegas too...same behaviour https://i.imgur.com/1JqmU0Z.mp4 For the "symbol" I thought it was mandatory to install it :/
No support will be provided for old versions, just run autobuild with build dependencies to get a new version. https://github.com/leecher1337/ntvdmx64/blob/master/ntvdmpatch/doc/autobuild.txt
If you just want to update the loaders (these are mandatory to update), you can replace them with the precompiled dlls from this repository, if - for whatever reason - you want to keep your old installer, but as mentioned, there will be no support for obsolete versions.
No support will be provided for old versions, just run autobuild with build dependencies to get a new version. https://github.com/leecher1337/ntvdmx64/blob/master/ntvdmpatch/doc/autobuild.txt
If you just want to update the loaders (these are mandatory to update), you can replace them with the precompiled dlls from this repository, if - for whatever reason - you want to keep your old installer, but as mentioned, there will be no support for obsolete versions.
Ok, i've built a new version, now it's even worse, skype it dosen't work anymore, and i've a new error...with every 16 apps
Check debug output of loader with Debugview, maybe you are missing some necessary loader symbols.
Check debug output of loader with Debugview, maybe you are missing some necessary loader symbols.
So, i've rebuilt (6 times now with the new ntvdmpatch) with your youtube video, NOW 16bit apps works again, but the skype and dos crashes persist
16bit paintbrush
skype error
dos error
There you have your problem:
"Cannot resolve LdrpInitializeProcess" --> NTDLL.DLL Symbols wrong/unresolvable DBGHELP: "C:\Windows\Symbols\wntdll.pdb\F1D5....." - drive not ready
May be due to a 0byte NTDLL symbol file (wntdll.pdb), this sometimes happens if symbol downloading fails. Just delete the given directory from the error message (The one starting with F1D5...)
If - for whatever reason - this also doesn't help, delete all symbols from \windows\Symbols directory (only the directories with the symbol files in there, not the other files) and remove the following registry keys to enforce redownloading all symbols:
HKEY_LOCAL_MACHINE\SOFTWARE\ldntvdm HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ldntvdm
Hi, i've tried the last solution, but it didn't work.
dos error with last build (the dos error has now the same error with the old build from january, maybe there is a connection...) skype error with last build skype with the old version from january works, but crashes when I open a link
I give up, maybe the culprit is this s*****y amd 5600x or win11, something broke, and pretty hard, a fresh install of win11 sadly has the same results. My favorite feature of ntvdm was the ability to see icons with 16bit applications, :/ next time i'll buy an intel cpu...
The faulty wntdll.pdb is still there, as you can see.. So you deleted this file and it was recreated and still has 0 bytes and is still incomplete? Did you check the file? Did you ensure that you deleted it?
It may be an issue with downloading the required symbols, then, if it always ends up as a 0 byte file for you. It's improtant that the file gets deleted, otherwise, it won't redownload it.
So, i've deleted the file "wntdll.pdb", reinstalled ntvdm and...that file is ALWAYS 0 byte, so i deleted the "wntdll.pdb" again, then i've tried the programs...NOW SKYPE and DOS WORKS WTF?!? I've done it at least 10 times! Now the file has some "weight"
Oh...i notice this when i'm installing ntvdm with "run like administrator", is there another way to download complete "symbols"? Last String has this comment "ERROR: i can't find a specific file" (????????????????????)
So, in short...there is something preventing me from downloading the symbols wtf? Thanks leecher1337, for now we have made progress!
Hi, after the last update of Windows 11 Ver 21H2 build 22000.527, a LOT of problems came out of nowhere, maybe it's a cpu related with my amd ryzen 5600x...
1: ntvdm the "inst-sym.bat" dosen't work, i've to copy manually the "symbols" folder in to "C:\Windows\System32\symbols" to make it work. the message says "I did not find the comm.sym in the symbols folder" 2: i cannot install/uninstall programs with "new" installshield or msi packages 3: libre office simply crash 4: adobe installer (acrobat, photoshop and audition) gives me a generic error, it simply refuses to install 5: skype crashes when i'm trying to open a link, chat or links like "about skype" 6: EVERY dos program has the same error
Without ntvdm, I don't have NONE of the problems mentioned above