Foxpro 2.6 windows 7

New to this forum. Developed acocunting software almost 20 years ago in Foxpro 2. Has worked fine in XP SP3. I cannot get Foxpro 2. Runs in a small window in Windows 7 32 bit. In Windows 7 64bit will run in XP mode but still only in a window. I have tried changing the fonts in the properties of the shortcut, but get the same result. Any suggestions for getting to work in full screen mode? About your only option is to maximize it. Windows 7 doesn't support full screen mode. Thanks for the info.

Got Foxpro 2. You need to download the XP drivers for your video card. Foxpro works fine although you will lose some of the cute stuff in Windows 7. Is there any way to get it to run of Windows 7 64 bit? Or is there some particlar flavor of Windows 7 Required? I'm just amazed that people are still running FoxPro. What a great product! Iolair MacWalter Network Engineer. This issue is resolved by looking at the code generated by the screen writer that Foxpro 2.

They create a Foxplus line in the code that needs to be rem out. Of course are old programs, that are written in FP2. I see, that the main problem, that the network sharing has problems on XP virtualbox. As desktop application works FP2. Not only are there old programs that still run fine, there are old problems that newer software make so much more difficult that they wouldn't be worth doing any more. I would have preferred to have used Windows 7 64 bit but Foxpro won't run in it.

Apparently, the 16 bit emulation is not included. Not completely through testing for my applications but foxpro appears to run right out of the box wihtout issue. No need for virtual machine. I figure that Windows 7 will be supported for the next ten years like XP had after which time I'll probably be ready to retire. Ironically, I had decided on Foxplus 25 years ago thinking that the open source code could be ported to any current platform de jour only for the screen formatting to become the real unsurmountalbe issue amoungst a host of impracticel issues.

What was I thinking???! I know this time the writing is on the wall: the only long-term solution is to migrate their app. But I wonder if anyone can suggest a temporary alternative path, which doesn't involve either:.

The easiest and fastest is b option using XP Mode. Give it a try. My guess for the reason that it doesn't run and will not run is because it's actually a bit application. Apparently, Win64 doesn't include the WoW Winsupport subsystem required to run bit apps.

You can definately run bit apps on bit windows. But if yours is bit then you're going to have to run an emulator. If it really is bit then make sure the bit libraries are installed and available. Also make sure to disable Data Execution Prevention or add your app as an exclusion to it or it also won't run. All the old 16 bit addressing compatibility modes were left out of 64 bit mode when AMD developed their 64 bit extensions to the x86 processor. This makes it impossible for Windows on Windows 64 bit WOW64 to support running older 16 bit software in the same way WOW32 is able to on a processor in 32 bit mode.

The 32 bit versions of Windows 7, 8, 8. I would suggest running it in a virtual machine using a 32 bit version of the main OS the company is currently running - so Windows 7 32 bit for now.

It's a little late perhaps, but you could try this: run the app on a Windows server, then install OpenSSH and configure passwordless login for every user.

Kind of like using Terminal Server, but may avoid the problems you anticipated with it. Also, if the users are accustomed to cmd. If done right and with a little luck they might not notice they're running the app somewhere else at all. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more.