- #Powercontrols cannot initialize the mapi subsystem software install
- #Powercontrols cannot initialize the mapi subsystem software drivers
- #Powercontrols cannot initialize the mapi subsystem software Pc
#Powercontrols cannot initialize the mapi subsystem software install
However, I too suspect WinPE 2.0 compatibility with older DVD drives, which the previous Vista install did not show up - as my Vista RTM install was done from an softmounted ISO (MSDN subscriber) and not a physical disk.
#Powercontrols cannot initialize the mapi subsystem software Pc
As for others, the PC had previously worked fine under XP, Server 2003, and Vista RTM. This was using WHS RTM bought at retail - the problem does not appear to be bad disks pre-RTM.
That worked, and now I have WHS RTM installed just fine. What ultimately fixed it for me was to use an alternative DVD boot device - an external USB DVD drive. I too had this problem, and tried everything in the thread with no luck (boot order, RAID, drive firmware and whatnot). Longhorn even seems to use the same bits to bootstrap the installer. I'm a little surprised that I can't even get to the F6 menu, since both Win2K3 and Longhorn installed just fine. I have been unable to find any MB jumpers, etc., that would kill the Perc5 any more than it already is. I still see a message at startup about "backplane not present", though, so it's possible that the Perc5 controller is still alive enough to cause problems. I've also flashed the Dell BIOS to the latest A09.Īs far as disabling the Perc5 controller, I've removed the backplane, removed the RAID key, and disabled the controller in the BIOS. I've already updated this card, but it's not the same RAID card they're talking about in that thread - it's the SATA300 TX4, and the most recent BIOS for this card is dated Apr-2005. I've also watched the thread about the Promise Raid controller, where people have had some success by flashing a new BIOS to the card. If anyone's listening, it sounds like we've got at least two PE systems where we can reproduce the problem pretty reliably. I submitted a bug on this a while back, but it was closed as "can't reproduce". I should hopefully have an IDE card I can try in this system shortly, but it sounds like I may still have problems. Your experience seems to match mine pretty closely. Has anyone ever gotten this installed on a Poweredge? I havent' heard any success stories. The DVD drives I've tried include an almost new Lite On and two somewhat older Pioneer slot loaders. As a matter of fact, until this install I thought this was a fairly stable beta. I have had no such trouble with my other test boxes. I'm really confused, it seems to have something to do with this poweredge system. Like you, this is long before setup even really starts going so there isn't any information to go on. Brought it home and I still get the same error. So off I went and downloaded the new CTP, and burned and verified it with imgburn. So I cruised the forums and found that almost everyone was saying that error means a bad burn or DVD drive.
#Powercontrols cannot initialize the mapi subsystem software drivers
That went perfectly with NO need to add drivers via F6 and I was booting to the OS in under an hour. Still got the same error.Īt this point I was worried that the PERC 3 card wasn't supported so for a sanity check I fired up my Server 2003 install. Then I tried an adaptec 2940UW and a scsi dvd drive since almost every server os supports that card. I added a promise ATA 133 controller and tried two different IDE DVD drives. I have used the same DVDs to install on my other server so I was pretty sure that the disk was fine. I get the same Could Not Start UI Subsystem Error. I have a Poweredge 2500 that I have been trying to install on. I went a little different route, but I fear my troubles might be related. At that point in the install, there's no place to even write a log file, so I don't know where else to go looking for symptoms. I've got the distinct impression that "Cannot initialize the UI subsystem" could be caused by a number of underlying problems. The same screen allows me to exclude devices from booting altogether, and I've done that for the A: drive, though not for the C: drive. There's also a boot priority setting where I can prioritize the Promise controller, A: drive, and C: drive (and the RAID and SCSI when they were turned on). I've been pretty meticulous about shutting down anything else the machine might be trying to boot from, including disabling the onboard SCSI and RAID. I haven't posted a question about that because I know it's not supported, but at least I can see what the console is all about.
Incidentally, WHS seems to run ok under VMWare, but the client can't connect to the box. I installed WHS under VMWare, so I've seen the install go all the way through. I'm not getting as far as the first reboot.
0 kommentar(er)
