RUN issues (again)

[NewsArchive]

Friedrich

Some time ago we had some conversation regarding my unhappiness with error
reporting re. the Run command.. and deciding whether to use the default
operation, or set to use ShellExecute.

Despite a couple of others advising to use ShellExecute, you were adamant
that you did not normally use it in your installations, and also cited that
it allowed less control over execution.

I was swayed by this, and reverted from my position of using ShelExecute,
back to the default.

Unfortunately this now appears to have been a big mistake - we are now
(tonight) distributing my latest upgrade, and are already getting reports
from several stores regarding Run issues - all with the same result!!!

The attached (faxed in by a helpful store) shows this repeating error - no
idea what the numbers mean (which was the source of my complaint last time)

Seems there is 'something going on' with the default Run call on a number
of computers 'out there' in the shops.

I shall be reverting to the use of ShelExecute, to see if I can salvage some
of these upgrade installations. But my advice to users setting up for major
distributions now is to be suspicious of using the default Run call, and to
use ShellExecute on Running
external programs.

Just my (NS)HO, of course
It looks like we are in for a long night....

HTH
Steve