Thx, this is great. If you could come in contact with Bernd and combine it with all his already existing bugfixes this would be VERY great.
And if you remember my bug report with config.sys menudefault (see: https://gitlab.com/FreeDOS/OS/fd-nls/-/issues/3) - I assume it is also a kenrel probllem - it would be NON PLUS ULTRA. This would really be a very good basis for the next kernel.
I am aware that this cannot be done in one day.
Willi
Sent: Thursday, March 27, 2025 at 5:56 PM
From: "tom ehlert via Freedos-devel" <freedos-devel@lists.sourceforge.net>
To: "Technical discussion and questions for FreeDOS developers." <freedos-devel@lists.sourceforge.net>
Cc: "tom ehlert" <t...@drivesnapshot.de>
Subject: Re: [Freedos-devel] Re: release MOVE 3.4 WAS: Re: XCOPY 1.7 Stack Overflow
From: "tom ehlert via Freedos-devel" <freedos-devel@lists.sourceforge.net>
To: "Technical discussion and questions for FreeDOS developers." <freedos-devel@lists.sourceforge.net>
Cc: "tom ehlert" <t...@drivesnapshot.de>
Subject: Re: [Freedos-devel] Re: release MOVE 3.4 WAS: Re: XCOPY 1.7 Stack Overflow
Hallo Herr Fritz Mueller via Freedos-devel,
am Donnerstag, 27. März 2025 um 17:51 schrieben Sie:
> thanks, I already tested it, also works fine. so only the copy command is over for the moment, but I will have to test if it is already fixed or not (i already reported anywhere at git that 3 files with 1,6 gb and copy a +b +c 4 gb creates a 4gb file where the rest of file c is written to the beginning of a on the 4gb file). but this is a thing that should rarely happen and can be fixed with the next kernel/command.com.
it's a kernel bug.
I will post a fix tomorrow.
Tom
> Willi
>> Sent: Thursday, March 27, 2025 at 3:48 PM
>> From: "perditionc--- via Freedos-devel" <freedos-devel@lists.sourceforge.net>
>> To: "Technical discussion and questions for FreeDOS developers." <freedos-devel@lists.sourceforge.net>
>> Cc: perditi...@gmail.com
>> Subject: Re: [Freedos-devel] Re: release MOVE 3.4 WAS: Re: XCOPY 1.7 Stack Overflow
>>
>> On Wed, Mar 26, 2025, 5:09 PM <perditi...@gmail.com> wrote:
>>
>> > On Tue, Mar 25, 2025 at 5:09 PM Wilhelm Spiegl <wilhelm.spi...@mail.com>
>> > wrote:
>> > >
>> > > Hi,
>> > > thanks, move works fine now.
>> > > But what about xcopy which reports the same bug?
>> > >
>> > > --
>> >
>> > Had time to apply an update, see:
>> > https://github.com/FDOS/xcopy/
>> > https://github.com/FDOS/xcopy/releases/download/v1.9/xcopy19.zip
>> >
>> > Jeremy
>> >
>> _______________________________________________
>> 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
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
am Donnerstag, 27. März 2025 um 17:51 schrieben Sie:
> thanks, I already tested it, also works fine. so only the copy command is over for the moment, but I will have to test if it is already fixed or not (i already reported anywhere at git that 3 files with 1,6 gb and copy a +b +c 4 gb creates a 4gb file where the rest of file c is written to the beginning of a on the 4gb file). but this is a thing that should rarely happen and can be fixed with the next kernel/command.com.
it's a kernel bug.
I will post a fix tomorrow.
Tom
> Willi
>> Sent: Thursday, March 27, 2025 at 3:48 PM
>> From: "perditionc--- via Freedos-devel" <freedos-devel@lists.sourceforge.net>
>> To: "Technical discussion and questions for FreeDOS developers." <freedos-devel@lists.sourceforge.net>
>> Cc: perditi...@gmail.com
>> Subject: Re: [Freedos-devel] Re: release MOVE 3.4 WAS: Re: XCOPY 1.7 Stack Overflow
>>
>> On Wed, Mar 26, 2025, 5:09 PM <perditi...@gmail.com> wrote:
>>
>> > On Tue, Mar 25, 2025 at 5:09 PM Wilhelm Spiegl <wilhelm.spi...@mail.com>
>> > wrote:
>> > >
>> > > Hi,
>> > > thanks, move works fine now.
>> > > But what about xcopy which reports the same bug?
>> > >
>> > > --
>> >
>> > Had time to apply an update, see:
>> > https://github.com/FDOS/xcopy/
>> > https://github.com/FDOS/xcopy/releases/download/v1.9/xcopy19.zip
>> >
>> > Jeremy
>> >
>> _______________________________________________
>> 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
_______________________________________________
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
