Power DVD 8
Hi Lads,
This is not about the installation of the product, more about the users experience with it. As a administrator, everything works fine. When a user logs on the first thing they get is a information message appear "You must register your new drive. Please login as the Administrator, launch PowerDVD, and then restart your computer to register this drive."
Not a problem, so i go and do what it says and it still appears to the user. Has anyone got this message appear and how they got passed it. Is there a reg key i need to change.
Any help would be gratefully appreciated at this point, as I need to get this done very soon.
This is not about the installation of the product, more about the users experience with it. As a administrator, everything works fine. When a user logs on the first thing they get is a information message appear "You must register your new drive. Please login as the Administrator, launch PowerDVD, and then restart your computer to register this drive."
Not a problem, so i go and do what it says and it still appears to the user. Has anyone got this message appear and how they got passed it. Is there a reg key i need to change.
Any help would be gratefully appreciated at this point, as I need to get this done very soon.
0 Comments
[ + ] Show comments
Answers (8)
Please log in to answer
Posted by:
anonymous_9363
15 years ago
In all likelihood, the app is trying to write information (probably a registry value) to a location to which ordinary users have no access rights. A quick session with ProcMon will determine that. Once you know what that location is, you can add it to your package. If it turns out to be machine-specific, you can add a Custom Action to assign appropriate permissions using SetACL, SubInACL or your favoured permissioning tool. You can, of course, use the LockPermissions table to do that, but I prefer command line tools for their flexibility.
Posted by:
Thegunner
15 years ago
Hi VBScab,
Thank you for the reply,
We have ran FileMon and RegMon and got the paths it accesses. C:\Program Files\Cyberlink and C:\Program Files\Common Files\Cyberlink. Via the registry we added a security to HKCU and put the user in that group and still got the message. Tried to run ProcMon, it needs SP2 we are running SP1
We put the user in the Domain Admins group and we didnt get it, so there is something else that we can not find.
Thank you for the reply,
We have ran FileMon and RegMon and got the paths it accesses. C:\Program Files\Cyberlink and C:\Program Files\Common Files\Cyberlink. Via the registry we added a security to HKCU and put the user in that group and still got the message. Tried to run ProcMon, it needs SP2 we are running SP1
We put the user in the Domain Admins group and we didnt get it, so there is something else that we can not find.
Posted by:
anonymous_9363
15 years ago
You added security to HKCU? Why? The logged-in user - by definition - has rights to that hive already.
I think PM required SP2 only for v2 and above. You can still get previous versions. Having said that, who on EARTH is still on SP1?!? Am I wrong in recalling that many OS updates are unavailable to non-SP2 installations?
Equally, FM and RM will still show you 'ACCESS DENIED' errors and 'PATH NOT FOUND'/'NAME NOT FOUND' errors.
It would probably be simpler to use a snapshotting tool like InstallWatch to watch the app's activity after installation and add whatever it's writing to your package.
I think PM required SP2 only for v2 and above. You can still get previous versions. Having said that, who on EARTH is still on SP1?!? Am I wrong in recalling that many OS updates are unavailable to non-SP2 installations?
Equally, FM and RM will still show you 'ACCESS DENIED' errors and 'PATH NOT FOUND'/'NAME NOT FOUND' errors.
It would probably be simpler to use a snapshotting tool like InstallWatch to watch the app's activity after installation and add whatever it's writing to your package.
Posted by:
Inabus
15 years ago
Posted by:
Thegunner
15 years ago
Hi all,
Well have found out the problem that was causing the Information Message to appear. It was a file called CLDRVCHK.EXE This file was not in the other version of PowerDVD8 we had. Our client has been on SP1 for a while, we are pushing out SP3 now, so it will be a little while before all devices get it.
We got FM and RM and checked out all the Access Denied messages and tested them and that didnt fix it, its seems this file fires off as soon as PowerDVD8 runs. FM didnt pick it up it seems. Strange. It was just by chance I noticed it and thought it was a drive check executable, so just renamed it and tested. All good now it seems.
Cheers all for your responses
Well have found out the problem that was causing the Information Message to appear. It was a file called CLDRVCHK.EXE This file was not in the other version of PowerDVD8 we had. Our client has been on SP1 for a while, we are pushing out SP3 now, so it will be a little while before all devices get it.
We got FM and RM and checked out all the Access Denied messages and tested them and that didnt fix it, its seems this file fires off as soon as PowerDVD8 runs. FM didnt pick it up it seems. Strange. It was just by chance I noticed it and thought it was a drive check executable, so just renamed it and tested. All good now it seems.
Cheers all for your responses
Posted by:
barrtrek
14 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.