call autoexec.bat sequence not loaded during boot up.

[Guest]

I recently installed a program and it requires some call sequences to be
loaded on my pc before the program can function correctly. I've added these
call sequences on the autoexec.bat file but after boot up it's not being
loaded in my pc. I have to manually call the autoexec. bat in ms-dos in
windows environment before it adds the sequences to the machine but since the
program requires it to be loaded during start-up it doesn't work. How can i
resolve this. Thanks.

 

[Jerry]

XP doesn't really use AUTOEXEC.BAT but, it uses CONFIG.NT and AUTOEXEC.NT.
What you do is make a copy of AUTOEXEC.NT, make your changes, and try again.
The edited file should be in the \system32 folder.

 

[Guest]

Hey Jerry,
Thanks for the reply, but it didn't really do the call sequence that I
wanted to add.
Here's the sequence I want to add, maybe this will help. It's saved under
PCOBENV.BAT so I added the CALL PCOBENV.BAT in the autoexec.nt file nothing
happened. I also looked at the other set commands included in the .nt file
and seems like it's not being processed. I.e. SET BLASTER=A220 I5 D1 P330 but
when I typed in set using MS-DOS mode I couldn't see this in there which
leads me to believe that windows is using something else to initialize it's
files. Any other suggestions? Thanks.


path=C:\PCOBWIN;
set cobdir=C:\PCOBWIN
set dsgdir=C:\PCOBWIN
set cobcpy=C:\PCOBWIN\CLASSLIB
set cobhnf=C:\PCOBWIN
set cobsw=+p3/s14000

 

[Alex Nichol]

I recently installed a program and it requires some call sequences to be
loaded on my pc before the program can function correctly. I've added these
call sequences on the autoexec.bat file but after boot up it's not being
loaded in my pc.

XP does not use or process autoexec.bat. And does not allow real mode
TSR programs such as that program probably wants. You can *try* putting
the lines in Windows\system32\autoexec,nt to be loaded when you invoke
the program; but I would not be optimistic. XP just will not run some
of these old legacy programs; they were allowed loopholes in Windows9x,
that resulted in instability