On Sun, 23 Sep 2018 00:00:44 -0700, Johnson wrote:

If anybody other than Winston posted that then my guess is that it
would be you doing your fake **** again. You are a known moronic
troll. You are probably a sulking like a baby because I challenged you
to prove I was wrong. When you coudn't you decided to strike from the
shadows like the slimy ****ing coward troll you are!

Hi Johnson,
I looked at your solution, where I appreciate that you seem to be providing
knowledge, which people can use or not use.

One thing that struck me as odd, though, was the "command" file had lines
far longer than 1000 characters, reminiscent of buffer overflow exploits.

Is that command file a buffer-overflow exploit?
Hell if I know ... but ... the command file *clearly* contains lines that
are far longer than they ever need to be.

Witness the number of extraneous characters in the command file.
That's suspicious in and of itself, since they're entirely unnecessary.

So, while I commend you for providing information for the rest of us to do
with as we please, I ask the _rest_ of the Windows users what they think of
that command file containing far too many lines with over 1000 characters
per line.

Does anyone here have any comments on why that command file might have so
many extraneous characters?