>>>I have a large number of files in application.
>>>To reduce number of installation disks I zip most of them to a single
>>>archieve before creating distribuion disks.
>>>
>>>I create distribution disks using VFP 5.0a setup wizard.
>>>For post-setup executable I specify the pif file to unzip my
>>>application.
>>>
>>>This pif file contains the following command:
>>>
>>>somedir\unzip.exe -o eeva
>>>
>>>Under windows 95 setup works.
>>>Under Windows NT I got a message after setup:
>>>
>>>Setup was not completed successfully
>>>
>>>and I must manually execute the pif file for unpacking.
>>>
>>>Why this will not work in Windows NT ??
>>
>>
>>I question the "fewer number of disks". The VFP setup wizard compresses files. Also, you technically need a distrubtion license for PKZIP to use it this way.
>
>Craig, I think this is not true.
>
>I have 120 reports and this produces 240 small separate files and
>also some hundres of small dbf and fpt files.
>
>Setup wizard (VFP 5 ) compresses small files inefficiently.
>If I use only setup wizard compression, it produces a larger number
>of distribution floppys ! Also, zip compresses a bit more efficiently than
>ms compress.
>

I can't speak directly to your issue here, since I don't know the program, and avoid using .PIF files like the plague. It's enough to know that executing a DOS application under the control of NT's command processor CMD.EXE is very different than the execution under the COMMAND of a DOS Box VDM under Win95/Win98, and the PIF file might well be attempting to invoke COMMAND.COM rather than CMD.EXE to host the operation, which just own't work under NT.

If you insist on using the zip file method (something I also don't agree with, but I'm not going to debate the philosophy of installs), why not bite the bullet and pay for a zip product that can create a self-extracting zip file for you that can be invoked as a WinApp, neatly avoidng the .PIF issues. If it's a matter of memory configuration or some DOS functionality not provided inside NT, you neatly sidestep the issue. I believe both WinZip and PKZIP for Windows have this capability.

You might also look at enhancing your install by creating a post setup executable based around the Windows Scripting Host. WSH gives considerable capability for erforming complex tasks to extend the installation; in fact, I'm moving many of my installs to using Wscript and the built-in Setup API, coupled with a standardized minimal VFP Setup Wizard install that loads up the VFP runtime environment, and then writing the remaining install in Wscript (you can scipt with VBSCript or JScript as an environment, and there is considerable capability in WSCRIPT itself. It's trivial to launch apps of any sort within a Wscript.

Or for that matter, write a post-setup mini app in VFP to run your uninstall from inside a VFP app.

>Has you see from my message I use info-zip unzip program.
>According to info zip licence, its zip and unzip are completely
>FREE for use in my knowledge.