As reported by some, vDos can’t run FoxProX due to not supporting memory paging in protected mode.
I just had once more a look at the vDos – FoxProX combination and only after some deep debugging, I saw a big oops.
I can now start the FoxProX demo program, but not sure if it will function with a “real” application.
If you dare to test it, send me your mail address mids my Profile Page (Send Message, top right).
Mind:
It’s unfinished work, some testing should be added to the translation of linear to physical addresses. Though that shouldn’t affect FoxProX running your application.
No optimization or caching is done in this translation, so FoxProX will run sloooooow.
You should of course NOT use your real databases and setup a test environment. DON’T complain if you didn’t and your databases got corrupted!
Jos
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I also have and old but very substantial foxprox project that I am trying to run on a windows 8.1 64 bit machine without success due to the memory paging error. I am also new to these discussion groups.
I have only just in early January 2015 downloaded Vdos and am running it successfully but experience the memory paging error and can't get foxprox to run as a consequence.
Reading the threads it appears that other have solved this problem to their great joy with I assume the latest version of Vdos or tweaking?
Can you please advise / point me in the right direction.
Thanks in advance - Stephen McFarland
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am running version 2014.10.19 of VDos with Foxpro2.5 Vdos config includes;
LOW = ON
EMS = ON
MOUSE = ON
Error I get is;
Phar Lap err 10118 Can't load EXP file Foxprox.exe
Insufficient physical memory available
107 total 4k memory pages available on system
A minimum of 379 memory pages required to run pgm
Thanks for your help its greatly appreciated
Stephen McFarland
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Great work, file & record locking works on my Foxpro application in a network!
Just found vDos, but so far it seems to work great.
I finally see a way to migrate to newer Windows 64 bit.
If you need debuging of FoxProX I am glad to assist.
/Olle
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
hello mark,
I have also a FoxPro application which is run under windows 7 32bit, now I have a windows 8 64bit pc, but my old FoxPro application not run. so help me how can I run FoxPro application under vdos, I don't have knowledger about vdos. so can you please help me, on my mail id jgajjar73@gmail.com
Regards,
Jayesh Gajjar
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Jos, thank you for vdos. Great program and solution for many old dos aplications on 64-bit machines. I would like to help and participate in testing vdos with foxprox.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for your efforts. I am more than willing to help with testing. We are also very interested in being able to run DOS FoxPro applications in 64-bit environments.
Regards.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I hope that this will work faster then I had earlyer with vDos and dBase5 for DOS.
The base of FoxPro and dBase is likely the same base with memeory pageing.
My dBase application won't work faster in vDos then I had with NTVDM in Win7 x86 or with Virtual XP in a x64 envoirement.
If the new realease comes out I should test it again and report it here in the forum.
Greeting Herman
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
dBase and FoxPro, both database managers, don’t use memory paging in protected mode. FoxProX does by means of the Phar Lapp DOS extender, so it can go beyond the 1MB memory barrier of DOS/real mode w/o using XMS or EMS memory.
Perhaps you should rather have a look at Harbour (http://sourceforge.net/p/vdos/discussion/xbase-clipper/thread/58f6f7e3/) to port your dBase program to Windows.
Jos
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
FoxProX will probably address the PIT controller to generate sound instead of just “displaying” ASCII 7. The PIT’s functionality to produce “fancy” sounds is not supported.
Jos
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you very much I have done some preliminary testing and has worked perfectly with my programs made FOXPROX . I can only say great alternative. Thank you .
Jos. You are a BERRACO.
Last edit: Anonymous 2014-10-31
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As reported by some, vDos can’t run FoxProX due to not supporting memory paging in protected mode.
I just had once more a look at the vDos – FoxProX combination and only after some deep debugging, I saw a big oops.
I can now start the FoxProX demo program, but not sure if it will function with a “real” application.
If you dare to test it, send me your mail address mids my Profile Page (Send Message, top right).
Mind:
It’s unfinished work, some testing should be added to the translation of linear to physical addresses. Though that shouldn’t affect FoxProX running your application.
No optimization or caching is done in this translation, so FoxProX will run sloooooow.
You should of course NOT use your real databases and setup a test environment. DON’T complain if you didn’t and your databases got corrupted!
Jos
View and moderate all "FoxPro(X)" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Hi Jos,
I also have and old but very substantial foxprox project that I am trying to run on a windows 8.1 64 bit machine without success due to the memory paging error. I am also new to these discussion groups.
I have only just in early January 2015 downloaded Vdos and am running it successfully but experience the memory paging error and can't get foxprox to run as a consequence.
Reading the threads it appears that other have solved this problem to their great joy with I assume the latest version of Vdos or tweaking?
Can you please advise / point me in the right direction.
Thanks in advance - Stephen McFarland
Version 2014.10.19 should run FoxProX without any problem.
So, do you use this version?
Jos
View and moderate all "FoxPro(X)" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
I am running version 2014.10.19 of VDos with Foxpro2.5 Vdos config includes;
LOW = ON
EMS = ON
MOUSE = ON
Error I get is;
Phar Lap err 10118 Can't load EXP file Foxprox.exe
Insufficient physical memory available
107 total 4k memory pages available on system
A minimum of 379 memory pages required to run pgm
Thanks for your help its greatly appreciated
Stephen McFarland
You have started FoxProX and Phar Lap needs XMS memory for memory paging.
So remout EMS = ON.
Or use FoxPro (no X).
Jos
Hi Jos
Great work, file & record locking works on my Foxpro application in a network!
Just found vDos, but so far it seems to work great.
I finally see a way to migrate to newer Windows 64 bit.
If you need debuging of FoxProX I am glad to assist.
/Olle
Thank for you offer, I'll send you a mail directly.
Jos
I'll be happy to assist as well. Running FoxPro (X) 2.6a successfully.
Thanks, but testing FoxProX is of no concern anymore.
Jos
I have a client on foxpro with a large database that works great under vDos in every way except performance.
I am happy to participate in the testing as well if it will help get foxprox working and the performance improved
Thanks
View and moderate all "FoxPro(X)" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
hello mark,
I have also a FoxPro application which is run under windows 7 32bit, now I have a windows 8 64bit pc, but my old FoxPro application not run. so help me how can I run FoxPro application under vdos, I don't have knowledger about vdos. so can you please help me, on my mail id jgajjar73@gmail.com
Regards,
Jayesh Gajjar
I also have a foxprox program and would like to use with vDos. Any word on if this will work?
Probably end next month a new release of vDos will be made available.
Support of FoxProX programs is still unclear pending feedback from testers.
Jos
View and moderate all "FoxPro(X)" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Thank you for good news...
I hope, FoxProX progs will be run in vDos...
Jos, thank you for vdos. Great program and solution for many old dos aplications on 64-bit machines. I would like to help and participate in testing vdos with foxprox.
Helo Jos,
Thank you for your efforts. I am more than willing to help with testing. We are also very interested in being able to run DOS FoxPro applications in 64-bit environments.
Regards.
View and moderate all "FoxPro(X)" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Hello jos willing to test foxprox
Ajay
email amja@rogers.com
View and moderate all "FoxPro(X)" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
I hope that this will work faster then I had earlyer with vDos and dBase5 for DOS.
The base of FoxPro and dBase is likely the same base with memeory pageing.
My dBase application won't work faster in vDos then I had with NTVDM in Win7 x86 or with Virtual XP in a x64 envoirement.
If the new realease comes out I should test it again and report it here in the forum.
Greeting Herman
dBase and FoxPro, both database managers, don’t use memory paging in protected mode. FoxProX does by means of the Phar Lapp DOS extender, so it can go beyond the 1MB memory barrier of DOS/real mode w/o using XMS or EMS memory.
Perhaps you should rather have a look at Harbour (http://sourceforge.net/p/vdos/discussion/xbase-clipper/thread/58f6f7e3/) to port your dBase program to Windows.
Jos
Memory mapping in protected mode made it to the new release of vDos.
So testing it is no object anymore.
Jos
It works. I love it. The only thing missing is sound when I make a mistake there is a beep. Is there a way to enable sound? Thanks for the great work.
No, the only sound is the simple DOS beep.
Jos
View and moderate all "FoxPro(X)" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
It is the DOS beep that I am referring to. I do get the beep when using dosbox. Other than that the FoxProX program is working.
Last edit: Arkdom 2014-10-21
FoxProX will probably address the PIT controller to generate sound instead of just “displaying” ASCII 7. The PIT’s functionality to produce “fancy” sounds is not supported.
Jos
View and moderate all "FoxPro(X)" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Thank you very much I have done some preliminary testing and has worked perfectly with my programs made FOXPROX . I can only say great alternative. Thank you .
Jos. You are a BERRACO.
Last edit: Anonymous 2014-10-31