v9 on win 7 64bit dual boot?

ushere wrote on 6/21/2009, 7:21 PM
ok, i'm about to take the plunge and dual boot my xp pro 32bit with win 7 rc 64bit. i really would like to have faster rending, etc.,

but, having past 60, i'm frankly nervous, i hate anything new, especially concerning computers.... so if any of you could reassure me about the following, i'd greatly appreciate it.

i have 2 hd's. (i've already created a win 7 partition on the 'system'), and all my data is on the second hd. (as is my acronis bk/up, etc.,) (most of my projects reside on ex hd's - if i'm working on one i usually have it (or transfer it) to my internal 2nd hd)

a. at the moment i have all 'my (whatever)' m$ folders pointing to d:data. will i be able to access them from both os's without problems, and is there anything i should be aware of?

b. is there anything i should be aware of setting-up, running, and using vegas from both os's. i realise i won't have all my plug'ins in 64bit, so i'll work around that if the need arises.

c. will events with 64bit plug in's (eg, new blue) work in 32 bit?

d. is there any difference in the veg's? ie. as long as i'm aware of the plugin factor, can i happily bounce between the two versions?

e. any feedback regarding experiences with this most welcome - i've read the various threads here, but they taper off quite quickly - as do those shouting about bugs!

thanks

leslie

Comments

MSK wrote on 6/23/2009, 3:02 PM
I've had Vegas 9 installed on Windows 7 x64 and have done a little testing. Seems to be pretty stable as far as I can tell.

From my own experience, regarding your system configuration I might recommend giving your second internal hard-drive a different drive letter. I've noticed on my own dual boot that my partitions on my primary hard drive want to be C: and D: always... For example, when I boot up to XP, XP thinks it's on C: and Vista partition is on D: --- and if I load up Vista, Vista thinks it's on C: and XP is on D:

Seems like assigning the secondary internal hard-drive away to a later drive letter (i.e., T:\data) might help to avoid drive paths getting screwy. Just a theory and I am a novice system builder so I could have made mistakes when creating my partitions.

As far as plugins go, I would recommend checking with the specific plug-in developers. There are a lot of problems when criss-crossing 32 bit and 64 bit plugs and apps.
ushere wrote on 6/23/2009, 4:38 PM
many thanks msk, most appreciated.

well, i went ahead and dual booted - remarkably simple really, and all so far, is working well (well, apart from 7 upgrading the giga network and then leaving me with no connection! a simple roll-back solved that though).

as far as drive letters went - in xp i have c: xp, d:data, e: win 7 on one drive, s:storage, w:work on the second.

after booting 7 i simply changed all my drive letters to match xp's (and in both os's hiding the other os's partition)

so far so good. it even picked up my canon printer and scanner, and loaded the latest drivers for them (as it did with my dual samsungs and nvidia card).

i must say i'm not find the new ui that appealing, but then again, i'm of an age where i hate change! the os system though seems very 'slick' and more robust than xp, but then again, i never bothered with vista....

later today i'm going to load photo cs4 and vegas - that's all i'm putting on at present - i'll look into a 'proper' setup once 7 is rtm'd.

i'll pop back later with an update if anyones interested.....

thanks

leslie
blink3times wrote on 6/23/2009, 5:35 PM
"I've noticed on my own dual boot that my partitions on my primary hard drive want to be C: and D: always... For example, when I boot up to XP, XP thinks it's on C: and Vista partition is on D: --- and if I load up Vista, Vista thinks it's on C: and XP is on D:"

In reality there is no such thing as "c drive" or "d drive"... etc. This is simply a labeling system that is used INSIDE a Microsoft OS. I say "inside" because the drive letters are written into the registry of the OS in question and therefore don't exist when 'that' particular copy of Microsoft os is not running. This is why your Microsoft boot loader lists drives in terms of dive numbers and partition numbers. The boot loader runs OUTSIDE the OS and as a result, does not know which one has been assigned as C... or D... or....
jabloomf1230 wrote on 6/23/2009, 7:28 PM
If you install W7 from within Vista, let's say to drive J:, it will always stay as drive J:. But if you install W7 by booting from the DVD, it will always be on drive C:, no matter what you do.
ushere wrote on 6/23/2009, 11:44 PM
ok, quick update if anyone's interested.....

both ps and v9 installed without problem (as did nb's sampler pack - a bit too tacky for my taste, but what the hell).

in comparison to xp pro 32 it's much snappier loading, the rendering lightening (yeah, unfortunately it always feels that way with new hardware the first few renders, then the, oh dear, it's SO SLOW factor starts creeping in).

due to the plug in problem i'm unlikely to use it for more than rendering and rough cutting at the moment, and will play with it, but not seriously till 7's rtm.

in the meantime, has anyone out there compared v9 32bit running on win 7 64 bit to how it runs on xp 32 bit? i know i could load it and see, but i've a rather large project on at the moment and really don't have the time.

again, i have to say how amazed i was with the simplicity of it all - whether 7 is actually vista sp 3, i have no idea, but it looks like i might be won over....