Vegas multiple installation legality

Gyan wrote on 10/8/2015, 1:35 PM
Hello,

My editing rig has developed a critical fault viz. after it's switched on, it powers down after a couple of seconds and then restarts and powers down again..etc. It may just be a short somewhere, or it could be a faulty PSU / CPU / MoBo..etc. My hardware guy's coming tomorrow for a look. However, I have a fairly simple editing task that I have to deliver in 24 hours. Is it allowed for me to install and use Vegas Pro 12 on another comp with the same serial# till my rig is back up and running?

Thanks.

Comments

musicvid10 wrote on 10/8/2015, 1:39 PM
Yes.
Also, clean the dust bunnies from your CPU cooler.
May save you a service call.
Geoff_Wood wrote on 10/8/2015, 2:00 PM
Not sure now, but the T&C said mutliple installs OK , bit only one to be used at same time.

If you can install and authorise, I'd say go for it. SCS are (very reasonable, and authorisation not a problem generally until after 4 different Computer ID installs.


geoff
silvertone1938 wrote on 10/8/2015, 2:45 PM
I've gotten this exact verbatim answer from SCS support more than once. Seems like a boilerplate response:

"According to our End User License Agreement, you have the right to run a single purchased copy of our software on more than one machine as long as these machines are not running simultaneously. For instance, it is completely within your legal right to have the software installed on your laptop and desktop computers. You cannot, however, have this one copy installed on multiple computers running simultaneously in your home or in your workplace."

So, I'd say you're fine.
Gyan wrote on 10/8/2015, 2:59 PM
Sounds like it's fine. Thanks, all.

musicvid10, I already dusted and tried a few permutations like single stick of RAM, disconnecting the front panel switches..etc. No luck.
Gyan wrote on 10/15/2015, 6:20 AM
An update, hopefully, to elicit some fresh ideas:

So, my hardware guy took the comp to his office. Removed and dusted everything and reseated everything starting with the MoBo and it just started working! So, I bring it back and it works fine for 3 days.

But yesterday, same issue occurs again. So, he comes over, tries the usual tricks - single RAM, no GFX card, new CMOS battery..etc - no luck. Except when he sets the RTC jumper to clear memory and switches it on, the computer and case fan/lights remain on - no rapid powercycling. Of course, after setting the RTC jumper back to normal, the problem recurs. That should be a clue. Any ideas? He doesn't think it's a short.

2nd update: My engineer took the system and reports it's working fine at his office. Brought it back here, and it works fine here too! Doesn't seem to be an internal problem. Puzzle is, that none of the other devices connected to the same UPS show any problems, and the UPS hasn't made any unusual beeps.
Chienworks wrote on 10/15/2015, 7:48 AM
Check the voltage coming out of your UPS; it might be a little low. Don't believe the display on it, if it has one. Get a multitester and check it yourself. Many devices will operate just fine on 5 to 10% lower voltage, but some computer power supplies aren't as tolerant.
musicvid10 wrote on 10/15/2015, 8:37 AM
"

Check the voltage from the UPS with the computer turned off, then with it turned on and running 100% cpu/gpu. If it does drop 5%, that "may" be too much for some computers, especially those whose power supplies are already stressed from h/w upgrades.

Bliss Video Productions wrote on 10/15/2015, 8:39 AM
Does your computer run Windows 7? I'm wondering if you got the faulty Win7 update, which caused (among other things) constant rebooting?
Bliss Video Productions wrote on 10/15/2015, 8:45 AM
Stop your computer from automatically rebooting as the result of a crash.

Go to Computer>Settings (Or Control Panel>System) >Advanced System Settings. Go to the 'Advanced' tab, the 'Startup and Recovery' section, and click on 'Settings'. Un-check the 'Automatically restart' option, and save.

If your system crashes, rather than automatically rebooting you will get the 'blue screen of death', which will display an error code. That error code may help you or your engineer track down the problem.

Good luck!
Bliss Video Productions wrote on 10/15/2015, 8:48 AM
A clue might be in the fact that clearing the memory fixes the problem for a time.

You said he tried booting it with a single memory DIMM -- but the one he used might be bad. Bad memory can cause crashes and reboots. If you have more than one memory DIMM, he should try booting it with each one singly.