It doesn't help much saying you couldn't get virtual pc set up.
Yes, it's possible to install DOS within an older Windows a virtual PC. The creation of a virtual PC already asks you about which OS it should support, DOS itself is not amongst them in most cases, but virtual PC by Microsfot isn't the only option for virtual PCs.
What problems do you have with the Virtual PC host software itself? Do you have sufficient RAM to support your native OS and a virtual PC? That's the only resource you really can't share in the sense of using it both for the physical and the virtual PC, the RAM is split into two parts and your host has lesser RAM and the virtual PC has whatever you give it. For running a virtual pc under Win7 you would best have at least 2GB and split it 1:1 or 1.5:.5 GB to run a XP 32bit in the virtual pc. FPDOS runs within XP eg by installing TameDos there, or even without any further seperate DOS installation, I don't know, but XP is among the OSes on which I now people use FP Dos applications.
I understand, that's a bad situation. This is never done in one phone call. I'd advise to point to a documentation of getting a virtaul PC up and running in the first place and take feedback on what was not understood on that step, and then continue with the installation of the fox app.
Depending on the affinity of that "gal" to computers it's easy or hard, but what can you do? Changing the etup of virtual PC is not in your power. I think it's rather straight forward even for less computer affine people. The installatio of virtual PC itself really just needs a double clik on the setup.exe and several OK button clicks. Once that software is installed creating a virtual machine as said mainly is specifying for which target OS to create it and how much memory to share, the other things can stay with defaults. And I'd advise to target for XP. You shouldn't choose an older OS for reasons of needing a license and security of the older OSes and their status of not being maintained anymore. Eg you could also specify to target Win98 and fox2.6 win or dos would be happy with that, but does your customer still have a win98 cd?
1) Got client to upgrade to Windows 7 Professional. They then downloaded the XP client software.
2) Foxpro2.6 works on that. Only tried Foxpro not Foxprox. Forgot the setup needs for that.
3) Noticed that the XP client starts with 256MG but that can be changed so I upped it 640mg.
4. With that memory the speed was fine as a local app. However, ran into problems with the network.
a. Seemed to slow down a lot.
b. Even though I mapped the network drives could get the XP
client to see them. That was particularly true in Fox
which only saw A,C, and D the local drives.
By the way also tried one on the 3rd party programs and it worked well local.
Any comments about speed or networks would be appreciated.
I have gotten Visual Foxpro to run well on Win7
* Turn UAC OFF
* Configure EXE as 32-bit (or XP Compatibility)
* Use 32-bit drivers for ODBC using ...\SysWOW64\odbcad32.exe
* Be careful of the directories you use
* etc.
But I have not tried to get FPD2.6 working in it, so I am not sure if anything else needs to be taken into consideration.
Maybe Olaf has some additional advice.
But I did do yet another Google Search, this time for foxpro win7. Some of those 'finds' might have your answers.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.