On Fri, Jul 30, 2021 at 5:20 PM Bret Johnson <bretj...@juno.com> wrote: [..] > First of all, you say that this is intended to put ASCII codes into > a file, but it just writes them to the screen. You indicate the > user was asking how to inject them into a file. The most obvious > way I can see to do that (though certainly not the only way) is to > redirect the output, e.g.: > > char 247 248 > file.txt > > Shouldn't that be mentioned somewhere in the documentation?
Fair point. And I did write the program to print to stdout so the user could see the character they were generating, with the assumption they would then run the program again to redirect the output to a file. I'll update the txt file to mention file redirction. > Lastly, the ASCII code that is seen on the screen for characters > >127 will depend on the current Code Page. E.g., the example you > used (character 248) is the degree symbol on both Code Pages 437 and > 850 (probably the two most common ones), but may not be a degree > symbol on any of the other Code Pages (I'm not sure). The next > character over (character 247) is even different between Code Pages > 437 and 850. You may also want to mention something about Code > Pages in the documentation. 248 is the degree symbol on every codepage referenced in the MS-DOS 5 manual on my bookshelf: 437 (English), 850 (Multilingual - Latin I), 852 (Slavic - Latin II), 860 (Portugal), 863 (Canadian-French), 865 (Nordic) -- > I also think I remember from a long time ago a TSR that could pop-up > an ASCII table on the screen and possibly "inject" the character > into an application. It was probably available on a now-obsolete > site like SimTel or Garbo but I don't remember any more than that. > I could also just be imagining things. The text editor I normally > use has a built-in pop-up ASCII table so I don't need any kind of > program like that. > I think I remember a program that did that, too. I don't know where to find it though. > For the Alt-key trick, sometimes it is necessary to have NumLock > enabled, while other times the NumLock state doesn't matter. If > just tried in VMWare Player and DOSBox-X and it works no matter the > NumLock state, while in QEMU it doesn't work at all no matter the > NumLock state. That seems to me like a bug in QEMU. I don't know what virtual machine this person was using, but I use QEMU and Alt+numpad doesn't work there. So that matches what you're saying here. Jim _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
