Ghost Solution Suite

 View Only
Expand all | Collapse all

Error: Failed to Reboot Client to Recovery Partition

  • 1.  Error: Failed to Reboot Client to Recovery Partition

    Posted Feb 16, 2007 09:49 AM
    Hi all,
    I am a bit of a newbie here, so thank you for bearing with me on this. I have been trying for some time now to pull an image for a Dell GX320 (SATA HDD, onboard NIC - Broadcom 440x, Windows XP SP2, Ghost 8.2) with out any luck. The problem started when I first attempted to remotely load the client to the machine, it kept failing to connect. This issue was solved by me adding the Broadcom 440x drives to the list that the ghost program already had (duh, felt like an idiot there :) ). After this I was able to remotely install the client and run an inventory task.
    My issue now is trying to run a creat image task. It always fails, and I have tried numerous things to correct. More recently I "F8'd" into the DOS boot up to manual control it and see where it was going wrong. Here is what I got:

    Starting PC DOS...

    blha-blah- prompt me - blah-blah

    IBM Protocol Manger Version 2.1
    PRO0008E: Invalid decimal digit in PROTOCOL.INI file
    Device=\NET\DIS_PKT.DOS {I hit Y to prceed}
    MAC/DIS to Packet Driver converter loaded. Version 1.18
    blah-blah-stuff-blah

    Protocol Manager not present
    Device=\NET\B44.DOS {I hit Y to proceed}
    Broadcom 440x 10/100 Integrated Controller DOS NDIS2 driver v3.12 (051216)
    blah-blah-blah
    The driver failed to load.

    etc.


    So this is an issue with the PROTOCOL.INI file then? When I compare it with others in the temples folder under all users, they look the same (sans the driver name I gave it).

    Really very frustrating and I would quite gladly welcome any thoughts or assistance anyone might be able to offer.

    Thanks a bunch!!


  • 2.  RE: Error: Failed to Reboot Client to Recovery Partition

    Posted Feb 16, 2007 10:35 AM
    Okay,
    A co-worker tried something and it has apparently worked thus far. She made an alteration to the PROTOCOL.INI file, I will provide the original and the new one.

    Original:


    drivername=PROTMAN$


    drivername=PKTDRV$
    bindings=nic
    intvec=0x60
    chainvec=0x66


    drivername = Broadcomm 440x 10/100$


    Modified:


    drivername=PROTMAN$


    drivername=PKTDRV$
    bindings=nic
    intvec=0x60
    chainvec=0x66


    drivername = B44$


    DriverName = "B44$"
    BusNum = 3
    DevNum = 14
    PortNum = 2
    ; LineSpeed = 100
    ; Duplex = Full
    ; NodeAddress = "001020304050"


    I then tried to run the task again and it took this time and is now pulling an image.

    If anyone has any idead as to why ghost didn't properly set this up to begin with, I would be glad to discuss it.

    Have wonderful days plz!! :) (mine is looking better!!)