anybody successfully running consequence demo on 64-bit Vista?

[5bongo5]

Doesn't work for me. Crashes FL Studio with a read access violation, and not recognized by cubase at all.

Anybody have success with it?

[deraudrl]

Not sure it's a problem with 64-bit: I'm having more-or-less the same issues on a Vista 32-bit setup. (I say 'more-or-less' because I don't use FL...but it crashed Reaper and both versions of energyXT, and fails during the scan for VSThost.)

[Sugar Bytes]

Under Vista, please make sure the UAC (in msconfig/tools) is turned off.
That fixed all Vista and Vista 64 releated problems until now.

best
Rico

[dsan@mail.com]

Under Vista, please make sure the UAC (in msconfig/tools) is turned off.
That fixed all Vista and Vista 64 releated problems until now.

best
Rico

Greetings,
FWIW - I run Vista 64 bit, with UAC ON, and have had no problems with Consequence crashes (although I do have ONE issue with the program but this is for another thread). My host is Sonar 8 PE running in 32 bit mode (I have to run 32 bit since many of my fave VST's are not 64 bit supported).

Personally I think the problem is with "Unblocking" the download before installing it, AND installing as an administrator. When you perform a download, Windows "Blocks" the file. To remove the block right click the ".exe" and select properties. You will find it blocked on the properties page. After this be sure to run the program as system administrator (again, right click).

Now, I ONLY THINK this is the problem because since I found out about the block thingy, back with Windows 98, I have always removed the block and just do not experience the problems others have with these crashes and other blips I see spoken of. It is my opinion that when installing a "blocked" file some of it does not get installed and this causes the problems others are having.

Hopes this helps, and if i can be of more help please let me know.

Regards,
dsan

[deraudrl]

Personally I think the problem is with "Unblocking" the download before installing it, AND installing as an administrator. When you perform a download, Windows "Blocks" the file.
[snip]
It is my opinion that when installing a "blocked" file some of it does not get installed and this causes the problems others are having.

If this were really a problem, I would expect to be able to hear the screams from users echoing around the world, given that there are millions of programs with much more complicated installation requirements than the typical VST.

I was under the impression that the only thing the block does is force you through a UAC confirmation cycle (enter admin password etc). "Run as admin" of course does that preemptively. (I have no idea whether that permanently removes the block: I very rarely run installers multiple times.)

In any case, assuming that turning UAC off actually solves the problems, IMHO it is indicative of somebody doing something unnecessarily clever with file access permissions. And all things considered, that's something I can live without.

[dsan@mail.com]

If this were really a problem, I would expect to be able to hear the screams from users echoing around the world, given that there are millions of programs with much more complicated installation requirements than the typical VST.

You make a good point; however, there are huge numbers of posts about software not running properly in every forum I have visited. I only know that I too had similar issues until I started unblocking before an install. Not saying it is the do all/end all; just saying it works for me.

I was under the impression that the only thing the block does is force you through a UAC confirmation cycle (enter admin password etc). "Run as admin" of course does that preemptively. (I have no idea whether that permanently removes the block: I very rarely run installers multiple times.)

For more information about why Windows does the block (It is written for XP SP2 but I imagine is carried into Vista as well):

http://support.microsoft.com/?kbid=883260

In any case, assuming that turning UAC off actually solves the problems, IMHO it is indicative of somebody doing something unnecessarily clever with file access permissions. And all things considered, that's something I can live without.

+1

[scnnr]

Same problem here, access violation error when opening Consequence in FL Studio. UAC fix worked, but i wasn't comfortable turning it off, so tried turning it back on and running FL Studio as admin - that solved the problem.

[scnnr]

Just a word of warning - changing UAC setting caused most of my plugins to reset to demo mode, i had to re-authorize them again (including Komplete 5 and PSP stuff among others)

[deraudrl]

Just a word of warning - changing UAC setting caused most of my plugins to reset to demo mode, i had to re-authorize them again (including Komplete 5 and PSP stuff among others)

Was it the UAC setting or running as admin? I'm thinking the demo mode could be triggered by being a "different" user than the one that authorized or validated it.

[scnnr]

Just a word of warning - changing UAC setting caused most of my plugins to reset to demo mode, i had to re-authorize them again (including Komplete 5 and PSP stuff among others)

Was it the UAC setting or running as admin? I'm thinking the demo mode could be triggered by being a "different" user than the one that authorized or validated it.

I do believe it was the UAC setting. I remember changing it, rebooting, and trying Consequence with Pro-53 and it asked me to authorize. I thought it was strange, but no big deal, reauthorized, then tried running in admin mode and that's when i noticed some other plugs became demo too. Not all of them were affected, i would imagine only the ones that store user specific registry info.

Speaking of which, C/R protection truly sucks