|
Post by andersostling on Nov 5, 2020 13:39:56 GMT 1
vDosPlus is based on an older version of vDos. Its ‘useful’ additions can be confusing and complicate the setup. No worry about the PHQGHUME file, it’s a bug in the DOS API implementation ... That is very re-assuring to hear. It got me a bit worried first .
|
|
|
Post by Jos on Nov 5, 2020 14:02:01 GMT 1
No, any distributed database program - DOS, Windows, Linux, whatever - needs RL to manage a (remote) database, not on a local disk. So what I said applies to all those programs, not just DOS programs under vDos (what is a Windows program itself). If anything, you could argue such a DOS program will run more reliable in vDos than in NTVDM or DOS. I was once told vDos solved some sharing problems of a program in NTVDM, though I have my doubts it was actually NTVDM causing the problems.
Modern Windows programs moved to using centralized database management, SQL, variants and the like. So those programs don’t have to deal with the details of managing the database themselves. Not exactly new, Novell Netware servers had that long before, but it was exclusive to the (DOS) Brequest database interface. Netware servers essentially vanished, and no - but a handful of - DOS programs were updated to work with a centralized (managed) database.
Jos
|
|
|
Post by andersostling on Nov 5, 2020 16:29:49 GMT 1
No, any distributed database program - DOS, Windows, Linux, whatever - needs RL to manage a (remote) database, not on a local disk. So what I said applies to all those programs, not just DOS programs under vDos (what is a Windows program itself). If anything, you could argue such a DOS program will run more reliable in vDos than in NTVDM or DOS. I was once told vDos solved some sharing problems of a program in NTVDM, though I have my doubts it was actually NTVDM causing the problems. Modern Windows programs moved to using centralized database management, SQL, variants and the like. So those programs don’t have to deal with the details of managing the database themselves. Not exactly new, Novell Netware servers had that long before, but it was exclusive to the (DOS) Brequest database interface. Netware servers essentially vanished, and no - but a handful of - DOS programs were updated to work with a centralized (managed) database. Jos Ok, this app has been running on Windows 95 (Novell NW server) between 1995-2010, on Windows 7 from 2011-2018 (Win 2102 server) and Win 10 (Win 2019 server) since 2018 without any known data corruption. We have daily backups, so I guess we will take our chances with vDOS starting late this year. THanks again for the clarification! Anders
|
|
|
Post by Jos on Nov 5, 2020 17:54:13 GMT 1
vDos is being used w/o problems by several with 10+ concurrent users at a time. Even one with over 150 users, so your guess should be sound. Creating regular backups is of course essential, with or w/o using vDos.
Jos
|
|
|
Post by chrisr on Jan 17, 2021 13:50:51 GMT 1
It is engineering design software that I was using for 15 years during my time working for other companies, then paid for when I set up my own business just over 20 years ago. So a lot of my time, effort and money has been allocated to understanding and using the software. The developer started porting from MS-DOS to Windows 95/98 before full Windows versions became available [for some of the software]. But as with a lot of Windows software, the developers keep on increasing the complexity by adding unnecessary features and unnecessary complication.
Out of the original 18 MS-DOS programs I was using 20 years ago, only about half of them are now available as full Windows software. [Standard problem with specialist engineering software that has a relatively small demand]. To avoid losing access, I have kept the original [licensed] MS-DOS software running in parallel. Interestingly, Windows 98 was good at keeping MS-DOS software working. Windows XP was even better. But all things come to an end. Windows 8, then Windows 10 scuppered everything. But I have been able to keep going using VMware. But this is costly and a big solution just to run an old MS-DOS program.
vDos is much more convenient, but I am still on a steep learning curve.
|
|
|
Post by andersostling on Jan 20, 2021 12:29:34 GMT 1
Jos, thanks again for this lifesaver! My client has not registered a domain license, and I have completed all test, including printing. We are very satisfied that they can continue to use the old dinosaur for years to come! Anders Edit: Change NOT to NOW. Again, thank you for your efforts !
|
|
|
Post by skully on Mar 10, 2022 22:27:40 GMT 1
I have been creating programs in "dBase III Plus" for about thirty years. To do this for my personal use, I have had to purchase a used laptop from eBay that was reconditioned with a fresh copy of Windows XP, where DOS still runs natively. One of the problems with that is having to carry around two laptops. The other problem is transferring files using a thumb drive between the two computers. I just found vDOS and decided to try it out. It works great on dBase!
Why do I still use dBase III Plus, you ask? Because when I first started using it, that was what my company was already using. When they went to upgrade it to be current on the license, they opted to purchase dBase V, which I immediately noticed the distributed architecture would not work with the "first person" programs what were written. Meaning that all of the programs had to be modified to "third person" references. In the end, they kept using dBase III Plus and were never questioned about the license. It also isn't bogged down with all of the unused "features" that Five has (so it really works fast).
One of the word processing programs that I like to use is "Professional Write". It is a DOS based program that is very easy to use, especially when writing programs in dBase. The reason that I prefer to use it is because it allows me to edit programs in vertical columns or blocks instead of text-style editors. It does not work in vDOS because the F-keys (F1 through F6) do not function correctly for the program, they still do their assigned keyboard functions, even while using the Function button. I have even tried alt and ctrl with no luck. I am not sure if its something that I have not configured correctly or not.
Thanks for creating vDOS! And if anyone can provide any assistance for my F-key issues, I would be very grateful.
|
|
|
Post by Jos on Mar 11, 2022 0:50:52 GMT 1
dBase V is generally considered far more superior to dBase III. Function keys should just work fine, complication you use a laptop. As you know, function keys are by default supposed to do other things. Like starting some Windows program, in/decreasing screen brightness, whatever. Attached DOS SCODE.COM program will show what is reported to a DOS program. Could help you to figure what setting of the (Window) keyboard driver is needed. Jos Attachments:SCODE.COM (2.97 KB)
|
|
|
Post by skully on Mar 11, 2022 16:23:06 GMT 1
I'm sure that dBase V has much more capabilities than III+ does. But in all of my years of writing programs, I have never had dBase III not be able to do what I want it to do. With that said, I did run into a limitation that may have been the computer that I was working on, in that the maximum number of records that it was capable of having in a single database was just over one million records. I was able to work around that problem by doing multiple sorts to create several smaller databases and indexes.
As for the function keys, while I'm out today I will purchase a new keyboard and mouse combo and see if that works. I could use a new keyboard anyway. Also, the SCODE.COM file failed to work with my laptop, which is a HP Notebook 64 bit, running Windows 10 Home version 21H1. The message that I got was, "This app can't run on your PC. To find a version for your PC, check with the software publisher."
|
|
|
Post by Jos on Mar 11, 2022 17:00:23 GMT 1
dBase V is also supposed to have fixed bugs of earlier versions...
SCODE.COM is a DOS program, so you should run that in vDos. You could also test what those function keys do and when in a Windows program that uses those keys. Like F1 and F5 in Notepad.
Jos
|
|
|
Post by skully on Mar 11, 2022 22:14:13 GMT 1
Okay... I ran SCODE.COM in vDOS and it showed what I expected to while holding the Function key and pressing F1 through F6. Even better is my new keyboard! Ten dollars for a new keyboard and mouse combo and no issues with the function keys at all. Everything works great!
Thanks for all of your help! You have added a great deal of functionality to Windows that it desperately needed!
And I'll look into getting dBase V again. You have piqued curiosity and so I will check it out!
|
|
|
Post by Jos on Mar 11, 2022 22:46:11 GMT 1
Glad to hear, but don’t expect real help to specific DOS programs like dBase, whatever version.
I essentially did no real DOS programming myself since the turn of the century.
Jos
|
|
|
Post by 37364nt on Jan 3, 2023 17:16:02 GMT 1
My small company will still be using it for very long time.
|
|
|
Post by xetwnk on Jun 14, 2023 0:20:46 GMT 1
Depends on whether I can get said DOS program to work at all; then we'll see! Right now it locks up at startup, for reasons unknown but resulting in enormous CPU consumption without ever arriving at the point where it accepts a command keystroke. No idea, yet, whether this is a vDOS issue, a corrupted-DOS-program or corrupted-program-data issue, "or what." Further bulletins, perhaps, someday, as things sort themselves out. (And what's this I hear about "starting vDOS with the logging option"? What "logging option?" Documentation, man, documentation... Xet
|
|
|
Post by Jos on Jun 14, 2023 8:29:22 GMT 1
The vDos download page states: Submitting an issue: Describe it as detailed as possible, eventually attach your autoexec and config.txt files. If autoexec.txt starts another batch file, include that also. A mere “My program won’t …” doesn’t help to come to a solution, how simple that even might be...
You seemingly found the logging option. It’s indeed not documented. People often don’t read the documentation, and that option is only useful in specific circumstances. At least me knowing what the program and problem would be.
Jos
|
|