Hi Tom,
> On Mar 21, 2025, at 9:36 AM, tom ehlert via Freedos-devel
> wrote:
>
> Hallo Herr Jerome Shidel via Freedos-devel,
>
> am Freitag, 21. März 2025 um 14:14 schrieben Sie:
>
>
>> Hi Eric,
>
>>> On Mar 21, 2025, at 6:03 AM, Eric Auer via Freedos-devel
>>> wrote:
>>>
>>>
>>> Hi! J
Hi Bernd,
am Freitag, 21. März 2025 um 15:05 schrieben Sie:
> The index.md [1] of the repo indicates that the XCOPY 1.7 binary is built
> with Open Watcom.
> There reportedly was an issue [2] regarding stack usage with the Open Watcom
> built binaries.
> Skimming over the source, especially [
Minor update 1.8a (last one for a while)
https://github.com/FDOS/xcopy
https://github.com/FDOS/xcopy/releases/download/v1.8a/xcopy18a.zip
Further reduce stack usage on recursive xcopy. Using Tom's example
C:\1\2\3\...\d\e\f\... a quick test worked for as deep as FreeCom
allowed to create a nested
Hi Eric,
> On Mar 21, 2025, at 6:03 AM, Eric Auer via Freedos-devel
> wrote:
>
>
> Hi! Just guessing, but...
>
> Maybe xcopy recursively copies directories? Have you tried to trigger
> the bug using a small set of files in a deep directory tree?
>
> Eric
Although there are a lot of files
> There reportedly was an issue [2] regarding stack usage with the Open Watcom
> built binaries.
> Skimming over the source, especially [3], indicates that this may use A LOT of
> stack space depending on what value MAXPATH is defined to be (it is 260 for my
> Open Watcom installation). That is ap
> On Mar 21, 2025, at 10:40 AM, tom ehlert via Freedos-devel
> wrote:
>
> Hi Bernd,
>
> am Freitag, 21. März 2025 um 15:05 schrieben Sie:
>
>> The index.md [1] of the repo indicates that the XCOPY 1.7 binary is built
>> with Open Watcom.
>
>> There reportedly was an issue [2] regarding sta
Hi! Just guessing, but...
Maybe xcopy recursively copies directories? Have you tried to trigger
the bug using a small set of files in a deep directory tree?
Eric
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sou
On Fri, Mar 21, 2025 at 2:30 PM Bernd Böckmann via Freedos-devel
wrote:
>
> While testing v1.7, I noticed that XCOPY creates a directory hierarchy at the
> target when called with parameter -L.
>
> Is this intended behavior? According to the usage info, -L means: „List files
> without copying th
While testing v1.7, I noticed that XCOPY creates a directory hierarchy at the
target when called with parameter -L.
Is this intended behavior? According to the usage info, -L means: „List files
without copying them. (simulates copying).“ So I would expect the file system
not being altered at al
Hallo Herr Jerome Shidel via Freedos-devel,
am Freitag, 21. März 2025 um 14:14 schrieben Sie:
> Hi Eric,
>> On Mar 21, 2025, at 6:03 AM, Eric Auer via Freedos-devel
>> wrote:
>>
>>
>> Hi! Just guessing, but...
>>
>> Maybe xcopy recursively copies directories? Have you tried to trigger
>>
Hallo Herr Jerome Shidel via Freedos-devel,
am Freitag, 21. März 2025 um 17:12 schrieben Sie:
> I was just sent a test build of xcopy with an increased stack size.
> The Stack Overflow did not occur on the existing filesystem during the copy.
> After adding some deeper sub-directory nesting, t
XCOPY Version 1.8 published
https://github.com/FDOS/xcopy/releases/download/v1.8/xcopy18.zip
It implements two changes to reduce stack overflows - it does not
eliminate it as that would require further review of other stack
variables used. The overall stack size increased slightly and the
reducti
I was just sent a test build of xcopy with an increased stack size.
The Stack Overflow did not occur on the existing filesystem during the copy.
After adding some deeper sub-directory nesting, the Overflow returned at that
point in the copy.
So, the increased stack size improved the problem.
just fixed this so that it is correct. Update enclosed.
Could you please check if this helps?
Willi
Sent: Friday, March 21, 2025 at 4:11 PM
From: "Jerome Shidel via Freedos-devel"
To: "FreeDOS Developers"
Cc: jer...@shidel.net
Subject: Re: [Freedos-devel] XCOP
The index.md [1] of the repo indicates that the XCOPY 1.7 binary is built with
Open Watcom.
There reportedly was an issue [2] regarding stack usage with the Open Watcom
built binaries.
Skimming over the source, especially [3], indicates that this may use A LOT of
stack space depending on what
Hi All,
While preparing to upgrade my Netbook from from 1.3 to 1.4rc3+ (slightly newer
OS build than RC3, possibly to be 1.4GM released on 4/1), I ran into a couple
issues.
The intent for this machine was keep all of its customizations. Me being well
aware of all of the differences between 1.3
16 matches
Mail list logo
