On 2017-07-11 15:13, Tracy Pearson wrote:
[email protected] wrote on 2017-07-11:
On 2017-06-08 13:57, [email protected]
wrote:
UPDATE FROM CLIENT:
"[Local IT guy] suggested trying to run the program in Windows 7
Compatibility mode. We tried that on several machines, including
Billy
K’s, and nothing ghosted. Hopefully that will continue to be the
case
and we can go forward happily. Suggest you have other customers
switching to Windows 10 use 7 compatibility mode."
This still baffles me as to why/how this is happening on Win10 and is
resolved by the Win7 Compatibility mode.
Mike,
We had a client do that to us. I remoted in to the workstation and
found out the overzealous anti-virus was killing our application due
to its "call home" feature. We check for an update to the current
version periodically at start up.
When the customer put the program in Compatibility mode, it runs it
with more administrative privileges and outside where anti-virus was
able to determine it was running. To me, and suddenly aware the tech,
it showed how that anti-virus can be avoided. The tech changed out
the anti-virus on the computer and our software runs without being in
compatibility mode.
Hi Tracy,
The only A/V software is the native Windows Defender, and we had
programmed exclusions for all the VFP data file types as well as
excluded the local app and network database folder.
Odd.
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
