From: Stephen Kitt Newsgroups: comp.os.msdos.djgpp Subject: Re: Install bash as DOS 6.22 shell Date: 02 Dec 1996 11:53:15 +0000 Organization: Dept of Artificial Intelligence, Edinburgh University, Scotland Lines: 30 Sender: stephenk AT rhubarb DOT dai DOT ed DOT ac DOT uk Message-ID: References: <574ef8$5dk AT nexp DOT crl DOT com> <01bbd8e8$2f3c16a0$010200c0 AT weiqigao> <3296BC7E DOT 6B9A AT stud DOT warande DOT ruu DOT nl> <01bbda1f$b76aed20$010200c0 AT weiqigao> <3298C61E DOT 79B6 AT cornell DOT edu> NNTP-Posting-Host: rhubarb.dai.ed.ac.uk To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp "A. Sinan Unur" writes: > Weiqi Gao wrote: > ok, i got interested in the idea myself. here is what happens if you > step through config.sys and autoexec.bat (using F8). in config.sys, the > install and installhigh lines are excuted LAST regardless of the order > you put them in! in particular, INSTALL=c:\djgpp\bin\cwsdpmi.exe -P gets > executed after the SHELL=c:\djgpp\bin\bash.exe /p/e:8192 (or whatever > you like...) > > i do not know if this is the cause of the problem. No. The SHELL line does get executed before the INSTALL lines, but all it does is tell DOS where to get the command processor. DOS only actually loads the processor at the very end of CONFIG.SYS, *after* everything else. If you need proof, just try loading everything you have in AUTOEXEC.BAT (including SETs) in CONFIG.SYS, and using Windows as your command processor (SHELL=C:\WINDOWS\WIN.COM). Everything you specified in the INSTALL lines will get loaded before Windows, and COMMAND.COM is never required, but PATH etc. are present under Windows. Try running MEM directly from Win, ie without using a DOS box; just use File/Run and type MEM. Stephen -- Stephen Kitt, the University of Edinburgh, Scotland My views are not necessarily the University's Email: s.kitt at ed.ac.uk Web: http://omni.bus.ed.ac.uk/skk "It's kind of fun to do the impossible" -- Walt Disney