324 replies to this topic

[dera]

Pleas post the .reg lines which cause the hex(3) to output!

as jaclaz wrote
when the registry changes captured by regshot
with that version which made by Paraglider
and in its output (~res.txt) the 'UseRegFormat=1' used
then in that ~res.txt every REG_BINARY value is written as
"value"=hex(3):F2,54,2D,
instead of
"value"=hex:F2,54,2D,

edit:
e.g.

REGEDIT4[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\RNG]"Seed"=hex(3):F2,54,2D,77,10,AF,C8,D6,95,20,0A,B5,3F,52,14,85,C9,99,A6,64,E1,9C,\  C1,BE,B3,AE,71,7E,67,86,F0,09,F0,D3,BC,27,F3,B8,A4,E5,CF,FA,87,55,11,F9,59,6A,\  1D,2A,EA,95,DC,A2,A2,ED,02,40,0D,A2,36,29,5F,2E,6A,C0,BD,A8,4E,BB,E0,D8,61,1A,\  9B,FD,1D,8D,C8,11[HKEY_USERS\S-1-5-21-1844237615-527237240-1801674531-1003\Control Panel\Desktop]"UserPreferencesMask"=hex(3):9E,3E,07,80

[was_jaclaz]

Just for the record, yesterday evening i was pretty p#$%§& because the program was disturbing my circles.

Really?
We didn't noticed that.

It seems to be a reg2WBScript bug and I'm going to look for that.

Waiter taste this soup....
http://www.imdb.com/...98/crazycredits

Aha. Aha! ...



jaclaz

[pscEx]

Version 3.1.1 on the server.

It processes also Paraglider's special hex(3):

Peter

[Lancelot]

Hi Peter,

no bug report,
REMOVED

Edit:
Thinking again, I removed this post, such a fix may cause other reg2wbs abilities malfunction.

[pscEx]

I have the original in my e-mail

Peter

[was_jaclaz]

Version 3.1.1 on the server.

It processes also Paraglider's special hex(3):

Peter

Is it also possible to know WHAT is hex(3) or it has to remain a secret between you and paraglider?

What about item #2 (dropped line)?

What about item #3?



jaclaz

[pscEx]

Is it also possible to know WHAT is hex(3) or it has to remain a secret between you and paraglider?

No secret:

Depening on (I do not know, and that really is a secret of Billy the door) some situations, in an exported *.reg file values are sometimes decribed by a sequence of hex values.

If the reg key is different from 0x3 (REG_BINARY) the code is preceeded by a 'hex' and in parentheses the type's ord number, e.g, hex(07):
In case of type REG_BINARY Billy theDoor writes only hex:
And Paraglider (my knowledge from some users' posts) in this case writes 'hex(3):' (what is logically correct)

Because until now, the (3) possibility has not been known and therefore not been coded in reg2WBS, the issue occurred.
And as you can see above, the issue is already fixed.

Peter

[Lancelot]

Hi Peter,

I have the original in my e-mail

I know, I only officially* removed my request , I know you are busy with new wim tool and hopefully chasing the with wb078sp4

What's wrong, psc not in the mood to play that you wanna pick a fight with me?

@Lancelot, I agree: To fight with me is really

• More exciting
• More interesting
• Bringing more new ideas
• Is usually more understandable
  Why in this topic at least 3 introducing posts of MedEvil are necessary, which all have been replied separately by me (and watched and commented by Jaclaz), when this in my opinion would have been possible / understandable / sufficient by posting:
  

  Possible bug:
  Input
  

  blabla,...,hex(3),...

  brings result
  

  0x3,...

  rather than the expected
  

  reg_add,0x3,...

Maybe I find some stuff due to new LiveXP server organisation for the next boxing. To some solutions you made I cannot agree on the first view ...
But they are very low importance, therefore maybe I postpone the next boxing start to 'when there are no other interesting topics'.

Peter

To have a "boxing" there is a goal of "good to better" to me, boxing for boxing does not give taste . That is the reason boxing* with you is good.

I have to admit, dera has verrry stronger punchs than me

when we have boxing with you, I agree everything you write. When we do things other than boxing, it is not good. Lets Keep boxing
"very low importance"
"I postpone the next boxing start to 'when there are no other interesting topics'."
Reminding there are pending boxing waiting you to be less busy

Since jaclaz do not obey some rules of boxing (1 on 1) , I guess the game name here is "American Gladiators",

Is it also possible to know WHAT is hex(3) or it has to remain a secret between you and paraglider?

What about item #2 (dropped line)?

What about item #3?



jaclaz

item #2
Line do not drop here, (tested with v3.03 , v3.10 , v3.11) , does it drop there ??

item #3
Works as intended, depends on the selected options,
for

[HKEY_CLASSES_ROOT\.]
@="C:\Windows\medevil.exe"

one can get
==>
RegWrite,HKLM,0x1,WB-Software\Classes\.,,"C:\Windows\medevil.exe"
reg_add,0x1,%reg%\Classes\.,,"C:\Windows\medevil.exe"
reg_add,0x2,%reg%\Classes\.,,"#$pSystemRoot#$p\medevil.exe"
reg_add,0x2,%reg%\Classes\.,,"#$pSystemRoot#$p\%ProgramEXE%"
...
...
...
.......

[was_jaclaz]

No secret:

Depening on (I do not know, and that really is a secret of Billy the door) some situations, in an exported *.reg file values are sometimes decribed by a sequence of hex values.

If the reg key is different from 0x3 (binary) the code is preceeded by a 'hex' and in parentheses the type, e.g, hex(07):
In case of type binary Billy theDoor writes only hex:
And Paraglider (my knowledge from some users' posts) writes hex(3):

Because until now, the (3) possibility has not been known and therefore not been coded in reg2WBS, the issue occurred.

Peter

So, if I am not mistaken, we should ask paraglider WHY this strange value is created, in other words the "fix" in your app introduces a new pseudo-bug: "unknown/unstandard hex(3): values" are treated as "hex".

As I see it this is allright if it's documented, but nonetheless there are two possibilities:

• the app by TianWei/paraglider is bugged (and should be fixed)
• there is actually a reason for this behaviour

What does the newer Regshot Unicode 2.0x do?

Should we "abandon" both TianWei's an Paraglider's versions to "adopt" and advise version 2.0x?:
http://translate.goo...t...it&ie=UTF-8


And what about the other 2 items?

Really, it is not difficult , three questions were asked, cleverly numbered #1, #2 and #3.
You are perfectly free, since you have replied to #1, to state:

I am not going to reply to #2, as I claim the priviledge of the fifth amendment ....
I am not going to reply to #3, as I claim the priviledge of the fifth amendment ....

(or whatever reason you may think fit)

but three questions call for three replies.



jaclaz

[pscEx]

So, if I am not mistaken, we should ask paraglider WHY this strange value is created, in other words the "fix" in your app introduces a new pseudo-bug: "unknown/unstandard hex(3): values" are treated as "hex".

I think that we should not discuss the 'why' or 'how'
In this case the issue is solved by an 'Understand the BACKGROUND'
And I do not find very interestig to discuss solved issues.

@question #2
Currently in reg2WBS I do not see any sence to write an empty key into registry.
BTW: WinBuilder does if you write the command to do so!
If somebody gives a sample where an empty key is really needed, I'll add the logic to reg2WBS.

@question #3
There are several reg2WBS options (startup parameters) to define different behaviours.
If a particular user's option cannot be solved with the provided switches, please let me know.

Peter

[MedEvil]

@question #2
Currently in reg2WBS I do not see any sence to write an empty key into registry.
BTW: WinBuilder does!
If somebody gives an sample, where an empty key is really used, I'll add it to reg2WBS.

HKLM\System\Setup\AllowStart\psc
When omitted, psc will not start.

[Lancelot]

Here reg2WBS converts

Windows Registry Editor Version 5.00

[HKEY_USERS\.DEFAULT\Software\Connectix]

[HKEY_USERS\.DEFAULT\Software\Connectix\Virtual PC]

[HKEY_USERS\.DEFAULT\Software\Connectix\Virtual PC\4.0]

to

RegHiveLoad,"WB-Default","%target_sys%\config\default"
RegWrite,HKLM,0x0,WB-Default\Software\Connectix
RegWrite,HKLM,0x0,"WB-Default\Software\Connectix\Virtual PC"
RegWrite,HKLM,0x0,"WB-Default\Software\Connectix\Virtual PC\4.0"
RegHiveUnLoad,"WB-Default"

what is the problem/issue/question ??????

[was_jaclaz]

Hey, Medevil, pssss .....Lancelot is saying you are a liar:

item #2
Line do not drop here, (tested with v3.03 , v3.10 , v3.11) , does it drop there ??

jaclaz

[pscEx]

Let me give some enumerations

• As posted 'anywhere' reg2WBS usually (exceptions are not a topic here) does not write empty keys into registry
• As posted 'anywhere' I do not intend to change that behaviour
• If a script needs to write an empty key into registry: The script MUST do so.
  If you do create your script w/o using reg2WBS, how do you write keys into registry????

If somebody wants to help to make reg2WBS more 'intelligent': please PM me.

[online]

I can confirm that all "reg2WBS" tested versions (3.0.2, 3.1.0 and 3.1.1) correctly translate here the previously reported registry entries

Windows Registry Editor Version 5.00



[HKEY_USERS\.DEFAULT\Software\Connectix]



[HKEY_USERS\.DEFAULT\Software\Connectix\Virtual PC]



[HKEY_USERS\.DEFAULT\Software\Connectix\Virtual PC\4.0]

in these ones

Hive_Load,Default

reg_add,0x0,%reg%\Software\Connectix

reg_add,0x0,"%reg%\Software\Connectix\Virtual PC"

reg_add,0x0,"%reg%\Software\Connectix\Virtual PC\4.0"

Hive_Unload,Default

or

RegHiveLoad,"WB-Default","%target_sys%\config\default"

RegWrite,HKLM,0x0,WB-Default\Software\Connectix

RegWrite,HKLM,0x0,"WB-Default\Software\Connectix\Virtual PC"

RegWrite,HKLM,0x0,"WB-Default\Software\Connectix\Virtual PC\4.0"

RegHiveUnLoad,"WB-Default"

So, the presumed bug seems only a mis-reporting.

Many thanks to psc for updates.

[Lancelot]

Hi Peter,

bugy report for the record (when you have time):

REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\7-Zip.7z\DefaultIcon]
@="C:\\Program Files\\7-Zip\\7z.dll,0"

==>

Hive_Load,Software
RegAddBoot,0x1,%reg%\Classes\7-Zip.7z\DefaultIcon,,"#$pSystemDrive#$p\Program#$sFiles\7-Zip\7z.dll#$c0"
Hive_Unload,Software

It should be

RegAddBoot,HKLM,0x1,Software\Classes\7-Zip.7z\DefaultIcon,,"#$pSystemDrive#$p\Program#$sFiles\7-Zip\7z.dll#$c0"

[dera]

Lancelot is right

i think the meaning of the 'RegAddBoot' command is the chance to use the variable '%PE_Programs%'
i mean to replace 'C:\Program Files' with '%PE_Programs%'

Edited by dera, 18 November 2009 - 08:27 AM.

[pscEx]

RegAddBoot line changed.

Version 3.1.2

Peter

[Lancelot]

Thanks Peter,
@dera

Lancelot is right

i think the meaning of the 'RegAddBoot' command is the chance to use the variable '%PE_Programs%'
i mean to replace 'C:\Program Files' with '%PE_Programs%'

I just simplified the bugy report
http://img696.images...6/7260/1564.gif

Besides, here we have another problem, since you know other pe2-pe3 projects better maybe you might have an idea (a fix for them !) so we won't need regaddboot much. Or maybe you can explain or give an idea to us to see the big picture.

[pscEx]

The latest version still has a bug.

It outputs %reg% which in this case is "WB_Software" rather than "Software".

I'm working on this, but is a bit difficult, because in the very beginning of reg2WBs the 'Local' reg keys are exchanged to the "Mounted" PE reg keys.

Peter

[Lancelot]

and not a bug, but a minor request
when "Replace Environment strings" selected, can you change relevant
RegAddBoot,HKLM,0x1
to
RegAddBoot,HKLM,0x2

this helps only to see if 0x1 is truly needed during tests and also might help for the future improvements on regaddboot

[online]

@psc
Making a video-driver script I found a couple of entries with "hex(a)" and "hex(8)" [REG_RESOURCE_LIST and REG_RESOURCE_REQUIREMENTS_LIST values http://pubs.logicale...icle.asp?ID=361] as following (simplified):

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\PCI\. . .\Control]

"FilteredConfigVector"=hex(a):c8,01,. . .

"AllocConfig"=hex(8):01,00,. . .

that are "translated" in the following

reg_add,0x1,%reg%\ControlSet001\. . .\Control,FilteredConfigVector,hex(a):c8#$c01#$c. . .

reg_add,0x1,%reg%\ControlSet001\\. . .\Control,AllocConfig,hex(8):01#$c00#$c. . .

Those entries types seem quite rare and furthermore they do not seem to be strictly needed in order to work the script, but...

[pscEx]

I currently do not even know what hex(a) and hex(8) mean

I'm going to google ...

Peter

[online]

I currently do not even know what hex(a) and hex(8) mean

I'm going to google ...

Peter

Please, note that I already provided a link...

http://pubs.logicale...icle.asp?ID=361

[online]

and not a bug, but a minor request
when "Replace Environment strings" selected, can you change relevant
RegAddBoot,HKLM,0x1
to
RegAddBoot,HKLM,0x2

this helps only to see if 0x1 is truly needed during tests and also might help for the future improvements on regaddboot

@Lancelot
Sorry if maybe I'm wrong, but I do not agree.
Frankly, it seems to me an unneeded forcing... most of all considering that someone can easily replace what he wants/needs with a good text editor.
I "see" a good tool as a "default" tool with default (not too forced) functions/translations, so I would prefer the default/correct/original one...
I've performed so few tests, but it seems to me that the "0x2" (REG_EXPAND_SZ ) string type "forcing" could work in some circumstances with "simple" program/script, but then in other ones (that's with more complex programs/circumstances or driver script) it does not seem to work...

Please, see here too http://www.boot-land...?...ost&p=85286