--------------- FIDO MESSAGE AREA==> TOPIC: 148 4 DOS Ref: F5G00226 Date: 04/28/98 From: RAYMOND BERIAU Time: 12:58am \/To: JASEN BETTS (Read 1 times) Subj: Calling another batch file... Hello Jasen! Quoting Jasen's message: RB>> SHELL=C:\4DOS\4DOS.COM C:\4DOS /F JB> major guess: maybe it's the /F (if it is it's a bug in 4dos), try JB> without it if that works, try critfail=yes in 4dos.ini. I tried removing everything, even the /F, but it did not solve the problem. Sincerely, Raymond Beriau. Co-Moderator 4DOS INFODATA Communications [+1 514 432 8467] ... Blue Wave! Not just for FIDONet anymore! --- LoraBBS-DOS v2.41b3 (Eval.) * Origin: INFODATA Communications - 4DOS Support (FidoNet 1:242/105) --------------- FIDO MESSAGE AREA==> TOPIC: 148 4 DOS Ref: F5G00227 Date: 04/27/98 From: JORJ STRUMOLO Time: 11:38pm \/To: BORIS TERZIC (Read 1 times) Subj: compressing EXEs BT> Not bad at all, but have you got WWPACK? It does a pretty decent job, I've tried it, at least some versions back, and it doesn't seem to like my setup, for whatever reason, and keeps locking me up. And to make up for the off-topic, a BTM fragment. Called by aliases 'da' thru 'dm', of the form 'call J x' where 'x' is the last letter of the alias and J.BTM starts out like: goto %1^goto End :A :B :C :D :E :F :G :H :I :J :K :L :M if %@ready[%1:] ne 1 ( echos |T|T|T|T Drive %@upper[%1]: not ready^quit) set Sz=%@disktotal[%1:,bc] byte capacity^set Na=%@lower[%@label[%1]] if %@diskused[%1:,b]==0 (echos |T|T|T Disk %1 {%Na} Empty * %Sz^goto DZ) echos |T|T|T -- %Sz --^echo |T %Na^*dir/h2vogeka %1:\%2& :DZ us Sz Na^quit ('|T' subbed for Ctrl-X T for Fido, plus other ascii-ization.) Produces output approximately like: 1 D:\SR$REPLY\CHOWDA>dc -- 2,035,200 byte capacity -- c2 charm autoexec.bat 1283 3-16-98 5:47p io.sys 40774 5-31-94 6:22a command.com 54645 5-31-94 6:22a msdos.sys 38138 5-31-94 6:22a config.sys 926 2-16-98 10:32p 135,766 bytes in 5 files and 0 dirs 136,704 bytes allocated 1,898,496 bytes free ... Ever notice that even the busiest people are never too busy --- SR 2.00 #1019 -!- to tell you just how busy they are? * Origin: Chowdanet! 20gb Amateur Radio BBS (401-331-5587) (1:323/120) --------------- FIDO MESSAGE AREA==> TOPIC: 148 4 DOS Ref: F5G00228 Date: 04/28/98 From: TOM HALL Time: 12:00am \/To: ALL (Read 1 times) Subj: Conference Rules 4DOS Users Guidelines: ---------------------- Please limit all discussion in the 4DOS echo to 4DOS/4OS2/TAKE COMMAND itself, or interfacing 4DOS/4OS2/TAKE COMMAND/etc. with other software. Threads dealing only with other software are off-topic for this echo. Commercial advertisements, or announcements of any kind not specifically related to the topic of 4DOS/4OS2/Take Command, are expressly forbidden. The official language of this echo is English. Please do not post to the 4DOS Echo in any other language. HI-BIT ASCII characters are not allowed in this echo. This is a Fidonet echo, and as such, may not be gated into other domains without the express permission of the moderator. Debates on "programming techniques" are strongly discouraged, unless they specifically apply to 4DOS/4OS2/TAKE COMMAND. Discussions on the merits (or lack of same) of other software is off-topic for this echo unless they specifically apply to 4DOS/4OS2/TAKE COMMAND. Discussion of the echo's moderation is OFF TOPIC in the echo. If you have a problem with the moderator, or the echo's moderation, take it to netmail. Violation of this rule will be grounds for immediate termination of your access to the 4DOS echo. One important change from the past: the posting of UUencoded BTM files is allowed. Please use your discretion when posting such files, keeping in mind that such encoded material tends to translate to very large messages, which MAY break other people's mail tossers, message readers, or both. If you see messages from others not obeying the echo rules, or the rules of good manners, please do NOT reply to them in this echo as I may have already done so via Netmail. Each SYSOP of systems carrying the 4DOS Echo is responsible for all traffic that enters the 4DOS Echo from his/her system. Since this is a FidoNet Backbone echo, all messages must include a FidoNet address in the origin line. And most of all: If you can do this with a sense of humor, all the better. If you must reply, do so only via Netmail, not in this echo! Tom Hall Moderator, 4DOS Echo February 18, 1997 --- MakeMsg v2.31 * Origin: Ten Forward: 4DOS Moderator (1:342/1.0) --------------- FIDO MESSAGE AREA==> TOPIC: 148 4 DOS Ref: F5G00229 Date: 04/26/98 From: RICHARD PEER Time: 05:24pm \/To: CLAUS MUELLER (Read 1 times) Subj: Re: EXECUTION PREFERENCE In a message of <23 Apr 1998 14:38>, Claus Mueller (2:2433/1204.32@fidonet) writes: CM>TM>If Eugene was right, the order of execution would have been: BAT, BTM, CM>TM>COM, EXE I would like the following order: BTM, BAT, COM, EXE ;-) CM>and the winner since dos 2.11 is: CM>COM (yeahhhh) CM>followed by exe followed by bat folluwed by btm Nope. Com first, then in order, Exe, Btm and finally Bat. Regards, Richard. --- Msged/Q 1.60 * Origin: Sysop "Novell User Group of SA" Pta, RSA (5:7106/22) --------------- FIDO MESSAGE AREA==> TOPIC: 148 4 DOS Ref: F5G00230 Date: 04/26/98 From: BARRY BLOCK Time: 04:01pm \/To: KLAUS MEINHARD (Read 1 times) Subj: don't work w/4dos Hello Klaus, BB>> echo @prompt Here's a displayed $l >~tmp.bat BB> command.com /e:625 /c ~tmp.bat>~tmp.dat type ~tmp.dat KM> ...CC's internal command PROMPT sends it's output "for no clear reason" KM> to stdout, while 4DOS's does not. KM> ... A little applied SETDOS before and after an ECHO command might do Very interesting :-) How does 4DOS process a prompt? Why not to standard out? Anyway...I had asked how to echo a > to the screen. 4DOS has no problem with this, of course. Echo `>` Regards, Barry --- Terminate 5.00/Pro * Origin: EBO-BBS A'dam +31-20-6002828 (2:280/901.42) --------------- FIDO MESSAGE AREA==> TOPIC: 148 4 DOS Ref: F5G00231 Date: 04/28/98 From: RAYMOND BERIAU Time: 09:46am \/To: KLAUS MEINHARD (Read 1 times) Subj: Calling another batch file... Hello Klaus! Quoting Klaus's message: KM> Please do not hit me if I ask for something obvious (I have not learned KM> every word you said in this thread by heart): Bang! Oops, I hope I didn't hit too hard... :) KM> Have you tried to name your alternative btm 4dosexec.BAT? Perhaps the KM> extension gets in the way, and you can always set loadbtm on later... Indeed, I have tried with the BAT extension without success, I have tried by removing AUTOEXEC.BAT from the root directory and leaving 4DOSEXEC.BAT (and .BTM) alone in the root directory, I have tried by placing 4DOSEXEC.BAT (and .BTM) in a sub-directory, and I have tried by placing AUTOEXEC.BAT in a sub-directory and modifying either CONFIG.SYS (the /P command) and 4DOS.INI (the AutoExecPath statement) to point to the new location of AUTOEXEC.BAT, all without success. :( I guess I will continue using my "bandaid" solution that is to call/load 4DOSEXEC.BTM depending of the choices made in CONFIG.SYS Sincerely, Raymond Beriau. Co-Moderator 4DOS INFODATA Communications [+1 514 432 8467] ... When all else fails, read the instructions. --- GoldED 3.00.Beta3+ * Origin: INFODATA Communications - 4DOS Support (FidoNet 1:242/105) --------------- FIDO MESSAGE AREA==> TOPIC: 148 4 DOS Ref: F5G00232 Date: 04/28/98 From: RAYMOND BERIAU Time: 09:57am \/To: KLAUS MEINHARD (Read 1 times) Subj: BTM files under win95 Hello Klaus! Quoting Klaus's message: SS>>>>> /* -!--Cut Here-!--!--!--!--!--!--!- (JPBATCH.REG) KM> Make that JPSOFT.INF or JP4DOS.INF... Indeed, that is what I have been using to make Windoes 95 more compatible with 4DOS... RB>>>> Where, may I ask, did you get that file from? TM>>> It *should* be available in every *original* 4Dos archive released TM>>> by JP Software, so I just checked the v6.01 archive I KM> it was, at least... That is where I found it with two other .INF files (if memory serve me ght). Sincerely, Raymond Beriau. Co-Moderator 4DOS INFODATA Communications [+1 514 432 8467] ... But soft, what light through yonder tagline breaks? --- GoldED 3.00.Beta3+ * Origin: INFODATA Communications - 4DOS Support (FidoNet 1:242/105) --------------- FIDO MESSAGE AREA==> TOPIC: 148 4 DOS Ref: F5G00233 Date: 04/28/98 From: JOHN HENTSCH Time: 09:28pm \/To: ALL (Read 1 times) Subj: Daylight savings time Before I set out and try to figure it out myself, I was wondering if someone already wrote a 4DOS BTM route to set an environmental variable depending on what date range it curently in. I need to set the set GTZ=UTC+7 for pacific daylight savings time and set GTZ=UTC+8 for standard pacific time. I would like to the GTZ adjustedg according to what the particular date it is. Thanks, jh - * WCE 2.1G1/2241 * --- ViaMAIL!/WC4 v1.40j * Origin: Mail Box BBS Glendora, CA USA (1:218/907) --------------- FIDO MESSAGE AREA==> TOPIC: 148 4 DOS Ref: F5G00234 Date: 04/28/98 From: GERALD MILLER Time: 07:29pm \/To: RAYMOND BERIAU (Read 1 times) Subj: Calling another batch file... Hello Raymond, On Friday April 24 1998 14:09, Raymond Beriau wrote to Gerald Miller: GM>> At this point, all I can say is to move AUTOEXEC.BAT to somewhere GM>> not on the path... RB> OK, here is what I tried so far: RB> with the following in CONFIG.SYS: RB> SHELL=C:\4DOS\4DOS.COM C:\4DOS /F RB> and the following in 4DOS.INI: RB> AutoExecPath=C:\4DOSEXEC.BTM RB> - I removed AUTOEXEC.BAT from the root directory and kept RB> 4DOSEXEC.BTM RB> Well, 4DOS booted but ignored completely 4DOSEXEC.BTM (a few RB> environment values set but no alias nor any TSR, etc.). RB> I then moved 4DOSEXEC.BTM to the 4DOS sub-directory and kept RB> AUTOEXEC.BAT in the root directory: RB> with the following in CONFIG.SYS: RB> SHELL=C:\4DOS\4DOS.COM C:\4DOS /F RB> and the following in 4DOS.INI: RB> AutoExecPath=C:\4DOS\4DOSEXEC.BTM RB> Well, 4DOS booted and loaded AUTOEXEC.BAT RB> I know that 4DOS read the "AutoExecPath=..." line as I entered a wrong RB> path and got an error message on the screen. RB> I even tried something else. I moved AUTOEXEC.BAT to my DOS RB> sub-directory, indicated the new location in the 4DOS.INI file, and RB> rebooted the computer. Well, 4DOS booted and went directly to the RB> prompt (as in my first example when 4DOS could not find AUTOEXEC.BAT RB> in the root directory... I wish I had an answer for you. I was bouncing alternatives off of you in the hope that one of them would provide a solution.... Have you tried NetMail to Rex Conn? GM>> + Origin: 4DOS for one and 4DOS for all! (1:153/715.6) RB> Should it not have been: "One for 4DOS, and 4DOS for all" :) Poetic license... ;^) G'Day ... Gerald --- GoldED/386 2.50 UNREG * Origin: 4DOS for one and 4DOS for all! (1:153/715.6)