XP and Windows 7 on same machine but getting different target ids.
XP and Windows 7 on same machine but getting different target ids.
(OP)
For some odd reason my company wants me to install XP on the machine we have Windows 7 on. So I did, I partitioned the drive and made the machine so you can boot XP or Windows 7 but heres the problem. I installed R18 and R20 (with Honda ENV) on the XP side and R20 (Honda Env) on the Windows 7 Side. But each OS is giving me a different Target ID. My nodelock License works fine for the XP side but I cant run it on Windows 7 Side.
Any ideas?
Any ideas?





RE: XP and Windows 7 on same machine but getting different target ids.
1)The ACID number allows you to run a multi session on the same computer.
The LUM server was not assigning an ACID number when a license is checked out. Dassault recommends the LUM version on the server to be 4.8.6 FP 15. This version only needs to be installed on the server and not every Catia client station.
If you cant find FP15 I will upload to your ftp site.
2)Legacy licensing. Dassault will be switching the license from LUM to the V6 method after R22
Set a system environment variable or add it your CATIA.V5R20.B20.txt
DSLICENSING = LEGACY
3) Different ID's on Windows. This is usually a permission problem
On Windows computers having more than one network card, it may happen that the Target ID used by different user accounts be not the same.
The problem can be fixed by setting "Full Control" permission for the registry key {HKEY_LOCAL_MACHINE\SOFTWARE\IBM\License Use Runtime}. This permission can be set for individual users or groups, or for Everyone.
Run Regedit. Go to HKEY_LOCAL_MACHINE\SOFTWARE\IBM\License Use Runtime. Right click on it. Select Permissions. Select the appropriate user and/or group, and allow Full Control. Or add Everyone group and allow Full Control.
Regards,
Derek
Win XP64
R20/21, 3DVIA Composer 2012, ST R20
Dell T7400 16GB Ram
Quadro FX 4800 - 1.5GB