Running DOS Foxpro 2.6 in 32-bit Win7 QUAD core

[Foxprox26]

Howdy all,

I am trying to run DOS Foxpro 2.6 on 32-bit Windows 7 on a fast Intel i3 computer. It's quad-core, of course, with a speed of 3.7. Foxpro is hanging up in the black DOS window. I have tried various suggestions found on the web, such as restricting ntvdm.exe to one core, disabling hyper-threading, down-clocking the computer, etc. No luck.

I have run Foxpro 2.6 DOS on fast dual core systems (3.0 speed) with absolutely no problem.

The tech guy who sold me the system is great at hardware but not experienced with running old DOS programs on fast computers. But he did try everything he knew to slow down the system to see if we could get Foxpro to run at any configuration. Everything has failed?

ANY suggestions? I went with 32-bit Win7 to avoid having to run virtualized or use XP mode. So those are NOT desired solutions.

Thanks for any help in advance!

 

[Scott24x7]

I've run FPD26 on this workstation which is dual 22 core Xeon processor, using 64bit OS. Your concern about the system or speed is unlikely the issue.
One thing you could try is running it in a VM. If it runs there, then it's not a machine issue.

Best Regards,
Scott
ATS, CDCE, CTIA, CTDC

"Everything should be made as simple as possible, and no simpler."

 

[Foxprox26]

Scott, thanks for the response. I'm trying to avoid using 64-bit O/S so I can avoid the need for using XP mode or any other add-on. Like your tag, I want to keep things as simple as possible.

I just tried tamedos and that didn't help.

You mention running FPD26 on a dual core processor. I have had no problems with dual core. This is the first 32-bit quad core I've tried to run FPD26 on, and this is the first time I've had this kind of failure. So it makes me suspect the quad core and/or the high speed.

I also tried to run FPW 2.6 and that failed as well.

I suppose if I can run it in a VM it tells me something but I'm not going to want to use it that way so I'd still be stuck.

Thanks again for the response. I will keep looking and post my results.

 

[Foxprox26]

OK FPD26 DOES run in Microsoft Virtual PC in XP mode.

So if it's not a machine issue, what is it?

 

[dbMark]

Does it have the 300 MHz code fix (2.6a) from way back in 1998 when users had problems with their new 300+ MHz CPUs? There also may have been issues with multiple cores (search CORE) and perhaps even 3000+ MHZ CPUs.

thread182-1557429 may contain some ideas or links you haven't tried.

 

[Olaf Doschke]

XP mode means runnning a virtual PC (hyper-v) under the hood, so while it runs on the same real hardware, it runs on simulated hardware and the simulated CPU will make use of the real CPU, but AFAIK only one core and the emulation makes it slower. The most important fix for FP2.6 apps is the division by zero patch (thread182-114129), if it's FPW2.6 from Microsoft.

So when able to run in XP mode (not to be confused with just compatibility mode), this isn't a proof it's not the hardware. It's likely this is your only way of running it and you won't get it running on the native hardware. Anyway, since XP mode runs seamless (visually), what's the problem with it? I think you got your solution.

Bye, Olaf.

 

[zimj]

FoxProx26,

I just installed FPD 2.6 on an Intel Core i7-6700 Processor (Quad Core, 3.4 GHz, 8MB) over Win 10 32-bit with no intermediate layer. A quick test proofed out. Printing is not working yet though.

Just FYI, one of my Fox systems (FPD or VFP) started crashing in one spot after an SBS upgrade. I inserted a momentary delay and operation was restored.

Good luck.