Re: WOWEXEC problem when I try to install an application

[Michele]

I have tried this solution and when I type "sysedit" in run, the "WOWEXEC"
fault comes up,, what next??? I am trying to re-install my printer and cannot
get past this error to do so. Please help if you can. thanks, Michele

"Greg R" wrote:

> On Sat, 14 Aug 2004 15:13:02 -0700, "Ionel"
> <Ionel@discussions.microsoft.com> wrote:
>
> >Hello everybody,
> >
> >I'm trying to install some applications and I get an error message in the
> >WOWEXEC and then another message pops-up telling me that there's a problem
> >with the Win 16 bit susbsytem which is unstable...
> >
> >Please advise.
> >
> >Thanks,
>
>
> Try this
> run sysedit
> Win.ini file
> see if all of the following is there.
>
> ; for 16-bit app support
> [fonts]
> [extensions]
> [mci extensions]
> [files]
> [Mail]
> MAPI=1
> [MCI Extensions.BAK]
> aif=MPEGVideo
> aifc=MPEGVideo
> aiff=MPEGVideo
> asf=MPEGVideo2
> asx=MPEGVideo2
> au=MPEGVideo
> m1v=MPEGVideo
> m3u=MPEGVideo2
> mp2=MPEGVideo
> mp2v=MPEGVideo
> mp3=MPEGVideo2
> mpa=MPEGVideo
> mpe=MPEGVideo
> mpeg=MPEGVideo
> mpg=MPEGVideo
> mpv2=MPEGVideo
> snd=MPEGVideo
> wax=MPEGVideo2
> wm=MPEGVideo2
> wma=MPEGVideo2
> wmv=MPEGVideo2
> wmx=MPEGVideo2
> wvx=MPEGVideo2
> wpl=MPEGVideo
>

[Taurarian]

Hi Michele, hope this helps


When a WinXP Home computer runs 16-bit applications it produces the following error
message: -
WOWEXEC caused a General Protection Fault in module MMSYSTEM.DLL at 000A:0032

WOWEXEC is short for "Windows on Windows Execute" and is a helper program used to run
16-bit applications under NT and XP.

A 16-bit program can give this error message when WOWEXEC is already running when the
16-bit program is started.

Make sure that WOWEXEC is not left in memory when a 16-bit program is closed.
To do this:
1. Log in as the administrator.
2. Run Regedit.exe (in \Windows).
3. Go to the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\WOW
4. Look for the entry DefaultSeparateVDM, and change it to Yes.
5. Close Regedit.

Another possibility is that the path name to the 16-bit program is longer than 128
characters. To solve this problem relocate the program on a path with a shorter name.

Note you can save the registry key first by:
On the File menu, click Export.
In the File name box, type SaveKey, and then click Save.
Or create a system restore point prior to editing.
Note: If the registry key is not there, you can simply create one by going edit>new.

http://support.microsoft.com/default...b;EN-US;322756
HOW TO: Back Up, Edit, and Restore the Registry in Windows XP
Disclaimer: Modifying the registry can cause serious problems that may require you to
reinstall your operating system. Use the information provided at your own risk.





"Michele" <Michele@discussions.microsoft.com> wrote in message
news:21BB8FD9-FBBA-4F7E-BD59-E6619FF53931@microsoft.com...
>I have tried this solution and when I type "sysedit" in run, the "WOWEXEC"
> fault comes up,, what next??? I am trying to re-install my printer and cannot
> get past this error to do so. Please help if you can. thanks, Michele
>
> "Greg R" wrote:
>
>> On Sat, 14 Aug 2004 15:13:02 -0700, "Ionel"
>> <Ionel@discussions.microsoft.com> wrote:
>>
>> >Hello everybody,
>> >
>> >I'm trying to install some applications and I get an error message in the
>> >WOWEXEC and then another message pops-up telling me that there's a problem
>> >with the Win 16 bit susbsytem which is unstable...
>> >
>> >Please advise.
>> >
>> >Thanks,
>>
>>
>> Try this
>> run sysedit
>> Win.ini file
>> see if all of the following is there.
>>
>> ; for 16-bit app support
>> [fonts]
>> [extensions]
>> [mci extensions]
>> [files]
>> [Mail]
>> MAPI=1
>> [MCI Extensions.BAK]
>> aif=MPEGVideo
>> aifc=MPEGVideo
>> aiff=MPEGVideo
>> asf=MPEGVideo2
>> asx=MPEGVideo2
>> au=MPEGVideo
>> m1v=MPEGVideo
>> m3u=MPEGVideo2
>> mp2=MPEGVideo
>> mp2v=MPEGVideo
>> mp3=MPEGVideo2
>> mpa=MPEGVideo
>> mpe=MPEGVideo
>> mpeg=MPEGVideo
>> mpg=MPEGVideo
>> mpv2=MPEGVideo
>> snd=MPEGVideo
>> wax=MPEGVideo2
>> wm=MPEGVideo2
>> wma=MPEGVideo2
>> wmv=MPEGVideo2
>> wmx=MPEGVideo2
>> wvx=MPEGVideo2
>> wpl=MPEGVideo
>>

[Michele]

Thanks Taurarian, but I already tried to go to regedit and I did change it to
yes, but no luck, Could you possible step me through the other idea you had,
I also tried another idea someone gave me which I had to run sysedit, which
prompt me to insert my XP disc, but also no luck, it said I am running a more
current version of xp and then closed. Im so frustrated!!, Thanks for your
help

"Taurarian" wrote:

> Hi Michele, hope this helps
>
>
> When a WinXP Home computer runs 16-bit applications it produces the following error
> message: -
> WOWEXEC caused a General Protection Fault in module MMSYSTEM.DLL at 000A:0032
>
> WOWEXEC is short for "Windows on Windows Execute" and is a helper program used to run
> 16-bit applications under NT and XP.
>
> A 16-bit program can give this error message when WOWEXEC is already running when the
> 16-bit program is started.
>
> Make sure that WOWEXEC is not left in memory when a 16-bit program is closed.
> To do this:
> 1. Log in as the administrator.
> 2. Run Regedit.exe (in \Windows).
> 3. Go to the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\WOW
> 4. Look for the entry DefaultSeparateVDM, and change it to Yes.
> 5. Close Regedit.
>
> Another possibility is that the path name to the 16-bit program is longer than 128
> characters. To solve this problem relocate the program on a path with a shorter name.
>
> Note you can save the registry key first by:
> On the File menu, click Export.
> In the File name box, type SaveKey, and then click Save.
> Or create a system restore point prior to editing.
> Note: If the registry key is not there, you can simply create one by going edit>new.
>
> http://support.microsoft.com/default...b;EN-US;322756
> HOW TO: Back Up, Edit, and Restore the Registry in Windows XP
> Disclaimer: Modifying the registry can cause serious problems that may require you to
> reinstall your operating system. Use the information provided at your own risk.
>
>
>
>
>
> "Michele" <Michele@discussions.microsoft.com> wrote in message
> news:21BB8FD9-FBBA-4F7E-BD59-E6619FF53931@microsoft.com...
> >I have tried this solution and when I type "sysedit" in run, the "WOWEXEC"
> > fault comes up,, what next??? I am trying to re-install my printer and cannot
> > get past this error to do so. Please help if you can. thanks, Michele
> >
> > "Greg R" wrote:
> >
> >> On Sat, 14 Aug 2004 15:13:02 -0700, "Ionel"
> >> <Ionel@discussions.microsoft.com> wrote:
> >>
> >> >Hello everybody,
> >> >
> >> >I'm trying to install some applications and I get an error message in the
> >> >WOWEXEC and then another message pops-up telling me that there's a problem
> >> >with the Win 16 bit susbsytem which is unstable...
> >> >
> >> >Please advise.
> >> >
> >> >Thanks,
> >>
> >>
> >> Try this
> >> run sysedit
> >> Win.ini file
> >> see if all of the following is there.
> >>
> >> ; for 16-bit app support
> >> [fonts]
> >> [extensions]
> >> [mci extensions]
> >> [files]
> >> [Mail]
> >> MAPI=1
> >> [MCI Extensions.BAK]
> >> aif=MPEGVideo
> >> aifc=MPEGVideo
> >> aiff=MPEGVideo
> >> asf=MPEGVideo2
> >> asx=MPEGVideo2
> >> au=MPEGVideo
> >> m1v=MPEGVideo
> >> m3u=MPEGVideo2
> >> mp2=MPEGVideo
> >> mp2v=MPEGVideo
> >> mp3=MPEGVideo2
> >> mpa=MPEGVideo
> >> mpe=MPEGVideo
> >> mpeg=MPEGVideo
> >> mpg=MPEGVideo
> >> mpv2=MPEGVideo
> >> snd=MPEGVideo
> >> wax=MPEGVideo2
> >> wm=MPEGVideo2
> >> wma=MPEGVideo2
> >> wmv=MPEGVideo2
> >> wmx=MPEGVideo2
> >> wvx=MPEGVideo2
> >> wpl=MPEGVideo
> >>
>
>

[Taurarian]

Just some other things to consider to see if relevant to your situation


http://support.microsoft.com/?kbid=324767
Error message when you install or start an MS-DOS or 16-bit Windows-based program

http://support.microsoft.com/default...b;EN-US;314106
Troubleshooting MS-DOS-Based Programs in Windows



16-bit MS-DOS Subsystem error while installing or running a DOS application:
http://windowsxp.mvps.org/16bit.htm

http://support.microsoft.com/?kbid=314495
How to Troubleshoot 16-Bit Windows Programs in Windows XP

"Michele" <Michele@discussions.microsoft.com> wrote in message
news:4C038643-7515-40A5-AB0B-1BE0BC0B139F@microsoft.com...

> Thanks Taurarian, but I already tried to go to regedit and I did change it to
> yes, but no luck, Could you possible step me through the other idea you had,
> I also tried another idea someone gave me which I had to run sysedit, which
> prompt me to insert my XP disc, but also no luck, it said I am running a more
> current version of xp and then closed. Im so frustrated!!, Thanks for your
> help
>
>