Home Forums Software InstaDMG No Output File

Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • #379339
    Nihilator
    Participant

    To Larkost:

    Why are you “deliberately” ignoring this problem with Mac OS X 10.5.x?

    Problem: No outputfile.

    Error: ###### There were no items to install in: /private/tmp/InstaDMG_temp_folder.agg2Vy/mount_point.CFjHDl/private/tmp/mount_point.oXxnM4 ######

    Solution:

    Comment out lines 573-575

    Insert the following on line 576: HOST_MOUNT_FOLDER=”/tmp”

    FIX IT IN YOUR NEXT RELEASE “LARKOST”. FIX YOUR “$MOUNT_FOLDER_TEMPLATE”!

    #379340
    dead2sin
    Participant

    [QUOTE][u]Quote by: Nihilator[/u][p]To Larkost:

    Why are you “deliberately” ignoring this problem with Mac OS X 10.5.x?

    Problem: No outputfile.

    Error: ###### There were no items to install in: /private/tmp/InstaDMG_temp_folder.agg2Vy/mount_point.CFjHDl/private/tmp/mount_point.oXxnM4 ######

    Solution:

    Comment out lines 573-575

    Insert the following on line 576: HOST_MOUNT_FOLDER=”/tmp”

    FIX IT IN YOUR NEXT RELEASE “LARKOST”. FIX YOUR “$MOUNT_FOLDER_TEMPLATE”![/p][/QUOTE]

    From what I gather his main focus is 10.6. Honestly, if you want something that works epically well with 10.5, use an older version of InstaDMG. Also, Larkost does this for free. He doesn’t get paid…so try to show a little more patience and respect for his work. He has a regular job just like all of us.

    Nate

    #379341
    foilpan
    Participant

    uhh… what?

    development focuses on 10.6 of late, as far as i know. and at that, the instadmg.bash script itself hasn’t changed much in awhile. if you need it changed to accommodate your environment, it’s freely editable. just make the change, post back here with your findings and don’t assume someone is willfully ignoring you.

    #379342
    nobrainer
    Participant

    These guys have been outstanding, and your question was answered in another thread. I’ve used their recommendations several times to build 10.5.x boxes.

    To make it a little easier, here is the thread…

    [url]https://www.afp548.com/forum/viewtopic.php?showtopic=27149[/url]

    #379353
    Allister Banks
    Participant

    Nihilator,

    Feel free to file bugs(“issues”) at the instadmg.googlecode.com site where the project is hosted.

    Also please understand other users of this forum may feel offended by your tone, especially when this is your first post. Everyone gladly bends over backwards to share knowledge and assistance, nobody is here to directly make ALL CAPS demands of others.

    Allister

    #379355
    larkost
    Participant

    Just to repeat things: on Intel 10.5 things seem to be working just fine for me. All of my tests run just fine. I only own 1 PPC computer, and that has been my mail server for quite some time and so is not available for testing. As far as I can tell everyone who is having the problem is making their images on PPC. If this is not the case, then people need to be specific about this.

    So I can’t fix what I can’t replicate.

    #379360
    Nihilator
    Participant

    [QUOTE][u]Quote by: larkost[/u][p]Just to repeat things: on Intel 10.5 things seem to be working just fine for me. All of my tests run just fine. I only own 1 PPC computer, and that has been my mail server for quite some time and so is not available for testing. As far as I can tell everyone who is having the problem is making their images on PPC. If this is not the case, then people need to be specific about this.

    So I can’t fix what I can’t replicate.[/p][/QUOTE]

    Larkost,

    I am using InstaDMG on a Mac Pro.

    PowerPC has nothing to do with it.

    InstaDMG is installed on Mac OS X 10.5.8.

    #379361
    larkost
    Participant

    OK, the PPC thing was just a guess, but:

    Can’t replicate = Can’t fix

    Until someone can come up with what is actually going on here, there will be no fix. And I am unlikely to be able to figure this out, as I can’t get the problem to happen.

    #379366
    nobrainer
    Participant

    I have been having the same problems as referenced in other threads with 10.5, I’d like to help narrow down the problem, but my knowledge is a little vague on how. Would allowing you to remote into a machine help or would the log / debug files help?

    #379402
    larkost
    Participant

    I have just checked in some changes that may have some impact on the problem. After 3 re-installs of 10.5 on a system I managed to re-create the problem. I think it has to do with lengths of a few paths, so have reduced the lengths, and switched to a python mounting system that should be a little more reliable (and more verbose when failing). I can’t guarantee anything, because I can’t point at a smoking gun (and the path length limitations listed in the man page don’t quite match what I am getting). There is theoretically one more thing I could do, but implementing that would have to wait until after conference season at least.

    #379414
    Nihilator
    Participant

    [QUOTE][u]Quote by: larkost[/u][p]I have just checked in some changes that may have some impact on the problem. After 3 re-installs of 10.5 on a system I managed to re-create the problem. I think it has to do with lengths of a few paths, so have reduced the lengths, and switched to a python mounting system that should be a little more reliable (and more verbose when failing). I can’t guarantee anything, because I can’t point at a smoking gun (and the path length limitations listed in the man page don’t quite match what I am getting). There is theoretically one more thing I could do, but implementing that would have to wait until after conference season at least.[/p][/QUOTE]

    Thank you Larkost. It works correctly now.

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

Comments are closed