Autoexec.bat == autoexec.nt under DOS & Win95
config.nt == config.sys under DOS & Win95
These two files — Config.nt and Autoexec.nt — are used by default to initialize every VDM started in Windows.
Special Note: Config.nt and Autoexec.nt are for DOS and Windows 16-bit application (VDM) support only. Settings in these files have no effect on Windows 32-bit applications.
If you have special device drivers, TSRs, initial programs, or environment variables that need to load for a majority of your DOS or Windows 16-bit applications, you may wish to place references to these items in Config.nt and Autoexec.nt. Remember that whatever you place in the files will be executed before each and every DOS or Windows 16-bit application that runs under Windows, but not prior to that event.
Tip for Windows 95 Users: Autoexec.bat and Config.sys have the same function in Windows 95 that they have in regular MS-DOS; that is, all lines in both files are executed before loading Windows 95. Windows NT 4.0 does not use the files in this manner; it uses them only for environment-variable information. If you maintain special lines in these files for your 16-bit DOS and Windows applications under Windows 95, you may need to copy or move these lines to the Config.nt and Autoexec.nt files.
i'm an application programmer (mostly c#, java and asp), so don't usually touch this stuff. i'll keep that in mind tonhu, but i'd still like the information without having to go outside.
____________________________________________________
If you like a post, show you care by giving it a <censored>.
It is an instruction to use the extended memory service to load a device driver outside of the base 640 memory address space to conserve it as much as possible for DOS.
I guess I was not clear in my original message. The autoexec.nt contains environment settings that are program dependent, device drives that are 16-bit dependent, and the occasional setting for DOS. It is used only when the virutal 16-bit DOS service is demanded under XP. There are no true "autoexec.bat"-only commands, which is the correlative to autoexec.nt. There are some true "config.sys"-only commands, but you did not ask about its correlative.
For autoexec.nt the commands will be any command native to 16-bit DOS.
what i'm really looking for is somewhere to put things like 'winipcfg /release' on startup. i have some script from our w98 machines that runs in autoexec.bat, i thought that there would be a way of doing the same things in autoexec.nt
____________________________________________________
If you like a post, show you care by giving it a <censored>.
i could do. i was really hoping for something that executes much earlier on startup. is there no way of just running a program from a command within autoexec.nt, and passing it some arguments?
____________________________________________________
If you like a post, show you care by giving it a <censored>.
Let me emphasis the point I made above in this thread. Autoexec.nt is only used to assist with the 16-bit DOS virtual machine. It is not run at startup on XP.
How early in the process do you need to run a program? What does this program do? If you provide clear answers to these questions Forum members can help you run the program:
. as a service, or
. from the preconfiguration .bat service,
. from another startup location,
. as an MSCONFIG entry using registry RUN services
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.