Windows Vista Config.nt file missing?!?
Posted: 01-20-2009, 10:53 PM
Hello. I have a concern that I need addressed. I have Windows Vista
Ultimate with SP1 installed on my computer. I have already installed 70+
programs/applications. One of the programs that I have installed is
Microsoft Streets & Trips 2007. I have no problems installing this core
part of this software until I get the part that I elect to select
"Install Windows Live Local for Outlook after Streets & Trips Setup is
finished". This installation option is available at the conclusion of
the core installation process. When this option is selected after the
conclusion of installing Streets & Trips, I get an error message that is
titled,"16 bit MS-DOS Subsystem". Inside the window states,
C:\Windows\SYSTEM32\CONFIG.NT. . This required system file is missing.
Choose 'Close" to terminate the application."
Now, I have installed Streets & Trips as a fresh install in the past on
same previously installed operating system electing this option to
install Windows Live Local for Outlook. I received no issues installing
the Windows Live Local option at that time. This time I did. I have read
online that Windows Vista does not support 16bit programs from a few
sources. Yet, some users say that Vista does support them. Well, if I
have been able to install the optional program before without any
issues, than I know Vista can.
Now what I need to know is the root of this issue: How do I get back
the config.nt file again since it is missing. I have searched online
ONLY to find the same lengthy solution on C:\Windows\SYSTEM32\CONFIG.NT
problems for ONLY Windows XP "everywhere" on the web to put the
config.nt file back in the operating system. I have not found any
solution for Windows Vista regarding this same missing config.nt file
issue. I need some detailed process in detailed steps on how to put the
config.nt file back into my Vista system. I also think that there is
more to it than simply adding the config.nt file back in Vista's
System32 Folder. I have read the solution around this type of error
message by just reading the Windows XP solution and it is long and
technical process. So I would figure that Windows Vista solution is
going to be a long process as well. Therefore I need your help in
re-creating a solution for Windows Vista.
Is there anything else I may be overlooking regarding the whole big
scheme of things beyond the config.nt issue?
PLEASE HELP ME!!!