There have been a lot of comments on the post about creating a dual boot Windows system for Traktor. I wanted to start this thread to provide some additional information on the subject and also to answer any questions people might have.
First off. I should have entitled the article “Windows Optimization Part II - Dual Booting” and been clearer that this is a series of articles discussing options for Windows optimization. I started this series with the script as I considered it to be easy to implement and minimally invasive. This second article was intended to show people how to create a dual boot environment with the third article looking at what you can do to optimize one or more of those partitions. The article did however read like it was a one-off complete guide and I know this frustrated people. I will be much clearer going forward!
Each of these articles are designed to provide you with options. It is rare that there is only one way to solve a specific problem in Windows and the dual boot method is just one option that has proven to be very reliable. I made the decision to provide a certain level of detail around this option rather than summarize multiple options where there wouldnt have been the opportunity to provide any useable detail. We may cover these other options in more detail in the future.
Shrink Volume
Some of you commented on why I didn’t show how to shrink an existing partition, rather than deleting the existing partition and creating two (or more partitions) from scratch. Shrinking an existing volume certainly eliminates the need to back up your data and go through two Windows installs so it’s certainly an option worth considering.
There can be issues shrinking volumes when data exists on the drive that is unmovable. If Windows is unable to move certain chunks of data, it cannot create a new volume from an existing one. You may see data that is reported as unmovable when performing a defrag on your hard disk. The shrink option will check to see if there is unmovable data so it’s worth looking at prior to doing everything from scratch as I showed in the video.
Here’s a very quick video showing the Shrink Volume capability in Win7. There’s no sound as it’s just a quick screen cap that I took while writing this.
http://www.youtube.com/watch?v=VaZ8MRfnzxQ
RAID
It was suggested that perhaps RAID could be used as an alternative to dual boots. RAID is an industry standard redundancy model and provides different fail over and performance benefits depending on how it is configured. RAID does however require multiple physical disks which is rarely standard with most laptops. RAID is also designed to provide protection at the hardware level. Should a drive in a RAID array fail, the other drives will keep the system going until the faulty drive is replaced and rebuilt. My goal in the article was to provide a solution that enabled the user to switch operating systems should something fail at the software level and this is not something that RAID would be a fit for. The article also (albeit briefly) discussed the ability to run two boot partitions for different uses and again, RAID could be used for hardware redundancy but would not add any value at the logical level if the goal was to deliver two independent operating systems on the same machine.
Virtual Machines
There were multiple comments on using a single partition with a virtual machine. In fact, I used Oracle’s Virtual Box to set up the demo used in the video as it allowed me to show the install process. Virtual Box is free and very easy to use. Check out Virtual box here
In the scenario where the user is looking to run two different setups for different purposes, this is a great solution. You would install the Traktor etc on the local Windows system and then create a virtual machine for everything else. In the scenario where a Traktor backup was needed, this woudn’t be a viable solution as Traktor and virtual machines don’t play well together due to driver and latency issues.
The one area where virtual machines really win is when it comes to backups and rolling back. With a VM you can take a snapshot of your machine at a given point and easily roll back to it. Additionally, VMs exist as just a few files which make them very portable and quick to restore.
Multiple User/Boot Profiles
There were some great suggestions and really helpful information posted in the comments section about about using a single partition and multiple profiles. Windows 7 has certainly made it much easier to segregate environments within a single machine. As a personal choice I have not gone down this road. This is not to say it’s not a good option it’s just that I would rather put the work in upfront and create two separate environments and avoid some of the potential administrative overhead going forward. I am also not sure (as I have not set it up, nor tested it) how individual users might be effected should a central resource such as the registry encounter an error.
If someone out there has this running it would be great to get some additional feedback on how the system would work both in a primary-backup scenario as well as two separate environments for different uses.
Wifi and Drivers
We recommended that you you have your drivers to hand and used a wired net connection where possible. As mentioned in the comments, Win 7 is the first OS that enables Wifi set up as part of the install. Win 7 also does a far better job with assigning drivers than any of its predecessors. Having said all that, I took the “be-prepared” approach much like most Djs would went playing at a gig. Better to assume that the Wifi might drop out or the drivers might not be available and be wrong, than the other way around.
Separating Application and Content
Someone suggested creating two partitions and using one for the operating system and applications and the other for your music etc. This certainly provides the benefit of protecting your music should Windows become infected with a virus or encounter some other serious error. It won’t however provide you with a back up boot option or allow you to optimize each partition individually given that there is still only one operating system installed.
“Older” Systems
The two optimization articles published so far are not aimed exclusively at people with older or lower spec machines. These articles are aimed at anyone who wants to dedicate the greatest amount of resources they have available to Traktor. Whether these articles will be of any value to you will be based solely on how well your machine is performing with Traktor. If your machine works fine then these articles are not for you but for many people, it’s simply not an option to dump their existing machine and go out an buy a high spec PC or Mac.
Hopefully this has helped provide some additional clarity on the article. Please use this thread to ask follow up questions or provide additional relevant information on this subject. If you have commentary outside of that please start a separate thread so that this thread remains useful to anyone looking for help on the subject.
Thanks,
SmiTTTen
Bookmarks