Foxpro26a Patch EXE running under a slowstart command... issues?

[Guest_imported]

We are currently to roll out a 2.6* EXE as an upgrade to a system we are unable to upgrade (alias rewrite!) to VFP.

The EXE is to be set up under 400+ machines, some of which already call the EXE using slowstart with vaious parameters (10 seconds max at present).

What are the problems/issues in running under
1)Win 3.1
2)Win95
3)NT4

What are the benefits or problems in running the 26a patched exe with slowstart Vs patched 26a exe alone?

 

[DSummZZZ]

For what it's worth, I have never used slowstart. I have however, used DZPATCH.
I have installed the patches from DZPATCH on Win95, Win98 and NT4.0 platforms, all with different hardware configurations and have had no problems whatsoever.

 

[9mattie]

Where can I get the dzpatch and how is it different from the other patch.exe for "divide by zero" error? How EXACTLY do you install it? Sorry, I just am not making any progress with overcoming this erroron a new , faster machine. I have win 2000, fp 2.6 just upgraded to 2.6a.

Thanks in advance,

mattie
crow@aloha.net

 

[rgbean]

Mattie,
DZPATCH was a fix to the divide by zero problem that a programmer supplied months before MS acknowledged the problem. When MS released their official patch to FPW2.6a (the only officially supported version of FPW), they asked that the DZPATCH code be removed from circulation and the author complied.

It's interesting to note that the code files Foxw2600.esl (runtime) and Foxprow.exe (development) for FPW2.6a are EXACTLY the same whether they were patched by DZPATCH or by the official MS patch.

The biggest difference is that the MS patch ONLY works on the FPW2.6a files, where the DZPATCH code works on all (?)versions of FPW - I'll used it on FPW 2.5b, FPW 2.6, FPW 2.6a. Also, the DZPATCH technically violates your FPW license.

Rick