242 replies to this topic

[MedEvil]

Just for fun.

Missed to report the first BSOD by a hair or two.
NaughtyPE with trash from this afternoon is very user friendly. Someone simplified all programs by stealing a whole bunch of buttons.

[Lancelot]

Just to explain things easier (which I feel mixed some minds)

"Initial Registry Values" created by RegEdit is following:
"1"=""
"3"=hex:
"2"=hex(2):00,00
"4"=dword:00000000
"7"=hex(7):00,00

"Empty Registry Values" that are available for Registry are:
"1"=""
"3"=hex:
"2"=hex(2):
"4" NOT POSSIBLE
"7"=hex(7):


SPECIAL RULES:
There is only special rules for 0x2 and 0x7 (Reg_Expand_SZ and Reg_Multi_SZ)

Reg_Multi_SZ
If there is value insides, It must end with 5 00
,00,00,00,00,00
hidden values and other tricks are not practical because regedit forces fixing them.
Above rules for Reg_Multi_SZ only valid if string used for 0x7 by winbuilder.

On the other hand everything possible for some special tasks (god knows what an application do, maybe one decides to write binary data to 0x7 for serial information knowing it will be fixed (hihi) by regedit when one tries to look to data by using regedit, a nice trick isn't it )

Reg_Expand_SZ
If there is value inside, It must end with 3 00
,00,00,00

more:
Reg_Expand SZ can have multistring and interestingly regedit have no objection to that.
On the other hand, you see only 1st string on regedit windows, others are hidden behind....
(You can smell things from here )
Everything is more possible for special tasks with Reg_Expand SZ......


Winbuilder
above schema (empty and initial value creations) is now appliable with wb078,
besides there is confusion with winbuilder development.

I do not know wb codes, guessing here are examples:
Reg_Binary (I guess from Medevil report):
In the past when script trying to write the value
wb first was creating Empty Reg_Binary data with 00 (wrong, in fact wb was creating with putting 00), than prepending the datas of the script
as a result
RegWrite,HKCU,0x3,Software\0TEST,3Comma,12,34
was ending with the value
12,34,00
This was wrong, but did not hurt anyone. Well now winbuilder creates empty value and all correct

Reg_Multi_SZ:
In the past when script tries to write a string with 0x7
wb first was creating Empty Reg_Multi_SZ data with 00,00 (wrong, in fact wb was creating 0x7 with initial data) than prepending the datas of the script by adding 00,00,00 to the end.
as a result we get 00,00,00,00,00 in the end

Today when script tries to write a string with 0x7
wb first creating Empty Reg_Multi_SZ data results with nothing, than prepending the datas of the script by adding 00,00,00 to the end.
as a result we get 00,00,00 in the end which is wrong.

With current more correct winbuilder, now it should be one of the following way:
wb first creating Empty Reg_Multi_SZ data results with nothing, than prepending the datas of the script by adding 00,00,00,00,00 to the end.
OR
wb first creating Initial Reg_Multi_SZ data results with 00,00, than prepending the datas of the script by adding 00,00,00 to the end.


wb development should be clearly knowing Empty and Initial differences in order not to cause troubles in future.
Past mistakes was based on wrong (or bugy) bases. 0x7 issue arise because this wrong base fixed but things depending on wrong base was not.
(like wb+hojope relation i wrote previously, in the past bugy wb+bugy hojope = correct, now only bugy hojope=false.
in the past bugy wb base + functions made with bugy base=correct , now only functions with bugy base = false)

[pscEx]

The impair number of byte is wrong.

The first byte of them belongs to the last character in 0x2 and 0x7.

In case of non-ascii, maybe east-asian strings, it can be any value besides 00.

Peter

[paraglider]

There should be no difference between 0x1, 0x2 types with respect to trailing 00. When viewed in ANSI they should both have one trailing 00. If read using unicode windows api then each character will be 2 bytes with a trailing 2 byte null.

so an 0x1 or 0x2 null value will be 2 bytes each of 00 in unicode or 00 in ANSI.

0x7 types should always be double null terminated which means 4 00 bytes when read using unicode api or 2 00 bytes when read using the ANSI api.

windows internally stores all 0x1,0x2, 0x7 types as unicode in the registry.

[Lancelot]

Hi paraglider,

we agreed with the defination you gave ,

this is about having strick (and trustable) wb syntax rules.

With the agreed rules, now adding comma would be the syntax to create the initial value (aka empty data) with exactly the way you described
RegWrite,HKLM,<typ>,<Key>,
RegWrite,HKLM,<typ>,<Key>,<Value>,

hoping this will be working fully on next trash.

Edit:

edits here moved to post 243 to find easier

[pscEx]

Empty (acedemic) key creation (acedemic=DO NOT use unless you know what you are doing)
RegWrite,HKLM,<typ>,<Key>, ==>keys with null value
RegWrite,HKLM,<typ>,<Key>,<Value>

This will bring a "Parameter count error" if the "Check parameter count" option is activated.

Peter

[Lancelot]

I was planning to make a none critical future request for wider box (to bug tracker request section for future releases),

on wb077rc2, box width is 120 pixels, my request would be a wider one since interface variables are also frequently used for definations which does not fit this box. (240 pixels)

and now I noticed box gone away.

wb077rc2
http://img175.images...02220225312.png

wb080trash
http://img638.images...02220226582.png


maybe a hot fix (and + 240 pixels) can be made, maybe not (nothing critical)

[MedEvil]

That's a good one! Didn't even notice that until you posted.
Wonder which registry_write fix caused that.

[Lancelot]

Wonder which registry_write fix caused that.

I can sacrifice more boxes to the medusa gods if it is what we need to get right registry

Well above is no critical at all, I just noticed and wrote here if it can quickly get fixed. (and i won't be happy if it can not )

Good night for today.

[Brito]

and i won't be happy if it can not

That's a bug introduced by me, sorry..

If you don't click on anything while editing the interface, you'll notice that the box is placed nicely on the left tool bar at the top position.

However, whenever you select another interface object it will be hidden.

Here's how it looks:


This is not difficult to correct, just need to place the box outside the specific object type frame. My apologies.

[Brito]

Maybe it would be easier to track reported bugs for wb 080 if they are mentioned on individual topics?

http://www.boot-land...hp?showforum=97

It's so difficult to keep track of conversation on long conversation threads and I know this would also help new users to lose the fear of joining the testing team and see what is being done.

Thanks..

[MedEvil]

Maybe i'm wrong, but why is the left pane populated when no object is selected?

[Lancelot]

If you don't click on anything while editing the interface, you'll notice that the box is placed nicely on the left tool bar at the top position.

I missed that, probably because very I am sleepy now

This is not difficult to correct,

I know this would also help new users to lose the fear of joining the testing team and see what is being done.

Nobody is new here Admiral, we are on defcon 4 and in a nuclear U-875 submarine
Normal users only see the water splashing because of our periscope
check what normal (and only carelful) user can see. Do not loggin and click following.
http://boot-land.net...s/wb_server.php

Maybe it would be easier to track reported bugs for wb 080 if they are mentioned on individual topics?

But also it is proved that using single topic is easier to do some development goals . (single topic helps others join more easly, also it is easy to find out what is going on for the people who join or follow the topic because topic has a head and tail to trace).
Honestly I can never find or remember lots of mini topics psc created to introduce things. I (and others) need a central page to all this topics. Syntax page mostly helps, maybe psc think to put relevant topic links to syntax rules !. (like "for more info click here")...

In order to find the midway to gain both methods advantage, we agreed with psc before to write non critical (not solved or posponed) bugs to bug tracker. I already wrote most of them.
And to summerize what essential done on topic, I summerize things to the end of post 230. I will spread these infos to psc's development topics (or some to new topic or etc.) after we get next wb so new wb80X users can easly practice what is new.

Further, If you request, I can also write important bug fixes to bug tracker by flagging them as fixed ?

After sometime passed with next release, better to close this topic (no need to be a longer topic) and rest for a while.... Another development topic will be better with another topic. Till than normal (unhidden) topics would do the bug report things easly like before.

Reminding: Before releasing a new version, opening a defcon4 topic for project admins to test critical bug is a good idea to follow for future releases.

(btw: today I noticed Max_Real QNX either do not have access (I guess) to here or did not notice this topic !? )

Some words:
For me, most important on this development topic is, registry operations and rules are settled down and I can call them now stable (or more properly, I can say now that they have a set of strick rules, so when we have issues in future we can easly follow the rules to find what is going on).
This was one of the big mess which was creating lots of things (vodoos, medusas) for a long while. Even hojope 69 which is not designed for wb80, works better with wb80 .

well, reallly good night for today, see you tomorrow.

[Brito]

check what normal (and only carelful) user can see. Do not loggin and click following.

That's an ancient bug and I've never noted it..

I would really appreciate if the bug tracker section was used more often. It's really important to keep everyone synchronized on what has been fixed and what is still missing to fix.

For long or secret discussions, defcon is still the place for them.

I think MaxReal has access to this section, or at least he should have as all .script developers do.

[Lancelot]

I would really appreciate if the bug tracker section was used more often. It's really important to keep everyone synchronized on what has been fixed and what is still missing to fix.

Check bug tracker Nuno, everything posponed (either in current topic or found elsewhere) already there

I have a request to ask if it is possible ?

Today boot-land was gone, and again opening html files were trying to get mini gif pictures....
(besides, even at normal times i do not like this, but yes it is good for new users )

Than i decide to make a log and try to change these pictures,

here is the original log I get
http://lancelot.winb...917_Original.7z

here is the modified one (which I loved a lot )
http://lancelot.winb...2_194917_Mod.7z

to get the modified one, I change lines like:
<img alt="[Success]" src="http://boot-land.net...ges/accept.gif" border="0">
to
<span class="s3"><span style="background-color: #9ECC85">--[Success]--</span></span>

all list is in the codebox (well, without any html coding knowledge )

Can we have such an option for log generating ?? (ex: "log with text display" checkbox with default disabled )

------------------------------------------------------------------------------------------------------------------------------------src="http://boot-land.net/images/WinBuilder.gif" border="0"><font color="#000000"> Build Bootable Environments</font>------------------------------------------------------------------------------------------------------------------------------------<img alt="[Success]" src="http://boot-land.net/images/accept.gif" border="0"><span class="s3"><span style="background-color: #9ECC85">--[Success]--</span></span>------------------------------------------------------------------------------------------------------------------------------------<img alt="[Done]" src="http://boot-land.net/images/app.gif" border="0"><span class="s3"><font color="#000000">--[Done]--</font></span>------------------------------------------------------------------------------------------------------------------------------------<img alt="[Clock]" src="http://boot-land.net/images/clock.gif" border="0"><span class="s3"><font color="#000000">--[Clock]--</font></span>------------------------------------------------------------------------------------------------------------------------------------<img alt="" src="http://boot-land.net/images/code.gif" border="0"><span class="s3">--Code--</span>------------------------------------------------------------------<img alt="[Failed]" src="http://boot-land.net/images/cross.gif" border="0"><font color="#FF6666"><b>--[Failed]--</b></font>------------------------------------------------------------------<img alt="" src="http://boot-land.net/images/cross.gif" border="0"><font color="#FF6666"><b>--Failed--</b></font>------------------------------------------------------------------------------------------------------------------------------------<img alt="[Skipped]" src="http://boot-land.net/images/ignore.gif" border="0"><span class="s3"><font color="#000000"><span style="background-color: #C0C0C0">--[Skipped]--</font></span>------------------------------------------------------------------<img alt="[Ignore]" src="http://boot-land.net/images/ignore.gif" border="0"><span class="s3"><font color="#000000"><span style="background-color: #C0C0C0">--[Ignore]--</font></span>------------------------------------------------------------------------------------------------------------------------------------<img alt="" src="http://boot-land.net/images/info.gif" border="0"><span class="s3"><font color="#0033CC">--Info--</font></span>------------------------------------------------------------------------------------------------------------------------------------<img alt="[Info]" src="http://boot-land.net/images/info.gif" border="0"><span class="s3"><font color="#0033CC">--[Info]--</font></span>------------------------------------------------------------------------------------------------------------------------------------<img alt="[Parameter]" src="http://boot-land.net/images/parameter.gif" border="0"><span class="s3"><font color="#0000FF">--[Parameter]--</font></span>------------------------------------------------------------------------------------------------------------------------------------<img alt="[Script]" src="http://boot-land.net/images/script.gif" border="0"><span class="s3">--[Script]--</span>------------------------------------------------------------------------------------------------------------------------------------<img alt="" src="http://boot-land.net/images/warning.gif" border="0"><span style="background-color: #FFFF00"><font color="#000000">--Warning--</font></span>------------------------------------------------------------------<img alt="[Warning]" src="http://boot-land.net/images/warning.gif" border="0"><span style="background-color: #FFFF00"><b>--[Warning]--</b></span>------------------------------------------------------------------------------------------------------------------------------------

[pscEx]

You know how I like (and do not) follow links in such posts.
Please write ONE explanation what you want.
Maybe in this explanation some links (SHOULD NOT BE usual) are necesary.

Peter

[Lancelot]

You know how I like (and do not) follow links in such posts.

There is no link to follow on my post. Only download links (and i do not know how to attach files without links )

Please write ONE explanation what you want.

download log_20100222_194917_Mod.7z from previous post , extract and open with your browser. You will see.

[Lancelot]

Hi Nuno, here is a nice example why we need topics. Syntax Decisions made by development without public awerness !!! I only luckly noticed by having an old dated ICQ message.

@ALL

check
http://www.boot-land...amp;showbug=254

congradulations, another series of escape in escape in escape ..... born

these escapes already causing troubles with some set of operations. There must be another, more solid method need to be invented. (not urgent for 080 , 082 or whatever developer team think silently behind closed doors)

an idea is adding an optional parameter to the syntax

as an example:
Reg_Add,NoRunParameter,0x1,"%reg%\ControlSet001\Control\CriticalDeviceDatabase\1394#609E&10483","Service","sbp2port"

this is just an example, it must be thinked 10 times with the known bad escape experiences to figure out a solid rule.







Edit:
Following edits made to gather (give summary) of some important infos at current topic:


Registry Handling:
Rules for initiating keys:
RegWrite,HKLM,<typ>,<Key>,,
RegWrite,HKLM,<typ>,<Key>,<Value>,

**initiating keys ovewrites the value before
**New Key creation when made with RegWrite,HKLM,0x1,<Key>,, overwrites if there is a value before (for some cases, it might be better to use preserve in the end, up to script author)

RegWrite,HKLM,<typ>,<Key> ==> creates totally (for all <typ>) empty key (I advice to use 0x1 for <typ> since it is more logical)

Empty (acedemic) key creation (acedemic=DO NOT use unless you know what you are doing)
RegWrite,HKLM,<typ>,<Key>, ==>keys with null value
RegWrite,HKLM,<typ>,<Key>,<Value>

**Empty (acedemic) key creation will bring "Parameter count error" if the "Check parameter count" option is activated.


**REG_DWORD must always contain a data. Ex: RegWrite,HKLM,0x4,<Key>,<Value>,<Data>

Registry Value Handling:
quotes are tolerated
and now we have an easy to understand syntax to handle basic 0x7 strings. post 12 post 13

RegMulti: (post22)
RegMulti,HKLM,Section,Key,APPEND,String
RegMulti,HKLM,Section,Key,PREPEND,String
RegMulti,HKLM,Section,Key,BEFORE,SubVal,String
RegMulti,HKLM,Section,Key,BEHIND,SubVal,String
RegMulti,HKLM,Section,Key,PLACE,Index,String
RegMulti,HKLM,Section,Key,DELETE,SubVal
RegMulti,HKLM,Section,Key,INDEX,SubVal,%Index%

When the BEFORE item does not exist, the new item is inserted as first one.
When the BEHIND item does not exist, the new item is appended.
In both cases there is a warning in the log.

If,EXISTREGMULTI,HKLM,Section,Key,SubVal post 35 post 36

Reg...Bin:
RegWriteBin[Ex],HKLM,0x?,Section,Key,53,00,55,00,00,00
RegReadBin,HKLM,Section,Key,%var%

Variable Handling Tip:
**
[process]
Set,%bla%,AnyContents,PERMANENT
Set,%bla%,NIL,PERMANENT

deletes %bla% from script.project
**
[process]
Set,%bla%,AnyContents,PERMANENT
Set,%bla%,"",PERMANENT

generates in script.project:
%bla%=
**
[process]
//Set,%bla%,AnyContents,PERMANENT
Set,%bla%,"",PERMANENT

produces a syntax error
That is, %bla% has to be defined as "something" before it can be given an empty value

Posponed:
*syntax rules with examples (where when we need them) to show escape in escape usage ## ###
*regreading fails where there is escape charecters in "value data" post 16 post 30