Tweet
Windows rant thread!
Anyone who wants to vent about their Windows OS, or any OS, go ahead and post them here. I just need to vent a bit.
------------------------------------
Damn, I hate NT. Here is the crap I had to put up with today. Took me 4 hours to fix it (the client didn't want me to ghost his computer, damn it).
PROBLEM:
User needs to have a tech come out and check his machine. User is trying to install Project 98 and he is recieving a error stating that the system file in not suited to run MSDOS or microsoft applications. Needs to have this looked at and Project 98 installed
SOLUTION:
See TechNet PSS ID Numbers Q142271 and Q103656 (see end of post for the TechNet listings) for a detailed explaination of what causes the problem and Microsoft's explaination of the solution.
After several failed attempts I did the following to get it working. Expanded CONFIG.NT_ [CONFIG.NT], AUTOEXEC.NT_ [AUTOEXEC.NT] and COMMAND.CO_ [COMMAND.COM] from the Windows NT 4.0 CD. Copied the files to C:\Winnt\System32 and replaced the old ones. I then renamed the files by adding a .ZZZ to the end to change the file type.
Ran the NT Repair disk operation, but only had it check the System Files. Replaced all system files and rebooted. Installed SP 6a for WinNT and rebooted. I noticed that only COMMAND.COM had been replaced by the service pack and system file install, so I renamed CONFIG.NT.ZZZ and AUTOEXEC.NT.ZZZ back to CONFIG.NT and AUTOEXEC.NT.
Ran the Project 98 install and everything starting working correctly. Install complete.
--------------------------------------
That really blew chewy chunks. You never really know how many problems Windows Os's have until you look in TechNet. It's amazing!
Jammrock
PSS ID Number: Q103656
Article last modified on 01-18-2000
:; WINDOWS:2000; winnt:3.5,3.51,4.0
WINDOWS winnt
================================================== ====================
-------------------------------------------------------------------------------
The information in this article applies to:
- Microsoft Windows NT operating system version 3.1
- Microsoft Windows NT Advanced Server
- Microsoft Windows NT Server versions 3.5, 3.51, 4.0
- Microsoft Windows NT Workstation versions 3.5, 3.51, 4.0
- Microsoft Windows 2000 Professional
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
-------------------------------------------------------------------------------
Many different 16-bit applications designed to run under Windows 3.1
have been tested with Windows NT. When you are troubleshooting a
16-bit Windows-based application that is not working properly under
Windows NT, the following items should be taken into consideration:
- If possible, verify that the application works correctly under Windows 3.0
and 3.1.
- If the application requires a VxD (virtual device driver), it will not work
properly under Windows NT.
- If the application requires Windows 3.0 or 3.1 to be running in 386 enhanced
mode, the application will not function properly on either the DEC Alpha or
MIPS versions of Windows NT at this time because these platforms currently
emulate only the Intel 80286 architecture.
- Check Print Manager to see that a default printer has been selected. Some
applications (such as Microsoft Word version 2.0 for Windows) will not
function properly under Windows NT unless a default printer has been
selected.
- Make sure that any dynamic link libraries (DLLs) used by the application are
both current and locatable by the application (either on the system path or
explicitly defined within the application or working directory.)
- Make sure that the default items in the CONFIG.NT and AUTOEXEC.NT files are
present and in the proper order.
In Windows NT 3.1, CONFIG.NT contains the following commands by default:
files=50
lastdrive=k
fcbs=4,0
dos=high, umb
device=%SystemRoot%\system32\himem.sys
In Windows NT 3.51 and 4.0, the CONFIG.NT contains the following commands by
default:
dos=high, umb
device=%SystemRoot%\system32\himem.sys
files=20
AUTOEXEC.NT contains the following commands by default:
@echo off
lh %SystemRoot%\system32\mscdexnt.exe
lh %SystemRoot%\system32\redir
lh %SystemRoot%\system32\dosx
- Any environment variables required by the Windows-based application should be
in the AUTOEXEC.BAT file; if they are, Windows NT will use them
appropriately.
Note that if any changes are made to variables related to the Windows 3.0 or
3.1 subsystem (WOWEXEC.EXE), the user may have to restart the computer in
order for these changes to be implemented.
- Determine whether Windows NT has been installed as a stand-alone operating
system or as an upgrade of a previous Windows 3.0 or 3.1 installation. If it
is an upgrade, information from the WIN.INI and/or SYSTEM.INI files may have
not been correctly copied into the Windows NT Registry database.
To correct this problem, you may have to either migrate these settings again,
or reinstall the application that is not working.
For help with migrating application information into the Windows NT Registry,
query on the following reference words in the Microsoft Knowledge Base:
migrate and WIN.INI
- Try running the application in a separate memory space by editing the icon or
shortcut[ASCII 146]s properties and checking the appropriate checkbox.
Additional query words: prodnt WOW apps tshoot 16bit
================================================== ====================
Keywords : kb3rdparty kbinterop nt16ap NTSrvWkst
Version : :; WINDOWS:2000; winnt:3.5,3.51,4.0
Platform : WINDOWS winnt
================================================== ===========================
Copyright Microsoft Corporation 2000.
PSS ID Number: Q142271
Article last modified on 01-25-2000
WINDOWS:2000; winnt:3.5,3.51,4.0
WINDOWS winnt
================================================== ====================
-------------------------------------------------------------------------------
The information in this article applies to:
- Microsoft Windows NT Workstation versions 3.5, 3.51, 4.0
- Microsoft Windows NT Server versions 3.5, 3.51, 4.0
- Microsoft Windows 2000 Professional
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
-------------------------------------------------------------------------------
SYMPTOMS
========
If you remove or rename %SystemRoot%\System32\COMMAND.COM, the following error
message appears when you start a 16-bit Windows or MS-DOS application:
16 bit MS-DOS Subsystem: config.nt. The system file is not suitable for
running MS-DOS and Microsoft Windows Applications.
RESOLUTION
==========
To correct this problem, do one of the following:
- Run the Windows NT Emergency Repair process and verify system files. Restart
Windows NT and run the application again.
-or-
- Expand COMMAND.CO_ from the Windows NT CD-ROM disc to
%SystemRoot%\SYSTEM32\COMMAND.COM.
-or-
- Expand Autoexec.nt_ and Config.nt_ from the Windows NT CD-ROM disc to
%SystemRoot%\SYSTEM32\Autoexec.nt and Config.nt, respectively.
For additional trouble-shooting steps on running 16-bit Windows applications,
please see the following Microsoft Knowledge Base article:
ARTICLE ID: Q103656
TITLE : Troubleshooting 16-Bit Windows Applications Under Windows NT
Additional query words: prodnt 4.0
================================================== ====================
Keywords : nt16ap
Version : WINDOWS:2000; winnt:3.5,3.51,4.0
Platform : WINDOWS winnt
================================================== ===========================
Copyright Microsoft Corporation 2000.
------------------------------------
Damn, I hate NT. Here is the crap I had to put up with today. Took me 4 hours to fix it (the client didn't want me to ghost his computer, damn it).
PROBLEM:
User needs to have a tech come out and check his machine. User is trying to install Project 98 and he is recieving a error stating that the system file in not suited to run MSDOS or microsoft applications. Needs to have this looked at and Project 98 installed
SOLUTION:
See TechNet PSS ID Numbers Q142271 and Q103656 (see end of post for the TechNet listings) for a detailed explaination of what causes the problem and Microsoft's explaination of the solution.
After several failed attempts I did the following to get it working. Expanded CONFIG.NT_ [CONFIG.NT], AUTOEXEC.NT_ [AUTOEXEC.NT] and COMMAND.CO_ [COMMAND.COM] from the Windows NT 4.0 CD. Copied the files to C:\Winnt\System32 and replaced the old ones. I then renamed the files by adding a .ZZZ to the end to change the file type.
Ran the NT Repair disk operation, but only had it check the System Files. Replaced all system files and rebooted. Installed SP 6a for WinNT and rebooted. I noticed that only COMMAND.COM had been replaced by the service pack and system file install, so I renamed CONFIG.NT.ZZZ and AUTOEXEC.NT.ZZZ back to CONFIG.NT and AUTOEXEC.NT.
Ran the Project 98 install and everything starting working correctly. Install complete.
--------------------------------------
That really blew chewy chunks. You never really know how many problems Windows Os's have until you look in TechNet. It's amazing!
Jammrock
PSS ID Number: Q103656
Article last modified on 01-18-2000
:; WINDOWS:2000; winnt:3.5,3.51,4.0
WINDOWS winnt
================================================== ====================
-------------------------------------------------------------------------------
The information in this article applies to:
- Microsoft Windows NT operating system version 3.1
- Microsoft Windows NT Advanced Server
- Microsoft Windows NT Server versions 3.5, 3.51, 4.0
- Microsoft Windows NT Workstation versions 3.5, 3.51, 4.0
- Microsoft Windows 2000 Professional
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
-------------------------------------------------------------------------------
Many different 16-bit applications designed to run under Windows 3.1
have been tested with Windows NT. When you are troubleshooting a
16-bit Windows-based application that is not working properly under
Windows NT, the following items should be taken into consideration:
- If possible, verify that the application works correctly under Windows 3.0
and 3.1.
- If the application requires a VxD (virtual device driver), it will not work
properly under Windows NT.
- If the application requires Windows 3.0 or 3.1 to be running in 386 enhanced
mode, the application will not function properly on either the DEC Alpha or
MIPS versions of Windows NT at this time because these platforms currently
emulate only the Intel 80286 architecture.
- Check Print Manager to see that a default printer has been selected. Some
applications (such as Microsoft Word version 2.0 for Windows) will not
function properly under Windows NT unless a default printer has been
selected.
- Make sure that any dynamic link libraries (DLLs) used by the application are
both current and locatable by the application (either on the system path or
explicitly defined within the application or working directory.)
- Make sure that the default items in the CONFIG.NT and AUTOEXEC.NT files are
present and in the proper order.
In Windows NT 3.1, CONFIG.NT contains the following commands by default:
files=50
lastdrive=k
fcbs=4,0
dos=high, umb
device=%SystemRoot%\system32\himem.sys
In Windows NT 3.51 and 4.0, the CONFIG.NT contains the following commands by
default:
dos=high, umb
device=%SystemRoot%\system32\himem.sys
files=20
AUTOEXEC.NT contains the following commands by default:
@echo off
lh %SystemRoot%\system32\mscdexnt.exe
lh %SystemRoot%\system32\redir
lh %SystemRoot%\system32\dosx
- Any environment variables required by the Windows-based application should be
in the AUTOEXEC.BAT file; if they are, Windows NT will use them
appropriately.
Note that if any changes are made to variables related to the Windows 3.0 or
3.1 subsystem (WOWEXEC.EXE), the user may have to restart the computer in
order for these changes to be implemented.
- Determine whether Windows NT has been installed as a stand-alone operating
system or as an upgrade of a previous Windows 3.0 or 3.1 installation. If it
is an upgrade, information from the WIN.INI and/or SYSTEM.INI files may have
not been correctly copied into the Windows NT Registry database.
To correct this problem, you may have to either migrate these settings again,
or reinstall the application that is not working.
For help with migrating application information into the Windows NT Registry,
query on the following reference words in the Microsoft Knowledge Base:
migrate and WIN.INI
- Try running the application in a separate memory space by editing the icon or
shortcut[ASCII 146]s properties and checking the appropriate checkbox.
Additional query words: prodnt WOW apps tshoot 16bit
================================================== ====================
Keywords : kb3rdparty kbinterop nt16ap NTSrvWkst
Version : :; WINDOWS:2000; winnt:3.5,3.51,4.0
Platform : WINDOWS winnt
================================================== ===========================
Copyright Microsoft Corporation 2000.
PSS ID Number: Q142271
Article last modified on 01-25-2000
WINDOWS:2000; winnt:3.5,3.51,4.0
WINDOWS winnt
================================================== ====================
-------------------------------------------------------------------------------
The information in this article applies to:
- Microsoft Windows NT Workstation versions 3.5, 3.51, 4.0
- Microsoft Windows NT Server versions 3.5, 3.51, 4.0
- Microsoft Windows 2000 Professional
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
-------------------------------------------------------------------------------
SYMPTOMS
========
If you remove or rename %SystemRoot%\System32\COMMAND.COM, the following error
message appears when you start a 16-bit Windows or MS-DOS application:
16 bit MS-DOS Subsystem: config.nt. The system file is not suitable for
running MS-DOS and Microsoft Windows Applications.
RESOLUTION
==========
To correct this problem, do one of the following:
- Run the Windows NT Emergency Repair process and verify system files. Restart
Windows NT and run the application again.
-or-
- Expand COMMAND.CO_ from the Windows NT CD-ROM disc to
%SystemRoot%\SYSTEM32\COMMAND.COM.
-or-
- Expand Autoexec.nt_ and Config.nt_ from the Windows NT CD-ROM disc to
%SystemRoot%\SYSTEM32\Autoexec.nt and Config.nt, respectively.
For additional trouble-shooting steps on running 16-bit Windows applications,
please see the following Microsoft Knowledge Base article:
ARTICLE ID: Q103656
TITLE : Troubleshooting 16-Bit Windows Applications Under Windows NT
Additional query words: prodnt 4.0
================================================== ====================
Keywords : nt16ap
Version : WINDOWS:2000; winnt:3.5,3.51,4.0
Platform : WINDOWS winnt
================================================== ===========================
Copyright Microsoft Corporation 2000.
Comment