Computer Hope

Microsoft => Microsoft Windows => Windows NT/2000 => Topic started by: burton on January 11, 2005, 10:07:59 AM

Title: 16 bit application stops responding (wowexec.exe)
Post by: burton on January 11, 2005, 10:07:59 AM

I use Win2000 professional.

When I extract a ZIP-file with WinZIP self-extractor, the program freezes / blocks. I had a similar problem before, in the case that the program stops responding when trying to run a 16-bit application.

In the task manager, the wowexec.exe was activated each time, so I suppose it has something to do with that. Maybe it is corrupt, can I reinstall this?

Or has this got anything to do with the NTVDM.exe in the C:\WINNT\SYSTEM32 folder?

Title: Re: 16 bit application stops responding (wowexec.e
Post by: merlin_2 on January 11, 2005, 03:07:15 PM

http://www.jsiinc.com/SUBN/tip6700/rh6753.htm

Title: Re: 16 bit application stops responding (wowexec.e
Post by: burton on January 13, 2005, 06:55:49 AM

Thanks for the link, but no specific help on my problem found.

I have contacted DELL and XEROX and we have tried several solutions, including a Intel Chipset update.
They have advised to reinstall Windows 2000, but that is an easy way out of the problem! They told me to do that once before, when finally I was able to correct a bad setting in the CONTROL PANEL - ADMINISTRATION - SERVICES folder.

Thats where I would like to continue this problem, so can somebody inform me where the 16-bit applications are listed within the SERVICES? (re: wowexec/NTVDM)

Title: Re: 16 bit application stops responding (wowexec.e
Post by: burton on January 14, 2005, 04:53:45 AM

Otherwise, if noone knows how to find the 16-bit configuration support in Win2000, does anybody know a website or forum that can discuss or explain the funtions of SERVICES in Win2000?

Title: Re: 16 bit application stops responding (wowexec.e
Post by: merlin_2 on January 14, 2005, 02:46:32 PM

http://support.microsoft.com/kb/142026

Title: Re: 16 bit application stops responding (wowexec.e
Post by: burton on January 14, 2005, 07:03:03 PM

Thanks, but I think the problem is solved here: http://support.microsoft.com/kb/196453/EN-US/

Will let you know next week if otherwise  ;)