Re: [Freedos-devel] Two remarks about FreeDOS 1.3 RC5

2021-12-27 Thread Juan Manuel Guerrero
Am Sun, 26 Dec 2021 11:25:22 -0500 schrieb Jerome Shidel : > Hi, > > > The second issue is that the DJGPP port of lynx distributed with > > RC5 is broken. As I have announced in: > > https://www.delorie.com/archives/browse.cgi?p=djgpp/2021/12/02/18:54:50 > > the fixed port is available as: > >

[Freedos-devel] Two remarks about FreeDOS 1.3 RC5

2021-12-24 Thread Juan Manuel Guerrero
I have been playing with the latestet FreeDOS 1.3 RC5 and I have observed that the line: if exist %dosdir%\LINKS\NUL set PATH=%path%;%dosdir%\LINKS in FDAUTO.BAT does not work because LINKS and all the other network stuff is installed in the C:\NET directory and not into the directory pointed by

[Freedos-devel] Broken pipe and file descriptor behavior of the kernel distributed by FreeDOS 1.3 RC1

2019-05-20 Thread Juan Manuel Guerrero
I have noted that FreeDOS 1.3 RC1 distributes a kernel 2042. This kernel seems to have serious issues concerning the redirection of file descriptors and the creation of pipes. I noted this when I tried to use the djgpp port of Bash 4.17 on FreeDOS 1.2 and later on FreeDOS 1.3 RC1. I use it to

Re: [Freedos-devel] Getting ready for FreeDOS 1.2

2016-10-22 Thread Juan Manuel Guerrero
Am 22.10.2016 18:08, schrieb Jerome E. Shidel Jr.: Hello Jerome and all the other interested ones, [snip] > What host OS are you using? openSUSE 11.4 > If you booted the CD under VMware and installed FreeDOS, > are you still booting the El Torito CD? Yes. I forgot to unmount it. Now I have

Re: [Freedos-devel] Getting ready for FreeDOS 1.2

2016-10-22 Thread Juan Manuel Guerrero
OFYI: I have tried to format a floppy image with a VMware Player 5.0.2 using FreeDOS 1.2-pre23 and I have observed the same issue as described for VirtualBox. If /q/u is used it becomes possible to format the image. I have also tried to format using only /d. See below for the output produced.

Re: [Freedos-devel] Getting ready for FreeDOS 1.2

2016-10-13 Thread Juan Manuel Guerrero
Hello Jerome and Eric Thank you for your comments. IMHO the issue of having a working keyboard is essential. DOS and its clones appear to their users as TUI thus if the keyboard does not allow to issue commands it makes the OS to become almost useless. An user that has to hit around ten

Re: [Freedos-devel] Getting ready for FreeDOS 1.2

2016-10-12 Thread Juan Manuel Guerrero
I have installed http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/previews/1.2-pre23/FD12CD.iso on a VMware virtual machine. The host is linux. The installation process runs flawlessly so far. But when finished and the machine is rebooted I end up with an US keyboard

Re: [Freedos-devel] Difference between command.com and frecom.com when parsing command line arguments of a batch file.

2014-07-23 Thread Juan Manuel Guerrero
Am 20.07.2014 23:20, schrieb perditi...@gmail.com: On Sun, Jul 20, 2014 at 2:53 PM, Eric Auer e.a...@jpberlin.de mailto:e.a...@jpberlin.de wrote: Hi Juan, ... Please note I am very happy to know that this issue has already been fixed but as a newbie to FreeDOS is it

Re: [Freedos-devel] Difference between command.com and frecom.com when parsing command line arguments of a batch file.

2014-07-21 Thread Juan Manuel Guerrero
Am 20.07.2014 20:53, schrieb Eric Auer: Hi Juan, It is still not fully clear to me how different DOS differs regarding the arguments passed to batch situation... Even if 4DOS solves it, what exactly is the difference in style? May be that the most important issue here is to understand that

Re: [Freedos-devel] Difference between command.com and frecom.com when parsing command line arguments of a batch file.

2014-07-20 Thread Juan Manuel Guerrero
Am 19.07.2014 12:43, schrieb Rugxulo: Hi, On Sat, Jul 19, 2014 at 12:00 AM, Mateusz Viste mate...@viste.fr wrote: I think this problem goes beyond path separators. As I understand it, any argument including a slash character will get exploded. So yes, this might be used as path separator,

Re: [Freedos-devel] Difference between command.com and frecom.com when parsing command line arguments of a batch file.

2014-07-19 Thread Juan Manuel Guerrero
Am 19.07.2014 00:37, schrieb Ralf Quint: On 7/18/2014 3:09 PM, Juan Manuel Guerrero wrote: This is not really disappointing. I was only testing for the possibility to recommend the FreeDOS 1.1 distribution as an alternative to WinXP and/or Win98SE to build DJGPP ports but this seems

Re: [Freedos-devel] Difference between command.com and frecom.com when parsing command line arguments of a batch file.

2014-07-19 Thread Juan Manuel Guerrero
Am 19.07.2014 07:35, schrieb Steve Nickolas: On Sat, 19 Jul 2014, Mateusz Viste wrote: Hi all, I think this problem goes beyond path separators. As I understand it, any argument including a slash character will get exploded. So yes, this might be used as path separator, but not only. For

[Freedos-devel] Difference between command.com and frecom.com when parsing command line arguments of a batch file.

2014-07-18 Thread Juan Manuel Guerrero
I do not know if this is the right place to report this FreCom issue and I do not know if this issue is already well known but I would like to report it anyway. Please inspect the following batch file: @echo off @echo %0 :loop @echo %1 shift if not %1 == goto loop @echo finished with arguments

Re: [Freedos-devel] Difference between command.com and frecom.com when parsing command line arguments of a batch file.

2014-07-18 Thread Juan Manuel Guerrero
Am 18.07.2014 22:30, schrieb Rugxulo: Hi, On Fri, Jul 18, 2014 at 2:00 PM, Juan Manuel Guerrero juan.guerr...@gmx.de wrote: I do not know if this is the right place to report this FreCom issue Dunno, not sure it's actively maintained by anyone anymore. I feared this. I do not know