Mail Archives: djgpp/2004/09/02/17:45:03
Jason,
**Its all true**
XP does indeed process C:\AUTOEXEC.BAT, but the file is only read when the
computer boots up. This means that any changes you make only take effect
after a reboot.
So, what I'm going to do is to do as you have done and remove everything
from this file and have only common stuff in autoexec.nt, and make my own
shortcuts that setup the environment as required for particular
applications.
Andrew
"Jason Hood" <jadoxa AT yahoo DOT com DOT au> wrote in message
news:413743AB DOT 4F5FEEAD AT yahoo DOT com DOT au...
| Andrew Wall wrote:
| >
| > That's very interesting, Rui, but on my system I haven't got an
Autoexec.bat
| > (Well I have, but that is located at C:\ and I know that isn't used
because
| > I never see any of the echoes from it), so I created one in
| > C:\Windows\System32 with just an echo in it and that never fires off!
| > This leaves Autoexec.nt as the only place to put these environment
| > variables.
|
| XP (don't about NT/2K) does indeed process AUTOEXEC.BAT, but *only*
| the environment variables (SET commands); everything else is ignored.
| This is useful in a dual-boot situation. I have "if 1==1 autow98.bat"
| as the first line in AUTOEXEC.BAT. If it's XP, it's ignored and the
| XP environment is setup, otherwise it processes the old AUTOEXEC.BAT.
|
| Jason.
- Raw text -