![]() ![]() ![]() The volume of writes (MB’s) FoxPro produces is no comparison to what Windows and its programs (GB’s) do. I wouldn’t worry that much of wearing the SSD out. If it does help (the real bottleneck could be the simulated vDos CPU), a SSD could be an alternative. ![]() You could eventually download and install a Windows RAM drive (many around), set some memory aside for that and experiment. I can’t estimate how much a RAM drive would speed up your processes. Perhaps a change in Windows optimistic locking scheme, or the files are now set to be available offline? Strange that (re-)writes to a network share would be slower than before. You have to help me with PDF access through FoxPro, you create PDF documents by printing to a virtual PDF printer? New transactions are accumulated on still another device.Ĭould vDos also be run from the ram-drive or must it remain with the operating system? What about the DOS FoxPro installation?Īny insights you can share will be greatly appreciated. My approach would be to load up the ram-drive from the latest previous day's archive which was created multiple times daily on multiple external HDDs. The entire process takes about a minute on my I7-4700MQ laptop with 16GB RAM and 1TB 5400-RPM HDD and is executed several times daily. What has me thinking in this direction is that I'm considering replacing my HDD with an SSD which I know would speed everything up considerably, but I'm concerned that the volume of re-writes might reduce the lifetime of the SSD. I'm wondering if there's a way to create the equivalent of a ram-drive accessible by vDOS such as that which enabled Foxpro 2.6 for DOS under Windows 98 to perform lightening fast. Processes involving series of extensive searches (reads) seem faster to me, but the corresponding series of replacements (re-writes) are definitely slower. ![]() So far I haven't been able to isolate any repeatable conditions On the other hand, the PDF access through FoxPro that you helped me with earlier doesn't always work now. The good news is that the colors Blue, Green, and White appear even richer than in the previous version. Just installed the Windows 10 Anniversary update. I know people can’t troubleshoot software they do not have or never have worked with before, but I am hoping that maybe people have had similar experiences and may be able to advise on how to troubleshoot. I can only have one instance of the application up when using it under vDOS. The minute I shut off one of the instances, the vDOS will run the legacy software flawlessly. Unfortunately, when I try to open more than once instance of the software with vDOS, I get the following, File ‘C:\Program\USER.DBF’ does not exist.’ I figured I would set up vDOS and get it working, then simply share out the vDOS shortcut on the other computers that require access. The software is currently sitting on a network share and is meant to be used by more than 1 user at a time. vDOS does load it and it seems to work perfectly fine from what I can tell, but the minute I attempt to use it again(a shortcut of vDOS) on a different computer, I run into an error message. I am trying to get a piece of legacy software to work under Windows10 \ vDOS so that I can drop 3 Windows XP Virtual Machines in order to run this one piece of software. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |