|
Post by stevecc on Jan 26, 2021 1:26:22 GMT 1
I am running 2015.11.01 build 2017.03.15 as reported by typing "ver" at Dos Prompt.
Is this the right version to be running for an old Dbase 4 program?
If not - Please point me to the right place to learn how best to update my install.
Edited since I figured out what version I am running
|
|
|
Post by Jos on Jan 26, 2021 2:10:59 GMT 1
I do not support old versions of vDos, certainly no vDosPlus (build 2017.03.15 or whatever) based on vDos 2015.11.01.
Eventually go to the vDos homepage (https://www.vdos.info) and go from there.
Jos
|
|
|
Post by stevecc on Jan 26, 2021 19:26:13 GMT 1
Hi Jos Thank you for your reply. I see now that I accidentally wandered here by mistake when I was looking for help with using VDosPlus - not VDos. Oops. I installed VDos Plus on my machine a while back when I was looking for a way to run my old dBaseIV program on more recent version of Windows - newer than Win7. It installed easily and I got it working but then let it sit because I was still maintaining a Win7 box to run it on. I am anticipating needing to abandon Win7 now so have gotten more serious and started doing more testing and tweaking hence my wanting to see if I have the latest version of VDos Plus. So I find myself now wanting to know if I should switch to the latest version of VDos or stick with VDosPlus. Can anyone here give me guidance on that choice or point me to somewhere to get that answer. My Dos App - dBaseIV is for crunching numbers and printing reports.
So sorry if my initial question was inadvertently insulting. I just need to make a choice about whether to stay with vDos Plus or switch to vDos
Thank you for all you do. Steve
|
|
|
Post by Jos on Jan 26, 2021 20:52:09 GMT 1
If you actually use any of the vDosPlus additions to vDos, you should just stick with vDosPlus since those additions won’t appear in vDos.
vDosPlus of course misses a few years of vDos development. Most apparent would some 150% speed increase and an internal print processor. If dBaseIV supports a FPU, number crunching would benefit a lot more since recent vDos versions have a FPU, so it is not emulated in 16-bit code.
Jos
|
|
|
Post by stevecc on Jan 26, 2021 21:06:47 GMT 1
I looked at www.vdosplus.org/featurelist.htm and I must admit that I do not know if I am using/needing any of the stuff listed there. It appears to me that vdosplus may no longer be supported so I am thinking maybe I should switch to VDos right now. Do you think that I will be able to run my dBaseIV program in vdos? Be able to print to Windows network printers instead of just a dot matrix on LPT1? Be able to print reports to a PDF creator program like CutePDF? Thanks
|
|
|
Post by Jos on Jan 26, 2021 22:21:52 GMT 1
If your program runs in vDosPlus, it should certainly run in ‘plain’ vDos. vDos incorporates a DOS-to-Windows printprocessor that supports Epson, PCL and IBM Proprinter input. You can print to any, real or virtual, printer installed in Windows.
Jos
|
|
|
Post by stevecc on Jan 28, 2021 3:40:51 GMT 1
Just wanted to touch back so that others who come to this thread in the future see. VDos works great with my dBase IV program. Gonna switch to it and not continue to use VDos Plus which was fine in many respects but printed a watermark on some print jobs and seems to no longer be supported actively. I sure appreciate that you stuck with me and helped me get clear about using it. I will bother you later with some other questions in new threads. Thanks
|
|