According to the FTP logs, a couple of you are downloading QBAT. It's still undergoing much experimentation and changes. The filename has changed. I have put it in a zipfile, ftp://lucky.syr.edu/4plugins/qbat.zip, along with a brief txtfile.
Did you get my emails? When you first reported that, there was a bug. Plugin>I'm still getting an error with QBAT when I do not specify a
>batch file name on the command line. See below. Something is
>inserting "Files\JPSoft\TCMD9\" after the current directory
>name. For the moment I have solved the problem by defining
>an alias that ensures that a file name is specified.
>
>-- Jay
>
>C:\temp>*qbat
>QBAT: Failed to open "C:\temp\Files\JPSoft\TCMD9\tcc.exe"
>
>C:\temp>echo %comspec
>C:\Program Files\JPSoft\TCMD9\tcc.exe
Well, I'm dumbfounded. I would expect that string in argv[0] when the string>Before my last reply, I had not read the rest of your message. I just
>downloaded and installed your version with the debug message. Here's
>what I get.
>
>C:\temp>*qbat
>QBAT will use the file: C:\temp\Files\JPSoft\TCMD9\tcc.exe
>QBAT: Bad file extension
Looks like an unquoted "C:\Program Files\....." Possibly your shortcut> Boy is this strange! Here's the output from the latest debugging version.
Strange! I'd say so. When I tested here, I saw the whole name of the exe in>Boy is this strange! Here's the output from the latest debugging version.
>
>-- Jay
>
>C:\temp>*qbat
>psz = ****
>argc = 2
>argv[0] = **C:\Program**
>argv[1] = **Files\JPSoft\TCMD9\tcc.exe**
>QBAT will use the file: C:\temp\Files\JPSoft\TCMD9\tcc.exe
>QBAT: Bad file extension
Jay, get a new one (ftp://lucky.syr.edu/4plugins/qbat.zip). I abandoned the use>Clearly some quotes are missing somewhere in the code, either Vince's
>code or Microsoft's code (or, I suppose, Rex's code). The directory
>"Program Files" is the normal directory for programs in Windows XP.
>(Vince, to answer your question, I'm running XP SP2.)
Looks like there are still a couple of trace lines in there:> Jay, I'm glad to hear it's working better. I added a handy feature ... a single-line
> edit control for parameters to the batch file. There's a new file in place.
A good idea. I'll work on it when I get home from work. I might have to signal>Here's another idea for accomplishing a similar end. How about allowing
>additional parameter on the QBAT command line that would become the
>initial parameter string for the QBAT editing session. Then command-line
>recall or an alias could be used to remember parameters that one wants
>each time.
QBAT writes "ON BREAK QUIT" at the beginning of the batch file before running>Looks like there are still a couple of trace lines in there:
>
>QBAT: idle
>QBAT: running D:\Data\qbat.bat
>
>ON BREAK QUIT
>echo hello
>hello
>
>QBAT: idle
>>QBAT: idle
>>QBAT: running D:\Data\qbat.bat
No, it's the QBAT: idle and similar lines I meant. Are they> QBAT writes "ON BREAK QUIT" at the beginning of the batch file before running
> it. If you're seeing the lines of the batch file, it's because you have batch
> echo on.
If you were referring to the "QBAT: ..." lines, they're present by design.>---Quote---
>>Looks like there are still a couple of trace lines in there:
>>
>>QBAT: idle
>>QBAT: running D:\Data\qbat.bat
>>
>>ON BREAK QUIT
>>echo hello
>>hello
>>
>>QBAT: idle
>---End Quote---
>QBAT writes "ON BREAK QUIT" at the beginning of the batch file before running
>it. If you're seeing the lines of the batch file, it's because you have batch
>echo on.
Yes they're intentional, to help make sense of what's in the console. Have you>---Quote---
>>>QBAT: idle
>>>QBAT: running D:\Data\qbat.bat
>---End Quote---
>
>
>---Quote---
>> QBAT writes "ON BREAK QUIT" at the beginning of the batch file before running
>> it. If you're seeing the lines of the batch file, it's because you have batch
>> echo on.
>---End Quote---
>No, it's the QBAT: idle and similar lines I meant. Are they
>intentional? (No problem if they are, I just assumed they were debug
>stuff).
How about just a line of 10 dashes or so in place of the QBAT: idle> Yes they're intentional, to help make sense of what's in the console. Have you
> got ideas for any shorter indications of when execution begins/ends? What they
> actually say doesn't help me any.
The 10 dashes works for me. And I added the @ as requested (good idea). I also allowed for QBAT command line parameters to the batfile (see /?). Those parameters are remembered across QBAT sessions (within the same TCC session) and are auto-restored if you use the parameters edit box to execute a command (still a preliminary feature with no safe-guards).2008/8/5 vefatica <>:
How about just a line of 10 dashes or so in place of the QBAT: idle
line, and remove the "Running" line altogether? That way each run is
separated by a single line.
Also, can you add an "@" at the start of the ON BREAK QUIT? I don't
have "Default batch echo" switched off, so the ON BREAK line gets
displayed, which is mildly irritating.
Paul.
Hmmm!>Another sudden thought. Would it be worth making the default filename
>QBAT.BTM, to run in the efficient BTM mode?