Ghost Solution Suite

 View Only

  • 1.  divide overflow

    Posted Jul 17, 2007 03:01 AM
    Hi!
     
    I have created a ghost boot disk (2 diskettes) without any but the standard (no usb, firewire, lpt etc...) but when i boot my machine from them it does it ok but when ghost starts it gets to the startup screen and then exits to dos again saying: "divide overflow". I have tried the disks on other machines where it works. The machine is one i built my self and i have never had problems with it...
     
    please help...


  • 2.  RE: divide overflow

    Posted Jul 17, 2007 04:47 AM
    Just to check, what specific version of Ghost is on the boot disk? It's cool that's it's a system you've built yourself, but it would be helpful to know the specific motherboard you used - we might well be able to source one. That's an unusual kind of problem and if we can quickly run some basic BIOS compatibility checks on the same board here in our labs that'd be useful before trying to remotely work our way through this.


  • 3.  RE: divide overflow

    Posted Jul 17, 2007 02:16 PM
    Hi!
     
    The mainboard is an MSI, model no MS-6728 with bios 2.50 with two HDS722512VLAT80 disks attached. There is also a dvd writer and dvd drive attached.
     
    The ghost version is 11.0.0.1502
     
    Hope this helps lead the way...


  • 4.  RE: divide overflow

    Posted Jul 18, 2007 02:21 AM
    hmmm...
     
    Tried loading the bios default values and now it seems to work... tried returning the settings to what they was but could not replicate the problem...
     
    The only issue i have now is getting ghost to store the image locally when initiating it from the windows client through the ghost console - but that is probably a user error connected to the path specified for the local file...
     
    So thanx for getting me to look to the mainboard for resolving the problem...:-)


  • 5.  RE: divide overflow

    Posted Jul 19, 2007 12:31 AM
    Good to hear; out of curiosity, do you know what the non-default setting was that you changed? It would still be nice if we could figure out what the trigger might have been, and we could reproduce it here and see if there's something we can do about it.