|
Post by emendelson on Dec 1, 2021 17:25:15 GMT 1
Jos can of course answer for himself, but I very much doubt that any of those things will ever be added to vDos. The purpose of vDos is to run DOS applications, not to automate Windows workflows.
|
|
|
Post by Jos on Dec 1, 2021 18:19:21 GMT 1
I envision you would spend lots of time at modifying vDos, so little time remains to do actual productive programming. Would be you since those ‘enhancements’ seem rather personal.
Adding options just because you can isn’t my thing, my goal is the opposite. The less, the better.
Furthermore, vDos is since version 2016 closed source. So that would set you back some years.
DOSPrinter is a mature program. I don’t think it is handicapped by missing recent development. You could eventually contact Bojan Banko, in the past he mentioned DOSPrinter becoming freeware (perhaps even opensource?).
I also think it’s best to leave Windows specific stuff to Windows programs. Those run far faster then a DOS program in an emulator like vDos, without the associated limitations.
Jos
|
|
|
Post by emendelson on Dec 1, 2021 18:30:30 GMT 1
And in fact the author of DOSPrinter added the ability to print "raw" data under recent Windows versions. He did this when I asked him to add it. So he's responsive to requests.
|
|
|
Post by levievre on Dec 1, 2021 19:06:58 GMT 1
Happy to read Bojan Banko still work on Dosprinter if necessary. It's such a great app. I can still update my app today only thanks to Vdos and Dosprinter.
I realize a lot of my programming consists in trying to add or connect my old app with windows programs. Fortunately thanks to Vdos, launching any app from inside my Dos app is possible.
Maybe I could hope for a more "customizable" version of Vdos. LFN would be great too.
|
|
|
Post by Jos on Dec 1, 2021 20:09:23 GMT 1
If of interest, you might also have a look at COPYCLIP (Printing.pdf). Perhaps the next version will have a shortcut setting for the double click action…
Don’t expect more possible customizations (options) in future vDos version. LFN support never was an object. Many (existing) DOS programs don’t even let you specify/select a file name/path. And if so, don’t support, let alone require LFN.
Jos
|
|
|
Post by levievre on Dec 1, 2021 20:20:44 GMT 1
i know about old DOS existing programs limitations. So vDos will always be aim at end users. And some specific improvement for Dos programmers (even if we are only a few) will never be an option ...
|
|
|
Post by Jos on Dec 1, 2021 20:44:18 GMT 1
I don’t believe (new) DOS programming has any future.
You could try DOSBox-X, at their website: “We also hope that DOSBox-X (along with DOSLIB) can aid in new DOS development.”. And they seem in for any wish or suggestion…
Jos
|
|
|
Post by levievre on Dec 1, 2021 21:37:16 GMT 1
Probably Dos programming has no long future but it still exists at the present time.
Dosbox-x project doesn't work with my app (can't lauch a windows app like dosprinter). And I don't need an emulator for Windows 95/98/XP.
I much prefer Vdos as it's only a DOS TEXT app emulator.
|
|
|
Post by Jos on Dec 1, 2021 21:50:13 GMT 1
You could ask DOSBox-X why a Windows program (like DOSPrinter) doesn’t start.
If you don’t need Windows 95/98/XP (XP?) emulation, don’t use that option? A bit like your wished for options to others.
DOSBox-X incorporated the vDos TTF code/engine, so should also run DOS text mode applications with a better experience.
Jos
|
|
|
Post by levievre on Dec 1, 2021 22:04:59 GMT 1
I agree. Windows 95/98/XP emulation can be useful for others and this is something I respect of course.
But in my opinion, it becomes much more complicate and Dosbox-X is still not mature.
At the end, I much prefer strong reliability to large functionnalities.
Vdos is almost perfect for me. I am just dreaming of something like a 2021 Vdosplus.
|
|
|
Post by whathim on Jan 4, 2022 12:36:00 GMT 1
I’m evaluating vDos (see vdos.proboards.com/thread/504/text-editor-program-ems-memory) and yesterday I got my editor program running very nicely in vDos after rewritten some of the editor code. Thank you, Jos, – generally I’m impressed with your vDos. My editor does not support long filenames but under vDos is able to open a long filename (via the 8.3 name), edit it and then save it with the long filename preserved. This is exactly the same behavior I had under NTVDM so on this metric I score vDos 100%. However, I wanted to tweak the text/background colors and was at first excited when I saw mention of the COLORS statement that allowed any RGB to be linked to any of the 16 text mode colors in the palette. Then my hopes were dashed when I learn this is no longer supported. I’ve tried the predefined THEME color schemes but all except the default (0) looked horrible. I’m skeptical there is any such thing as “a great looking COLORS=sequence”. Surely, it’s always the case that a scheme could look great with a particular application but look hideous in others. For what it’s worth, can I add my vote for bringing the COLORS setting back. Further: When I right-click on the title bar of a NTVDM window in Windows XP/7 32-bit or a Command Prompt in Windows 10 64-bit and select “Properties” I get a dialog with a “Colors” tab. Using this dialog, I’m able to set each of the 16 colors in the palette to an RGB of my choice. Yet in vDos I’m unable to do this, either via a dialog or via a command. This can’t be right. It was a mistake to remove this ability from vDos IMNSHO.
|
|
|
Post by Jos on Jan 4, 2022 15:19:25 GMT 1
And so noted.
Jos
|
|
|
Post by kostas on Feb 3, 2022 16:24:06 GMT 1
Hello levievre. And I'm still writing code in Borland Pascal 7 (& Delphi of course) and I never regretted it
|
|
|
Post by levievre on May 1, 2022 12:54:25 GMT 1
Hello Kostas, And so do I. Im' still programming with BP7 every day and really love it.
Just noted there's a new 2022 Vdos update. Thank you Jos for that. A bit disappointed however since I still can't set colors. Please Jos, bring the COLORS setting back.
Levievre.
|
|
|
Post by Jos on May 1, 2022 15:17:49 GMT 1
Still not convinced of the usefulness of COLORS=, I’ll give it a further thought next week.
Perhaps an undocumented comeback, setting the colors of scheme no. 9 that’s obviously somewhat a spare.
Jos
|
|