On Sunday 29 March 2009 04:35:30 Clayton Carson wrote:
> Thanks Oisin I posted on that page and maybe with some luck ill be
> able to recover my cards. Besides this though my .mnemosyne directory
> still is not saving backups even after i reinstalled Mnemosyne. Is
> there anything else which might be causing this?

Is there anything in the error log? Is this the latest version of Mnemosyne? 
Are there issues with write permission? Have you changed the 'number of 
backups to keep' configuration option in config.py? Is there only 1 install of 
Mnemosyne present instead of one on a USB key as well? The backups could end 
up in the USB install too.

Peter

> On Mar 27, 12:35 am, Oisín Mac Fhearaí <[email protected]> wrote:
> > 2009/3/26 Clayton Carson <[email protected]>:
> > > TT not that easy, file is corrupted so i cant open with mnemosyne I
> > > have to manually take out of the programming script. Is there any
> > > function which can help to selectively delete certain things so as to
> > > make getting the cards I want easier?
> >
> > Hi,
> >
> > Have you had a look at some Python docs/resources on dealing with
> > these 'pickle' files? Maybe something
> > likehttp://stackoverflow.com/questions/664444/how-to-recover-a-broken-pyt
> >... might help you write a recovery/fix script?
> >
> > Oisín
>
> 
------------------------------------------------
Peter Bienstman
Ghent University, Dept. of Information Technology 
Sint-Pietersnieuwstraat 41, B-9000 Gent, Belgium
tel: +32 9 264 34 46, fax: +32 9 264 35 93
WWW: http://photonics.intec.UGent.be
email: [email protected]
------------------------------------------------

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"mnemosyne-proj-users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/mnemosyne-proj-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to