Integrate b1601 Patch to PowerDVD 10 b1516
hi guys,
am trying to figure out if there's a way to integrate b1601 patch onto the PowerDVD 10 v10.0.1516.51?
I managed to create an AIP for b1516 successfully.
and downloaded b1601 (exe patch) from http://update.cyberlink.com/ftpdload/patch/powerdvd/10/Ultra/CyberLink.1601(Patch)_DVD100331-01.exe
i was thinking the b1601 patch within the exe will just contain MSP, and boy i was wrong! inside this exe, it's a whole new *standalone* package (data1.cab, setup.exe, powerdvd.msi, etc. etc.)
any thoughts/ideas would be interesting to integrate b1601 patch onto b1516 installer.
thanx!
am trying to figure out if there's a way to integrate b1601 patch onto the PowerDVD 10 v10.0.1516.51?
I managed to create an AIP for b1516 successfully.
and downloaded b1601 (exe patch) from http://update.cyberlink.com/ftpdload/patch/powerdvd/10/Ultra/CyberLink.1601(Patch)_DVD100331-01.exe
i was thinking the b1601 patch within the exe will just contain MSP, and boy i was wrong! inside this exe, it's a whole new *standalone* package (data1.cab, setup.exe, powerdvd.msi, etc. etc.)
any thoughts/ideas would be interesting to integrate b1601 patch onto b1516 installer.
thanx!
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
Yankir
14 years ago
I think b1601 is a major upgrade for b1516 , just check if the same installs the complete application. If it installs the complete application then patching is not required.
Posted by:
davidlimcg23
14 years ago
b1516 is around 125MB.
b1601 patch is around 111MB. <-- required existing powerdvd10 to be installed.
b1601 patch is around 111MB. <-- required existing powerdvd10 to be installed.
Posted by:
anonymous_9363
14 years ago
If it were me, I'd just treat the new package as an upgrade, rather than a patch. If you want to persist, though:
- examine how the new package is determining th einstalled state of PowerDVD
- use that information to "foll" the machine into believing that it IS installed
- test-install the "patch"
- test the application
- create a proper patch using your authoring tool's patch-creation tool
- return to clean state
- re-install PowerDVD
- test-install the patch
- test the application
- patch the AIP
Which is easier? Upgrading or trying to create a proper patch? No-brainer, eh?
- examine how the new package is determining th einstalled state of PowerDVD
- use that information to "foll" the machine into believing that it IS installed
- test-install the "patch"
- test the application
- create a proper patch using your authoring tool's patch-creation tool
- return to clean state
- re-install PowerDVD
- test-install the patch
- test the application
- patch the AIP
Which is easier? Upgrading or trying to create a proper patch? No-brainer, eh?
Posted by:
nheim
14 years ago
Hi David,
the chance is relatively high, that this "patch" is a full installation. Seen this quite a few times (Filemaker f.ex.).
Have a closer look at the log file. Particular at the "FindRelatedProducts" and the "RemoveExistingProducts" actions.
Maybe the installed version gets completely uninstalled.
Also check the actual download version. Is there a difference to the "patch"?
Good luck.
Regards, Nick
the chance is relatively high, that this "patch" is a full installation. Seen this quite a few times (Filemaker f.ex.).
Have a closer look at the log file. Particular at the "FindRelatedProducts" and the "RemoveExistingProducts" actions.
Maybe the installed version gets completely uninstalled.
Also check the actual download version. Is there a difference to the "patch"?
Good luck.
Regards, Nick
Posted by:
davidlimcg23
14 years ago
thanx VBScab and nheim, i might stay away from integrating b1601 "update" into the original b1516 setup ;)
possibly, i could chain both of them to install in sequential: b1516 + b1601 :)
thx guys!
possibly, i could chain both of them to install in sequential: b1516 + b1601 :)
thx guys!
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.