MSFN Forums > Can't make Registry entry

MSFN Forums > Customizing Windows and Graphics > Windows Tips 'n' Tweaks

snowtox

Oct 6 2008, 02:31 PM

Hi all

I made an install file with Inno Setup for Adobe Photoshop CS3
However I have to make some registry entries at

CODE

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\]

and Regedit blocks them...
Can anyone tell me how to do this?

CODE

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_FLEXNET_LICENSING_SERVICE]
"NextInstance"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_FLEXNET_LICENSING_SERVICE\0000]
"Service"="FLEXnet Licensing Service"
"Legacy"=dword:00000001
"ConfigFlags"=dword:00000000
"Class"="LegacyDriver"
"ClassGUID"="{8ECC055D-047F-11D1-A537-0000F8753ED1}"
"DeviceDesc"="FLEXnet Licensing Service"
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Enum\Root\LEGACY_FLEXNET_LICENSING_SERVICE]
"NextInstance"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Enum\Root\LEGACY_FLEXNET_LICENSING_SERVICE\0000]
"Service"="FLEXnet Licensing Service"
"Legacy"=dword:00000001
"ConfigFlags"=dword:00000000
"Class"="LegacyDriver"
"ClassGUID"="{8ECC055D-047F-11D1-A537-0000F8753ED1}"
"DeviceDesc"="FLEXnet Licensing Service"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_FLEXNET_LICENSING_SERVICE]
"NextInstance"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_FLEXNET_LICENSING_SERVICE\0000]
"Service"="FLEXnet Licensing Service"
"Legacy"=dword:00000001
"ConfigFlags"=dword:00000000
"Class"="LegacyDriver"
"ClassGUID"="{8ECC055D-047F-11D1-A537-0000F8753ED1}"
"DeviceDesc"="FLEXnet Licensing Service"

Hope you can help me with that
snowtox

killerb255

Oct 6 2008, 03:08 PM

Are you running Vista? If so, UAC may be blocking it...

You'll have to run regedit elevated.

snowtox

Oct 6 2008, 04:22 PM

Your are right I'm running Vista however I deleted UAC with vlite...

and how do I run regedit elevated?

x-Shadow-x

Oct 7 2008, 07:51 PM

You need to add

CODE

Windows Registry Editor Version 5.00

to the top of the registry file.

CODE

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_FLEXNET_LICENSING_SERVICE]
"NextInstance"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_FLEXNET_LICENSING_SERVICE\0000]
"Service"="FLEXnet Licensing Service"
"Legacy"=dword:00000001
"ConfigFlags"=dword:00000000
"Class"="LegacyDriver"
"ClassGUID"="{8ECC055D-047F-11D1-A537-0000F8753ED1}"
"DeviceDesc"="FLEXnet Licensing Service"
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Enum\Root\LEGACY_FLEXNET_LICENSING_SERVICE]
"NextInstance"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Enum\Root\LEGACY_FLEXNET_LICENSING_SERVICE\0000]
"Service"="FLEXnet Licensing Service"
"Legacy"=dword:00000001
"ConfigFlags"=dword:00000000
"Class"="LegacyDriver"
"ClassGUID"="{8ECC055D-047F-11D1-A537-0000F8753ED1}"
"DeviceDesc"="FLEXnet Licensing Service"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_FLEXNET_LICENSING_SERVICE]
"NextInstance"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_FLEXNET_LICENSING_SERVICE\0000]
"Service"="FLEXnet Licensing Service"
"Legacy"=dword:00000001
"ConfigFlags"=dword:00000000
"Class"="LegacyDriver"
"ClassGUID"="{8ECC055D-047F-11D1-A537-0000F8753ED1}"
"DeviceDesc"="FLEXnet Licensing Service"

snowtox

Oct 8 2008, 05:04 AM

I knew that I have to add

CODE

Windows Registry Editor Version 5.00

on top...

It is in my .reg-file but thx...

GrofLuigi

Oct 8 2008, 05:16 AM

Set permissions on the ENUM key. Give yourself or your group full control. If you want to use it programatically, use cacls or similar.

That's Microsoft's idea of security. This was changed in XP SP2 and later OSes. To try to prevent a thief from entering your house, they leave the front door slightly closed, but double lock all inside doors.

(The worm/virus that would install itself as a service here is already inside your system and running, so this would stop nobody except legitimate users.)

GL

snowtox

Oct 8 2008, 07:03 AM

Solved it now... found a patch on the adobe homepage...

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.