@Auric__: Sorry for the late answer! I had some heavy days, last week. (And sorry for my English! It's getting worse and "worser" with every decade since leaving school.)
"Auric__" <***@email.address> wrote in message news:***@88.198.244.100...
| Acamas wrote:
|
| > You mean the developers of WinRAR <...>
|
| Yes. (Although ISTR one of them died several years ago.)
Oh! :(
|
| <...>
|
| A few minutes of experimenting would have given you the answers you wanted.
That's exactly why I think I should NOT start with the developer(s). Presumably, I'd be given a similar answer, maybe something like "RTFM, PLZ".
Of course, you're right -- theoretically. ;)
Practically, there are about 62 values in each of more than 20 chaotic profiles (at this machine), behind more than half a dozen nested GUI dialogues of a program I didn't use for years, to be honest... :(
Sure, I tried to figure out the meaning of most of the values, and I've got it, for all except the last 15 values.
Anyway, trial and error with a black box isn't that easy when you have *different methods* inside the black box.
Example:
The *ONE* variable $Method (compression strength) has six values, 0 - 5, for 6 elements of *ONE* respective GUI drop-down list.
One list (6 elements) --> one variable (6 options)
Sounds quite simple. However, for the four elements of the *one* drop-down list "path-inclusion type" (or something), there are (btw: only *3*) different 1-bit variables: $PathAbs, $PathNone, and $PathAbsDrive, i.e.:
one list (4 elements) --> three variables (3 x 1 bit)
What if I check ALL of them (set them ALL to "1") at the same time? $PathAbs=one + $PathNone=one --> $PathAbsNone? There must be any priority?
Furthermore, the value of $default is "0" for ALL profiles */INCLUDING/* the standard profile. So this value is, maybe, a SWITCH rather than a constant, i.e. it seems to be set temporarily only, just to CHANGE the standard profile. It's a possibility, at least.
Also, regarding "a few minutes": after several hours, I've got tired and unconcentrated. Hence, I read the "ArcRecBin" as "archive RECOVERY binary" and looked around in the GUI for a recovery-related switch or check box. I just didn't come to "recycle" instead of "recovery".
To make a long story short, it isn't that easy as is seems to be, unfortunately.
Hence, I'm very happy to find some help -- without having to bother Russian academics.
|
| That fact that you're poking around in the registry puts you outside of
| "common".
Yes, some call me that way: "beyond common". ;-)
In the following lines, I just leave some comments to your answers. You don't have to answer it again. It's just a kind of feedback, asking some questions to myself. However, any reply will be appreciated, of course!
| ______________________________________________________________________
|
| > ArcRecBin
|
| Delete mode. 0 = Delete files, 1 = Move to Recycle Bin.
I was too blind to read "rec" as recycle instead of "recover" -- sorry!
|
| > ArcWipe
|
| Delete mode. 0 = use the value of the ArcRecBin key, 1 = Wipe files.
Now, in combination with $ArcRecBin it makes sense. Thanks for the hint!
|
| > AV
|
| Put authenticity verification. 0 = no, 1 = yes.
Oh, man! I have to clean my crystal ball! I'd never have find out this.
|
| > CmtDataWide
|
| I'm using version 3.93 and don't have that regkey, and I don't see anything
| that it would match in the settings dialogs, so I'm going to guess it's
| something added in v4. (Use Unicode, perhaps? No clue.)
No idea, too. (You're right; I'm using v4.01, currently.)
|
| > CmtFile
|
| Comment filename.
Sure. However, in the GUI I can't find any option to use a file as comment. Maybe, it's a console option only. On the other hand, does it automatically create an internal file for comments? However, why should be stored in the registry instead of the archive itself? It doesn't make sense. :-/
|
| > Default
|
| Is this profile the default profile? 0 = no, 1 = yes.
See above: In ALL profiles, including standard profile, $Default is zero. :-/
|
| > DictSizeLZ
|
| General compression Dictionary size. Should be set to a whole power of 2
| between 0x10000 and 0x400000. (In hexadecimal, should be 1, 2, 4, or 8,
| followed by 4-6 zeros.)
I see. Just wonder, if there's any field for this value in the GUI. I can't find it. Anyway, it's good to know it can be changed directly in the registry.
Btw.: Does it make sense to set it to a different value than one or more whole cluster of the storage medium? Is it read from storage medium directly (separately), or from RAM, after expanding ALL the header/meta/dictionary data of the archive file to RAM?
|
| > EncryptHeaders
|
| Equivalent to the "Encrypt file names" setting.
OK, they mean "file names" when saying "headers". Just wasn't sure. Thanks!
|
| > Fresh
|
| Update mode: 0 = use the value of the Update key, 1 = Fresh existing files
| only.
I see. I wasn't sure with this too. I didn't use the "Fresh" option so far. In my GUI, it's called "Update existing files only", so I was a little bit confused with the other $update value.
|
| > RecVolNumber
|
| Number of recovery volumes to generate.
Sorry for having asked this. It's been quite clear, already. Sorry!
|
| > SFXElevate
|
| Should self-extracting archives request admin privileges? 0 = no, 1 = yes.
That makes sense. OK. Thanks!
|
| > SFXIcon
|
| Icon used for self-extracting archives. Must be the full path to an
| existing icon file.
Ah, now I understand. I thought: Why specifying a path to an archive-file-related icon file when the icon has to be included within the archive-file anyway (and not within profile settings)? However, they mean the path to where the icon file shall be taken from for packing process. No that makes sense, of course.
|
| > SFXLogo
|
| Logo used for self-extracting archives. Must be the full path to an
| existing bitmap file.
Same as with $SFXLogo
|
| > SFXModule
|
| What self-extracting module should be used. "*" = use the default sfx file
| (default.sfx), otherwise must be the full path to an existing .sfx file,
| preferably one that understands the RAR format.
Same as with $SFXLogo
|
| > VersionControl
|
| Keep previous file versions. 0 = no, 1 = yes.
I see. I wasn't sure with this too. Now I know it. Thanks!
Anyway, thank you very much for