Home Forums Software InstaDMG Using InstallESD.dmg 10.7.3

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #381616
    ramuntcho
    Participant

    Hello,

    I have tried to replace our InstallESD.dmg (in folder InstallerDiscs) in 10.7.2 by a new InstallESD.dmg in 10.7.3 (you can download a complete Installation MacOS X Lio.app from the AppStore, and then extract the dmg).

    But no chance, it’s not working.

    Is it normal with this version of instaDMG that we can’t use an InstallESD.dmg in 10.7.3 ? Do we have to use rather one InstallESD.dmg in 10.7.2 and one update to 10.7.3 ?

    Thanks

    Christian

    #381617
    Allister Banks
    Participant

    Hey ramuntcho,

    Please update the file in /AddOns/InstaUp2Date/CatalogFiles/10.7_vanilla to add the new build number for 10.7.3. You can find the build number by mounting the InstallESD.dmg and then navigating to MacOSXInstallESD/System/Library/CoreServices and inspecting SystemVersion.plist for ProductBuildVersion(should be 11D50).

    Allister

    #381620
    ramuntcho
    Participant

    Hi Allister,

    It was so simple ! Thanks for the quick answer

    Christian

    #381646
    elvisizer
    Participant

    Hmmmmm . . . .I was able to import my 10.7.3 installESD.dmg file using the instaUptoDate importDisk.py script, so i have a ‘MacOS X Client 10.7.3 11D50.dmg file in InstallerDiscs, but running instaUptoDate gives me the ‘no valid installer discs found’ error.
    11D50 is already listed in the catalog file:
    Installer Disc Builds: 11A511, 11B26, 11C74, 11D50

    And I verified the plist file in the DMG has 11D50 as well.

    Any ideas?

    #381649
    elvisizer
    Participant

    reboot fixed it . . . anyone know why a reboot fixes installer disc identification issues? i seem to remember having this happen occasionally in the past, too.

    #381707
    ktappe
    Participant

    [QUOTE][u]Quote by: elvisizer[/u][p]reboot fixed it . . . anyone know why a reboot fixes installer disc identification issues? i seem to remember having this happen occasionally in the past, too.[/p][/QUOTE]

    Wow, you’re right. Rebooting (or in my case, kernel panicking) did fix the problem.

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

Comments are closed