Loading...
Logo
Processing Forum
I have created a Processing application on my machine that runs just fine when exported on my machine.  But, when on another person's machine, it won't even launch.  There are so many variables, I am not sure where to start debugging. I am looking for help on approaching the troubleshooting process.  So far, users on 64 bit Windows systems cannot launch the app.

- I programmed it on Mac OSX, and then via Boot Camp, corrected some code, and re-exported on Windows 7 64 bit.  I checked the app thoroughly and it was working as expected.  (I don't have a separate "pure" Windows unit to test on, myself)
- I am using several libraries: minim, soundcipher, toxilibs, controlp5
- I noticed from the beginning that there were font issues.  I could not use the .vlw files that I made in OSX on Windows, they just generated errors.  When I recreated the .vlw's in Windows, they appeared to work ok.  Possibly this could be a source of the error.
- I have asked the users for error log reports, but as of this writing I do not yet have any further info from them.  I will post when I get something useful.

I appreciate any help in getting direction for troubleshooting this issue.  What are the first things that I should check or ask for to narrow down the problem?

thanks!

Replies(3)

your app does run on your bootcamp win 7/64 but not on others? 
is java installed on the machine in question?

some suggestions (sorted by chance of success):
* get at the machine in question to test yourself
* get some hints on what is going wrong. i.e. java error logs
* try some test programs, one very simple one without libraries. then one for each of the libraries. observe any errors on the console. are theses libraries all running on the os/version in question?



There seems to be a small problem with how they are published which should be fine with the debug mode.  There is actually a side by side run debug class that will probably help you with this.  Not sure though how you are going to bridge the difference between Mac and Windows domains but considering that they are the same in the implementation, you could assume that they are fine with this too.
Ubeam, what is the debug mode you are talking about?  I am not sure I understand.

To all, it looks like I will have to make a troubleshooting app that uses all of the libraries, and executes at least one function from each, wrapping try/catch statements around everything, writing out to a log.

I dont have direct access to the user's workstations.  These folks have downloaded my app via a link, and they are all over the place.  So, being able to see what's going wrong at their desk will be impossible.