Primary OS, loving it so far.
Primary OS, loving it so far.
I *was* going to try dual booting Windows 8CP side by side with my existing Windows 7 x64 partition, but right now I'm running my laptop with a 120 GB OCZ Vertex3 SSD (about 66 GB free on it, OS + apps, which should be plenty), but I'm concerned that the Windows 8 partition would end up misaligned (starting sector offset of the partition won't be divisible by 4096), which could cause major performance and wear issues on the SSD.
Besides, it's true: it really is hard going back to the old spinner drive technology, after running with one of these things for a few months, as I have been. They're just so sick st00pid FAST!
Here's a screen scrape of an ATTO disk drive benchmark run I did a couple days ago:
516 MB/s writes, 557 MB/s reads - crazy
I think you are looking at the wrong nums. The 4K nums count for the OS - and even those do not mean a lot because the OS does not R/W a lot. All the performance comes from the 0.1ms access time.
And if you make a second partition for Windows 8 on the SSD, you need not worry about alignment. It will be well aligned because it is MBs (even GBs) away from the beginning of the disk. Convert that to K-bytes and you can always divide by 4.
On my laptop, I run Windows 8 on a 90GB OCZ Vertex in double boot. But I really do not like it too much because you need to go thru the BIOS twice to get to Win7. On my desktop I put it into Virtual Box (also on a SSD). That works a lot better and I can keep running Win7 and Windows 8 in paralell all day long.
Last edited by whs; 06 Mar 2012 at 06:46 PM.
I guess you have 2 options:
1. you can install on a seperate drive (internal or external) by disconnecting all other drives. Then you switch the boot order via the BIOS. That is extremely convenient and dows not mess up your bootmgr. On one system I used to run Windows 8 DP from an eSata drive like this - Windows 8 CP I put into Virtual Box which is optimal for playing with it.
2. you install on a seperate drive and leave all drives connected. Then the installer will put the Windows 8 BCD into your current bootmgr and you have a double boot. I have done a dual boot on another system (but on the same SSD). But it is a real pain. My boot time increased 4-fold for Windows 8 and 10-fold for Win7 (as compared to when Win7 was alone). I will dismantle this arrangement and put it on an external drive.
I have a multi-booting system - XP on one disk, and Windows 7 x86,Windows7 x64, Windows 8 CTP x86 and Windows 8 CTP x64, as well as Windows 2000, and various Windows Embedded and Thin PC installations each on their own partitions.
Because these partitions are limited in size to about 15GB, I could not use the Windows 8 setup program which requires at least 20GB to proceed, so I used Imagex.exe to apply the install.wim for Windows 8 from the .iso download mounted as a virtual DVD drive using Virtual CloneDrive (no need in Windows 8 - mounting .isos is a welcome built-in feature)
The (elevated) command was
>imagex /apply R:\sources\install.wim 1 J:
where R: was the virtual DVD drive, and J: was the partition I had just formatted - it previously contained a Windows 7 embedded installation, and I did not need to edit the BCD - it just booted straight into the new OS from the old boot menu entry. If it has not been used for an OS before, I would have used BCDBOOT as follows:
>bcdboot J:\windows /s c:
This just adds an entry to the boot menu on the C: drive where the boot folder resides - when Windows 8 boots, it takes the C: drive letter for its own.
Imagex is very fast - takes about 10 minutes to apply the image to the partition, then it takes another 20 minutes for Windows to prepare the installation.
Imagex.exe comes with the WAIK - the Windows Automated Installation Kit, or the Windows Embedded Standard Toolkit or Image Builder downloads from Microsoft - but they are all huge multi GB downloads for a tiny little executable.
Download: Windows® AIK for Windows® 7 - Microsoft Download Center - Download Details
Download Windows Embedded Standard 7 | Product Information and Trials
Imagex.exe may already be hiding on your PC if your OEM has a recovery partition on your disk. It may be hidden within the boot.wim image which contains a WinPE installation, under sources\PETools\ or on some other path. If you have 7-Zip File Manager, it is easy to find and extract stuff buried in nested archive formats like this. Download
I have recently come across SmartWIM from SmartDeploy OS Deployment Products which seems to be functionally similar to Imagex. It is a free download for personal use, and uses the Microsoft wimgapi.dll Windows Imaging technology, either from the command prompt or in a scripted environment. It is available after a short registration form is completed and is a tiny download, so it might be more convenient than the Microsoft download.
Interesting you got it to work .
I always install that way.
I tried to install wcp like that also - no go.
In the end I had to resort to installing from the dvd.
There are a few variables at play here. There are 32- and 64-bit versions of Imagex.exe and Wimgapi.dll for a start. Then there are probably older and newer versions of Imagex.exe knocking around too.
Here are the details of the versions I had no apparent problems with:
And yeah, I still use Excel 97 (and Word 97)
Having now read all 11 pages in this thread - it is fairly obvious that the Windows 8 boot on my machine is just chainloaded from the Windows 7 bootloader already installed - so no 'return to bios, reboot from 7' issues for me. Just the windows 7 boot menu and straight in. It also means I am not getting the full experience :lol - but I intend to install on an old Packard Bell machine from 2001 that I found dumped to see how retro 8 will go.
Last edited by fafhrd; 11 Mar 2012 at 06:22 AM.
64 bit Dual boot