On 10.12.2021 14:55, Jerome Shidel wrote:
>> >> Ouch. PGM.BAT works just fine, I was looking for PGME.BAT, my bad. > > No problem. > > When PGME is installed using it’s installer, it mentions the batch > loader PGM. But when installed via FreeDOS package, there isn’t a good > way to make these of PGM.BAT obvious. > > It doesn’t matter but… Technically, it is Program Manager version > Eternity updated last on whatever date. Not Program Manager Eternity > version (some date). So the E is actual a version reference. Even the Hm, I'll need to update the translations then. > abbreviated PGM is a through-back to an earlier time when it was once > called “Program and Game Menu”. It has been around a very long time. It > has been renamed several times and it’s first real version was just > called Menu and ran on MS-DOS 3.3. However, that was my first use of DOS > and I found a need for it almost immediately. However, it’s roots > pre-date my first use of MS-DOS and the PC. The seed for what would > eventually become PGME was first planted circa 1983-84 on the Coleco > Vision Adam and some bit hacking I did on a third party multi-boot game > loader I did not make. Wow, the word "Eternity" makes more sense now. >>>> But the Turkish Q keyboard doesn't work >>>> after installation (haven't tested the F layout yet) so bug # 306 on SF >>>> still seems to be with us. >>> >>> Is it being set correctly in FDAUTO and just not working? >> >> It would seem so. I see the line >> keyb TR,857,%DOSDIR%BINKEYBRD2.SYS >> in FDAUTO.BAT > > Not %DOSDIR%\BIN\KEYBRD.SYS? > > If those slashes are missing, it is a minor bug with the RBE not being > told to escape the \ character. They are indeed missing. I added them and the keyboard layout seems to be perfectly OK now. > Please, file a bug report preferably > at https://gitlab.com/FreeDOS/OS/builder/-/issues > <https://gitlab.com/FreeDOS/OS/builder/-/issues> or on FD-NLS so I don’t > forget to fix it. > Also, one for the stripped characters. :-) Understood :) > So, for your example you can “wrap” them several ways… > > CD.TRY_DRVR= /g "tentative d'utilisation du pilote CD" /fYellow "%1" /fGrey > ERROR.HARDWARE=/fLightRed "La mise en réseau matérielle n’est > actuellement pas prise en charge." /fGrey /p > > or > > CD.TRY_DRVR= /g tentative "d'utilisation" du pilote CD /fYellow "%1" /fGrey > ERROR.HARDWARE=/fLightRed La mise en réseau matérielle "n’est" > actuellement pas prise en charge. /fGrey /p > > or what ever makes sense to you. > > Actually, since %1 won’t contain a quote character or /, it doesn’t > actually need wrapped. It’s just habit. Thank you for the explanation. I had tried with double quotes and that had gotten rid of the parameter errors but wasn't sure if that was the right thing to do. Now, time to get work to wrap stuff correctly. > Running TEST.BAT outputs three lines, with the “line” a different color > and number with color attribute 15 (white on black). Also, the last line > has a blue background the width of the display. (Grey and Gray are the > same color) > > > Anyhow, I hope that all makes sense. Looking forward to you pull request. Yes, thanks again. Bug reports and pull requests will be incoming in the next few days :-) _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
