bug-wget
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: wget-1.21.3-win32/64


From: WQ
Subject: Re: wget-1.21.3-win32/64
Date: Tue, 31 May 2022 16:11:46 +0200
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1

To be 100% sure I retested it with wget

32bit :


64bit :


So we know it's not 32/64 related


On 31/05/2022 15:12, gerdd@mweb.co.za wrote:
@WQ,

now that's impressive!

I still wonder how that came about,though ...


@Tim,

as soon a I have a moment I will take that exe and try it out with my use cases and any new options that might be useful to me.

Anything interesting, I'll let you know.

Gerd

------------------------------------------------------------------------
*From: *"WQ" <wquatan@belgacom.net>
*To: *"Tim Ruehsen" <tim.ruehsen@gmx.de>, gerdd@mweb.co.za
*Cc: *"bug-wget" <bug-wget@gnu.org>, "darnir" <darnir@gnu.org>
*Sent: *Tuesday, May 31, 2022 2:35:41 PM
*Subject: *Re: wget-1.21.3-win32/64

Hi,

I just tested the wget2 executable on my Win10 with exactly the same command : *wget2.exe -O TargetPath\TargetFile http://source*

And now it's working everywhere, *even on the Netgear* !!!!



As you can see, I now get the original DateTme-stamp under all circmstances.
So that's great news, and will start to use wget2 from now on.

But, to be clear, I did not do any other tests, so I can't tell if all wget2 functionality is working properly.

Thanks for having informed about the exe !

Kind regards

Walter

On 31/05/2022 12:54, Tim Rühsen wrote:

    On 30.05.22 14:57, WQ wrote:

        Hi,

        Thank you for having replied anyway !

        The testing I did was always with the same server and file. So
        I'm 100% sure about the results (different behaviour on the
        Netgear)
        When I wrote "path/file" then I did mean something like
        F:\Download\thefile.txt
        I know the documented -O feature, but it remains unclear why
        the original datetime works locally and on the Thecus, even if
        it should not (as documented)
        When a local wget (with/without -O) is done followed by a move
        to the Netgear, the time-stamp is ok, I tested that before
        too. But I'm trying to avoid the move as this involves extra
        time, especially with giga-files.
        Yes, a real renaming mechanism, is a missing option.

        I didn't know about wget2, but it seems there are no compiled
        versions available.


    With the latest release of wget2 (v2.0.1), there is a .exe version
    available. It doesn't have all features yet, but hopefully works.
    I can only test it with a Windows emulation (wine) on Linux.

    Go to the bottom at https://gitlab.com/gnuwget/wget2/-/tags/v2.0.1

    Regards, Tim






reply via email to

[Prev in Thread] Current Thread [Next in Thread]