rpcclient from tng

Todd Sabin tastas at home.com
Wed Feb 9 00:51:57 GMT 2000


Luke Kenneth Casson Leighton <lkcl at samba.org> writes:

> oops, it may be too long (large) for the current regenum code.  does
> anyone with some MSDN / Reg* experience want to take a look at the code
> and try and fix this?  the api is pretty much identical except it will be
> reg_enum_values not RegEnumValues etc :)
> 

The problem appears to be that the registry value has no name.  I.e.,
its name is "", the null string.  Yes, the geniuses at Microsoft allow
you to create values with the null string as its name.  If fact, large
sections of the registry (typically the stuff developed on Win9x
first) are full of this.  When you look at them with regedit.exe it
calls them "Default" in the UI.  When you look at them with
regedt32.exe it calls them "<No Name>".

Not sure what rpcclient needs to do to handle this...


Todd

> On Wed, 9 Feb 2000, Seth Vidal wrote:
> > HKLM\SOFTWARE\COMPANYNAME\SOFTWARENAME\LICENSEKEY\
> > 
> > the only (default) key under this tree is a string type licensekey.
> > 
> > How do I set the value for the default entry?
> > As well when I do a regenum It never lists the  current value.
> > the errors I see:
> > [skvidal at JORDAN]$ regenum "HKEY_LOCAL_MACHINE\SOFTWARE\PASCO
> > Scientific\DataStudio\LicenseKey"
> > regenum "HKEY_LOCAL_MACHINE\SOFTWARE\PASCO Scientific\DataStudio\LicenseKey"
> > vuid_init_db: failed
> > Key Name:   HKEY_LOCAL_MACHINE\SOFTWARE\PASCO Scientific\DataStudio\LicenseKey
> > Key Values
> > ----------
> > REG_ENUM_VALUE: 
> > 
> > [skvidal at JORDAN]$ regenum "HKEY_LOCAL_MACHINE\SOFTWARE\PASCOScientific\DataStudio\SerialNumber" 
> > regenum "HKEY_LOCAL_MACHINE\SOFTWARE\PASCO Scientific\DataStudio\SerialNumber"
> > vuid_init_db: failed
> > Key Name:  HKEY_LOCAL_MACHINE\SOFTWARE\PASCOScientific\DataStudio\SerialNumber
> > Key Values
> > ----------
> > 	:	string:	5895
> > 
> > 
> > so you see the next key does have values but the licensekey doesn't.
> > 
> > I've checked the machine and there is an entry.


More information about the samba-ntdom mailing list