Question:

Adobe CS3 / Macrovision DRM residue

by  |  earlier

0 LIKES UnLike

This is a genuine request to the very best of the best to join me in solvingthe TECHNICAL aspects of this problem.It has nothing to do with illegal software p****y, and everything to do with the sanctity of our person and our property from illegal violation under the 4th amendment of the US constitution. Politics, however, is not the topic of this request.Failed legitimate installation of Adobe CS3 demo-ware:Premiere and After Effects, downloaded from the Adobeweb-site on July 15, 2008.========================================has left DRM / Macrovision Flexnet residue on my system, which not onlyprevents the demo-ware from being re-installed, but it has destabilizedother legitimate licenses on my machine.1) Adobe is aware of this problem, thousands of customers are affected, but Adobe is unable and/or unwilling to fix it. Their tech support staff claim it is only a recent "WEB-site problem" which only affects "some" computers and it is "no big deal"2) The new Macrovission DRM introduced with CS3 is extremely aggressive and predatory, far worse than the infamous SONY root-kit of two years ago, as my personal research seems to indicate. I think criminal prosecution of Adobe, like SONY is strongly indicated but that is another topic. All I want to do is remove this repugnant **** from (my!!!!) machine, and gain the ability to help other victims to do the same.3) The CS3 installation program crashes and exits without any messages, but it does place uninstall hooks into the registry which do not work. The lame Windows "add-remove programs" starts the CS3 unisnstaller, which promptly crashes and terminates. (as expected)4) The Adobe cleanup script run at levels 1,2,3,4 fails to fully remove CS3.5) Popular third party cleaner tools remove more garbage, but not all of it.6) Manual registry and directory tear-out, finds a few small minor hooks but not all: Adobe, CS3, Flexnet, LMService, Macrovision, Safe-cast, Licenses, I am very good at this, but obviously not good enough (yet!) I also searched for embedded nulls in registry keys, invalid chars in file names and other common root-kit critters, like NTFS alternate data streams attached to temp directories, ... etc. but so far, No dice7) I have read that the Macrovision anchors will survive disk re-formatting, but not low level format (this is hardly a desirable step, however) The vermin at Macrovision actually brag about this and refer to a mutating polymorphic anchor engine on their web-site. Can you spell V-I-R-U-S ?! 8) The anchors survived OS and Application partition restoration, partition resizing and sliding. They also survive bad sector scanning, re-testing and repair.9) I am determined to defeat this sub-scumbag terrorist filth and for ever purge their garbage products from civilized society. Let's face it no company with any finite number of employees can survive to concentrated attack of angry customer on the global internetI am willing to do some of the work, with your help and genius.I am an engineer, not a hacker, so perhaps I am approaching thisfrom the wrong angle, your help is very much appreciated.Thank you, Martin

 Tags:

   Report
Please Login to view 2 answers to this question

Question Stats

Latest activity: earlier.
This question has 2 answers.

BECOME A GUIDE

Share your knowledge and help people by answering questions.