TIP: Click on subject to list as thread! ANSI
echo: 4dos
to: RAYMOND BERIAU
from: GERALD MILLER
date: 1998-04-20 08:59:00
subject: Calling another batch file...

Hello Raymond,
 \|/  Subject:  Calling another batch file...
 /|\  On Sunday April 19 1998 at 15:31, 
      you wrote to Laurent Jumet saying:
 RB>>> I have included in my 4DOS.INI file the following line:
 RB>>> AutoExecPath = C:\4DOSEXEC.BAT
 RB>>> With the above statement, and according to the docs/help file,
 RB>>> when 4DOS installs itself, it should call (load) 4DOSEXEC.BAT
 RB>>> rather than calling (loading) AUTOEXEC.BAT
 LJ>> Don't forget that statements in CONFIG.SYS line override those in
 LJ>> 4dos.ini.
 RB> I know that...
 RB> Just to be sure that 4DOS would call directly 4DOSEXEC.BTM directly
 RB> (without first calling AUTOEXEC.BAT), I placed the line
 RB>     AutoExecPath = C:\4DOSEXEC.BTM
 RB> in my 4DOS.INI file, and the line:
 RB>     SHELL=C:\4DOS\4DOS.COM C:\4DOS @C:\4DOS\4DOS.INI /PC:\4DOSEXEC.BTM
 RB> in my CONFIG.SYS file.
I can't help but wonder if the "@C:\4DOS\4DOS.INI" section in your CONFIG.SYS 
could be causing _some_ of the problem...  I had my CONFIG.SYS file 
established in a manner similar to yours and for some reason that I forget, I 
dropped the "@C:\4DOS\4DOS.INI" from the line and I've not had a problem.
=== Cut Begin: 4DOS.HLP ===
  @d:\path\inifile:  This option sets the path and name of the 4DOS.INI
  file.  You don't need this option if you aren't using an .INI file at
  all, or if the file is called 4DOS.INI and it is either in the same
  directory as 4DOS.COM or in the root directory of the boot drive.
  This option is not necessary for a secondary shell if you want 4DOS to
  use the same .INI file that you used for the primary shell, because
  values from that file -- including those in its [Secondary] section --
  will be passed automatically to secondary shells.
=== Cut End:   4DOS.HLP ===
With your /PC:\4DOSEXEC.BTM example, I think you should try renaming it to
a BAT file and use a LOADBTM ON statement within your 4DOSEXEC.BAT file...
Or -- Drop the C:\4DOSEXEC.BTM part from your /P directive; you have it 
specified within the 4DOS.INI file (AutoExecPath = C:\4DOSEXEC.BTM) and the 
system could be confused that the filename is specified TWICE! ???
=== Cut Begin: 4DOS.HLP ===
  /P[:filename]:  This option tells 4DOS to load permanently and to run
  AUTOEXEC.BAT.  If you specify a filename after the /P, that file will be
  run instead of AUTOEXEC.BAT.  You should specify the full name of the
  file, including drive and directory.  A filename after /P will OVERRIDE
                                                                 ^^^^^^^^
  the AutoExecPath option in 4DOS.INI.
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
=== Cut End:   4DOS.HLP ===
 RB> Unfortunately, 4DOS still calls AUTOEXEC.BAT and not 4DOSEXEC.BTM...
Try the following:
    SHELL=C:\4DOS\4DOS.COM C:\4DOS\ /P
and maintain your "AutoExecPath = C:\4DOSEXEC.BTM" within your 4DOS.INI file 
(or maybe move it to 4DOS -- "AutoExecPath = C:\4DOS\4DOSEXEC.BTM") [you may 
also have to move the AUTOEXEC.BAT file to C:\DOS]...
              G'Day ... Gerald
--- GoldED/386 2.50 UNREG
---------------
* Origin: 4DOS for one and 4DOS for all! (1:153/715.6)

SOURCE: echomail via exec-pc

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.