Need Advice on Dedicated DAW setup
- Thread starter KAI
- Start date
blueprintstudios
New member
otpp : you there? i'd like to know too. actually I do, but just wondering if your methods are the same as mine.
Cheez
Moderator
Installation the same one copy of Windows into one PC is not a problem. Just install them into different partitions. The QUESTION is whether that is the best for a DAW. I'm still unsure whether the other installations of the same copy of Windows in the same PC (even though they are in different partitions) links the registry to the first partition installation. If so, the system is not optimized.
I know for sure installing 2 different copies of Windows into one PC doesn't link the registry - they are true separate OS. Is this true for one copy of Windows? Please, somebody confirm this.
I know for sure installing 2 different copies of Windows into one PC doesn't link the registry - they are true separate OS. Is this true for one copy of Windows? Please, somebody confirm this.
Personally I don't see why anyone would want to install more than one copy of windows because from my standpoint, windoze ain't worth it.. but moving right along...
The registries are not linked because they are stored in a file local to that partition. In fact, windows and linux can have multiple OS installations in just ONE partition too but to be honest, it's a pain that is only worth the effort in special circumstances (separate registries are stored in installation specific folders (bare minimum is each installation will have it's own X:\Windows folder -> X:\Windows, X:\Windows.1, X:\Windows.2).
blueprintstudios
New member
ok this is what I THINK i remember from my past experience.
install windows on C:..
normal..
after done.. boot cd again.
install windows on D: partition
i get a dual boot prompt in C: and D:.
registry wise i believe they don't share. cos I installed nonsense in C: and then nonsense B in D: , they're seperated.
but the problem is, sometimes you tend to mix up installing in C:\program files or D:\program files?? then you start messing up your pc heheh..
install windows on C:..
normal..
after done.. boot cd again.
install windows on D: partition
i get a dual boot prompt in C: and D:.
registry wise i believe they don't share. cos I installed nonsense in C: and then nonsense B in D: , they're seperated.
but the problem is, sometimes you tend to mix up installing in C:\program files or D:\program files?? then you start messing up your pc heheh..
Cheez
Moderator
Blueprintstudios, mixing up installation partition usually doesn't happen since by default, the installation software prompts you to install in the drive the OS is installed. So if you are running partition D for windows, then installing software should automatically prompt you to install in D:. Unless, of course, registry is somehow linked...
But good to hear that it's not linked. I recall having problems with that in the past, causing me to use Home and Pro in one machine. That means saving money!!!
Firethorn, separate Windows is crucial to a DAW machine. DAW need to be dedicated to DAW software - that means it has only DAW software and no other mess in it (not even internet explorer). The registry must be extremely clean. Then the system is optimised for DAW which taxes quite a bit of RAM and CPU resources. You also cannot any instability in the system esp for live performance or middle of a big project. My DAW is totally stripped out of IE such that the GUI looks like Windows 98 - all the shell is removed. And it's amazingly fast and stable.
The problem is not everybody can afford multiple PCs and notebooks. So the way around that would be 2 installations of Windows in different partitions - one for everyday purposes, and one for DAW.
But good to hear that it's not linked. I recall having problems with that in the past, causing me to use Home and Pro in one machine. That means saving money!!!
Firethorn, separate Windows is crucial to a DAW machine. DAW need to be dedicated to DAW software - that means it has only DAW software and no other mess in it (not even internet explorer). The registry must be extremely clean. Then the system is optimised for DAW which taxes quite a bit of RAM and CPU resources. You also cannot any instability in the system esp for live performance or middle of a big project. My DAW is totally stripped out of IE such that the GUI looks like Windows 98 - all the shell is removed. And it's amazingly fast and stable.
The problem is not everybody can afford multiple PCs and notebooks. So the way around that would be 2 installations of Windows in different partitions - one for everyday purposes, and one for DAW.
blueprintstudios
New member
cheez : well some softwares setup.exe they don't have that %systemroot% thingy, they assume that it will ALWAYS be installed to C:\. thats how i get mixed up the last time.
so safe to say the registry is not linked.unless you mess up with the installation process of softwares.
so safe to say the registry is not linked.unless you mess up with the installation process of softwares.
gutturalpiss
New member
That is the problem, many applications are hardcoded with C:\ and I'm not talking about the installation files which you're able to mess around with and provide your own paths for during the installation prompt. The system files and registry add/remove/edit functions (which is what a Windows install is basically) do not bother, they directly write to the traditional C drive.
More than one installation of the same operating system (multiple instances of the same core libraries, headers, executables) in the same partition is not a sane or recognized practice in any OS, and you can't really call it "installing the same OS multiple times in the same partition". In Linux eg. /dev/sda1 can have only one / mount point including /boot. Well, one can of course chroot, say /x86 becomes the 32-bit root in a 64-bit system on demand. Then there are symlinks and path variables, so you can export PATH=whatever and you can dynamically be superman.
More than one installation of the same operating system (multiple instances of the same core libraries, headers, executables) in the same partition is not a sane or recognized practice in any OS, and you can't really call it "installing the same OS multiple times in the same partition". In Linux eg. /dev/sda1 can have only one / mount point including /boot. Well, one can of course chroot, say /x86 becomes the 32-bit root in a 64-bit system on demand. Then there are symlinks and path variables, so you can export PATH=whatever and you can dynamically be superman.
Last edited:
Great info. Thanks all.
So is it confirm that the same window install in different partition WILL NOT share the same registry?
yep
er... applications hardcoded to point to C:\Drive? er... nt really..
Windows XP is a fairly intelligent OS and does not write to C:\Drive automatically. There is no way to write registry entries into a registry hive that has not been loaded (i.e. the other installations registry hive). The exception being if you use an external program to manually load the file into that program.
Installing the same OS multiples times in the same partition is not insane but it will cause problems in the long run for the novice user who may accidentally install the stuff into the wrong directory and will thus mess up the segregation between the OSes.
In Linux, /dev/sda1 can only have one mount point. This is true as you have pointed out. BUT. "It can only have one mount point at a time" is the more accurate statement. You can reboot your computer and change/choose a different mount point which is similar to installing and running multiple Windows OSes.
In the first place, the way Linux works and the way Windows works is fundamentally different so there shouldn't even have been any comparison. Linux can even mount a filesystem from a "file.ext".
Cheez
Moderator
My c: drive is for everyday use. D: drive is for DAW. And in the DAW partition, only DAW software is installed. Nothing else. And so far, no software (inlcuding Gigastudio) would force you to install onto C:. So... if such software exists, then it is most likely to be non-DAW software, so better to make C: your everyday partition. Other possibility is that the registry are somehow mixed and linked.
Here is where I thought the problem lies. Now I vaguely recalled why I used 2 different version of Windows for dual booting. If think when I installed the same copy of Windows in 2 partitions, software will somehow access C: drive registry and install stuff there even if you choose another partition to install. This is not just about same copy of Windows, but the exact same version of Windows (even if it is a different copy). This doesn't happen when I use 2 different versions of Windows (eg: Home and Pro). The partition the version of Windows is installed automatically becomes the default partition - d: or e: of f: of whatever, it doesn't matter.
Again, this is the distant past. Since I've used 2 different Windows (XP Home and Pro) for dual booting years ago, I've not not tried using the same version. So I cannot recall very clearly why I did that. And it's a hassle to try out - means lots of work reinstalling. If somebody has a new PC and wants to dual boot, maybe can try out and tell us once and for all.
James is getting a new PC. Maybe he can try out and tell us?
Here is where I thought the problem lies. Now I vaguely recalled why I used 2 different version of Windows for dual booting. If think when I installed the same copy of Windows in 2 partitions, software will somehow access C: drive registry and install stuff there even if you choose another partition to install. This is not just about same copy of Windows, but the exact same version of Windows (even if it is a different copy). This doesn't happen when I use 2 different versions of Windows (eg: Home and Pro). The partition the version of Windows is installed automatically becomes the default partition - d: or e: of f: of whatever, it doesn't matter.
Again, this is the distant past. Since I've used 2 different Windows (XP Home and Pro) for dual booting years ago, I've not not tried using the same version. So I cannot recall very clearly why I did that. And it's a hassle to try out - means lots of work reinstalling. If somebody has a new PC and wants to dual boot, maybe can try out and tell us once and for all.
James is getting a new PC. Maybe he can try out and tell us?
From personal experience as well as an understanding of how it should work, I would probably say that the wrong installation was loaded.
I once installed 3 copies of Windows XP (1 is updated all the way, 2 are basic). No problems.
It could be that both installations were installed without knowing the other was there and so ended up sharing files. Other than that, something really really funky had to be going on.
I once installed 3 copies of Windows XP (1 is updated all the way, 2 are basic). No problems.
It could be that both installations were installed without knowing the other was there and so ended up sharing files. Other than that, something really really funky had to be going on.
gutturalpiss
New member
Let me rephrase - functions of applications hardcoded. I will not mention names, however chances of an average person installing one of those is near none, but not none. Neither are the numbers of such application small. You can have one entirely different partition hosting a different install of the OS, but if you do have the C drive mounted the bug gets its chance. Don't really know Windows' software management details beyond this, but as you have mentioned there is no problem (generally) since each installation will have its own registry hive and most applications are not unorthodox to cross-source.
Nobody boots into a system to edit /etc/fstab everytime, nor have a script do that. Right, installation in different platforms is different. So we can say, multiple installations of the "operating system" do not occur in Linux. But hey wait, having a zillion kernels in /boot pretty much beats that. Thus, yes, Linux is totally not a subject here, nor is OS X.
Multiple "installations" of one OS in one partition is a little too uncommon to be sane. So I must have yet to come across a server implementing such a method. Well, depending on the definition of an install, it can be both possible and impossible. You can't expect the Windows installer to provide you with a prompt similar to "Install Windows to C:\ and keep previous installation"
Last edited:
Cheez
Moderator
Definitely not the wrong installation loaded. I've been installation and reinstalling entire Windows partitions more than 50 times in the past 7 years or so - and loading the wrong partition is something I wouldn't do. I vaguely recall in that installation, I experimented installation and reinstallation about 5-6 times (fresh installs - wipe everything out) to get the perfect dual boot for my DAW. I did it in various combinations. But then again, it was really many years ago. Getting old, so memory may not serve me very well... need to re-experiment again.
You can't expect the Windows installer to provide you with a prompt similar to "Install Windows to C:\ and keep previous installation"
Actually, there is. But it's more to the tune of "Windows has already previously been installed here, do you want to continue, bla bla, etc".
