Installed new Boot drive...where's Vegas ?

winrockpost wrote on 9/1/2015, 7:18 PM

Pretty sure you have to run them from from the windows drive/ c

wwaag wrote on 9/1/2015, 7:24 PM

AFAIK, if you just did a clean install of the operating system on your new SSD (now drive c:), then you'll have to re-install all of your programs onto the new drive. To run programs on your old drive, you would have to boot into that drive, which kinda defeats the purpose of a new SSD.

wwaag

FoskeyMedia wrote on 9/1/2015, 7:36 PM

I still want the applications installed on and running from the H drive...so I don't eat up C drive space. If I re-install.. i would still just install it onto the H drive,

Chienworks wrote on 9/1/2015, 8:37 PM

Windows is pretty restricted this way. You cannot simply move an installed application around. If you want it to run from H: then you have to install it there.

Just curious, but how often do you boot your computer that it really makes that much difference to you how fast it boots? I'd think you'd be much more concerned about how fast programs start up, since by definition you have to start them at least as often as you boot, and probably much much more often.

For me, system boots tend to happen a few times a year, while i launch Vegas maybe once or twice a week or so. In the grand scheme of things, making all that happen faster wouldn't really matter to me in the slightest since the time involved in launch and booting is practically nothing compared to the time spent using the software.

FoskeyMedia wrote on 9/1/2015, 8:50 PM

Intetestingly enough I had (almost) the same conversation with a friend today. He's a school teacher/home user and I told him he really wasn't gaining much adding an SSD to his old I3 laptop. He says Windows takes a long time to boot... so it's his money if it's worth it.

And yes...booting my computer isn't nearly as important as booting Vegas. I plan on installing Vegas and DVD Arch and a few other programs on C(only the producion important ones..don't want to take up too much space). The rest I can install and run from H. I just didn't want to have to go through the hassell of installing ALL of those other programs.

I just installed Vegas on C...and now of course I have to reassociate some of my files. I guess I'll just plug the "old C" drive in and work from there until I retire anything active. Migrate the new drive in slowly.
Thoughts ?

TheHappyFriar wrote on 9/2/2015, 5:43 AM

You can install your software on any drive you want, just that most software needs to be installed (the software is designed that way, it's not an OS thing). You will most likely need to choose "custom" install to pick the drive.

For example, I have Windows & programs on C, games on G. D is my editing drive and E is my external that stores projects & some audio/graphics.

Win 8.1 on my IDE drive, AMD phenom 9600 (2007) took 30 seconds to be in the desktop from a cold boot. Win 10 takes ~60 seconds on the same hardware. My wife's Win 7 laptop takes ~60-75 seconds from cold boot to desktop.

FoskeyMedia wrote on 9/2/2015, 10:13 AM

Thanks.. That's what I thought.. just didn't know if there was a work around. Think I'll leave both drives in and chose upon boot up if I want old (HDD) system or new (SDD) untill I migrate everything over. Once migrated...I was thinking about deleting Windows from the old HDD drive for space. Now I'm thinking....maybe I'll keep it just incase I need to access the old system again.

Speed of cold boot isn't a real concern for me (which is making me think,,, did I waste $$ on this SSD drive and should have spent it on a bigger HDD and gotten more space). As Chien said...I don't boot the desktop cold that often (even if it's once a day that's not much...I can get a soda or check what's on TV while it's booting). On a laptop it's a much different story. (boots more frequently),

TheHappyFriar wrote on 9/2/2015, 2:19 PM

With the Win 8.1 fast boot time I started to use hibernate vs sleep. Saved power & still kept my program & Win state when I turned it back on. Only reason to not cold boot is to save time.

ushere wrote on 9/2/2015, 7:52 PM

a. ssd certainly speeds up boot, but how often do you need to boot during the day?

b. ssd certainly speeds up prog launch - that's the reason i use them in all my equipment (rather than a.)

c. even with ALL my stuff loaded (and there's a lot of stuff) i've still got a lot of free space on a 250gb ssd.

d. even though you can install progs (using custom install) i think it's a very bad idea indeed. i did this many years ago and found that updates, etc., sometimes wouldn't / couldn't install. frankly it was a mess.

i like a simple life ;-)

FoskeyMedia wrote on 9/2/2015, 8:28 PM

Are you saying updates couldn't/wouldn't install on SSD or on a program not on the C drive ?

ushere wrote on 9/2/2015, 9:04 PM

never had any update problems with ssd - just like any hd.

HOWEVER - many updates used to (probably still do) expect to find the program in the default install location - which is normally c:

TheHappyFriar wrote on 9/2/2015, 10:07 PM

Any installed program I've never had an update not detect where it should go. Stuff I didn't need to install to run had issues, but those were the exception not the rule.

I'm currently re-setting up my Win10 machine. Just got the new MB+CPU+PSU+RAM today. Still moving things around to the drives they belong to, but I've done this so much before I'm expecting 0 trouble.

ushere wrote on 9/3/2015, 2:42 AM

oh thf, I'm expecting 0 trouble

i only wish i had your confidence even after 30+ years of computer use ;-)

TheHappyFriar wrote on 9/3/2015, 8:56 PM

I've only got ~20 but so far no problems.

FoskeyMedia wrote on 9/6/2015, 1:46 AM

WAIT A MINUTE~~~~~~
So.. I just thought of something ( still sorting all of this out mentally) :
1) I have original HDD with programs installed on it,
2) Get a SSD, make it my primary with OS
3) Make my old HDD a storage drive (don't wipe it clean) Let's say it's not my "H" drive.
4) Fresh install everything from the new OS on the SSD, but install to the new "H" drive for space
5) So now I have programs installed 2x on the old HDD "H" drive. The original instal and the new install from the new OS install.

I would imagine that would create havoc with Windows.
I've read a few places (including here) that you can install OS on primary drive and programs on secondary. I'm sure it would be better to install OS and programs on the pr\imary, but I've heard it's not always done and doesn't really make s difference. I guess I'm trying to 'preserve' my original drive and not have to deal with transfering back and forth. Does this make sense or am I confusing ??

I guess the question(s) is,,,,,do I need to wipe the old drive clean ? Is it possible/practical to have the same program installed twice on the same drive but with different targeting drives ?

diverG wrote on 9/6/2015, 5:29 AM

I take it that you cannot run Vegas from your new SSD and you still have your original boot drive. Can you still boot from your original HDD and is it functioning normally?

If so is your original HDD set up UEFI or MBR. If UEFI structure why not simply clone you old HDD to the SSD.

Would suggest doing a 'cleandisk' from within windows and taking out all but the last couple of restore points before you clone.
G

TheHappyFriar wrote on 9/6/2015, 6:05 AM

Any old installs on an old drive won't be recognized by windows so there's no need to worry about them. If there's no intention to use anything on the old drive then just format it & reuse it.

My philosophy on drives is this: keep OS & programs on one drive (boot), plus other stuff (pictures, itunes library, etc). I want all my captured footage on the fastest drive I got. If possible, I have another fast drive to render to I keep my projects on my external, along with my stock audio files.

FoskeyMedia wrote on 9/6/2015, 4:21 PM

I intend to use the OLD drive as a secondary drive, which is why I don't want to wipe it clean. It has all of my old programs and data on it.

I want to reinstall all of my programs so that I can access them from my NEW PRIMARY drive, but I want to install them onto the OLD drive (which already has them under a previous installation) to reserve space on the NEW Boot drive.

ushere wrote on 9/6/2015, 6:48 PM

how big is your new ssd? if >120gb you're safe to install all os AND progs. doing the way you suggest is pretty pointless otherwise.

FoskeyMedia wrote on 9/6/2015, 8:51 PM

There's not enough space on the primary drive....that's why I'm trying to find out if 2 installations of the same program on the same drive is possible or will it mess up windows.

ushere wrote on 9/6/2015, 10:20 PM

again, how big is your primary drive?

i have an 'old' 120gb ssd on my nle rig that is loaded with more than enough nle's, graphics, audio software to sink the proverbial battleship - and i still have around 20gb free.

don't quite understand 2 x installs on the same drive? do you mean to have a dual booting hd?

Geoff_Wood wrote on 9/6/2015, 10:32 PM

The 'data' on your old drive is simple to retain. There is nothing to lose wiping the old Program Files folder (etc) - just not folder(s) where your data is stored (probably now H:\Documents and Settings\ ).

Copy your VST folders first though, as these do not require 'installation' as such. Just their presence (in the right folder) is all that is required. They are in the Program Files folder (and P..F... (X86) folder).

THE PROGRAMS ARE NOT [B]INSTALLED[/B] IN YOU NEW wINDOWS INSTALLATION (SIMPLY BEING PRESENT IS NOT THE SAME AS BEING 'INSTALLED' AND YOUR NEW wINDOWS INSTALL WON'T EVEN KNOW THAT THEY EXIST) , SO AFTER YOU GET RID OF THE OLD PROGRAMS FOLDER (MAYBE TEMPORARILY *RENAME* THE FOLDER FOR REASSURANCE instead of deleting) - ooops capslock - you must re-install them, either to your new faster C: (best), or you big older slower H drive.

Then when everything is running happily again, delete the old Program Files folder.

geoff

FoskeyMedia wrote on 9/10/2015, 11:17 PM

The why is not really the question. I'm not looking to explore alternative solutions here..would take too much time to explain and distract. I'm just tryibng to find out CAN it be done.

IF (for whatever reason) you have multiple boot drives... and IF (for whatever reason) you need or want to install your programs on another drive ( so for example boot drive C has SVP installed on drive K and boot drive E has SVP installed on Drive K) and 2 seperate instances of SVP, or any program, exist on the same drive without Windows having an anxiety attack?

MSmart wrote on 9/11/2015, 2:40 AM

and 2 seperate instances of SVP, or any program, exist on the same drive

One set of program files in the same folder/directory path? Or two sets of the program files in separate folder/directory paths?

( so for example boot drive C has SVP installed on drive K

Basic, no problem. Let's assume you installed it in K:\Programs\Sony\Vegas Pro 12.0. The registry entries are created on the C drive with entries pointed to that folder path on the K drive.

and boot drive E has SVP installed on Drive K)

If you're using the same folder as above, the question is whether or not the installation program will allow SVP to be installed over the same files or will it complain that the files already exist. If the files can be overwritten, great. Registry entries will be created on the E drive pointing to the same folder path on the K drive.

If the program files can't be overwritten, you'll have to install the second instance of SVP in say K:\Programs2\Sony\Vegas Pro 12.0, then the installation should fly with no issues. The registry entries will be created on the E drive pointing to the second folder path on the K drive.

Remember, it's not just about where the files are installed to, it's the registry entries that are created on the boot drive. Separate boot drives, separate registry entries that hopefully can point to one program folder path on the K drive.