|
Post by Jos on May 21, 2019 22:14:10 GMT 1
What about future use of your DOS program?
Jos
|
|
|
Post by herman on Jun 3, 2019 13:24:52 GMT 1
What about future use of your DOS program? Jos At the moment I use my programs because of the NTVDM speed of Windows x86 and the large amount of data such as music and historical data. The amount of these applications and the intensive manupulation effect on data will no longer lead to a Windows alternative. There is no commercial use; most is out of hobby and / or association consideration. It all works in Dosbox 0.74 and other emulators too. I continue to keep interest and hope for speed improvement for a definitive switch to x64 environments. Herman
|
|
|
Post by Jos on Jun 3, 2019 21:57:30 GMT 1
I don’t see the relevance of Windows 32-bit/NTVDM and data such as music and historical data.
MS won’t come with a 64-bit NTVDM version, it’s just too much trouble for a very small audience.
DOS emulators (have to) run in a single core, DOS programs work stricly synchronously. Although processors get faster, the individual cores don’t keep up, you mostly just get more. So don’t get your hopes up for any real speed improvement with DOS emulators.
Jos
|
|
|
Post by herman on Jun 4, 2019 10:02:12 GMT 1
The relevance is the way data is entered, managed and presented (internal and external) and due to a lack of knowledge in new environments, can continue to expand. Software rights also play a major role in this. What I build is mine. Knowledge and functionality that you do not just write over again, without proper handling.
Programs with me usually handle process-oriented and very conditionally and therefore never end up at a dead end. Above all, they always give the correct comments if they cannot continue.
I initially wanted to respond negatively to it, but the only thing I can think of is: Unfortunately; insights differ; nobody knows everything; everyone knows a lot;
Luckily there are people who see it and those people also see many disadvantages with applications in Windows themselves.
That MS does not come with a 64-bit NTVDM version, I also saw about 30 years ago coming. It will be quite a long time before DOS is really dead.
What is wrong with synchronous processing, if it can continue to be sent asynchronously. Hundreds of simultaneous external assignments are possible. Ever seen in CMD windows?
Regarding speed (in NTVDM) simply optimal and sensitive Windows software comparable. Hundredthousands of records no problem Difference NTVDM - VDOS is certainly 10 - 1 mbt to disk I / O. VDOS works fine in processor and memory, there are small to no problems.
It's about the tricks needed to get something done with data that determine why I stick with my DOS applications. Being allowed to use (rights free) is something that plays a role.
Herman
Sorry for my bad Englisch
|
|
|
Post by gerald on Jun 9, 2019 16:35:14 GMT 1
I wrote a warehousing management application, WARES, 30 years ago in Advanced Revelation. Revelation Software later produced a windows application which was way less functional than their DOS product. Consequently I have continued to support the DOS WARES program and I have no current intention of replacing it. vDosPlus has been a big boon to allow us to run WARES in 64bit Windows environments. I am also testing to see if vDos offers the same benefits as vDosPlus while avoiding printing problems.
|
|
|
Post by Jos on Jun 9, 2019 22:04:58 GMT 1
I proclaimed at several occasions: 90% of DOS developers time went into functionality; not much to do with (bloated) appearance. 90% of Windows developers time seems now to go into the latter.
Once contacted Revalation to inquire their interest in supporting DOS. Didn’t get an answer. Not that surprising, they also dropped DOS support. No money to get with that.
You obviously once acknowledged what was added to vDos by vDosPlus. Those additions will however never be incorporated to vDos. You’ll have to stick with vDosPlus (and eventually an external DOS-to-Windows print processor).
Jos
|
|
|
Post by kalev on Jun 25, 2019 8:32:54 GMT 1
Migrating from Oracle Financials back to FoxPro accounting. It's a tiny company in enterprise and there is no point to spend half a day on tasks which can be done in 15 minutes. Developer tried to port this FoxPro app to windows but there was no way to retain the functionality and speed. All turned to point'n'click fest.
|
|
|
Post by jjjoseph on Jun 28, 2019 7:41:04 GMT 1
What about future use of your DOS program? Jos I don't know how I'd replace my VP-Info DOS tools simply because they're so incredibly easy to use and maintain. Even my dear aged wife has learned how to program - and to manage the several hundred applications used in our business.
|
|
|
Post by andrew on Jul 17, 2019 15:52:55 GMT 1
I would have to hire someone to create a whole new application for me. The company and program that made the Foxpro program is long gone and we don't have the source. There are decompile programs but we'd rather wait until the day we hire someone to recreate this program.
With the FOXPRO Dos app I did have the source code to we simply took the time to port it to VFP9 which is also a sorta dead end but running. If they drop 32-bit support for some reason it'll be dead in the water.
|
|
|
Post by Jos on Jul 17, 2019 22:09:17 GMT 1
Can’t imagine a software company dropping their 32-bit version, if there’s a 64-bit at all. Although the next vDos release will also have a 64-bit version, it’s more a parachute for if MS itself would drop 32-bit support on some Windows edition. For now, 64-bit programs (like vDos64) will generally only be bigger and run slower.
Jos
|
|
|
Post by andrew on Jul 18, 2019 18:30:09 GMT 1
Can’t imagine a software company dropping their 32-bit version, if there’s a 64-bit at all. Although the next vDos release will also have a 64-bit version, it’s more a parachute for if MS itself would drop 32-bit support on some Windows edition. For now, 64-bit programs (like vDos64) will generally only be bigger and run slower. Jos It's more they was a rumor about Windows Server going full 64-bit with no 32-bit support but it turned out to be they just didn't enable WoW64 by default on certain installations. I think it would be crazy to do this but maybe one day they'll drop it all together. I am running Desktops on Amazon Workspaces which run Server in Workstation mode as their in the Cloud Desktop platform. So I now keep an eye out for this in the 5 year ahead plan.
Basically VDos Saved me 3 years back when our DOS program couldn't be recreated in time and VDos for the most part gets everything right. The File locking routine is a requirement as i'm in a networked environment which Dosbox doesn't handle so I gladly paid for the license.
|
|
|
Post by Jos on Jul 18, 2019 19:38:50 GMT 1
DOSBox lack isn’t as much File, but Record locking (https://www.vdos.info/faqs.html - SHARE - Record locking (RL) by multi-user applications).
The devious part is you can test a program (DOSBox mod) locally and it will function properly. The server-based implementation will initially also seem to. But as it is really put to its paces, updating data, it’s only a matter of time until a database file gets corrupted. Hopefully this is then discovered soon after the actual deed, so a recent backup can be used to restore the system. The risk is however this will be unnoticed for some time, and then you have big problems to restore the integrity of the system, besides of course losing extensive work.
Jos
|
|
|
Post by ejgtuc on Oct 12, 2019 17:03:28 GMT 1
Lo seguire usando mientras corra sobre windows, es muy valioso para muchas utilidades. Eduardo Tucuman Argentina
|
|
|
Post by cmoon on Oct 16, 2019 18:06:12 GMT 1
For those using old DB systems why not to change to windows? If someone need any help please contact me. Regards
|
|
|
Post by Jos on Oct 16, 2019 18:47:29 GMT 1
Sure, the best solution for DOS database oriented software would be to switch to a Windows alternative. I doubt however that is a feasible option for most, some even tried, but gave up. While others just need more time to gradually migrate to a Windows solution.
It’s not just maintaining some database files, there will be extensive logic in keeping the complex structures/relations operational. These programs are often developed and refined over many years, with a great knowledge what’s needed and going on in a company. Far more than a simple filing system, else the program(s) would have been replaced long time ago.
Jos
|
|