Command line - odd "multiple executions" problem

[laserfan]

I manually executed an x264 .cmd from the Command Prompt of Windows XP, one no different from others I've run except perhaps that the file was in .cmd format instead of .bat, and it ran twice in succession BY ITSELF (over-writing & ruining the 1st video-out and wasting 32 hours in the process):

D:\job1>job1_EncodeVideoPass2.cmd

D:\job1>"C:\Program Files\x264\x264.exe" "D:\job1\job1.avs"
--bitrate 4174 --level 4.1 --sar 1:1 --aud --vbv-bufsize 14745 --vbv-maxrate 17500 --filter 0,0 --ref 3 --mixed-refs --bframes 3 --b-rdo --bime --weightb --direct auto --subme 6 --trellis 1 --analyse p8x8,b8x8,i4x4,i8x8 --8x8dct --me umh --threads auto --thread-input --progress --no-psnr --no-ssim --stats "D:\job1\job1.stats" --pass 2 --output "E:\video.264"
avis [info]: 1920x1080 @ 23.98 fps (184119 frames)
.
.
.
x264 [info]: kb/s:4173.8

encoded 184119 frames, 1.58 fps, 4175.57 kb/s

D:\job1>job1_EncodeVideoPass2.cmd

D:\job1>"C:\Program Files\x264\x264.exe" "D:\job1\job1.avs" --bitrate 4174 --level 4.1 --sar 1:1 --aud --vbv-bufsize 14745 --vbv-maxrate 17500 --filter 0,0 --ref 3 --mixed-refs --frames 3 --b-rdo --bime --weightb --direct auto --subme 6 --trellis 1 --analyse p8x8,b8x8,i4x4,i8x8 --8x8dct --me umh --threads auto --thread-input --progress --no-psnr --no-ssim --stats "D:\job1\job1.stats" --pass 2 --output "E:\video.264"
avis [info]: 1920x1080 @ 23.98 fps (184119 frames)
.
.
.
x264 [info]: kb/s:4173.8

encoded 184119 frames, 1.63 fps, 4175.57 kb/s

D:\job1>
D:\job1>l
'l' is not recognized as an internal or external command,
operable program or batch file.

D:\job1>
D:\job1>l
'l' is not recognized as an internal or external command,
operable program or batch file.

D:\job1>This morning I opened the E: drive and saw my encoding was there & complete (whew), but when I opened the minimized Command Prompt window I witnessed the last two entries appear before my eyes, by themselves/hands-off the keyboard i.e. the "l" (and CR) errors!

Can anyone here who understands cmd.exe better than I comment: how might the initial command have been executed twice when I was not present? And then the couple of l's w/CRs that appeared afterwards when I opened the window--can keyboard entries get queued-up and be executed "by themselves"? Like maybe an "up-arrow" keystroke invoked the 2nd cmd (but then it needs a CR to execute)? I looked-in on the PC a time or two using VNC but don't think I ran any other programs or typed anything while the .cmd was running...

I'm at a loss to explain this bizarre behavior, unless maybe my battery-operated keyboard is flaky & sending random keystrokes... is that the best possibility? :confused:

[kemuri-_9]

i myself use .bat/.cmds on a regular basis:
the command prompt can and will queue keys and use them when next able to:

starting a command that doesn't require keyboard input will then have command prompt queue up the keys hit to be used when the command finishes.
If the command does use keyboard input, then those keys that were pressed will be used when it requires input (if not redirected).

so starting a command that doesn't require such input,
hitting up and enter will then have it run again when it finished the first time.

[RunningSkittle]

post your script please!

[laserfan]

i myself use .bat/.cmds on a regular basis:
the command prompt can and will queue keys and use them when next able to:

starting a command that doesn't require keyboard input will then have command prompt queue up the keys hit to be used when the command finishes.
If the command does use keyboard input, then those keys that were pressed will be used when it requires input (if not redirected).

so starting a command that doesn't require such input,
hitting up and enter will then have it run again when it finished the first time.Thanks a lot for that, I appreciate it. It does appear that my Airboard kb is wierding-out on me (technical term) on return-from-powersave and sending keypresses when I have not made any; then the cmd window and/or Windows is trying to execute them. I'm gonna deep-six it accordingly.