On Sat, 2 Oct 2004, Martin Bammer wrote:
When I remove the Enum-key under hkey_local_machine then Windows redetects all hardware. So a reinstall would not be needed. Wine has a regedit. But I don't know how to tell wine that it uses the registry from the installed windows.
For sure it would not be needed, but as for Wines regedit I am not sure. AFAIK, it can only read NT-system registry, but not write it.
Would be a nice "recovery" feature for Linux to be able to edit windows registries, because a defective registry is often a problem in windows...
You can always try using Offline NT Password & Registry Editor. It uses console UI and is more of command line editing, but whatever [1].
BTW, you or someone else can try merging both the ntreg library [1] and Wine registry editor code to make a GUI tool to suffice your needs. I hope there would be no license [2] collisions.
[1] http://home.eunet.no/~pnordahl/ntpasswd/ [2] http://home.eunet.no/~pnordahl/ntpasswd/COPYING.txt
Saulius Krasuckas wrote:
I hope there would be no license [2] collisions.
You meant to say that you hope that the license collisions are resolvable.
The current license is not LGPL compatible due to the "no making money" clause. The "docs" credit is also not LGPL compatible. However, the author also says:
If you ask I will very likely allow other types of distribution. (have already had questions of it as a bonus on eBay auctions. ask, and you will likely get permission) I'm just a kind of control freak, so I want to know what's going on.
which gives hope that if you ask him nicely, he will be willing to relicense the relevant parts as LGPL.
Shachar p.s. The "no commercial distribution" runs counter to item 1 of the open source definition (http://opensource.org/docs/definition.php). This means that this license is not an open source license. One has, of course, every justification for saying "so what", but I just wanted to mention this.
Sh.
-
Saulius Krasuckas -
Shachar Shemesh