[Command] list-reg not sufficient? ...
[1/5] from: petr:krenzelok:trz:cz at: 18-Aug-2003 14:02
Hi,
I wanted to try Windows registry functions, but I can find the way it
works insufficient ...
eg. - inspired by virus, I wanted to check following section:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
'Run tree node contains directly some info + one subnode. list-reg
function returns only that subnote. That way, we can't build dynamic
system - there is no way of how to obtain listing of items, unless we
know their name:
->> list-reg/hklm "SOFTWARE\Microsoft\Windows\CurrentVersion\Run"
== ["OptionalComponents"]
while 'Run node itself contains lot's of stuff my machine runs after
start ...
->> get-reg/hklm "SOFTWARE\Microsoft\Windows\CurrentVersion\Run" "ICQ Lite"
== "C:\Program Files\ICQLite\ICQLite.exe -minimize"
... get-reg is fine, but I need to explicitly know what the name (ID) of
item is. .... I don't find it sufficient - list-reg should imo report
also what is directly stored under "Run" node ...
nor does it help to go one level up:
->> get-reg/hklm "SOFTWARE\Microsoft\Windows\CurrentVersion\" "Run"
== none
... sending to feedback ...
-pekr-
[2/5] from: greggirwin:mindspring at: 18-Aug-2003 10:24
Hi Petr,
PK> I wanted to try Windows registry functions, but I can find the way it
PK> works insufficient ...
Look like they could add a refinement to tell what you want to list
for a key, or add meta info so listing a key gives you details about
what is inside a key. Frank's old registry functions work for all
this IIRC.
--Gregg
[3/5] from: petr:krenzelok:trz:cz at: 18-Aug-2003 18:56
Gregg Irwin wrote:
>Hi Petr,
>PK> I wanted to try Windows registry functions, but I can find the way it
<<quoted lines omitted: 3>>
>what is inside a key. Frank's old registry functions work for all
>this IIRC.
I imagined it could work as reading a directory... direct node items, as
in the case of "Run node, could be just strings, and subnodes could be
like dirs blabla/ It could work ...
-pekr-
[4/5] from: greggirwin::mindspring::com at: 18-Aug-2003 11:33
Hi Petr,
PK> I imagined it could work as reading a directory... direct node items, as
PK> in the case of "Run node, could be just strings, and subnodes could be
PK> like dirs blabla/ It could work ...
Think that's what Frank did, pretty much. The registry APIs should map
well to a port idiom because you have to open a key, read from it, and
close it.
-- Gregg
[5/5] from: petr:krenzelok:trz:cz at: 18-Aug-2003 21:04
Gregg Irwin wrote:
>Hi Petr,
>PK> I imagined it could work as reading a directory... direct node items, as
<<quoted lines omitted: 4>>
>close it.
>-- Gregg
I wonder too, why we see them as functions, and not abstracted ports?
Today I read another Q&A session with Amiga's TCO Fleecy Moss where he
describes "orthogonal persistence" - I thought to myself - rebol port
abstraction and then suddenly I though - why registry functions are not
simply a port? :-)
-pekr-
Notes
- Quoted lines have been omitted from some messages.
View the message alone to see the lines that have been omitted