Re: Sucessful install but boot failure
- From: "Dave Patrick" <DSPatrick@xxxxxxxxxxxxxxxx>
- Date: Mon, 10 Apr 2006 11:18:35 -0600
Yes with no controller bios enabled you would need to copy the correct
manufacturer controller driver to the system partition but renamed to
ntbootdd.sys then use scsi syntax in place of multi in boot.ini
--
Regards,
Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
"Julian Ratcliffe" wrote:
|
| The issue was resolved by making sure that the OPROM for the SCSI
| controller was executed when the install was booting from the CD.
| Windows was smart enough to continue with the install if it was not
| there but this led to an incosistency in accessing the disk when the OS
| tried to boot using the SCSI OPROM after the install.
|
| Julian Ratcliffe wrote:
| >
| > The driver is supported in the setup (LSI 53C1020 U320), I've also tried
| > adding an alternative driver via the F6 method. This is Windows Server
| > 2003 R2 x64 Enterprise Edition. I suspect something inthe MBR.
.
- References:
- Sucessful install but boot failure
- From: Julian Ratcliffe
- Re: Sucessful install but boot failure
- From: Dave Patrick
- Re: Sucessful install but boot failure
- From: Julian Ratcliffe
- Re: Sucessful install but boot failure
- From: Julian Ratcliffe
- Sucessful install but boot failure
- Prev by Date: Re: Sucessful install but boot failure
- Next by Date: Re: Win2k domain to Win2003
- Previous by thread: Re: Sucessful install but boot failure
- Next by thread: Targeting which ADSL connection to use
- Index(es):
Relevant Pages
|
