AFP548 Changing the world one server at a time.

Cannot Allocate Memory

Home › Forums › Software › InstaDMG › Cannot Allocate Memory

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #371784
    ershler
    Participant

    I have attempted to build a ASR dmg with InstaDMG. The build, starting from a retail Leopard distribution, and updated with the 10.5.2 combo updater seemed to go fine. The build system was a MDD G4 processor running Leopard Server, updated to 10.5.2.

    After starting ASR on the server and booting a G4 client with 768 Mbytes of ram off of the Leopard install disk, I start the restore on the client machine. The server acknowledges the clients request and the restore appears to start. However shortly thereafter the client throws an error “Cannot Allocate Memory” and quits. Any suggestions as to where I went wrong?

    Thanks

    #371785
    Patrick Fergus
    Participant

    I had some issues with the earlier revisions of 10.5 and Disk Utility not restoring the ASR dmgs created by InstaDMG (various miscellaneous errors). I took that same machine and started it up into Tiger and was able to restore the same DMGs without issue.

    Since the retail disc is 10.5.0, try performing the restore with either 10.4 or 10.5.2.

    – Patrick

    #371787
    ershler
    Participant

    OK, I booted the machine from a 10.4.0 install disk. If I try to run Restore from Disk Utility, is asks me to authenticate. I have no idea how to authenticate to an install DVD. But I ran asr from the command line and it “seems” to be working so far.

    Thanks

    #371793
    ershler
    Participant

    Yes, I am indeed trying to use mASR.

    Thanks

    #371811
    ershler
    Participant

    OK, I finally hit on a combination that works. The target machine is booted off of the 10.5.0 client installer. Then if I Initiate asr from the command line in terminal, rather than from Disk Utility, everything works great.

    Thanks

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.