Joost 't Hart schrieb: Hi!
> Ensure that the *Directory* field in the crafty properties dialog refers to > an > existing path. Simply '.' (which I think is the default after installation) > did not always help for me. It is safe to take e.g. the (absolute path to > the) directory where the exe/binary of crafty is located, provided that the > normal user of 'scid' (you?) has write access to that directory. Then probably /tmp would be a better place to point to? -- Kind regards, Alexander Wagner Universitaetsbibliothek Ilmenau Langewiesener Str. 37 98693 Ilmenau Tel.: 03677/69-4521 , Fax.: 03677/69-4617 ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ Scid-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/scid-users
