Subj : Revisions ... To : Jasen Betts From : Gerald Miller Date : Tue Oct 22 2002 12:15 am Hello Jasen, On Monday October 21 2002 at 05:57, Jasen Betts [3:640/531.42] wrote to Gerald Miller, about: Revisions ... GM>>>> === Cut Begin: XBOOT2.BTM === [snip] GM>> Oooops. Okay, I admit to the pipe character in exchange of the GM>> "³" character, but didn't know about not being permitted to use GM>> "%=" within a quote (trying to prevent wordwrap truncation) and GM>> require clarification about your error of the date format JB> the dates in the data file were not compatible with the date format JB> here and causing errors etc.. once I editied that it started to work. Would a Country / CodePage "checking" routine be a requirement within the BTM? With a well designed routine, it should be able to determine current system's Country / CodePage / Date / Time formats and "self" correct itself and apply likewise corrections to the data file (and any other included files)..... GM>>>> and obtain the "NEXT RUN" value, which I had tried to do in the GM>>>> INCLUDE subroutine. I found that it wasn't quite as simple... JB>>> It is that simple. GM>> Just maybe.... Went to the ":INCLUDE" subroutine. Ammended to: GM>> === *** === GM>> :include GM>> set i=%@inc[%i] GM>> set run%i=%prog GM>> set nextdate=%@date[%@eval[%@date[%today] + %when]] GM>> return GM>> === *** === GM>> I then went to the line(s): GM>> === *** === GM>> iff "%ask" eq "N" .or. "%ask" eq "" then GM>> gosub include GM>> echo %@format[-41.41,%prog]³%@format[-10.10,%when]³%= GM>> %@makedate[%today]³%@makedate[%nextdate]³%ask >> %temp JB> (that's one of the echo lines) GM>> endiff GM>> elseiff "%prog" ne "" then GM>> echo GM>> %@format[-41.41,%prog]³%@format[-10.10,%when]³%last%= GM>> ³ ³%ask >>> %temp JB> (another one) JB> I made that mistake forst time. right here it deletes nextdate again. Yes, I discovered that little glitch also. I compensated for it by changing: === *** === ³ ³%ask >>> %temp === *** === to === *** === ³%next³%ask >>> %temp === *** === which should extract the "old" values for this "non-run" program from line %n of the previous data file. Okay, I am now understanding what "echo" lines you are referring to: === *** === :ask echo %@format[-41.41,%prog]³%@format[-10.10,%when]³%@makedate[%today]%= ³%@makedate[%nextdate]³%ask >> %temp ....... echo %@format[-41.41,%prog]³%@format[-10.10,%when]³%last³%next³%ask >> %temp ....... ....... :no-ask echo %@format[-41.41,%prog]³%@format[-10.10,%when]³%@makedate[%today]%= ³%@makedate[%nextdate]³%ask >> %temp ....... echo %@format[-41.41,%prog]³%@format[-10.10,%when]³%last³%next³%ask >> %temp === *** === And, before you ask, NO, the ":ask" and ":no-ask" labels are not in the batch file.... :)) The way I understand it, the ASK section and the NO-ASK section are essentially the same. The NO-ASK section is more automatic as the %ask variable is set to N and the batch file can perform in a continuous run. The ASK section is only for those times when user interaction is required for a query about whether the batch file should run that program or not. What exactly are you proposing for the echo lines? GM>> I then ran the BTM. It looks promising.... JB>>> It maay be easier if you first but first you should split the JB>>> echo that writes to the data file off into a subroutine instead JB>>> of having it repeated 4 times. GM>> I'm sorry, I'm not understanding your intent. Would you explain GM>> in more detail and/or example JB> nextdate is being read from the file as " " which 4dos shortens JB> to "" so you'll need to use a %format or something when you copy lines JB> to the temp file, JB> you'll probably have seen what I mean by now. Sigh.... Yes, you are correct and I did have to make some revisions. Hopefully, this has been addressed by XBOOT3.BTM.... I'm still running my tests to verify. :)) In the meantime, I'll see about crafting up a check routine for the XBOOT4.BTM release.... Cheers ... Gerald --- GoldED+/386 v1.1.5-21011 * Origin: I woke above ground again today. (1:342/512) .