@Charvel
it's usually enough if you initially write an email saying 'i have problems running this thing'. it's easy to figure the best course of action there, which often is basically one of:
1) checking you have no remains of previous installation -- people sometimes copy fryingpan's modules to their LIBS: directory, which is very bad
2) collecting ramdebug logs that helps understand where the issue is, or
3) collecting the fryingpan-generated debug data, which actually helps locate the issue within the program logic
this way i just fixed the big issue with 1.3.0 that was mentioned recently - and i think these dvds can still be recovered
.
so basically -- it would be best if you could just write me an email and specify how exactly program behaves (what you do, where it crashes etc), if this is just a matter of detecting drive -- in best case this could be fixed within minutes (but i don't know anyone who has this issue and would want to help fixing it straight away - so i never heard of it).
thanks,
tomek