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" <t...@drivesnapshot.de>
To: "Technical discussion and questions for FreeDOS developers." <freedos-devel@lists.sourceforge.net>
Subject: Re: [Freedos-devel] FreeDOS 1.3-RC5
From: "tom ehlert" <t...@drivesnapshot.de>
To: "Technical discussion and questions for FreeDOS developers." <freedos-devel@lists.sourceforge.net>
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
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
