Ghost Solution Suite

 View Only

  • 1.  Genetal Protection Fault

    Posted Mar 21, 2007 06:55 AM
    I have Ghost Solution Suite 2.0
    Until yesterday it was OK. Now when I try to run a Ghost boot floppy, the NDis drivers load, Ghost comes up and I then select multicast/broadcast/unicast, the bar at the bottom says it is "initializing packet driver and IP address" and then the software gets a error
    "General Protection Fault at eip......
    General Protection fault in RMCB....."

    This has happened on several PCs and with both static and dynamic IP address.

    Can anyone help?


  • 2.  RE: Genetal Protection Fault

    Posted Mar 25, 2007 01:49 AM

    Hi Simon,

     

    We recently identified a situation where Ghost could GPF, depending on number of DNS and WINS servers in the network. Since it stopped working suddenly, you may be experiencing this issue.

     

    If you try a local imaging operation, would it work correctly?

     

    Were there any changes to the network structure? How many DNS and WINS servers do you have (if you get the output of ipconfig /all in a Windows machine, it will have all the details)

     

    Krish



  • 3.  RE: Genetal Protection Fault

    Posted Mar 25, 2007 10:08 PM
    When I used the bad floppy disks, I also got general protection falut error.
    After I change to new floppy disks, it went away.
    I think this happened because ghost.exe is splitted into 2 floppies.
    (I believe they use some kind of merge program to create ghost.exe from 2 floppies)
     
    or it could be just simply the issue with DNS/WINS server as Krish mentioned.
     
     

    Message Edited by Ethan Hunt on 03-25-200707:09 PM



  • 4.  RE: Genetal Protection Fault

    Posted Mar 29, 2007 11:08 AM
     
    We had a similar issue come up this week. We have 'several' old IBM PCs with NT 4.0, and they backup to external DVD with a Ghost 2003 Boot Floppy. The error was:
     
    General Protection Fault
    eip=2103293
    error error 868000
     
    Or something closely approximating such. Our best guess is a bad boot disk.