On Fri, Aug 21, 2015 at 10:14 AM, DrFranken <midrange@xxxxxxxxxxxx> wrote:
I think it matters if you care that "it didn't work" is different from "It
ONLY didn't work because the command is too long."

Fair enough. But your approach of designing a test which only fails
due to command length is, in my opinion, the only real way to deal
this failure mode accurately. I'm still highly skeptical of either the
need or the utility of detecting emulator details.

I would guess that you could do the same thing in a DOS batch
file but my DOS batch files skills would require use of the the google.

As does almost everyone else's! And I'm confident your guess is right.
But, assuming you have control of a DOS batch file (or any other type
of script on the PC side; there are newer and better options these
days) to accomplish this test, then you really ought to be able to
just shift some of the work over to the PC and keep your request
string short, obviating the need to detect command-too-long failure in
the first place.

John Y.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].