--------------- FIDO MESSAGE AREA==> TOPIC: 148 4 DOS Ref: F5G00127 Date: 04/18/98 From: BILL DRAKE Time: 07:37pm \/To: VIC BATES (Read 1 times) Subj: win95 dos prompt propert VB>I have 4dos setup as primary shell in my config.sys file... VB>shell=c:\4dos\4dos.com c:\4dos /P VB>In win95 I have a shortcut desktop icon setup to run 4dos, VB>because for some reason even though it's the primary shell VB>it doesn't automatically run when VB>I open a dos prompt. VB>Doing it this way I'm also able to open a normal MSdos box from win95 u VB>the normal dos prompt menu option. But the only problem I VB>had with this was MSDOS didn't like my 4dos prompt too VB>much. In the prog properties for the dos prompt where the VB>command line etc is specified there's a section to setup a VB>batch file which is automatically run. I thought I'd use VB>this to change the prompt to something command.com can VB>handle. Problem is that whenever I specify anything here VB>4dos always starts instead of command.com, no matter what! VB>It doesn't matter that command.com is specified as the program command VB>as soon as I specify a batch file/command to be run 4dos VB>starts instead of command.com! The only way I've found to VB>get around this is to use the /K switch after the command VB>line. Is this a win95 problem or something wrong with how VB>I've setup 4dos? Hi, Vic. Your problem is a consequence of how W95 executes batch files. By default, W95 uses the COMSPEC environment variable to find the command processor when a batchfile is called in a DOSbox PIF. Since you load 4DOS through the SHELL statement in Config.Sys, COMSPEC points to 4DOS.COM and those services are used for batchfiles. Using the /K switch on the command line in the PIF overrides the use of COMSPEC to load the batchfile -- permitting the use of COMMAND.COM as the shell for a batchfile rather than the command processor pointed to by COMSPEC. Note: Open a 4DOS window. Type SET in that window and look at the COMSPEC variable. Now type COMMAND in that window. Watch as the COMMAND processor loads over 4DOS. Now type SET again and look at COMSPEC. See how the COMSPEC variable tracks the active command processor? Now type Exit to close the COMMAND processor and return to 4DOS. Type SET again and look at COMSPEC. Back to 4DOS, as consistent with the active command processor, just as it should be. The above works fine as long as the methodology described above is used. However, things break down if you make an MS-DOS PIF loading COMMAND.COM without the /K switch, when using 4DOS as the primary shell. Since the COMSPEC environment variable in the master environment (which the COMMAND.COM shell inherits) is still pointing to 4DOS.COM, a PIF pointing to COMMAND.COM without the /K parameter is schizoid. Note: See the "MSDOS 6.22" Helpfile for further info on the requirements for the /K parameter in Windows PIFs. Type "Help" from the Command.Com DOSbox for further info. The DOS7 helpfiles are installed in the WINDOWS/COMMAND folder -- data as follows: HELP COM 413 07-11-95 9:50a HELP.COM HELP HLP 301,961 07-11-95 9:50a HELP.HLP These files are found on W95 systems with the Supplemental Utilities installed from the W95/W95A CD-ROM or with the appropriate CD-ROM Addons downloaded from the MS website. Please note the W95 version of the Helpfile is NOT identical to the real MSDOS 6.22 Helpfile, which has data as follows: HELP COM 413 05-31-94 6:22a HELP.COM HELP HLP 299,832 05-31-94 6:22a HELP.HLP If you wish to use a full COMMAND.COM DOSbox with 4DOS as your default shell, using COMMAND.COM as the batchfile processor in that DOSbox, then make a dedicated PIF as follows: C:\WINDOWS\COMMAND.COM /K (OPTIONAL BATCHFILE> Default Folder: as desired. Batchfile: CANNOT BE USED IN PIF WITH ALTERNATE SHELL Voila, a *real* COMMAND.COM DOSbox with all its limitations, operating with 4DOS as the primary shell. Potential Gotchas: 1. As noted above, once a PIF opens a DOSbox on the desktop or fullscreen, subsequent batchfiles and subshellloads/unloads can be performed at will. It is only the batchfile-load process for the opening of the PIF which is limited in scope. 2. Do NOT leave a DOSbox open while editing its PIF. If you do, the PIF properties of the open DOSbox will overwrite your changes when that DOSbox window is closed. 3. Edits to a DOSbox PIF will not be saved until cached info is written back to disk. Ensure that you wait for the DOSbox PIF's icon to "blink" before you re-open an edited dosbox PIF. (normally 2-3 seconds) Best I can do for now. Bill ___ * PW * --- Maximus 2.02 * Origin: VKUG/VPCC 4DOS Echo - Richmond, BC (1:153/151) --------------- FIDO MESSAGE AREA==> TOPIC: 148 4 DOS Ref: F5G00128 Date: 04/18/98 From: BILL DRAKE Time: 07:40pm \/To: RAYMOND BERIAU (Read 1 times) Subj: Re: Calling another batc RB> Well, no matter what I do and what I try, I cannot get 4DOS to call RB> (load) directly 4DOSEXEC.BAT - for some unknown reasons, 4DOS alway RB> call (load) AUTOEXEC.BAT first. RB> RB> Why? What am I doing wrong? Hi, Raymond. As far as I am aware, the subsidiary-batchfile-exec process is *in addition* to the Autoexec.Bat -- it is not a substitute. The intent is to put 4DOS-specific commands in the 4DOSEXEC.BAT and leave commands that are generic to both COMMAND.COM and 4DOS in the AUTOEXEC.BAT file. Best I can do for now. Bill ___ * PW * --- Maximus 2.02 * Origin: VKUG/VPCC 4DOS Echo - Richmond, BC (1:153/151) --------------- FIDO MESSAGE AREA==> TOPIC: 148 4 DOS Ref: F5G00129 Date: 04/19/98 From: VIC BATES Time: 12:53am \/To: KLAUS MEINHARD (Read 1 times) Subj: no memory for 4dos under win95 Hello Klaus, KM> you need a line in your SYSTEM.INI, section [386enh], reading KM> LocalLoadHigh=1 Thanks for the tip Klaus. I've not heard of this before. I couldn't find any reference to it in any win95 books or even in the resource kit. KM> even if you are running Windows95 (vs. 3.1n) to grant UMBs to DOS KM> sessions. I'm not at my win95 machine at the moment so can't try it on that. I just tried it on this wfwg machine and it stopped windows running altogether. I had to remove it to run windows again. Must be a win95 only thing. Rgds, Vic --- GoldED/386 2.50+43UK1 * Origin: The Bates Motel! Bolton, UK. (2:250/167) --------------- FIDO MESSAGE AREA==> TOPIC: 148 4 DOS Ref: F5G00130 Date: 04/19/98 From: VIC BATES Time: 12:22am \/To: KLAUS MEINHARD (Read 1 times) Subj: no memory for 4dos under win95 Hello Klaus, KM> As I told before in a message that went unacknowledged, I've just replied to your other msg Klaus. Both of msgs arrived yesterday but I was unable to reply immediately. KM> WIN 3.1x _and_ WIN 95/98 _must_ have an System.ini entry in section KM> [386ENH] that reads LocalLoadHigh=1 in order to provide UMBs to a KM> DOS session. Simply add that line and reboot. As mentioned in my previous msg, I assumed that was a win95 only thing as I tried it on this wfwg system and it stopped windows from running! KM> One hitch: there must be free UMB mem before WIN starts to provide KM> some later... Yes there is, it will be created by Qemm. Although it can't be seen by opening a 4DOS prompt from within win95 as by that time it's too late, vmm32 has grabbed the lot. Thanx again Klaus. Rgds, Vic --- GoldED/386 2.50+43UK1 * Origin: The Bates Motel! Bolton, UK. (2:250/167) --------------- FIDO MESSAGE AREA==> TOPIC: 148 4 DOS Ref: F5G00131 Date: 04/19/98 From: VIC BATES Time: 12:37am \/To: STEVE STACHER (Read 1 times) Subj: BTM files under win95 Hello Steve, VB>> Why does win95 explorer not recognize BTM files as executable? SS> Because you need to define it. Here is the JP solution: Thanks Steve, I'll give it a try although mine does recognize normal BAT files it's BTM files it doesn't recognize. SS> If your Windows configuration already allows you to edit the Properties SS> of batch files (file type "batfile") by opening an Explorer Window ("My SS> Computer", for example) and selecting "View", "Options", then "File SS> Types", you don't need this file. Do I still need it then? I'm confused.. As I said BAT files are ok, not BTM. Rgds, Vic --- GoldED/386 2.50+43UK1 * Origin: The Bates Motel! Bolton, UK. (2:250/167) --------------- FIDO MESSAGE AREA==> TOPIC: 148 4 DOS Ref: F5G00132 Date: 04/01/98 From: ANDY ROBERTS Time: 06:51pm \/To: JIM HAUGHT (Read 1 times) Subj: File base Sorry about that problem. From the File menu press N for New and enter 98215 (date) again. It should work ok now. Also I started a new echo TSR-FILES which has a listing of new files received since the 1st of March. I update that with new msgs as new files come in. Have fun! Thanks and Good Luck, Andy Roberts <:{) NetMail 1:109/921.1 --- AdeptXBBS v1.11y (FREEWare/2) * Origin: TSR - TERMINATE SUPPORT REGISTRATIONS (1:109/921) --------------- FIDO MESSAGE AREA==> TOPIC: 148 4 DOS Ref: F5G00133 Date: 04/07/98 From: JASON DOVEL Time: 08:59pm \/To: ANDY ROBERTS (Read 1 times) Subj: Re: NE2000.zip AR> D/L Ne2000.zip for the manual. Thanks. The network is up and running. Jeff, my neighbor, went and got me the cables and connectors I needed while I was at school. I installed Windows for Workgroups 3.11 on the 486, put the 440MB and 120MB HD's in the 486, and made it the dedicated server, and copied all of the neccessary network files to it, so drive C: now has 300 MB free on it and drive D: (the 120mb drive) has 5-10 MB free. The load off the Pentium 200 (and the makeup in disk slack), on top of deleting no longer needed files, brought me from 120 MB free on my 1.6 GB to 400 MB free. EVerything is running wonderfully, and very, very quickly. LAter, Jason Dovel --- AdeptXBBS v1.11y (FREEWare/2) * Origin: TSR - TERMINATE SUPPORT REGISTRATIONS (1:109/921) --------------- FIDO MESSAGE AREA==> TOPIC: 148 4 DOS Ref: F5G00134 Date: 04/06/98 From: ANDY ROBERTS Time: 10:00pm \/To: JASON DOVEL (Read 1 times) Subj: NE2000.zip D/L Ne2000.zip for the manual. Thanks and Good Luck, Andy Roberts <:{) NetMail 1:109/921.1 --- AdeptXBBS v1.11y (FREEWare/2) * Origin: TSR - TERMINATE SUPPORT REGISTRATIONS (1:109/921) --------------- FIDO MESSAGE AREA==> TOPIC: 148 4 DOS Ref: F5G00135 Date: 04/16/98 From: PAUL WALKER Time: 05:19pm \/To: KLAUS MEINHARD (Read 1 times) Subj: BTM / GoldED / Win95 Hi Klaus, Klaus Meinhard to Paul Walker, 02 Apr 98 08:05. KM> drop target. According to JPSOFT's support, you would have to patch KM> W95 files to change this. Ah. I'm not into patching Win95, it has enough problems anyway. ;) KM> I do not know, however, how this may relate to your problem. If the KM> btm file does not get executed, perhaps a fully qualified call KM> (C:\4DOS\4DOS.COM mybatch.btm) or something like that might help? It would; I just wanted to see if there was a way to solve it, since the problem's bound to come up again in a situation where I can't solve it that way. Doesn't look like it. :( Thanks anyway, Paul (p.r.walker@warwick.ac.uk) ... "A lie is a very poor way to say hello." Keeler --- FMail/386 1.22 * Origin: "I think, Sebastian, therefore I am." -- Pris (2:254/60.11) --------------- FIDO MESSAGE AREA==> TOPIC: 148 4 DOS Ref: F5G00136 Date: 04/16/98 From: PAUL WALKER Time: 05:23pm \/To: KLAUS MEINHARD (Read 1 times) Subj: no memory for 4dos under win95 Hi Klaus, Klaus Meinhard to Vic Bates, 09 Apr 98 07:52. KM> you need a line in your SYSTEM.INI, section [386enh], reading KM> LocalLoadHigh=1 KM> even if you are running Windows95 (vs. 3.1n) to grant UMBs to DOS That's fixed it - thanks. :) Paul (p.r.walker@warwick.ac.uk) ... "Mudhole? Slimy? My home this is!" - Yoda --- FMail/386 1.22 * Origin: "No more rules." -- Duncan MacLeod (2:254/60.11)