Archived from groups: microsoft.public.windowsxp.configuration_manage (More info?)
I am getting 16 BIT windows errors when trying to run applications or install
them all of a sudden. All the reading that I have done references the
autoexec.nt file as the one providing support to 16 BIT apps. A recent patch
or modification to our systems has resulted in this problem but can't
isolate. Below is a copy of one of the systems. Windows 2000. I don't
understand enough to know what is going on here but it doesn't match the one
in the repair folder. Do installed applications such as acrobat 4 write
comments to these files. Or are they meant to be the same all of the time?
{\rtf1\ansi\deff0{\fonttbl{\f0\fnil\fcharset0 Courier New;}}
\viewkind4\uc1\pard\lang1033\f0\fs20 @echo off\par
\par
REM AUTOEXEC.BAT is not used to initialize the MS-DOS environment.\par
REM AUTOEXEC.NT is used to initialize the MS-DOS environment unless a\par
REM different startup file is specified in an application's PIF.\par
\par
REM Install CD ROM extensions\par
lh %SystemRoot%\\system32\\mscdexnt.exe\par
\par
REM Install network redirector (load before dosx.exe)\par
lh %SystemRoot%\\system32\\redir\par
\par
REM Install DPMI support\par
lh %SystemRoot%\\system32\\dosx\par
\par
}
In news:B1F04B4D-90A7-48BF-B6C1-5BAAEE771F7D@microsoft.com,
RASTER <RASTER@discussions.microsoft.com> hunted and pecked:
> I am getting 16 BIT windows errors when trying to run applications or
> install them all of a sudden. All the reading that I have done
> references the autoexec.nt file as the one providing support to 16
> BIT apps. A recent patch or modification to our systems has resulted
> in this problem but can't isolate. Below is a copy of one of the
> systems. Windows 2000. I don't understand enough to know what is
> going on here but it doesn't match the one in the repair folder. Do
> installed applications such as acrobat 4 write comments to these
> files. Or are they meant to be the same all of the time?
>
> {\rtf1\ansi\deff0{\fonttbl{\f0\fnil\fcharset0 Courier New;}}
> \viewkind4\uc1\pard\lang1033\f0\fs20 @echo off\par
> \par
> REM AUTOEXEC.BAT is not used to initialize the MS-DOS environment.\par
> REM AUTOEXEC.NT is used to initialize the MS-DOS environment unless
> a\par REM different startup file is specified in an application's
> PIF.\par \par
> REM Install CD ROM extensions\par
> lh %SystemRoot%\\system32\\mscdexnt.exe\par
> \par
> REM Install network redirector (load before dosx.exe)\par
> lh %SystemRoot%\\system32\\redir\par
> \par
> REM Install DPMI support\par
> lh %SystemRoot%\\system32\\dosx\par
> \par
> }
>
> Any assistance would be greatly appreciated.
Archived from groups: microsoft.public.windowsxp.configuration_manage (More info?)
RASTER wrote:
> I am getting 16 BIT windows errors when trying to run applications or install
> them all of a sudden. All the reading that I have done references the
> autoexec.nt file as the one providing support to 16 BIT apps. A recent patch
> or modification to our systems has resulted in this problem but can't
> isolate.
Hi
You can put back the standard version of autoexec.nt/config.nt by
copying a backup copy held in %windir%\repair\ to %windir%\system32\
(%windir% is typically C:\Windows) instead of using the procedure in
the KB article above.
Archived from groups: microsoft.public.windowsxp.configuration_manage (More info?)
Just wanted to say a big THANK-YOU. The kellys-korner-xp.com resolved the
problem on my computer.
"Wesley Vogel" wrote:
> This issue may occur if one or more of the following files are missing or
> damaged:
> Config.nt
> Autoexec.nt
> Command.com
>
> Looks like your Autoexec.nt is FUBAR. It should start with... @echo off
>
> Seems to be an epidemic lately....
>
> MS-DOS or 16-bit Windows-based program Error Message
> http://www.kellys-korner-xp.com/xp_m.htm#16bit >
> Error message when you install or start an MS-DOS or 16-bit Windows-based
> program
> http://support.microsoft.com/defau [...] -us;324767 >
> --
> Hope this helps. Let us know.
> Wes
>
> In news:B1F04B4D-90A7-48BF-B6C1-5BAAEE771F7D@microsoft.com,
> RASTER <RASTER@discussions.microsoft.com> hunted and pecked:
> > I am getting 16 BIT windows errors when trying to run applications or
> > install them all of a sudden. All the reading that I have done
> > references the autoexec.nt file as the one providing support to 16
> > BIT apps. A recent patch or modification to our systems has resulted
> > in this problem but can't isolate. Below is a copy of one of the
> > systems. Windows 2000. I don't understand enough to know what is
> > going on here but it doesn't match the one in the repair folder. Do
> > installed applications such as acrobat 4 write comments to these
> > files. Or are they meant to be the same all of the time?
> >
> > {\rtf1\ansi\deff0{\fonttbl{\f0\fnil\fcharset0 Courier New;}}
> > \viewkind4\uc1\pard\lang1033\f0\fs20 @echo off\par
> > \par
> > REM AUTOEXEC.BAT is not used to initialize the MS-DOS environment.\par
> > REM AUTOEXEC.NT is used to initialize the MS-DOS environment unless
> > a\par REM different startup file is specified in an application's
> > PIF.\par \par
> > REM Install CD ROM extensions\par
> > lh %SystemRoot%\\system32\\mscdexnt.exe\par
> > \par
> > REM Install network redirector (load before dosx.exe)\par
> > lh %SystemRoot%\\system32\\redir\par
> > \par
> > REM Install DPMI support\par
> > lh %SystemRoot%\\system32\\dosx\par
> > \par
> > }
> >
> > Any assistance would be greatly appreciated.
>
>
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.