Windows 7 build 6801 on the Desktop

I removed Windows 7 from the Laptop for trying Windows Vista x64 so I didn’t have Windows 7 installed anywhere. I am going to install Windows 7 build 6801 on the Desktop while waiting for the public beta.

Reordered the HDD boot sequence again.

  1. ST3500 - WINDOWS/DOCS
  2. WD7500JB - BACKUP
  3. ST5750 - SERVER
  4. WD3000JB – MUSIC

The only difference from last time is that I swapped BACKUP and WINDOWS/DOCS. I probably shouldn’t have done that because I realized it doesn’t make any difference to how Windows 7 setup lists the HDDs. It does

  1. PATA0 = SERVER
  2. PATA1 = MUSIC
  3. SATA0 = BACKUP
  4. SATA1 = WINDOWS/DOCS

no matter what your HDD boot order is.

So I have Windows XP SP3 installed in BACKUP. You have to understand the drive letter mess-up Windows Vista or 7 does when you install Windows, especially when you are using Autounattend.xml to relocate your Users folder. Because Windows 7 setup follows the PATA and SATA sequence I listed above, the setup would initially show you that it is going to assign drive letters this way:

  1. C: SERVER
  2. D: MUSIC
  3. E: BACKUP
  4. F: WINDOWS
  5. G: DOCS

Suppose you are installing Windows 7 to WINDOWS HDD and if you configure your Autounattend.xml to follow these drive letters, then you are stuffed. After installing Windows, the WINDOWS HDD will take the drive letter C: so that could change the drive letter for DOCS HDD. After installing Windows:

  1. D: SERVER
  2. E: MUSIC
  3. F: BACKUP
  4. C: WINDOWS
  5. G: DOCS

OK that time DOCS drive letter didn’t change because initially DOCS was listed after WINDOWS. The logic still remains. Windows 7 build 6801 did something strange when I installed yesterday. It fully ignored assigning a drive letter to BACKUP. So BACKUP wasn’t even listed in Computer. That made DOCS to be F: rather than G: so my Autounattend.xml rendered useless again. This is why I had to reinstall it today.

Today’s reinstall didn’t ignore BACKUP. So this time Users folder was created in BACKUP rather than DOCS. It wasn’t right again! I reverted back to the old HDD boot sequence:

  1. WD7500JB - BACKUP
  2. ST3500 - WINDOWS/DOCS
  3. ST5750 - SERVER
  4. WD3000JB – MUSIC

This is the default boot sequence from BIOS and I think I will allow this permanently. I rebooted and I got Windows XP SP3 back. It doesn’t know anything about the Windows 7 build 6801 installation I did to WINDOWS HDD.

Comments

Post a Comment

Popular posts from this blog

Tagging Classic Music albums with Mp3tag for iTunes and Last.fm

Image
I realized a lot of people having trouble with tagging Classic music. Initially, I got into Classical music to take up this challenge but now I am hooked into it because of its nice sophisticated melodies. There has to be a very straight forward way of tagging music. The ID3v2 specification provides us frames for the following tags that can be used to organize classical music:   Artist AlbumArtist Conductor OriginalArtist Composer Album Name   My goal is to devise a plan to fit all of these tags into Classical music appropriately, so that the Classic music composers will appear in Last.fm statistics music will be organized and displayed well in iTunes   The primary focus is given to how the music is organized. This means tagging conventions for track names is not one of the primary concerns in this article. First we familiarise ourselves with the ID3v2 frames for the tags above.   TPE1 The 'Lead artist/Lead performer/S
Read more

DVD to WMV9 Guide 4.5

Version 4.5 is being designed using Dreamweaver MX 2004 to make the site 100% compatible with Netscape 7.0 and Opera 7.0. Until the announcement of DVD to WMV9 Guide 4.5, there will be no updates to DVD to WMV9 Guide. Visit DVD to WMV9 Version 4.4
Read more

DVD2WMV Encoder 1.0 ALPHA Started

Now it's under active development. The main challenge is WMEncoder refusing AviSynth script files. While writing the CCE to WMV guide this idea was to born to create a tool to calculate the total time of a movie. This will be added to DVD2WMV Encoder -- not as a standalone executable but integrated, so that the values can be used by the WM9 Bitrate Calulator part to determine the target Video Bitrate. 0:41:38 + 0:39:15 + 0:39:11 = 0:119:64 = 1:59:64 = 1:60:04 = 2:00:04
Read more