I think Christof gave you some good pointers.

--

rk -----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Kent Belan Sent: Wednesday, July 06, 2016 2:45 PM To: profoxtech@leafe.com Subject: RE: Do prompt when starting EXE

Thanks for the info. I checked and there is a config.fpw built into the project but it is very basic and should not cause this problem. No other config.fpw files were found.

Here is the config.fpw file that is in the project: RESOURCE=OFF SCREEN=OFF EDITWORK="C:\TEMP" PROGWORK="C:\TEMP" TMPFILES="C:\TEMP" SORTWORK="C:\TEMP"

I also just checked for a foxuser.dbf and had them delete all they could find but that did not help ....

Thanks, Kent

-----Original Message----- From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of Richard Kaye Sent: Wednesday, July 6, 2016 12:27 PM To: profox@leafe.com Subject: RE: Do prompt when starting EXE

Maybe a config.fpw pointing somewhere else?

--

rk -----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Kent Belan Sent: Wednesday, July 06, 2016 12:17 PM To: profoxtech@leafe.com Subject: Do prompt when starting EXE

Hello,

I have an VFP 9 EXE that runs fine on mapped drive on the network from the main folder. They made a copy of the folder and a new mapped drive to the new folder but when we try to start the EXE we get a DO prompt. We can select the EXE at this point and the program will start. Very weird.

Has anyone had this problem and know of a solution ?

Thanks, Kent

[excessive quoting removed by server]

Hello Christof,

Thanks, I had not thought about a virus scanner. We have the program working fine when mapped to the regular R: drive but they created a new Q: mapped drive with a copy of the folder that is working. This new Q: mapped drive is the one that has the problem. We get the same Do prompt when we try to run any of our VFP9 programs from the Q: folder but they all work fine in the R: folder.

Sounds very much like a virus scanner is trapping the EXE on the new Q: mapped drive.

Thanks, we will check it out and report back if solved

-----Original Message----- From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of Wollenhaupt, Christof Sent: Wednesday, July 6, 2016 1:47 PM To: profox@leafe.com Subject: Re: Do prompt when starting EXE

I have an VFP 9 EXE that runs fine on mapped drive on the network from the main folder. They made a copy of the folder and a new mapped drive to the new folder but when we try to start the EXE we get a DO prompt. We can select the EXE at this point and the program will start. Very

weird.

Has anyone had this problem and know of a solution ?

Usually this is either a corrupted EXE or an EXE that is partially blocked by a virus scanner.

A common issue with virus scanner is that the exclusion list only has the mapped drive path, but the EXE is launched from an UNC path (or vice versa).

Mixing mapped drives and UNC paths can also lead to different App_Compat flags in the registry that cause different behavior.

-- Christof

--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---

[excessive quoting removed by server]

Thanks Mike,

I will check this out also. We can't test again till the morning when they let us back on their computers.

-----Original Message----- From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of Michael Glassman Sent: Wednesday, July 6, 2016 4:25 PM To: profox@leafe.com Subject: RE: Do prompt when starting EXE

Kent,

Christof's suggestion reminded me that Windows' own security settings can cause this behavior as well. Launch Internet Options (from either the run box, the networking center, or the tools menu in Internet Explorer). Click on the Security tab, select Local intranet, click Sites, and click Advanced. Add the Q: drive to the zone, and close everything up. That will tell Windows that it's safe to run executables on that drive.

Mike

-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Kent Belan Sent: Wednesday, July 06, 2016 12:48 PM To: profoxtech@leafe.com Subject: RE: Do prompt when starting EXE

Hello Christof,

Thanks, I had not thought about a virus scanner. We have the program working fine when mapped to the regular R: drive but they created a new Q: mapped drive with a copy of the folder that is working. This new Q: mapped drive is the one that has the problem. We get the same Do prompt when we try to run any of our VFP9 programs from the Q: folder but they all work fine in the R: folder.

Sounds very much like a virus scanner is trapping the EXE on the new Q: mapped drive.

Thanks, we will check it out and report back if solved

-----Original Message----- From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of Wollenhaupt, Christof Sent: Wednesday, July 6, 2016 1:47 PM To: profox@leafe.com Subject: Re: Do prompt when starting EXE

I have an VFP 9 EXE that runs fine on mapped drive on the network from the main folder. They made a copy of the folder and a new mapped drive to the new folder but when we try to start the EXE we get a DO prompt. We can select the EXE at this point and the program will start. Very

weird.

Has anyone had this problem and know of a solution ?

Usually this is either a corrupted EXE or an EXE that is partially blocked by a virus scanner.

A common issue with virus scanner is that the exclusion list only has the mapped drive path, but the EXE is launched from an UNC path (or vice versa).

Mixing mapped drives and UNC paths can also lead to different App_Compat flags in the registry that cause different behavior.

-- Christof

--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---

[excessive quoting removed by server]