http://www.backupassist.com/blog/support/esata-and-wbadmin-support/ BackupAssist blog Sun, 22 Jan 2012 22:14:33 +0000 hourly 1 http://wordpress.org/?v=3.3 http://www.backupassist.com/blog/support/esata-and-wbadmin-support/comment-page-1/#comment-82 Raymond Sun, 25 Jan 2009 06:01:30 +0000 http://www.backupassist.com/blog/?p=36#comment-82 Graeme, the article says he was using Windows Server 2008. Am I missing something? Graeme, the article says he was using Windows Server 2008. Am I missing something?

]]> http://www.backupassist.com/blog/support/esata-and-wbadmin-support/comment-page-1/#comment-81 Raymond Sun, 25 Jan 2009 06:01:03 +0000 http://www.backupassist.com/blog/?p=36#comment-81 Graeme, the article says he was using Windows Server 2008. Am I missing something? Graeme, the article says he was using Windows Server 2008. Am I missing something?

]]> http://www.backupassist.com/blog/support/esata-and-wbadmin-support/comment-page-1/#comment-55 Graeme Thu, 13 Nov 2008 03:44:21 +0000 http://www.backupassist.com/blog/?p=36#comment-55 THe BSOD occurs after enabling AHCI in the bios because the AHCI driver has been disabled by the WIndows 2003 OS. You can override this disable by a change to the registry. This problem does not exist for Windows 2008 as it checks during the boot process whether an AHCI driver is required. Alternatively, if you do a Windows 2003 or 2008 instal with AHCI enabled then all will be OK THe BSOD occurs after enabling AHCI in the bios because the AHCI driver has been disabled by the WIndows 2003 OS. You can override this disable by a change to the registry. This problem does not exist for Windows 2008 as it checks during the boot process whether an AHCI driver is required. Alternatively, if you do a Windows 2003 or 2008 instal with AHCI enabled then all will be OK

]]>