problem with Non-Win16 application shell

  • Thread starter Thread starter aki999
  • Start date Start date
A

aki999

I cannot install applications with 16bit installation
programs (Mustek scanner drivers for example). Setup
programs fails with WINOLDAP access violation and Windows
NT Non-Win16 application shell error .

I installed those programs without any problems a few
months ago.

I already tried method described in article KB196453
(NTVDM and WOW problems). Tried XP setup repair mode
too...

Please help before format C:...

My system: XP PRO SP1 + all patches from windowsupdate,
Office XP, Norton Antyvirus 2002
 
aki999 said:
I cannot install applications with 16bit installation
programs (Mustek scanner drivers for example). Setup
programs fails with WINOLDAP access violation and Windows
NT Non-Win16 application shell error .

I may be misreading your post here, but I wouldn't attempt to install ANY
drivers that pre-date Windows 2000. You are going to run into trouble. What
Mustek scanner do you have?

JW
 
Mustek BearPaw 1200, and I use drivers file named
WIN_98_ME_W2K_XP\web.exe from mustek.com. This is 16bit
installation package. It works fine a little time ago -
now it crashes during expanding package (suppose).

This problem occurs with other applications with 16bit
installation packages and Microsoft localize that as
NTVDM and WOW problem. I tried solutions from KB but it
does not work...

aki999
 
aki999 said:
Mustek BearPaw 1200, and I use drivers file named
WIN_98_ME_W2K_XP\web.exe from mustek.com. This is 16bit
installation package. It works fine a little time ago -
now it crashes during expanding package (suppose).

This problem occurs with other applications with 16bit
installation packages and Microsoft localize that as
NTVDM and WOW problem. I tried solutions from KB but it
does not work...

aki999
I did have major problems with Mustek drivers (1200UB) for quite some time
following my Win XP upgrade. But these were centred around the installation
package not wanting to work under anything later than Win 2000, rather than
being incompatible with Win XP. The later drivers fixed my problems though.

I'm sorry I can't help any more. Hopefully someone else may be able to shed
some light.

Cheers

JW
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top