By registering with us, you'll be able to discuss, share and private message with other members of our community.
SignUp Now!> Was it every suggested that TCC adds support for the Registry as a file
> system?
file> On Thu, 17 Jun 2010 13:56:02 -0400, rconn <> wrote:
>
> |---Quote---
> |> Was it every suggested that TCC adds support for the Registry as a
need> |> system?
> |---End Quote---
> |It was suggested, but nobody's been able to come up with a real-world
be> |for it (other than "it would be cool").
>
> It **would** be really cool.
>
> A very crude approximation could be done with a plugin, but it couldn't
Together> integrated with TCC. This (below) wouldn't be too hard. But I'm
> disinclined to
> do it because it would just be an exercise in being cool (and it
> wouldn't be all
> that cool).
>
> REGENTER hive - open a hive
> REGHIVE hive - change hive
> REGCD key - enter a key (up/down only)
> REGDIR - list subkeys/valuenmes_and_types (current key only)
> REGTYPE value - show data in reg value (current key)
>
> Try to make it just a little more like navigating a file system
> (REGCD anywhere,
> REGDIR anykey, REGTYPE any value) and the work necessary skyrockets.
>
> However, it seems that a REGENUM command could be useful (and easy).
mod> with what TCC already makes available it might help the user (who was so
> compelled) to create a collection of aliases, variables and user-defined
> functions (maybe batch files) to roam around the registry.
>
> Simply, it might be:
>
> REGENUM hive[\key\subkey\...] - give a dir-like listing of subkeys (with
> times) and values (with types).
> --
> - Vince
>
>
>
>
However, it seems that a REGENUM command could be useful (and easy). Together with what TCC already makes available it might help the user (who was so compelled) to create a collection of aliases, variables and user-defined functions (maybe batch files) to roam around the registry.
Simply, it might be:
REGENUM hive[\key\subkey\...] - give a dir-like listing of subkeys (with mod times) and values (with types).
As an aside, I was first made aware of that information being available when I discovered the very nice GUI registry editor called Registry Workshop. It has an undo function for those who like to whack things, but you can get them back if needed. And you can even browse down into normally inaccessible secured registry keys.With the exception of modification times. I
didn't know that information was even available.
> ---Quote---
> > Was it every suggested that TCC adds support for the Registry as a file
> > system?
> ---End Quote---
> It was suggested, but nobody's been able to come up with a real-world need
> for it (other than "it would be cool").
>
> Rex Conn
> JP Software
>
>
>
>
>
Hello -
Was it every suggested that TCC adds support for the Registry as a file system?
/Frank
> Perhaps adding hooks into the plugin system so plugin developer's could
> add their own pseudo-devices would be possible.
>
> So I could create a REG: pseudo-device that would operate akin to the
> FTP: pseudo-device you have in place already
It was suggested, but nobody's been able to come up with a real-world need
for it (other than "it would be cool").
Rex Conn
JP Software
> What about a drive which contains the registry from your old system,
> which you moved to a new system as an extra drive? One would really
> like to duplicate the registry entries which make the software on
> that drive usable, and likewise, prepare for the time when the
> current system is to be replaced by a newer (but not necessarily
> better) one.
> ---Quote (Originally by rconn)---
> It was suggested, but nobody's been able to come up with a real-world
> need for it (other than "it would be cool").
>
> ---End Quote---
> Some time age I came across a cygwin alternative call kwin from att
> research. It contains a korn shell that has the registry mounted as a
> file system
On Thu, 17 Jun 2010 17:47:41 -0400, Joe Caverly <> wrote:
As I recall, with PS you can navigate many things as if they were directory
trees (WMI trees is another example, I think)... even have the current
"location" appear in the prompt. The whole thing might be WMI based.
--
- Vince