- 29th November 2008 at 11:54 #43485
Anyone know how install NOD32 version 4 on server 2008? I tried ORCA and an hexdecimal but didn`t work?, tried denied permissions on regedit but also didn`t work…
- 29th November 2008 at 16:21 #47733
what u removed with ORCA ?
- 29th November 2008 at 19:23 #47734
i took out all parameters.
- 16th December 2008 at 03:58 #47735
It seems only the older MSI’s use LaunchConditions, it’s getting more common to use CustomActions I’ve noticed – probably to try and prevent people like us from doing exactly this – ha! In this case with the NOD v4.1 Beta MSI, it’s the CA “InstSuppPrepareInstall” which uses InstSupp.dll [inside the MSI] to do somesuch nonsense to, well, prepair the system I guess.
I spent about an hour figuring this one out, and was even trying to hack the InstSupp.dll, but after some random experimentation I found the way to get around it with just Orca.
Under the table “InstallUISequence”, drop the row “InstSuppPrepareInstall”. Thats it!
EDIT: Also had to do this as I found it would fail install…
Under the table “InstallUISequence”, drop the row “InstSuppApplyUIChanges”. NOW thats it!
Hope it works for you, it does for me =D Peace!!!
- 21st March 2009 at 07:18 #47736
- 12th June 2009 at 19:12 #47737
It worked perfect for me, thank you!
- 12th July 2009 at 17:41 #47738
- 21st August 2009 at 23:52 #47739Anonymous
as i already mentioned on the security software page comments – i tried “hacking” around with permission values and stuff all the way too – but that is not the fact – the setup doesn’t seem to care about it – only important thing is to have a “business edition” by only changing the “producttype” value from eav/ess to eavbe/essbe – and it will work.
simple as that ^^
- 20th October 2011 at 13:02 #47740
dude, it worked, thank’s a lot
- You must be logged in to reply to this topic.