Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#79 Error starting from install script

open
nobody
None
5
2008-02-28
2008-02-28
Ben Whitman
No

I am creating my own songs for FoF, and I think it would be nice to package my songs as an installer, so it could be really easy to distribute, as well as use the installer license page as a means of pointing people to my band's website (I'm using our own songs, just because I thought it would be really amazing), as well as for giving to noobs who wouldn't know what to do with the songs if I distributed them as .zip files. However, as the last step of the installation process, when it comes to the "Installation Finished" page, it is customary to have a "launch program now" checkbox, so I thought why not launch FoF when the songs are done installing? Well, when I do that, it launches FoF, then immediately crashes, giving me the following error message:

cx_Freeze: Python error in main script

Traceback (most recent call last):
File "c:\users\proj\cx_Freeze-3.0.3\initscripts\console.py", line 27, in ?
File "src/FretsOnFire.py", line 68, in ?
File "src\GameEngine.py", line 180, in __init__
File "src\Mod.py", line 32, in init
File "src\Mod.py", line 41, in getAvailableMods
WindowsError: (3, 'The system cannot find the path specified', 'data\\mods/*.*')

I am using NSIS 2.33, and I am attaching my installer script so maybe someone can figure out what is going haywire. If I don't try to launch FoF from the installer, everything works perfectly, and if I launch FoF by double-clicking my desktop icon immediately after the installation, it works fine, and the song has installed and everything. Any help would be much appreciated. I'm kinda new to NSIS, so I may be making a mistake somewhere, but the whole rest of the script works great if I take that part out, or even if I compile that script and just uncheck the box to launch FoF on the last page. Again, any help would be greatly appreciated.

Discussion

  • Ben Whitman
    Ben Whitman
    2008-02-28

    NSIS script

     
    Attachments
  • Ben Whitman
    Ben Whitman
    2008-04-03

    Logged In: YES
    user_id=1944448
    Originator: YES

    Hmm... I think I may have found the problem. If you call FoF in such a way that the FoF install directory is not the "working directory" you get this error. Setting the working directory, then executing seems to work, but it's still weird that you have to call it from that directory, it makes it hard to call it in any way other than normal shortcuts :P.

     
  • Ben Whitman
    Ben Whitman
    2008-04-03

    Logged In: YES
    user_id=1944448
    Originator: YES

    Hmm... I think I may have found the problem. If you call FoF in such a way that the FoF install directory is not the "working directory" you get this error. Setting the working directory, then executing seems to work, but it's still weird that you have to call it from that directory, it makes it hard to call it in any way other than normal shortcuts :P.