|
|
Post by advlaser on May 13, 2021 0:24:09 GMT 1
I just updated to the latest vDos and it's working great. However there is one issue.
In my config.sys, I have the following line...
COLORS = #000000 #000080 #008000 #008080 #800000 #800080 #808000 #c0c0c0 #808080 #0000ff #00ff00 #00ffff #ff0000 #ff00ff #ffff00 #ffffff\
With this line I get the error "COLORS= Only MONO allowed". I can comment out the line, but it alters the colors and I prefer the colors they way they used to look.
Any Ideas? Thanks!
|
|
|
|
Post by Jos on May 13, 2021 9:38:05 GMT 1
COLORS= has proven to be too cumbersome. So it’s replaced by THEME=. And yes, you’ll have to do with those 9 color schemes.
Jos
|
|
|
|
Post by advlaser on May 13, 2021 19:51:33 GMT 1
That fixed my problem, Theme = 1 looks great!
|
|
|
|
Post by Jos on May 13, 2021 20:02:16 GMT 1
Theme 1 is a high contrast version of the standard DOS colors, created by Edward Mendelson.
Jos
|
|
|
|
Post by kostas on Nov 23, 2021 17:44:52 GMT 1
Good Evening
All well and good, but the older/full color definition options, was much better!!
|
|
|
|
Post by Jos on Nov 23, 2021 18:02:43 GMT 1
Well, at least one can now easily test some THEME= settings and it provides for a dark mode.
That can’t be done with COLORS= since more than 16 colors are then defined/used.
Jos
|
|
|
|
Post by jamesb52 on Nov 23, 2021 21:37:06 GMT 1
I'm using SharkBase (www.sharkbase.ca) on vDOS. SharkBase allows 256 color choices from inside the application. Is that not permitted on your newest release of vDOS?
|
|
|
|
Post by Jos on Nov 23, 2021 22:09:58 GMT 1
I don’t know what those 256 color choices would be. A DAC color setting? Will be and was ignored by vDos.
DOS programs only support 16 colors in text mode. Those colors could of course be linked to any RGB value, 16M colors, by COLORS=. As THEME= now does with predefined RGB values.
The DARK mode option is based on the THEME=number setting. At runtime an algorithm not only converts those colors, but also differentiates between fore- and background colors. You can’t do that with COLORS=, or whatever.
Jos
|
|
|
|
Post by jamesb52 on Nov 24, 2021 22:56:11 GMT 1
Interesting! Here's a link to the COLORS section in the SharkBase on-line manual: www.sharkbase.ca/shark-colors.htmlThere seems to be hundreds of simple color setting options. I only use a handful. |
|
|
|
Post by Jos on Nov 24, 2021 23:08:57 GMT 1
That seems for people willing to spend endless time experimenting with those settings, like the previously COLORS= (it’s mostly the same).
You now have to do with the extra 9 predefined THEME values. All done with this in SharkBase was already ignored by vDos.
If one comes with a great looking COLORS=sequence, I could surely replace one of the predefined with that.
Jos
|
|
|
|
Post by levievre on Nov 28, 2021 18:51:35 GMT 1
Just like Costas, I think old COLORS= setting was much better.
Please Jos, bring COLORS setting back.
Levievre.
|
|
|
|
Post by Jos on Nov 28, 2021 20:13:35 GMT 1
Sorry, but vDos is mainly intended for end-users of DOS programs. I can’t imagine those spending big time experimenting with COLORS=.
And again: If one comes with a great looking COLORS=sequence, I could surely replace one of the predefined with that.
Jos
|
|
|
|
Post by levievre on Nov 30, 2021 20:36:19 GMT 1
Vdos is great for end-users of Dos programs, but wonderful for "advanced users" as well.
Personally, since i'm still coding in Turbo pascal today, i would love some kind of "programmer Vdos" project and would be ready to financially support such a project.
Levievre.
|
|
|
|
Post by Jos on Nov 30, 2021 21:00:01 GMT 1
What would set a “programmer vDos” apart from standard vDos?
Jos
|
|
|
|
Post by levievre on Dec 1, 2021 17:17:18 GMT 1
Hi Jos,
First of all, it is possible to customize as many parameters as possible in Vdos: Display, keyboard, mouse. Then incorporate some of the functionality of Vdosplus, in particular LFN management, and pursue the idea of going as far as possible into customization. That’s for the most part. Then depending on what is possible, here is a non-exhaustive list of the needs that I meet and that an "Extended" version of vdos might allow me to accomplish more easily: I use a lot of external applications to increase the functionality of my application, dosprinter for printing, thanks to which I can embed a recipient's email address in documents or insert images in specific locations on a page. The development of Dosprinter was halted in 2015. So I would like Vdos to perpetuate such functions. Today for example, I am looking for a way to download the attachments of received emails by stipulating one or more filters: sender's email address, keyword in the subject, in the message or in the name of the files attached. I think I can achieve this with a script in Python that I will run from my application but if such a function were included in Vdos it would be great. I would also need a quick COPY command which displays in a window the name of the file being copied with a progress bar.
There are a lot of things I can imagine but perhaps it's out of vdos borderland.
Levievre.
|
|
