Re: wget-1.21.3-win32/64

[WQ]

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