Mike, > Great to hear from you, Bill!
Likewise :-) > I came to the same "full speed ahead, damn the absence of corporate acknowledgement VFP exists!" conclusion soon after VFP's demise was announced. As long as it keeps working...it's the most productive platform for me by a wide margin. So far it does what I need it to do, And I share what someone earlier said about having confidence that VFPx and 3rd party extensions will provide new/improved functionality and also help us deal with any glitches that may occur with Windows that affect VFP apps. >I recently discovered vDOS (vdos.info) and can't get over the joy of firing up a Foxpro DOS application on my Windows 10 Pro 64-bit desktop! > vDOS is fast, easy to use, and it works! If anyone is curious, vDOS is based on (fork of) DOSBox. But, according to the vDOS author, DOSBox + Foxpro DOS = data corruption due to the DOSBox authors including some network data buffering (delayed > writes.) I have a client using 6 WIN10 Pro workstations with vDOS + my Foxpro DOS application simultaneously, and no data corruption issues so far. The users like not having to start the virtual computer, then start the app. Thanks for the info. I do have one customer still using an ancient FPD2.6 app. I passed this info to her. >So far I'm really happy with VFP9 on Win10. I noticed last night that Win10 workstations no longer leave file handles open when my applications shut down. When the workstations were running Win7 Pro, probably half of the 50 workstations that > connected to my Linux data server would report DLL files remaining open and active after all the VFP9 applications on the workstation were closed. Plus, the overall network management (listing of files in Windows Explorer, mapping drives, disconnecting > drives) is snappier and more reliable. Good news. So far (2 months) my testing with Windows 10 has not hit any problems. >You mentioned VM's on Win10 to run VFP9...I found that Oracle's VirtualBox is much slower at writing text to files, although overall the speed is fine. The best performer, for pure speed of all overall operations, is VMWare Workstation 12 Player. But, to >use in a business environment it's $150 per workstation. vDOS seems to be even slower than VirtualBox for high volume text-to-file IO, but it is very acceptable otherwise. If things get bad enough to where we have no choice but to use VM, it would be a small price to pay (compared to a re-write in another language - God, I hate doing that!). Mike [excessive quoting removed by server] _______________________________________________ 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.
