software problem

[bodybuilders1]

yes but i have installed this product on my other pc, to see if the program was currupt, and it installed just fine. the problem is, that i need it on this pc, and it will not install. its not the program, i need to know why it will not install on this pc anymore after the demo. and i have been trying to contact the maker.

[bodybuilders1]

hey folks thanks for all the help
it was verry much appreciated!!!
so long!!

[indolikaa]

Don't leave yet. The ass-beatings are only just beginning!

[jimmalenko]

what about the sodomy ?

[tweedledee]

This site makes my day

[bodybuilders1]

alright lets begin. whose first?

[Roderz]

Anybody knowing a way to identify how a timed demo program
knows that it has been installed before , should speak up.
I have an Enquiring Mind... I Wanna Know.

The hard ones are in the CLSIDs I think , which are difficult to make sense of.

There are two freely available M$ downloads Regmon and Filemon both have filtering capabilities (so one can narrow down a single program) to check what files and registry locations a program is accessing

M$ also have a d/l prog for monitoring programe installs (showing whats been changed)

All very intresting if you got an Enquiring Mind

the limit on a recent beta was found in 2mins using filemon (no further info will be given so please don't ask)

[pyscrow]

Anybody knowing a way to identify how a timed demo program
knows that it has been installed before , should speak up.
I have an Enquiring Mind... I Wanna Know.

The hard ones are in the CLSIDs I think , which are difficult to make sense of.

Easiest way to do it, and hardest to find, is to install a *.dll, (The dll can contain any crap you like, or nothing), using a windows sounding name.

Then you just do a search for this file on your software startup, and check its file date.

You can get fancier by multilayering this effect, by adding several, and randomly polling for them in the software. You can also trigger new ones being added during the first or subsequent sessions of the software, so that "change loggers" used during installation are ineffective.

Extremely hard to find, and effective.

[indolikaa]

Don't leave yet. The ass-beatings are only just beginning!

alright lets begin. whose first?

Me!

It's all in good fun. Everybody is entitled to a bad moment. Ranting can be good, the occasional outburst can be even better. Hey, you apologized! That says a lot right there.

There are a multitude of ways to keep people from using software beyond a designated point in time. Editing the registry is no longer the surefire way to do it. Hell, I don't know if it ever was. OK, maybe asking for help around the problem was the wrong approach. That would depend on whether the subject would be viewed as warez or not.

But coming here and saying 'Company XYZ is shit because I bought their damned software and it won't run and they won't answer their e-mails!' is totally fair game in my book. Demand better service, or tell all your friends about how you got screwed. Word of mouth advertising means something here.

I do hope you solve the problem. Good luck!

[FOO]

I have done the following...
Log every file access during an install - this will find your dll thing.
Log every Registry access during an install


The above is insufficient when a program registers a new CSLID

edit: CLSID . oops

[bodybuilders1]

well guys, they finally answered, and re-sent me a new install, guess the other one was faulty, this one opened without a problem.
hey foo, glad to see that you replied, i thought that i would never hear from you again. Guys, thanks a mill for all the help, i'm shure that we will bulshit again on another subject, since i'm also trying to learn CLEANER XL. fo the meanwhile though, i know what i,m doing with CLEANER.
oh, foo, i'll be talkin to you about de-logo again in a minuit, so dont dissapear.
thanks again everybody, its been fun!!!!