Re: [Freedos-user] From BTTR: FAT32 ramdisk, SvarCOM shell, Doszip commander
Off topic and flagrant necromancy, yet I'll briefly note somebody (kind of) did. * (Disclaimer: "correct" loosely defined)* https://bestofcpp.com/repo/AnttiTakala-SSH2DOS P.S. Thanks Eric On Sun, Mar 13, 2022 at 5:45 PM Karen Lewellen wrote: > Seems like some fine efforts. > Speaking personally, I wish someone would devote time to upgrading ssh > for dos, so that the dh key exchange issue was corrected. > Kare > > > > On Sun, 13 Mar 2022, Eric Auer wrote: > > > > > Hi! > > > > Today is a day full of announcements on BTTR-SOFTWARE.DE :-) > > > > https://www.bttr-software.de/forum/forum_entry.php?id=18797 > > > >> RDRVSX32: FAT32 RAM drive for HimemSX (Announce) > >> > >> posted by jadoxa, Queensland, Australia, 13.03.2022, 13:58 > >> > >> I had a request (via email) to create a RAM drive greater than 4GiB. > >> It sort of works (works on his and mine 8GiB AMD, but has issues with > >> his 32GiB Intel) so if anyone has the time and inclination to test, > >> that'd be great. You will need more than 4GiB RAM (in order to access > >> super-extended memory), preferably more than 8GiB (in order to test > >> accessing beyond 4GiB). Our testing has been simple so far: just copy > >> large files (he was able to create a 28GiB RAM drive, copy hundreds > >> of 64MiB files, but it fails copying a 1GiB file). > > > > Link: http://shsufdrv.adoxa.vze.com/rdrvsx32.zip > > > > > > > > https://www.bttr-software.de/forum/forum_entry.php?id=18799 > > > >> Doszip Commander version 2.63 available (Announce) > >> > >> posted by rr, Berlin, Germany, 13.03.2022, 14:20 > >> > >> On 02 March 2022 Hjort Nidudsson released a new version. > >> > >> Home page: https://github.com/nidud/doszip > >> Download: https://github.com/nidud/doszip/releases/tag/v2.63 > >> > >> Changes since version 2.55 are: > >> Changes in 2.63 - 2 Mar 2022 > >> - extended country-specific date format > >> > >> Changes in 2.58 - 15 Feb 2022 > >> - added country-specific date format > >> > >> Changes in 2.57 - 12 Feb 2022 > >> - changed "Jump" to "Skip" in Delete dialog > >> - fixed color issue in Move dialog > >> - fixed issue with pipe command -- unzip -hh | more > > > > > > > > https://www.bttr-software.de/forum/forum_entry.php?id=18798 > > > >> On 13 March 2022 Mateusz Viste released SvarCOM version 2022.3. > >> > >> What is SvarCOM? > >> > >> Quoting from http://svardos.org/svarcom/: > >> SvarCOM is the SvarDOS command line interpreter, known usually under > >> the name "COMMAND.COM". It is designed and maintained by Mateusz > >> Viste, and distributed under the terms of the MIT license. > >> > >> For the time being, it is a work-in-progress project that - although > >> functional - is not entirely polished yet and might miss a few bits > >> and pieces. SvarCOM version 2022.0 must be considered a "preview" > >> version. See the documentation included in the zip file for details. > >> > >> SvarCOM is minimalist and I'd like to keep it that way. It aims to be > >> functionaly equivalent to COMMAND.COM from MS-DOS 5.x/6.x. No LFN > >> support. > >> > >> As of version 2022.0, SvarCOM's resident footprint is under 2 KiB. > >> > >> What is new in version 2022.3? > >> > >> Here is his 2022.3 announcement to the SvarDOS mailing list: > >> Hello all, > >> > >> SvarCOM 2022.3 has been published right now. It comes with many > >> improvements and bug fixes. Many thanks to Robert Riebisch who > dedicated > >> a lot of time to perform extensive tests on SvarCOM and had the > strength > >> to annoy me over and over about the various glitches he found. > >> > >> The new SvarCOM package is already available on the SvarDOS packages > >> repository. It can also be downloaded from the SvarCOM sub-project page > >> at http://svardos.org/svarcom > >> > >> As an experiment I did a SvarDOS build that uses SvarCOM instead of > >> FreeCOM. It is the build 20220312, available in the "files" section of > >> the website: http://svardos.org/?p=files > >> > >> If this build proves stable enough, it might become the default > download > >> presented on the main page, but for now it needs some testing. There is > >> also still one or two things that needs to be added (like DIR/O > support). > >> > >> The main advantage of SvarCOM over the legacy FreeCOM is that the > former > >> is much lighter (2K of memory footprint), which is esp. important on > >> pre-386 machines. > >> > >> An interesting side effect of replacing FreeCOM by SvarCOM is that some > >> of the SvarDOS floppy sets decreased: > >> > >> 720K set went from 4 floppies to 3 floppies > >> 1.2M set went from 3 floppies to 2 floppies > >> > >> Other sets remained the same amount of floppies (6x 360K, 2x 1.44M and > >> 1x 2.88M) > >> > >> Note for the future: there are cases where it is possible to decrease > >> the amount of floppies simply by ordering files on the floppies > >> differently. For instance, it is possible to decrease the 360K set to 5 > >>
Re: [Freedos-user] DOS Fonts
Like Aitor mentioned there are some basic tools for it. (Like GNU and Display) Also, there are some others. V8PowerTools VFONT.COM can load the normal raster fonts (like GNU load font) temporarily. When the video mode is reset (or changed) the fonts will revert back to their previous state. ImgEdit can edit standard raster fonts and always uses that file format for 8x?? size fonts. Fonts wider than 8 bits use a different format and are for the “Danger Engine” and graphics modes only. PGME uses a different font file format and includes its own editor (EFNTDSGN). However, it also comes with utilities to convert from its format to/from raster format. It also includes tools to temporarily load them. It even includes a utility that can turn the font into a stand alone executable TSR that keeps the font persistent for mode resets and changes. There are other tools as well. :-) Jerome ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] DOS Fonts
Hello, The graphic card maintains information of how character glyphs are made out of their character code. Basically it is limited to being able to represent just 256 characters together at a time (there is a trick to double this to 512, but doesn't make a difference here). Each of such configuration set is called a codepage, and the different codepages usually maintain the first 128 characters the same (ASCII), whereas the other 128 characters are used to represent different characters that may vary between countries. Ideally, one could define different codepages that do not change which character is represented, but the way the character is printed to screen. But it is usually not the case: codepages usually have the same "appearance" but different locale characters (at least in the characters 129-255). Also notice that after screen resolution changes usually reset the original codepage the BIOS came with (usually CP437, US-English), so your CP or font is wipped out. This means that you'd need some resident code that would restore your codepage after each time that resolution is changed. This "screen" stuff is, in the end, part of the Console management. Thus, it should be the responsibility of DOS' CON (console) devide. But as the codepage change is very rarely executed (I assume) inside the US, this particular resident code is not shipped with kernel's CON device, but you have to enlarge your CON and load it yourself as you boot your PC. SO, what are your options in FreeDOS? There are two options that I do know of: * DISPLAY is the standard DOS way of doing this (in MS-DOS, it is DISPLAY.SYS, in FreeDOS it is DISPLAY.COM). You can try and create a CPI file with your "font", and thus use standard (MODE CON...) mechanism to load this font within DISPLAY. DISPLAY will guarantee that the font remains after a change of resolution. In addition, this would be incompatible with any DOS user that wants to actually change a codepage (and set, for example, the standard western european with Euro CP858), unless you create fonts for each of the codepages. * There is GNU LOADFONT: you can create a font for GNU Loadfont, and load it within a single executable. However, I am not sure that Loadfont will help you keep your codepage on a resolution change (I believe it does not). Also I ignore how loadfont deals with different codepages (I seem to remember that some fonts have different configurations for different codepages). Aitor On Wed, 15 Jun 2022 at 19:37, Ralf Quint wrote: > On 6/15/2022 10:30 AM, Daniel wrote: > > Is anyone familiar with how DOS fonts work? > > > > There are some .com files that will change the original font with > > another and ya can create your own. I created a TI-99/4aA font to use. > > > > So how does it work? Is the hardware font cached and the cache is > > changed? Some programs will revert back to the original font when > > exiting back to DOS. > > > > Is there a location where one can read/write the font information? > > There is no such thing as a "DOS Font". Seriously! > > Any font functionality is totally dependent on the graphics card being > used. Any attempts to (kind of) standardize the use of fonts (incl. > modification) might be found in the description of INT 10h functions > (BIOS Video interrupt) but pretty much all of those, beside some VERY > BASIC stuff common on VGA adapters) is totally manufacturer dependent... > > > Ralf > > > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] DOS Fonts
On 6/15/2022 10:30 AM, Daniel wrote: Is anyone familiar with how DOS fonts work? There are some .com files that will change the original font with another and ya can create your own. I created a TI-99/4aA font to use. So how does it work? Is the hardware font cached and the cache is changed? Some programs will revert back to the original font when exiting back to DOS. Is there a location where one can read/write the font information? There is no such thing as a "DOS Font". Seriously! Any font functionality is totally dependent on the graphics card being used. Any attempts to (kind of) standardize the use of fonts (incl. modification) might be found in the description of INT 10h functions (BIOS Video interrupt) but pretty much all of those, beside some VERY BASIC stuff common on VGA adapters) is totally manufacturer dependent... Ralf ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] DOS Fonts
Is anyone familiar with how DOS fonts work? There are some .com files that will change the original font with another and ya can create your own. I created a TI-99/4aA font to use. So how does it work? Is the hardware font cached and the cache is changed? Some programs will revert back to the original font when exiting back to DOS. Is there a location where one can read/write the font information? ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] SBPmixer
Tanks Il lun 13 giu 2022, 17:32 Jerome Shidel ha scritto: > Hi All, > > Today, I released the NASM port of my ancient (Turbo Pascal) Sound Blaster > Pro (and compatible) Mixer driver. It is a program-loadable device driver > for adjusting mixer settings like volume levels. The driver can also be > compiled into executables. The release also includes a 2.5K command line > program for viewing and adjusting mixer settings. If you only want to use > the command-line tool, you can just delete the driver file. The utility has > the driver compiled into it and does not need or use the external driver > file. > > https://fd.lod.bz/repos/current/pkg-html/sbpmixer.html > > :-) > > Jerome > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Limit text output to specific area
> NT 10h has only some window scrolling/clearing functions. And you can > query/position the cursor. [..] > That windowing function that Jim referenced in his little sample program > is one that does the basic window management for you. But this will only > work if you are using library functions for the compiler that are aware > of the selected window coordinates, it will not work for a simple > printf()/puts() etc. Thanks, that's I was afraid of ;) just wanted to make sure I didn't miss anything -- regards, Z. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
