AFP548 Changing the world one server at a time.

InstaDMG 1.6b2 and 10.6.3

Home › Forums › Software › InstaDMG › InstaDMG 1.6b2 and 10.6.3

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #378352
    jlramos
    Participant

    I’ve dl InstaDMG 1.6b2 and followed the steps listed in the pdf, but it errors out at the end when it tries to created the output fille. The steps I followed:

    1. sudo ./instadmg/AddOns/InstaUp2Date/importDisk.py –automatic –legacy
    2.sudo ./instadmg/AddOns/InstaUp2Date/instaUp2Date.py 10.6_vanilla –process

    And at the very end here is what’s in the log file:

     15:03:49 ###### Creating the deployment DMG and scanning for ASR ######
    	Rename the deployment volume: Macintosh HD
    		Volume on disk1s2 renamed to Macintosh HD 
    	Create a read-only image
    		 
    		Unmounted the Target image image from /private/tmp/InstaDMG_temp_folder.1FB2sI/mount_point.gAra7p
    		MESSAGE:Preparing imaging engine… 
    		MESSAGE:Reading Protective Master Boot Record (MBR : 0)… 
    		PERCENT:0.000000 
    	Scanning image for ASR: ./OutputFiles/10.6.3 Vanilla(as of 4/1/2010).dmg
    		can't open "/Users/jlramos/Desktop/instadmg/OutputFiles/10.6.3 Vanilla(as of 4/1/2010).dmg" read/write 
    		asr: image scan failed - No such file or directory. 
    	ASR image scan complete
    15:04:02 ###### InstaDMG Complete ######
    15:04:02 ###### Cleaning up ######
    	Restoring normal installd daemon
    	Ejecting images
    	Deleting scratch DMG

    Has anyone else run into this issue?

    Host system is a MBP running 10.6.3

    #378353
    Allister Banks
    Participant

    Hey there,

    The catalog file was faulty. Please run “svn update” from the directory you downloaded instadmg to(in your case on your desktop in an instadmg folder) and try again. I’m pretty sure it’s the parentheses in the name of the DMG. Sorry about that.

    Allister

    #378354
    jlramos
    Participant

    That did the trick.

    Thanks.

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