I have used Vue for years and Vue 7 infinite since it was released and never ran in to this.

After installing the 7.4 update  I get a couple of issues.
Every time launching it says "Bad activation number". I have entered the given activation number but it continues arguing about it.

Second thing is I get e-on's water marks all over my renders (probably connected with the activation thingy). 

Anyone else had this? Do I have to uninstall and go back to the build before 429999?
Sigh...

Make sure you are either using "Run as Administrator" or have turned of UAC when entering the activation number.

If you still get the message, you should try reactivating (your INST code may have changed for some reason).

 Thank you Noel, that was it!  

Installed it as Admin instead and it works fine now. Puh... got a bit "panicky" there for a while.

/me sends hug to noel

Tiny,,
http://www.silverblades-suitcase.com/tutorials/htm/39.html
points to 2/3rds of the way down the page, "Note to Vista users ;)

Nrudock hit the nail on the head, you have ot run as administrator, get that damnable UAC turned off, ick!! UAC causes problems for many other apps, too!
:)

A better solution is not to install those programs that have trouble with UAC into the "Program Files" tree.

Quote - A better solution is not to install those programs that have trouble with UAC into the "Program Files" tree.

In the last, and working, install I selected the'Program files (x86)' instead. I'm glad I did something right in the end.

Thanks silverblade for the link. Will keep it until I forget next time. If I can remember it then... :blushing:
at least I can find this thread when searching. 

Quote - > Quote - A better solution is not to install those programs that have trouble with UAC into the "Program Files" tree.

In the last, and working, install I selected the'Program files (x86)' instead. I'm glad I did something right in the end.

Actually that won't help, as that's a protected directory just like "Program Files" that Microsoft uses as the default location for 32-bit programs in their 64-bit OSs.

Quote - > Quote - > Quote - A better solution is not to install those programs that have trouble with UAC into the "Program Files" tree.

In the last, and working, install I selected the'Program files (x86)' instead. I'm glad I did something right in the end.

Actually that won't help, as that's a protected directory just like "Program Files" that Microsoft uses as the default location for 32-bit programs in their 64-bit OSs.

I see. Ok, so I didn't do it right at the end... typical...
So do you install in another dir of your choice then?

mine is D:E-onSoftwareVue7 or something like that.  Saves a whole world of pain :)

avoid vista - avoid pain ;)

Anybody using Windows 7 RC yet with Vue?

Quote - avoid vista - avoid pain ;)

Perhaps you'd be better off avoiding programs from software houses where "programmers" have not yet understood how Win32 security works, something which dates back to Win NT 3.1, released on July 27th, 1993 (almost 16 YEARS ago).

Bye...

Quote - So do you install in another dir of your choice then?

That's the idea, basically anything not beginning "Program Files".
This avoids trouble with programs that need to write to their install directory.

Having said that, Vue writes the activation information to the Windows directory, so you can't avoid running as Administrator on the first launch.

Some programs like Vue also allow you to relocate their content directory (at install time) which can be helpful if you want it on another disk or just not under "My Documents" (and don't want to mess about relocating profiles).

Quote - Anybody using Windows 7 RC yet with Vue?

Yes and it works fine in my experience.

I am using Windows 7 64-Bit, runs very well, havent had any problems with Windows or running Vue with it. 

Everything runs as it should

ditto, the two above.

The only problem I have found however that sometimes it is a little too eager to claim a program has crashed/not responding and so sets about trying to close it. 

This would be great normally but occasionally it can be a pain when, for example, vue/lightwave is thinking and it interprets it as having stopped responding.   I can probably turn this off but havent really looked yet :P

I found that too Rich, like when you go to stop a render, it thinks Vue has stopped working.