In that case I would do a repair.
Insert the Server CD and boot from it and repair the current
installation.
If it asks to overwrite the array drivers you have installed, let it do
so.
 

________________________________

From: TNN [mailto:[EMAIL PROTECTED] 
Sent: Monday, June 23, 2008 11:20 AM
To: NT System Admin Issues
Subject: Re: Domain controller wont boot - stops at acpitabl.dat


I upgraded the Array drivers after the server would not boot. Dont think
that was the cause. I tried it as a solution, no avail.


On Mon, Jun 23, 2008 at 4:55 PM, Tom Strader - NCBPAC Systems
Administrator <[EMAIL PROTECTED]> wrote:


        When did you update the array drivers?
        The error indicates one of the drivers is incompatible with
Server 2003.
         
        Try doing an in-place upgrade. This gives you a chance to
replace the array drivers with the correct ones.
        Reboot the server with a Server 2003 CD, when the setup starts,
watch the screen and press F6 and install the correct drivers for the
array. You will have to get the drivers on to a floppy drive. If the
server doesn't have a FD use a USB floppy disk drive to make this
happen.
         
        See this Microsoft article for help:
http://support.microsoft.com/default.aspx?scid=kb;en-us;816579
         
        HTH,
        Tom
         
         

________________________________

        From: TNN [mailto:[EMAIL PROTECTED] 
        Sent: Monday, June 23, 2008 10:32 AM
        To: NT System Admin Issues
        Subject: Domain controller wont boot - stops at acpitabl.dat
        
        
        Hi
        
        I have a Windows 2003 SP2 32-bit domain controller that wont
boot. It stops at acpitabl.dat when you when you choose to boot from
safe mode - any option. . If you choose the normal boot process, it
shows the boot screen for forever and never gets to the login screen.
        The server is an HP Proliant ML350 G5.
        
        I have updated the storage array and bios drivers to the latest
versions. I have also taken out the memory and used each DIMM
seperately. None of this helped.
        
        Any ideas out there?
        My last option is to perform an in-place upgrade. How will this
impact on my AD database? 
        
        

        

        

        


        

        

        



~ Upgrade to Next Generation Antispam/Antivirus with Ninja!    ~
~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm>  ~

Reply via email to