Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WARNING: Can't load settings file! #45

Closed
lvntbkdmr opened this issue Feb 7, 2013 · 6 comments
Closed

WARNING: Can't load settings file! #45

lvntbkdmr opened this issue Feb 7, 2013 · 6 comments

Comments

@lvntbkdmr
Copy link

Hi,

i downloaded developement files as .zip format and tried to open with Netbeans 7.2.1
however , when i try to run the project it gives me some errors.

starting with settings file errors. it tries to locate a file named ".UniversalGcodeSender.properties" but it can't find it.

how can i overcome this problem?

thanks

@winder
Copy link
Owner

winder commented Feb 7, 2013

Does that happen every time you start? The settings file should be created automatically after it isn't found.

@lazyzero
Copy link
Contributor

lazyzero commented Feb 7, 2013

It will be generated on the shutdown of the application. If you cancel it from Netbeans it will not save the settings.

@lvntbkdmr
Copy link
Author

yes it happens everytime , i try to run.
this is my output screen : http://img541.imageshack.us/img541/9394/adszoh.png

@lazyzero
Copy link
Contributor

lazyzero commented Feb 7, 2013

Okay, that is because you don't have the rxtx native lib installed to your system, like mentioned on the readme page
"For development you will need to install RXTX."

@lvntbkdmr
Copy link
Author

ah yes i saw that. now i installed rxtx . program runs but still gives Settings file warning.
and it outputs something like

"WARNING: RXTX Version mismatch
Jar version = RXTX-2.1-7
native lib Version = RXTX-2.2-20081207 Cloudhopper Build rxtx.cloudhopper.net"

@lvntbkdmr lvntbkdmr reopened this Feb 7, 2013
@winder
Copy link
Owner

winder commented Feb 7, 2013

The version mismatch should be safe to ignore, it has been there for a long time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants