On 7/10/13 07:56 , Shannon Watson wrote: > Operating this way ties me down to only one directory. I want to have a > production directory that is current release and stable version. That > directory is linuxcnc. I want updates and currently untested (by me) items to > be run in its own directory so that there is no interference with the machine > that makes money for our company. Can this be done?
I'm not sure if you're talking about different directories for different versions of LinuxCNC or different directories for different kinds of gcode files. I think you mean different kinds of gcode files, because that's what the error message you posted complained about. If so, then the good news is that there is no such limit: you can have gcode files in many directories. I often use one directory per project. You can have one directory for completed, proven gcode files and another directory for experimental gcode files under development if that's what you like. The error you posted is informing you that the path you told your gui to look for gcode files in does not exist. You should create that directory (or point your gui at some other directory), then create a "stable" and "experimental" subdirectories under that directory, and you should be good to go. (If i understand what you're trying to do.) -- Sebastian Kuzminsky ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
