Trying to get 7zip to run from a command line, I can sub that in the setup.
7zip used as
7z e nodelist.z08
results in
Nodelist.108 (0 bytes)
Isn't that enough to drive you dippy.
7z e nodelist.z08
results in
Nodelist.108 (0 bytes)
Isn't that enough to drive you dippy.
7zip used as
7z e nodelist.z08
results in
Nodelist.108 (0 bytes)
Isn't that enough to drive you dippy.
Hello Alan,
7z e nodelist.z08
results in
Nodelist.108 (0 bytes)
Isn't that enough to drive you dippy.
Doesn't the Windows file manager support zip natively?
But zip and unzip from the command line should be easy to use (I think).
Ttyl :-), Al
-+- GoldED+/LNX
@ ORIGINAL: The Rusty MailBox - Penticton, BC Canada (1:153/757)
The second I intstalled a trial of winzip my system was hijacked by
it.
Hi Alan,
On 2020-04-23 07:40:47, you wrote to Alan Ianson:
The second I intstalled a trial of winzip my system was hijacked by it.
What do you mean by 'hijacked'?
Bye, Wilfred.
-+- FMail-lnx64 2.1.0.18-B20170815
@ ORIGINAL: FMail development HQ (2:280/464)
I get about the same weird result as August:
===
d:\com\inbound>"c:\Program Files\7-Zip\7z.exe" e NODELIST.Z08
But afterwards there is a correct unpacked NODELIST.108 file.
When I rename the NODELIST.Z08 to NODELIST.ZIP, it unpacks without complaining:
So it seems 7z gets confused by the .Z08 extension. It probably thinks it's file 8 in a multiple file archive...
Alan Beck wrote to all <=-
Nodelist.108 (0 bytes)
Isn't that enough to drive you dippy.
Sysop: | Coz |
---|---|
Location: | Anoka, MN |
Users: | 2 |
Nodes: | 4 (0 / 4) |
Uptime: | 140:28:33 |
Calls: | 328 |
Files: | 5,823 |
Messages: | 228,086 |