Post Install - Samsung 840 EVO SSD

SSD and OS reinstall notes

1.  Installation of SSD hardware was easy (I followed the instructions of a YouTube video on my iPad while installing the SSD).

2. I found that I could NOT use my restore image that I created when I first received the laptop.  Apparently, it will not install onto the SSD because my image is bigger than the drive itself?  The image is stored on an 8GB USB drive, but throws an error every time I try to use it to install the backed up factory install onto the SSD.  I used AlienRespawn to create it (but never tested it).  I used the factory restore CD that came with the R3 instead (very slow process compared to installing from a USB drive).

3.  I had an issue getting the SSD drive to show in the Windows drive install option section of the OS install.  I installed the SSD in the Drive 1 slot, but initially it wasn’t showing at all.  I went into the BIOS and switched the drive setup from RAID to AHCI, then tried again and the SSD drive showed as Drive #1.

4.  Later, after the install finished, I installed the SSD management software.  I followed it’s optimization instructions and saw that it stated that the drive setup should be set to RAID.  When I set it back to RAID, the install would no longer boot up.  I even tried letting Windows repair it, but it could not fix the issue.  Granted, there’s a BIOS prompt when you attempt to switch between the two settings...it states that switching could make the system not boot back up.  Next time, I won’t follow Samsung’s recommendations, at least regarding this setting.  I’m reinstalling Windows 7 again as I type this.

5.  I noticed that with a fresh install of Windows 7, none of the damned network devices work...at all.  It looks like I might have to download them onto a USB drive from another system to get them installed onto the R3.  [This was actually rather easy to fix.  I just went to Dell’s site (they have a list of M17x software, listed by revision #, that listed the specific driver I needed for the ethernet hardware)...I downloaded it to a spare USB drive, transferred it to the R3, then installed it...I instantly had internet access.]

6.  I’m using the following URL for instructions (other FAQs and help guides for the R3 did not work):  http://forum.notebookreview.com/alienware-17-m17x/562751-m17xr3-clean-install-ssd-instructions-recommendations.html  

This is the first one that worked.

7.  In hindsight, I could’ve bought Window 8.1 from Microcenter for $100 (but I was trying to cut costs). I do have a license for Windows 8 (and 8.1 was/is a free upgrade if you've v8 already), but I'd have had to download Win 8 again and I didn't want to spend any more time downloading, as I spent a great bit of time downloading all the damned security updates/patches for Win 7.

Some URLs of interest with this install:

• http://www.dell.com/support/troubleshooting/us/en/04/KCS/KcsArticles/ArticleView?c=us&l=en&s=bsd&docid=536193
• http://www.qca.qualcomm.com/resources/driverdownloads/
• http://www.sevenforums.com/tutorials/330-system-protection-turn-off.html

Thrustmaster T16000M and Windows 8

They don't mix.  I'm trying to fly planes in BF3 again and I didn't have this issue with Windows 7, but within Windows 8, I don't have full rudder control, even if I configure it within BF3.

I've downloaded these (2009_FFD_2.exe...based on the naming convention, these are rather old...Thrustmaster, fix this shit, please) drivers from Thrustmaster's support pages.  We'll see if that helps.

EDIT:  Yes, the drivers got the rudder to work.  BUT!  The drivers also appear to be causing some weird issues.  For example, whenever I get into a chopper, I occasionally hear my primary weapon being fired (ie, a sniper rifle, for example).  Also, once I exit the chopper, I can't sprint or reload a clip...the buttons will not work.  I experimented a bit, trying to determine where the issue lied until I realized that the joystick was the factor...when I disconnected the joystick, I found that I could sprint again, and reload a magazine.  the sniper firing while piloting a vehicle has stopped.  I captured footage of this happening.  It's a shame, because I was planning on practicing the upcoming DLC release of End Game.  I do not want to have to adapt to flying via mouse...screw that!  So, count this as a rather major negative in migrating to Windows 8...this did not occur with Windows 7.  Sure, this probably isn't the fault of Microsoft and is more than likely a Thrustmaster driver issue (that I'll report), but it ruins the experience of Windows 8 regardless.

Alienware: Upgraded to Windows 8 Pro

Last month, I saw several posted articles mentioning MS selling upgrades for Windows 8 Pro for $40 ($39.99, actually).  I bit.  Why?  Because it was a good price for an upgrade and if I found I didn't like Windows 8, I could always go back to Windows 7 with little money spent.

The install wasn't bad and wasn't the best either.  Since this was an upgrade and it is typically best to use a fresh install, I opted to restore my system back to factory configuration.  I did not want any issues with programs that I'd installed in Windows 7 not working in Windows 8.  The factory configuration wouldn't negate this but the factory configuration doesn't have as much installed either.  So, I whipped out my special flash drive with the copy of the factory image and installed.  I then immediately installed Windows 8 from flash drive as well (to speed up the install).  It was rather cumbersome and long, even via flash drive, but it installed flawlessly.

Afterward, I checked to see what wasn't running against the listing of what Windows 8 had flagged that might not work.  Alien Respawn wasn't working.  I'll have to get a Win8-specific copy of that and install it.  Everything else worked.

I then installed my free copy of Windows 8 Media Center.  When I entered the product key, it conflicted with the product key for Windows 8 Pro, which I thought was odd.  Many people were complaining of the same issue and there were some solutions but none worked for me.  Apparently, the system didn't like being upgraded then immediately having Media Center added.  So, I had to call the automated Microsoft number listed in System Information (I believe...I'll check that and correct myself if I'm wrong).  I called the number and followed the instructions.  I had to key in 8 or 9 five-digit codes via phone keypad, then the automated system read back 8 or 9 five-digit codes that I keyed into the config window.  After I did that, the system properly registered!

I did NOT like Metro.  I know there's a way to remove it, but I'm now getting used to it and I think it is oddly intuitive.  I'll keep using it for now.  What I also like is the Windows 7 shell...I can fall back to that when I feel the need.  Chrome only works within the Windows 7 shell, which I don't like, but it's not a huge deal.

The system appears to be quite a deal quicker, but I've never benchmarked Windows 7 on this system and haven't benchmarked Windows 8 either.  Note that I'm not using an SSD (I'm running two 750GB drives in RAID0).  SSD will not help me all that much...it's not going to make my gameplay any faster (only upload faster, but really, that's nota huge deal for me).  One day, I'll go the SSD route, but I want lots of drive space and SSDs aren't cutting it in that department yet.

So, I'm keeping Windows 8 for now.  I may even reinstall it just to get a pristine image of it captured onto flash drive (backup copy).