Corrupt download or incomplete installation of Microsoft Windows software. They also exist in Windows NT but they are called CONFIG.NT and AUTOEXEC.NT and reside in C:\WINNT\SYSTEM32. The best part is that repairing registry errors can also dramatically improve system speed and performance. Take a look at this article for how to fix it: http://support.microsoft.com/default.aspx?scid=kb;en-us;324767 fixes it.
Virtual Device Driver Format in the Registry is Invalid. Alternatively, you might consider creating a special Autoexec.nt file for use with WordPerfect only. Note: In order to make expanded memory available to all your DOS applications, it may help (or it may not, but it can't hurt) to modify the file named _default.pif (note path=C:\windows\;C:\ as well so when you type in finder it knows to not only associate the shortened name to the command but where to find the command you are reffering to http://ccm.net/faq/1278-autoexec-nt-windows-16-bit-subsystem
Step 1: Repair Registry Entries Associated with Microsoft Windows Sometimes autoexec.nt and other NT system errors can be related to problems in the Windows registry. Microsoft Windows) under the Name column. Windows XP uses Config.nt and Autoexec.nt, not Config.sys or Autoexec.bat If you have a Config.sys or Autoexec.bat file left over from your old system, Windows NT, 2000, and XP will (mostly) You can help keep The Sierra Help Pages alive by helping to defray some of the costs of hosting this site.
However a reboot will reestablish the problem. Running WinSweeper once per day (using automatic scanning) will ensure that your computer is always clean, running fast, and free of autoexec.nt errors related to temporary files. Additionally, scan with Ad-aware, SpyBot and CWShredder. If you use the Tame utility, many aspects of its performance will be far superior than under Windows 95, 98, or Me, or under pure DOS.
printing). What it basically says is that you need to replace the files AUTOEXEC.NT, CONFIG.NT, and COMMAND.COM which are found in your Windows System32 folder with the same-named files found on your If you do not have those disks, or if you want to retain all the macros, keyboard layouts, printer drivers, and other settings of your current installation, you can simply copy Fix Windows error messages "The system cannot open COM1 port requested by the application" or "Driver does not support selected baud rate" When you start WPDOS under Windows XP, you may
See further information on VESA drivers, video cards, and other issues in this site's graphics mode survival guide. Autoexec.nt is used for the same kind of tasks formerly performed by Autoexec.bat (launching memory-resident programs, etc.) Advanced users should note that only old-style 16-bit DOS and Windows 3.1 programs can Microsoft Windows) under the Name column. The system file is not suitable for running MS-DOS and Microsoft Windows applications.
If the other changes cause problems with other applications, then experiment with the Autoexec.nt file by removing one or more of the REM lines that you added earlier in this procedure http://filext.com/faq/manage_autoexec_nt_file.php The latest known version of Autoexec.nt is 5.1.2600.5512, which was produced for Windows XP. Select New..., then Shortcut. The next steps in manually editing your registry will not be discussed in this article due to the high risk of damaging your system.
But, you might still want or need to run older programs and will need the AUTOEXEC.NT file to do that. Now open a text editor (Notepad will do) and type the following lines... @Echo OFF Copy C:\PITA\AUTOEXEC.NT C:\Windows\System32\ Attrib +R C:\Windows\System32\AUTOEXEC.NT Save this file as C:\PITA\DOIT.BAT. Click in the field so that the filename is not highlighted, and move the cursor to the very start of the field, at the extreme left. (If the filename disappears, click Type "command" in the search box...
Depending on your configuration, you may have an additional 35 KB of available memory the next time you open WPDOS. After the contents of all the diskettes have been copied, store the diskettes safely, then open a command prompt and run the INSTALL command from from the copy on the hard If you need help, read this site's instructions for creating and modifying a DOS prompt and for creating and modifying desktop shortcuts. The Parasite Fight - Quick Fix Protocol Get a copy of Autoruns tool (latest version allows managing the Startup locations for other user profiles).
The message shows up. Next, download, install, and buy (US$25) MJMSoft Design's KeyText utility. Then, create a one-line batch file that launches your DOS program, and create a desktop shortcut for it. (Help!
Then, in Windows Explorer, start with the first program listed in your batch file (for example, ST.EXE or PRD.COM), and find it in its own directory (for example, C:\st or C:\pplus2). get started Managing Problems with the AUTOEXEC.NT File You may encounter a message, particularly after the Windows XP SP2 upgrade, about either CONFIG.NT or AUTOEXEC.NT being "...not suitable for running MS-DOS How to Edit Autoexec.NT and Config.NT in Windows 7 Sometimes you need programs such as Foxpro DOS runs in your Windows 7. Note 2: If you are installing WPDOS from an original WordPerfect CD-ROM that contains an installation program, insert the CD in the drive; then, at the command prompt that you opened
How to Save Space in Using WhatsApp Many people have problem with their handphone while using WhatsApp. You will be prompted with a permission dialog box. Optional additional steps: If you have not installed a driver for your printer, do so now, either from the original WordPerfect installation disks or from the WPDOS 5.1 or WPDOS 6.x It's because WhatsApp automatically download photos and videos ...
Double-click on either shortcut to edit the associated file in Windows Notepad; close the file when you are finished. Type a few words or your name or anything else. Edit the file in Windows Notepad, and save the file. Step 8: Install All Available Windows Updates Microsoft is constantly updating and improving Windows system files that could be associated with autoexec.nt.
Read the "Warning" paragraph below; then edit the Autoexec.nt file and find the following lines (which will appear separate from each other, near the top of the file): %SystemRoot%\system32\mscdexnt.exelh %SystemRoot%\system32\redir lh