I just found this by googling. It may help and it may not:
http://www.techradar.com/news/computing/pc/how-to-make-old-programs-work-on-windows-7-922313
Bob
On Feb 7, 2012, at 9:58 AM, Andrew Henshaw wrote:
> I did think it might be a cache, but not in this case.
>
> If I restart the computer,
I did think it might be a cache, but not in this case.
If I restart the computer, log in as the standard user then right click and
start the app in administrator mode it starts immediately. If I then close
the app and re-launch it using the normal double click it takes forever to
load, so
That may be a bit of a misnomer. Windows (and OS X) is designed to keep recent
code from an app in virtual memory. You will discover this phenomenon to be
true with all programs. The first time you run it, the startup time may be
longer than you expect, but quit it and start it up again, and the
Thanks
Its also easy to test, if you compile the simplest of apps and compile it,
then switch to a standard user account and run the app it is slow to start. If
you close the app, the right click on it and select 'run as administrator' to
start it again it starts instantly.
I cant really t
Hi folks,
I've seen this much-delayed startup of LiveCode apps, though only on Windows 7.
On 7 Feb 2012, at 12:08, Andrew Henshaw wrote:
> There was a thread a few days ago about the differences between the Windows
> Admin and Standard users.
>
> This may be related, but can anyone explain (or
There was a thread a few days ago about the differences between the Windows
Admin and Standard users.
This may be related, but can anyone explain (or replicate) why, when a
Livecode app is compiled with the UAC Execution Level set to either default, or
same as invoker and on a Windows 7 pc,
