Freonpsandoz

Any chance of ever getting a fix? Or at least a UTC time value with the -slt option?

So, it doesn't really work on 64-bit Windows without a huge amount of special setup. Nobody installs both 32 and 64 bit versions of python, Perl, etc. so only VBscript is actually possible. Not ready for prime time.

Not ready for prime time.

The modification times displayed by the 7z 'l' command for files stored in .wv archives (in ISO format, I believe) change according to whether DST is currently in effect. This is inconsistent with the display for files stored in .rar or .zip archives, which show the same modification times no matter when 7z is run. I haven't checked whether this also happens with .iso files or not. I don't know whether this is a result of options used when the archive was created.

The modification times displayed by the 7z 'l' command for files stored in .wv archives (in ISO format, I believe) change according to whether DST is currently in effect. This is inconsistent with the display for files stored in .rar or .zip archives, which show the same modification times no matter when 7z is run. I haven't checked whether this also happens with .iso files or not.

It took me awhile to figure this out: I was clicking and shift-clicking on the checkboxes instead of the names. A short set of notes would help.

I can't get Keepass2 to open on XUbuntu Desktop in an RDP session from Windows 10. If I run it from the terminal, no error message is displayed. Keepass2 runs normally from a normal login on XUbuntu Desktop. Any ideas? Thanks.

Any chance of a fix? Or is there a workaround? This problem affects most recent torrent files.