---------------------------
Unsupported 16-Bit Application
---------------------------
The program or feature "\??\c:\program files (x86)\microsoft visual foxpro 7\foxrun.pif" cannot start or run due to incompatibity with 64-bit versions of Windows. Please contact the software vendor to ask if a 64-bit Windows compatible version is available.
Solution:
FOXRUN.PIF is just shortcut to MS-DOS program (COMMAND.COM)
Command.com is not exist in 64 bit machine.
CMD.EXE is working in 64 bit.
So make shortcut of C:\Windows\System32\cmd.exe at D:\LD\ with name of FOXRUN.PIF
Now your application will work fine.
-----alternate solution
16 bit applications do not run under 64 bits. foxrun.pif is not required in 64 bit machines.
\ld\foxrun.pif delete or rename it.
Thanks Problem solved. I renamed file as you suggested now it's running perfectly well
ReplyDeleteBipin shah
\ld\foxrun.pif delete or rename it.
I believe your solution will also apply to my problem. My client is running FoxPro for Windows 2.6 in a simulated 16-bit environment on a Windows 10 workstation. Viewing (but not editing) the foxrun.pif file in Notepad displays a reference to COMMAND.COM instead of CMD.EXE. Editing foxrun.pif with Notepad and simply substituting CMD.EXE for COMMAND.COM does not work, and I suspect that's because Notepad is a text editor and foxrun.pif needs to be modified with a PIF editing tool. Unfortunately, there don't seem to be any apps that can be used to edit a .PIF, which I assume has a proprietary format,
ReplyDeleteYour solution includes the following line:
So make shortcut of C:\Windows\System32\cmd.exe at D:\LD\ with name of FOXRUN.PIF
I don't understand what this means, so I'm hoping you can explain. First of all, I have no idea why you're referencing D:\LD\ since that drive and directory may not even exist. (Is it possible that "D:\LD\" is simply your way of saying "Drive\Local Directory" ? Second, how are you making the new shortcut in a Windows environment?