On 07/08/13 08:13 AM, Kevin Cully wrote:
Any tips from the Foxpro DOS pros? Is it time to get them into some
sort of VM? Perhaps DOSBox? I haven't really started to dig into this
area of the program to see if I can determine which line of the code is
actually causing the problem. I thought I'd ask here to see if there is
some sort of memory allocation setting I can do at the startup of the
application.
One of my old clients still runs a FP2.6 app - it does exactly what he
wants and he can't afford to have it rewritten. How to run it after Win XP?
We tried DOSBox. It ran fine, but we never did get printing to work.
I set up an XPMode VM. It ran fine, and we could print simple reports,
but the formatted ones (which use the old HP PCL codes) never worked. I
found XP Mode a PITA in general.
My client found the answer. He took a spare machine and installed the
32-bit version of Win 7. Program ran like a champ! He had to disable
the Windows printer drivers, and then all the printing worked as well.
I understand this also works with Windows 8 (32-bit). In the Win 8 case
you have to 'enable' something, but that's described in the Google universe.
So I'm off the hook, and DOS Box and XP Mode I can forget about.
Dan Covill
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
