Hello, > On Mar 19, 2023, at 10:27 PM, Prime Seal <sealpri...@gmail.com> wrote: > > Mr J Hall here is the links to the video of FreeDOS after configuration. > The errors after configuring fdauto.bat file > YouTube: https://www.youtube.com/watch?v=h5_fXGL36yo > <https://www.youtube.com/watch?v=h5_fXGL36yo> There a a couple problems with your additions.
First, that is a lot of environment variables. As Willi suggested, you may want to increase you environment space. But, there is a more serious problem… You have 11 variables with a minimum of 15 characters each. Which is over 150 characters. Which you then attempt to append into the PATH variable. This is not possible. Those variables are expanded before the set a new variable. This means toy are attempting to use a command line of well over the 125 character limitation in FreeCOM batch files. You need to go about this a different way. If you want easy access to all of those tools, here is what I suggest. 1) return the FDAUTO.BAT back to its original state. 2) create a environment setting batch file under the C:\FREEDOS\LINKS\ directory to configure things for the different tools. 3) create an “unset” batch under that directory as well. This would easily allow you to select or switch development environments. Here is a quick example of files you could create under the links directory…. ———————————————————————— NODEVENV.BAT ———————————————————————— @echo off rem remove any development specific environment varaibles set LUAC= set WATC= set FASM= set BCC= set DGP= set DJGPP= rem add more as needed to clean stuff up rem Return the system path to it’s default setting. if not “%DEFAULTPATH%” == “” set PATH=%DEFAULTPATH% set DEFAULTPATH=%PATH% ———————————————————————— FASM.BAT ———————————————————————— @echo off rem clear any existing development settings call %DOSDIR%\LINKS\NODEVENV.BAT set FASM=C:\DEVEL\FASM set PATH=%FASM%;%PATH% cd %FASM% echo Switched to FASM development environment. ———————————————————————— Then simply typing “FASM” will switch everything you need to work with FASM. Since, the C:\DEVEL\FASM directory would be first in the PATH setting, you do not need to worry about any file name collisions. For example, typing FASM again would now try to run the C:\DEVEL\FASM\FASM.EXE and not the FASM.BAT file. > > Kind regards > Seal Prime > _______________________________________________ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel
_______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
