On 14/07/16 19:50, IonicBasher . wrote:
Like I said I tried the run.py file incrementally on a BRAND NEW image
before any updates. Only grabbed the configuration files, machineface
and cetus from github into home folder.
Apologies, I read that you had installed Wheezy, as in installing the OS
not a new copy of the RCN image
I expect this is what confused me
>> I tried installing by packages on a stock debian image but failed to
open even the sample configuration for cramps. Another problem for
another time.
>> I reflashed the latest wheezy image of machinekit to climate
possible sources of errors.
There are all sorts of questions which have never been covered
Did the image EVER work?
If so, what changed?
Why did you try to 'upgrade' in the first place, was it because of the
error finding instances?
In which case we might be trying to fix your attempt to fix, not the
actual problem.
In any event, as I said before, trying to 'upgrade' a binary image with
a package is a really bad idea,
because all original files get overwritten and there is no uninstall option.
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you are subscribed to the Google Groups "Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.
