I recognise this one, I think. 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.
Cheers, Joost. On Wednesday 28 November 2007 20:55:08 J. Varsoke wrote: > I just DLed and installed scid-3.6.20. When opening crafty engine I get > an error that crafty has terminated: "The analysis engine terminated > without warning; it probably crashed or had an internal error." Is > there an error log where I can get a better description? > > Crafty works just fine from the command line. > > -jason > > ------------------------------------------------------------------------- > 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 ------------------------------------------------------------------------- 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
