Why can't I install Windows 2003 server checked build on HP Pr
in [Device Drivers]
|
From: May on 17 Apr 2008 13:34 Don, Thanks for the information. I have other question: When the setup stopped, I saw it was after copy "adpAHCI.sys". I was thinking to delete or replace this driver, but I couldn't find anything called "adpA*.*" on Windows Server 2003 checked build disk or setup directory on hard drive. Could you please tell me where is this file hiding? Thanks, Yaning "Don Burn" wrote: > The most likely cause is you are hitting an assert (there is one in ACPI.SYS > that seems to go off for many systems). I wrote an article about debugging > at install time, see http://www.osronline.com/article.cfm?id=264. The > simplest technique to get around this is connect windbg to com2 of the > Proliant and and on install press F8 when it says press F6 for adding > storage drivers. This will cause the system to run as if the following were > added to the boot.ini line: > > /debug /debugport=com2 /baudrate=19200 > > > -- > Don Burn (MVP, Windows DDK) > Windows 2k/XP/2k3 Filesystem and Driver Consulting > Website: http://www.windrvr.com > Blog: http://msmvps.com/blogs/WinDrvr > Remove StopSpam to reply > > > "May" <May(a)discussions.microsoft.com> wrote in message > news:C7734229-9067-4081-AABB-913FD697DBB8(a)microsoft.com... > > Hi, > > I don't know why I couldn't install Windows 2003 enterprise checked build > > server on HP Proliant server computer? > > There is no message, it hang at Windows Setup: > > "Setup is starting Windows" > > It is hang there fever. > > > > I have tried to disconnect network cable, it is not working. > > > > Any idea? > > > > Thanks, > > Yaning > > > > >
From: Don Burn on 17 Apr 2008 17:32 I have not encountered that one. Was this in the debugger, I find I can ride through the ASSERT's by continuing. -- Don Burn (MVP, Windows DDK) Windows 2k/XP/2k3 Filesystem and Driver Consulting Website: http://www.windrvr.com Blog: http://msmvps.com/blogs/WinDrvr Remove StopSpam to reply "May" <May(a)discussions.microsoft.com> wrote in message news:6A621A2C-A2FC-4F20-A87F-5C8C09B62808(a)microsoft.com... > Don, > Thanks for the information. > I have other question: > When the setup stopped, I saw it was after copy "adpAHCI.sys". I was > thinking to delete or replace this driver, but I couldn't find anything > called "adpA*.*" on Windows Server 2003 checked build disk or setup > directory > on hard drive. Could you please tell me where is this file hiding? > > Thanks, > > Yaning > > > "Don Burn" wrote: > >> The most likely cause is you are hitting an assert (there is one in >> ACPI.SYS >> that seems to go off for many systems). I wrote an article about >> debugging >> at install time, see http://www.osronline.com/article.cfm?id=264. The >> simplest technique to get around this is connect windbg to com2 of the >> Proliant and and on install press F8 when it says press F6 for adding >> storage drivers. This will cause the system to run as if the following >> were >> added to the boot.ini line: >> >> /debug /debugport=com2 /baudrate=19200 >> >> >> -- >> Don Burn (MVP, Windows DDK) >> Windows 2k/XP/2k3 Filesystem and Driver Consulting >> Website: http://www.windrvr.com >> Blog: http://msmvps.com/blogs/WinDrvr >> Remove StopSpam to reply >> >> >> "May" <May(a)discussions.microsoft.com> wrote in message >> news:C7734229-9067-4081-AABB-913FD697DBB8(a)microsoft.com... >> > Hi, >> > I don't know why I couldn't install Windows 2003 enterprise checked >> > build >> > server on HP Proliant server computer? >> > There is no message, it hang at Windows Setup: >> > "Setup is starting Windows" >> > It is hang there fever. >> > >> > I have tried to disconnect network cable, it is not working. >> > >> > Any idea? >> > >> > Thanks, >> > Yaning >> > >> >> >>
From: May on 18 Apr 2008 14:39 Don, 1. So far, I haven't connected to windbg since HP proviant has no way to set to COM2. (I set BIOS only enable COM2, but from device manager, I only see COM1, strange!, I pressed F8 when I see F6, but it is not working.). Why we must set it to COM2 not COM1? Is there other way to get into Windbg? 2. I was told that adpAHCI.sys is in driver.cab, but I still couldn't find it. I even opened all the *.cab on install CD, I still couldn't find adpAHCI.sys file. Where it could be? Thanks, Yaning "Don Burn" wrote: > I have not encountered that one. Was this in the debugger, I find I can > ride through the ASSERT's by continuing. > > > -- > Don Burn (MVP, Windows DDK) > Windows 2k/XP/2k3 Filesystem and Driver Consulting > Website: http://www.windrvr.com > Blog: http://msmvps.com/blogs/WinDrvr > Remove StopSpam to reply > > "May" <May(a)discussions.microsoft.com> wrote in message > news:6A621A2C-A2FC-4F20-A87F-5C8C09B62808(a)microsoft.com... > > Don, > > Thanks for the information. > > I have other question: > > When the setup stopped, I saw it was after copy "adpAHCI.sys". I was > > thinking to delete or replace this driver, but I couldn't find anything > > called "adpA*.*" on Windows Server 2003 checked build disk or setup > > directory > > on hard drive. Could you please tell me where is this file hiding? > > > > Thanks, > > > > Yaning > > > > > > "Don Burn" wrote: > > > >> The most likely cause is you are hitting an assert (there is one in > >> ACPI.SYS > >> that seems to go off for many systems). I wrote an article about > >> debugging > >> at install time, see http://www.osronline.com/article.cfm?id=264. The > >> simplest technique to get around this is connect windbg to com2 of the > >> Proliant and and on install press F8 when it says press F6 for adding > >> storage drivers. This will cause the system to run as if the following > >> were > >> added to the boot.ini line: > >> > >> /debug /debugport=com2 /baudrate=19200 > >> > >> > >> -- > >> Don Burn (MVP, Windows DDK) > >> Windows 2k/XP/2k3 Filesystem and Driver Consulting > >> Website: http://www.windrvr.com > >> Blog: http://msmvps.com/blogs/WinDrvr > >> Remove StopSpam to reply > >> > >> > >> "May" <May(a)discussions.microsoft.com> wrote in message > >> news:C7734229-9067-4081-AABB-913FD697DBB8(a)microsoft.com... > >> > Hi, > >> > I don't know why I couldn't install Windows 2003 enterprise checked > >> > build > >> > server on HP Proliant server computer? > >> > There is no message, it hang at Windows Setup: > >> > "Setup is starting Windows" > >> > It is hang there fever. > >> > > >> > I have tried to disconnect network cable, it is not working. > >> > > >> > Any idea? > >> > > >> > Thanks, > >> > Yaning > >> > > >> > >> > >> > > >
From: Don Burn on 18 Apr 2008 14:51 If you only have COM1 then you are going to use one of the other techniques from my article. I would recommend installing the free build, then doing a winnt32.exe based upgrade to the checked build and after winnt32 runs but before the reboot, modify txtsetup.sif to have the debug parameters you want. -- Don Burn (MVP, Windows DDK) Windows 2k/XP/2k3 Filesystem and Driver Consulting Website: http://www.windrvr.com Blog: http://msmvps.com/blogs/WinDrvr Remove StopSpam to reply "May" <May(a)discussions.microsoft.com> wrote in message news:CD0C3DF6-415E-4716-86BD-13EA8EB07CB4(a)microsoft.com... > Don, > 1. So far, I haven't connected to windbg since HP proviant has no way to > set > to COM2. (I set BIOS only enable COM2, but from device manager, I only see > COM1, strange!, I pressed F8 when I see F6, but it is not working.). Why > we > must set it to COM2 not COM1? Is there other way to get into Windbg? > > 2. I was told that adpAHCI.sys is in driver.cab, but I still couldn't find > it. I even opened all the *.cab on install CD, I still couldn't find > adpAHCI.sys file. Where it could be? > > Thanks, > > Yaning > > "Don Burn" wrote: > >> I have not encountered that one. Was this in the debugger, I find I can >> ride through the ASSERT's by continuing. >> >> >> -- >> Don Burn (MVP, Windows DDK) >> Windows 2k/XP/2k3 Filesystem and Driver Consulting >> Website: http://www.windrvr.com >> Blog: http://msmvps.com/blogs/WinDrvr >> Remove StopSpam to reply >> >> "May" <May(a)discussions.microsoft.com> wrote in message >> news:6A621A2C-A2FC-4F20-A87F-5C8C09B62808(a)microsoft.com... >> > Don, >> > Thanks for the information. >> > I have other question: >> > When the setup stopped, I saw it was after copy "adpAHCI.sys". I was >> > thinking to delete or replace this driver, but I couldn't find anything >> > called "adpA*.*" on Windows Server 2003 checked build disk or setup >> > directory >> > on hard drive. Could you please tell me where is this file hiding? >> > >> > Thanks, >> > >> > Yaning >> > >> > >> > "Don Burn" wrote: >> > >> >> The most likely cause is you are hitting an assert (there is one in >> >> ACPI.SYS >> >> that seems to go off for many systems). I wrote an article about >> >> debugging >> >> at install time, see http://www.osronline.com/article.cfm?id=264. The >> >> simplest technique to get around this is connect windbg to com2 of the >> >> Proliant and and on install press F8 when it says press F6 for adding >> >> storage drivers. This will cause the system to run as if the >> >> following >> >> were >> >> added to the boot.ini line: >> >> >> >> /debug /debugport=com2 /baudrate=19200 >> >> >> >> >> >> -- >> >> Don Burn (MVP, Windows DDK) >> >> Windows 2k/XP/2k3 Filesystem and Driver Consulting >> >> Website: http://www.windrvr.com >> >> Blog: http://msmvps.com/blogs/WinDrvr >> >> Remove StopSpam to reply >> >> >> >> >> >> "May" <May(a)discussions.microsoft.com> wrote in message >> >> news:C7734229-9067-4081-AABB-913FD697DBB8(a)microsoft.com... >> >> > Hi, >> >> > I don't know why I couldn't install Windows 2003 enterprise checked >> >> > build >> >> > server on HP Proliant server computer? >> >> > There is no message, it hang at Windows Setup: >> >> > "Setup is starting Windows" >> >> > It is hang there fever. >> >> > >> >> > I have tried to disconnect network cable, it is not working. >> >> > >> >> > Any idea? >> >> > >> >> > Thanks, >> >> > Yaning >> >> > >> >> >> >> >> >> >> >> >>
From: May on 18 Apr 2008 16:55 Don, I have followed your instructions, run the winnt32.exe first, d:\i386\WINNT32.exe /noreboot /debug4:install.log When a windows appear, I choice update. than modified txtsetup.sif in the directory c:\$WIN_NT$.~BT, OsLoadOptions = "/noguiboot /fastdetect /debug /baudrate=115200 /debugport=com1" OsLoadOptionsVar = '/fastdetect /debug /baudrate=115200 /debugport=com1" reboot computer, but the Windbg is still not connect and setup hang at Windows logo. I have tested two computers with HyperTerminal, the serial connection is working on both HyperTerminal. Windbg was setup long time ago when I connect to other computer and develop other Windows Driver, so Windbg setup on develop computer has no problem. So what you see is wrong here? Why my Windbg is still not ruining? I am trying to install Windows 2003 Server checked build, should I use: SetupDebugOptions="/fastdetect /debug /baudrate=115200 /debugport=com1" instead of OsLoadOptions and OsLoadOptionsVar? Thanks, Yaning "Don Burn" wrote: > If you only have COM1 then you are going to use one of the other techniques > from my article. I would recommend installing the free build, then doing a > winnt32.exe based upgrade to the checked build and after winnt32 runs but > before the reboot, modify txtsetup.sif to have the debug parameters you > want. > > > -- > Don Burn (MVP, Windows DDK) > Windows 2k/XP/2k3 Filesystem and Driver Consulting > Website: http://www.windrvr.com > Blog: http://msmvps.com/blogs/WinDrvr > Remove StopSpam to reply > > > "May" <May(a)discussions.microsoft.com> wrote in message > news:CD0C3DF6-415E-4716-86BD-13EA8EB07CB4(a)microsoft.com... > > Don, > > 1. So far, I haven't connected to windbg since HP proviant has no way to > > set > > to COM2. (I set BIOS only enable COM2, but from device manager, I only see > > COM1, strange!, I pressed F8 when I see F6, but it is not working.). Why > > we > > must set it to COM2 not COM1? Is there other way to get into Windbg? > > > > 2. I was told that adpAHCI.sys is in driver.cab, but I still couldn't find > > it. I even opened all the *.cab on install CD, I still couldn't find > > adpAHCI.sys file. Where it could be? > > > > Thanks, > > > > Yaning > > > > "Don Burn" wrote: > > > >> I have not encountered that one. Was this in the debugger, I find I can > >> ride through the ASSERT's by continuing. > >> > >> > >> -- > >> Don Burn (MVP, Windows DDK) > >> Windows 2k/XP/2k3 Filesystem and Driver Consulting > >> Website: http://www.windrvr.com > >> Blog: http://msmvps.com/blogs/WinDrvr > >> Remove StopSpam to reply > >> > >> "May" <May(a)discussions.microsoft.com> wrote in message > >> news:6A621A2C-A2FC-4F20-A87F-5C8C09B62808(a)microsoft.com... > >> > Don, > >> > Thanks for the information. > >> > I have other question: > >> > When the setup stopped, I saw it was after copy "adpAHCI.sys". I was > >> > thinking to delete or replace this driver, but I couldn't find anything > >> > called "adpA*.*" on Windows Server 2003 checked build disk or setup > >> > directory > >> > on hard drive. Could you please tell me where is this file hiding? > >> > > >> > Thanks, > >> > > >> > Yaning > >> > > >> > > >> > "Don Burn" wrote: > >> > > >> >> The most likely cause is you are hitting an assert (there is one in > >> >> ACPI.SYS > >> >> that seems to go off for many systems). I wrote an article about > >> >> debugging > >> >> at install time, see http://www.osronline.com/article.cfm?id=264. The > >> >> simplest technique to get around this is connect windbg to com2 of the > >> >> Proliant and and on install press F8 when it says press F6 for adding > >> >> storage drivers. This will cause the system to run as if the > >> >> following > >> >> were > >> >> added to the boot.ini line: > >> >> > >> >> /debug /debugport=com2 /baudrate=19200 > >> >> > >> >> > >> >> -- > >> >> Don Burn (MVP, Windows DDK) > >> >> Windows 2k/XP/2k3 Filesystem and Driver Consulting > >> >> Website: http://www.windrvr.com > >> >> Blog: http://msmvps.com/blogs/WinDrvr > >> >> Remove StopSpam to reply > >> >> > >> >> > >> >> "May" <May(a)discussions.microsoft.com> wrote in message > >> >> news:C7734229-9067-4081-AABB-913FD697DBB8(a)microsoft.com... > >> >> > Hi, > >> >> > I don't know why I couldn't install Windows 2003 enterprise checked > >> >> > build > >> >> > server on HP Proliant server computer? > >> >> > There is no message, it hang at Windows Setup: > >> >> > "Setup is starting Windows" > >> >> > It is hang there fever. > >> >> > > >> >> > I have tried to disconnect network cable, it is not working. > >> >> > > >> >> > Any idea? > >> >> > > >> >> > Thanks, > >> >> > Yaning > >> >> > > >> >> > >> >> > >> >> > >> > >> > >> > > >
|
Next
|
Last
Pages: 1 2 3 Prev: AsyncUI sample in Vista WDK Next: Synchronization on multiple USB read/writes |