| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Late breaking news .... |
Hello Jasen,
Remember when I asked about:
on errormsg (log /w %{at}path[%{at}search[%0]]%{at}upper[%{at}name[%0]].ERR)
??? Well, I've had some form of results.... I put that line in one of the
batch files that was misfiring sporadically when called from xboot3.btm. I
have an error log file that is 27 lines long; each line starts with the
date and time, then has a 4dos btm code segment (from the misbehaving btm);
BUT, no 4dos error message, no line numbers, and the log file even contains
some commands from 4EXIT.BTM.
I think I will experiment with some of the following to see what will
happen:
on errormsg ? (log /w %{at}path[%{at}search[%0]]%{at}upper[%{at}name[%0]].ERR)
on errormsg ?? (log /w %{at}path[%{at}search[%0]]%{at}upper[%{at}name[%0]].ERR)
on errormsg _? (log /w %{at}path[%{at}search[%0]]%{at}upper[%{at}name[%0]].ERR)
on errormsg _syserr (log /w %{at}path[%{at}search[%0]]%{at}upper[%{at}name[%0]].ERR)
Any opinions or suggestions?
Thanks ... Gerald
... For some reason, the mention of slug oils turned my stomach.
--- GoldED+/386 v1.1.5-21124
* Origin: If it's stupid but works, it isn't stupid. (1:342/512)SEEN-BY: 24/903 106/2000 120/544 123/500 140/1 342/5 512 400/300 633/104 260 SEEN-BY: 633/262 267 270 285 640/954 690/682 771/4020 774/605 2432/200 @PATH: 342/512 5 140/1 106/2000 123/500 774/605 633/260 285 267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
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™.