Re: [Freedos-devel] FreeDOS 1.3-RC5
On 9.12.2021 18:35, Jerome Shidel wrote: > >> * When launching PGME, I couldn't find the PGME.BAT file. So I can't >> start FDIMPLES for instance. > > There is no such file as PGME.BAT. Ouch. PGM.BAT works just fine, I was looking for PGME.BAT, my bad. >> * Speaking of FDIMPLES, it doesn't display Turkish characters like ş, ğ, >> ı and so on. > > Well, the problem would not be FDIMPLES itself. It doesn’t care what > character is being displayed. The exception being when converting upper/lower > case may have odd behaviors with non-english characters. > > That leaves the original translation, code page conversion, possible old > metadata that has not been updated, an issue processing the meta-data by one > of the package management utilities or processing done in the RBE. > > It will need further investigation. Okay, have fun :-P As an additional information, French letters such as é, ê, è and so on aren't displayed either. >> 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 > So to help determine what is going on. See it it still happens when LANG=EN. > If it does, then the problem is probably not the FDNET.BAT file. Everything is working fine now. I don't know what the problem was and like Tom said, I should have written down the error message. Anyway, in English, French and Turkish in VirtualBox FDNPKG can connect and update the packages. >> I also noticed some translation typos, stuff like a Parameter Error in >> French in CDROM.BAT, a /p in the installer in Turkish and some slight >> layout problems mem because of a missing space. After playing a little >> more with the new RC, I'll send corrections to FD-NLS. Alright, the /p was enclosed in quotation marks, so this was easy. Regarding the Parameter Error messages, I noticed them in cdrom.fr and fdnet.fr for instance. Let's consider: CD.TRY_DRVR= /g tentative d'utilisation du pilote CD /fYellow "%1" /fGrey in cdrom.fr, in English it's ERROR.HARDWARE=/fLightRed Physical hardware networking is not supported at this time. /fGrey /p or ERROR.HARDWARE=/fLightRed La mise en réseau matérielle n'est actuellement pas prise en charge. /fGrey /p in fdnet.fr -- in English it's ERROR.HARDWARE=/fLightRed Physical hardware networking is not supported at this time. /fGrey /p I guess these are used in batch files and that the ' character is the problem. Should it be escaped or be in double quotation marks? ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] FreeDOS 1.3-RC5
Hi Tom, I regret that you had a bad day today. The reason: thraex and I are translators of this (a little buggy) OS. I know several of them, among others I reported that in fdisk it is not possible to enter partition sizes bigger than 999 GB for FAT32 partitions because the possible number of digits does not support this. I assume this bug still exists although it is longer time ago since I reported it. You remember? Years ago I reported that mkeyb gr mixes x and z in virtual box. I remember your answer... Years later it was fixed... As I tested a lot of programs (Win, Linux, DOS) in the last 22 years of work, I learned that you never know what the programmer really wants to receive as error message - where the logs are - if there are some at all. I personally learned to give as much feedback as possible, but sometimes it is not possible or very hard to describe for someone who never learned programming. My experience was that screenshots are often helpful to show what I mean. But some programmers of FDOS do not like them as they need so much space in mails... @Berki: have a look at Github, zzz-notes-and-misc-items NLS-was-funzt-was-nicht, among others you will find: "edlin" edlin files now have name edlin16/32 - NLS exists but DOES NOT WORK! PLEASE CHECK! I think append and others that were translated by us had the same problem, so do not be astonished. Willi Sent: Thursday, December 09, 2021 at 6:35 PM From: "tom ehlert" To: "Technical discussion and questions for FreeDOS developers." Subject: Re: [Freedos-devel] FreeDOS 1.3-RC5 Hallo Herr thraex, am Donnerstag, 9. Dezember 2021 um 14:55 schrieben Sie: > I gave it a quick try in VirtualBox thanks for testing > * In VirtualBox the network seems to be automagically detected, which is > *great*. But when I try to use say FDNET, I get a packet driver error > and it can't establish a connection. 'I get a packet driver error' is pretty useless for diagnosis. I'm fairly certain there is more detail available for this concrete error message. Why don't you people spend the minimal effort to report the EXACT ERROR that you get? even when many (modern?) error messages are not helpful, some are. And it saves a full email round trip if you tell us the error message on first contact. Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] FreeDOS 1.3-RC5
Hallo Herr thraex, am Donnerstag, 9. Dezember 2021 um 14:55 schrieben Sie: > I gave it a quick try in VirtualBox thanks for testing > * In VirtualBox the network seems to be automagically detected, which is > *great*. But when I try to use say FDNET, I get a packet driver error > and it can't establish a connection. 'I get a packet driver error' is pretty useless for diagnosis. I'm fairly certain there is more detail available for this concrete error message. Why don't you people spend the minimal effort to report the EXACT ERROR that you get? even when many (modern?) error messages are not helpful, some are. And it saves a full email round trip if you tell us the error message on first contact. Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] FreeDOS 1.3-RC5
Hi, > On Dec 9, 2021, at 8:55 AM, thraex wrote: > > > > On 9.12.2021 01:15, Jerome Shidel wrote: >> Hello FreeDOS Community, >> >> The wait for 1.3-RC5 is over. It has arrived! > > Yay! Thank you! :-) > I gave it a quick try in VirtualBox after choosing French and Turkish in > the installer and here are some remarks: > > * Blocek needs to be updated to 1.62r2, translations do not seem to be > included for 1.4 Not sure whats going on with Blocek. I’ve tried to run it a couple times in a VM, but have never been able to get them to work. So, IDK. > * When launching PGME, I couldn't find the PGME.BAT file. So I can't > start FDIMPLES for instance. There is no such file as PGME.BAT. Instead of running PGME.EXE, just run PGM it is in the path spec. Basically, there are several ways to run PGME. As the warning states when you tried to run FDIMPLES, that when PGME is directly invoked by using PGME.EXE and not started through the Launch Batch file PGM.BAT (No E), some functions are not available. When PGME launches a program, it reduces its memory footprint down to about 10k. Usually, this is adequate. But for some programs or special tasks, PGME completely removes itself from memory using some batch magic. There are various reasons you may want PGME to completely exit memory. And generally, PGME handles wether or not it leaves a stub in memory or completely shuts down automatically. However, the free all memory / 0k footprint requires starting PGME through the launcher batch. PGME is smart enough to notice that you did or did not start it using the batch. You can also start it to a menu or specific program… pgm games pgm doom And so on. > * Speaking of FDIMPLES, it doesn't display Turkish characters like ş, ğ, > ı and so on. Well, the problem would not be FDIMPLES itself. It doesn’t care what character is being displayed. The exception being when converting upper/lower case may have odd behaviors with non-english characters. That leaves the original translation, code page conversion, possible old metadata that has not been updated, an issue processing the meta-data by one of the package management utilities or processing done in the RBE. It will need further investigation. > * APPEND /? is in English whereas translations for several languages > exist on FD-NLS repo. We will need to check if APPEND is actually using any NLS. > * After installing in French, the keyboard layout is correct, so bug > #282 on SF seems to be fixed. Good. > 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? > * In VirtualBox the network seems to be automagically detected, which is > *great*. But when I try to use say FDNET, I get a packet driver error > and it can't establish a connection. Has anyone tried to see if that > works by default with a NAT connection? Works fine for me in VirtualBox. Which is where I do most of my testing. There were some changes in FDNet and the DHCP client was also updated. But, the packet drivers haven’t changed. So to help determine what is going on. See it it still happens when LANG=EN. If it does, then the problem is probably not the FDNET.BAT file. I’m always running the latest version of VirtualBox (6.1.30) on a Mac and the default VM config using PCnet-FAST III adapter as NAT works fine. DHCP reports: IPADDR 10.0.2.15 NETMASK 255.255.255.0 GATEWAY 10.0.2.2 NAMESERVER 192.168.10.1 (which is correct for this subnet on my network) > On my side the gateway is > detected as 10.0.2.2 whereas it should be 192.168.0.1. When using NAT, the gateway is some network range made up by the host computer and not your home network. Using Bridged mode, kinda shares the ethernet adapter and puts the VM directly on the network (probably 192.168.x.x) > I also noticed some translation typos, stuff like a Parameter Error in > French in CDROM.BAT, a /p in the installer in Turkish and some slight > layout problems mem because of a missing space. After playing a little > more with the new RC, I'll send corrections to FD-NLS. Sounds great. > Thanks again for the RC5! :-) Jerome ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] FreeDOS 1.3-RC5
On 9.12.2021 01:15, Jerome Shidel wrote: > Hello FreeDOS Community, > > The wait for 1.3-RC5 is over. It has arrived! Yay! Thank you! I gave it a quick try in VirtualBox after choosing French and Turkish in the installer and here are some remarks: * Blocek needs to be updated to 1.62r2, translations do not seem to be included for 1.4 * When launching PGME, I couldn't find the PGME.BAT file. So I can't start FDIMPLES for instance. * Speaking of FDIMPLES, it doesn't display Turkish characters like ş, ğ, ı and so on. * APPEND /? is in English whereas translations for several languages exist on FD-NLS repo. * After installing in French, the keyboard layout is correct, so bug #282 on SF seems to be fixed. 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. * In VirtualBox the network seems to be automagically detected, which is *great*. But when I try to use say FDNET, I get a packet driver error and it can't establish a connection. Has anyone tried to see if that works by default with a NAT connection? On my side the gateway is detected as 10.0.2.2 whereas it should be 192.168.0.1. I also noticed some translation typos, stuff like a Parameter Error in French in CDROM.BAT, a /p in the installer in Turkish and some slight layout problems mem because of a missing space. After playing a little more with the new RC, I'll send corrections to FD-NLS. Thanks again for the RC5! ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
