The NTVDM has encountered... Pops up with DOS programs under Win 10 32bit under VMWare Workstation Pro more than I'd like. Is there any way to automatically get rid of this message so that my midnight maint can continue
on with the rest of its stuff? I know back in my NT days there was a program that would automatically click on dialogue boxes just for this case. Is
there still such a beast?

--
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
,wss) (Ports 22,23,110,21,119,8080) (ssh login 'bbs' pass 'shsbbs').


*** THE READER V4.50 [freeware]
---
* Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (618:300/50)

To: Shurato
Re: Error Messages...
By: Shurato to All on Mon May 27 2024 10:12 am

From Newsgroup: micronet.comp

The NTVDM has encountered... Pops up with DOS programs under Win 10 32bit under VMWare Workstation Pro more than I'd like. Is there any way to automatically get rid of this message so that my midnight maint can continue on with the rest of its stuff? I know back in my NT days there was a program that would automatically click on dialogue boxes just for this case. Is
there still such a beast?

well you need to fix the issue, not treat the symptom.
in earlier versions i believe there were ways to turn off some errors, but not sure now. it's been so long.

what exactly is causing this error? what have you done to your OS that may have caused issues? any installations of software?

--- Synchronet 3.19b-Win32 NewsLink 1.113
* bbses.info - http://bbses.info - telnet://bbses.info
* Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (618:250/1)

On 27 May 24 10:12:00, Shurato said the following to All:

The NTVDM has encountered... Pops up with DOS programs under Win 10 32bit under VMWare Workstation Pro more than I'd like. Is there any way to automatically get rid of this message so that my midnight maint can continue on with the rest of its stuff? I know back in my NT days there was a progra

No for two reasons.

Firstly... a Windows 10 update broke NTVDM several months ago.... think it was January. Exodus had the same problem too I think.

It had something to do with the console-session portion updated that NTVDM depends on. Think I saw something that a registry key can be added to make it use the old console version but not sure. Also double check that an update did not reset the "Legacy console" setting in Cmd properties.

You could try uninstalling whatever recent cumulative-updates were installed?

Second, the NTVDM error is a message generated by a system process. Very unlikely you will find something that would interact with the system
process to click away errors not wanted.

NTVDM really only worked properly from before 10 with XP & 7 being "right".

Nick

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (618:500/24)

To: Shurato
Re: Error Messages... By: Shurato to All on Mon May 27 2024 10:12
am

From Newsgroup: micronet.comp

The NTVDM has encountered... Pops up with DOS programs under Win 10

32bit

under VMWare Workstation Pro more than I'd like. Is there any way to automatically get rid of this message so that my midnight maint can

continue

on with the rest of its stuff? I know back in my NT days there was a program that would automatically click on dialogue boxes just for this

case.

Is there still such a beast?

well you need to fix the issue, not treat the symptom. in earlier
versions i believe there were ways to turn off some errors, but not
sure now. it's been so long.

what exactly is causing this error? what have you done to your OS that may have caused issues? any installations of software?

It seems to be at random with various DOS executables in my nightly maintenance. Sometimes it doesn't happen, sometimes it happens up to 3 times and I have to be there to click OK, then the batch file continues.

--
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
,wss) (Ports 22,23,110,21,119,8080) (ssh login 'bbs' pass 'shsbbs').


*** THE READER V4.50 [freeware]
---
* Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (618:300/50)

On 27 May 24 10:12:00, Shurato said the following to All:

The NTVDM has encountered... Pops up with DOS programs under Win 10

32bit

under VMWare Workstation Pro more than I'd like. Is there any way to
automatically get rid of this message so that my midnight maint can

continue

on with the rest of its stuff? I know back in my NT days there was a

progra

No for two reasons.

Firstly... a Windows 10 update broke NTVDM several months ago.... think it was January. Exodus had the same problem too I think.

It had something to do with the console-session portion updated that NTVDM

depends on. Think I saw something that a registry key can be added to make it use the old console version but not sure. Also double check that
an update did not reset the "Legacy console" setting in Cmd
properties.

I checked the default properties for console and they're set to use the
Legacy Console settings. Is that where I needed to look?

You could try uninstalling whatever recent cumulative-updates were installed?

Second, the NTVDM error is a message generated by a system process. Very unlikely you will find something that would interact with the system process to click away errors not wanted.

NTVDM really only worked properly from before 10 with XP & 7 being "right".

Nick

--- Renegade vY2Ka2 * Origin: Joey, do you like movies about
gladiators? (618:500/24)

--
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
,wss) (Ports 22,23,110,21,119,8080) (ssh login 'bbs' pass 'shsbbs').


*** THE READER V4.50 [freeware]
---
* Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (618:300/50)

On 27 May 24 16:13:00, Shurato said the following to Nick Andre:

depends on. Think I saw something that a registry key can be added to m it use the old console version but not sure. Also double check that
an update did not reset the "Legacy console" setting in Cmd
properties.

I checked the default properties for console and they're set to use the Legacy Console settings. Is that where I needed to look?

Yes but believe me.... "been there got the T shirt" with NTVDM. This drove me nuts with Windows 10 and I was running the LTSB/LTSC builds which are stripped down from retail and specifically designed to run mission-critical.

NTVDM on 10 just never worked right over a long period of time. BBS would run fine for a few days, sometimes a few weeks, maybe even a month or so then
would start having the same problems you have and other weird nonsense. Out of handles, out of memory, memory leaking on a supposedly Enterprise-grade OS.

Nick

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (618:500/24)

To: Shurato
Re: Error Messages...
By: Shurato to Jas Hud on Mon May 27 2024 04:09 pm

well you need to fix the issue, not treat the symptom. in earlier versions i believe there were ways to turn off some errors, but not sure now. it's been so long.

what exactly is causing this error? what have you done to your OS that may have caused issues? any installations of software?

It seems to be at random with various DOS executables in my nightly maintenance. Sometimes it doesn't happen, sometimes it happens up to 3 times and I have to be there to click OK, then the batch file continues.

it could be that you have some corruption in your OS, it could be you have bad memory or any other problem. It could be the executables are bad and one time it will give you an error in the command line and other times it will bomb out with the ntvdm error. I would try to trouble shoot it out.
I had this happen years ago. I just ended up redoing things.

Create a fresh windows vm and run it and see if they bomb out.
let me know if you want an iso. i have those all in ones on my server.
--- Synchronet 3.19b-Win32 NewsLink 1.113
* bbses.info - http://bbses.info - telnet://bbses.info
* Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (618:250/1)

Firstly... a Windows 10 update broke NTVDM several months ago.... think it January. Exodus had the same problem too I think.

Yup, the raeson I jumped back to Win7. If Win10 NTVDM would work, I would be on it. I don't understand why they keep pissing with it if they plan on getting rid of it? Just leave it alone and phase it out, don't fuck with it.

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (618:500/24)

NTVDM really only worked properly from before 10 with XP & 7 being "right".

XP more than 7, but 7 works okay, as it's the most compatible if you want to run something "newer" ....

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (618:500/24)

On 27 May 24 21:44, T.J. Mcmillen said the following to Nick Andre:

Firstly... a Windows 10 update broke NTVDM several months ago.... think it January. Exodus had the same problem too I think.

Yup, the raeson I jumped back to Win7. If Win10 NTVDM would work, I would on it. I don't understand why they keep pissing with it if they plan on getting rid of it? Just leave it alone and phase it out, don't fuck with

They've been taking heat from security firms of recent discoveries of flaws in that whole DOS subsystem. Seems like M$ did just enough to shut them up but
at the expense of trashing something thats worked perfectly for decades.

Nick

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (618:500/24)

On 27 May 24 21:45, T.J. Mcmillen said the following to Nick Andre:

NTVDM really only worked properly from before 10 with XP & 7 being "right".

XP more than 7, but 7 works okay, as it's the most compatible if you want t run something "newer" ....

XP and 7 were the best Windows. Maybe even NT4 and 2000.... everyone always trashed M$ but they gave you RDP, Vpn and backup stuff that actually worked.

Sure was nice to have those OS's just shut up and run programs.

Nick

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (618:500/24)

To: T.J. Mcmillen
Re: Re: Error Messages...
By: T.J. Mcmillen to Nick Andre on Mon May 27 2024 09:45 pm

From Newsgroup: micronet.comp

NTVDM really only worked properly from before 10 with XP & 7 being "right".

XP more than 7, but 7 works okay, as it's the most compatible if you want to run something "newer" ....

can you name off any doorgames or utils that bomb out on windows 10 32bit?
I haven't had any issues with ntvmd screwing up on that vm i run. i have had issues in the past with windows 7. i think maybe i had problems with net2bbs or netfoss. not sure it was so long ago.
--- Synchronet 3.19b-Win32 NewsLink 1.113
* bbses.info - http://bbses.info - telnet://bbses.info
* Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (618:250/1)

I reinstalled my VM and we'll see if it helps any. At the very least, it
gave me something to do. The only thing I wasn't able to get back functional was MRC. Is mrc.bottomlessabyss.net down? The mrc_client.py script is
unable to connect. I don't know if it's a coincidence or not. I checked my firewall rules for python and mrc_client.py as well as outbound to port 5001 and they all check out.

--
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
,wss) (Ports 22,23,110,21,119,8080) (ssh login 'bbs' pass 'shsbbs').


*** THE READER V4.50 [freeware]
---
* Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (618:300/50)

can you name off any doorgames or utils that bomb out on windows 10 32bit? I haven't had any issues with ntvmd screwing up on that vm i run. i have h issues in the past with windows 7. i think maybe i had problems with net2b or netfoss. not sure it was so long ago.

Any of .. oh shit ... Any of the Ray Clammet doors that went looking for DOOR.SYS from a config file, if I loaded command.com they would still run, cmd, would not find it for some reason. There are others, but I can't think of any off hand. None anyone really plays, but I have and they MUST work to stay online.

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (618:500/24)

To: T.J. Mcmillen
Re: Re: Error Messages...
By: T.J. Mcmillen to Jas Hud on Tue May 28 2024 06:38 pm

Any of .. oh shit ... Any of the Ray Clammet doors that went looking for DOOR.SYS from a config file, if I loaded command.com they would still run, cmd, would not find it for some reason. There are others, but I can't think of any off hand. None anyone really plays, but I have and they MUST work to stay online.

oh those are ones bad with that a shitty quickbasic doorkit, right?
--- Synchronet 3.19b-Win32 NewsLink 1.113
* bbses.info - http://bbses.info - telnet://bbses.info
* Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (618:250/1)

oh those are ones bad with that a shitty quickbasic doorkit, right?

Yup.

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (618:500/24)

On 28 May 24 21:04, T.J. Mcmillen said the following to Jas Hud:

oh those are ones bad with that a shitty quickbasic doorkit, right?

Yup.

There are programs running here dating back to 1987.

Nick

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (618:500/24)

To: T.J. Mcmillen
Re: Re: Error Messages...
By: T.J. Mcmillen to Jas Hud on Tue May 28 2024 09:04 pm

From Newsgroup: micronet.comp

oh those are ones bad with that a shitty quickbasic doorkit, right?

Yup.

I've actually used the commercial version of moslo to launch those things and didn't have them bomb out.

Usually they are junk doors and not worth it. I had a few lord igms that i used in that way.
--- Synchronet 3.19b-Win32 NewsLink 1.113
* bbses.info - http://bbses.info - telnet://bbses.info
* Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (618:250/1)