Yes, just did.  Let me finish the 16 remaining scheduled cards for the day, 
then froze after about 5 unlearned cards.  The program will hang for me 
both on the regularly scheduled cards, and in new, unlearned cards, which I 
neglected to mention before (I mention it because I noticed another poster 
said they have it on learning new cards).  I did the defragging, didn't 
seem to have an effect (my computer was only at 1% fragmentation to 
start).  The sysinternal trick seems a bit too advanced for me.  

I was thinking, I could load the program on another computer that I only 
rarely use, mount the database in that copy of th program, and see if it 
occurs there; which may let us know if it's something to do with the 
database, or the computer?  This may or may not be of help, I really don't 
know.  That other computer is a Windows 7 64-bit desktop, this one is a 
Windows 7 Starter netbook.  Let me know if it is worthwhile.  I may just do 
it temporarily so I can keep up on my card repetitions, and then start 
using my netbook again once the problem is fixed.  I prefer not to have to 
use the desktop comp for review though.  

   Thanks again, Chris Shanks.

On Monday, July 9, 2012 10:06:30 PM UTC-7, Peter Bienstman wrote:
>
> Thanks for the info. More importantly, did you try the new version?
>
> Peter
>
> Chris <[email protected]> wrote:
>>
>> REGARDING your questions here:
>>
>> I am running Windows 7 Starter, which I believe is 32-bit, but I may be 
>> mistaken.
>> No anti-virus running.
>> Don't really know what python is, so probably don't have another version 
>> of it running, hopefully!
>> Also not sure how to find default.db, doesn't come up on a file search of 
>> My Computer.
>> No funny characters in my username ("Chris")
>> Everything is on C drive.
>> Have had the problem without using the card browser, repeatedly.
>> I'll try the defragment this afternoon, and read up on the process 
>> monitor to see if I could figure it out without too much risk!  :)
>>
>>    Good luck, Chris S.
>>
>> On Monday, July 9, 2012 11:48:42 AM UTC-7, Peter Bienstman wrote:
>>>
>>> Hi, 
>>>
>>> As you know, there have been quite some reports of Mnemosyne sometimes   
>>> hanging on Windows. I had hoped that the new PyQt version would fix   
>>> this, but unfortunately, that turned out not be the case. The hangs   
>>> never happen on my system, so I need help to debug this. 
>>>
>>> To summarise what I understand the problem to be (but feel free to   
>>> correct me), Mnemosyne sometimes hangs when trying to grade a card,   
>>> and this happens regardsless of whether the cards contain images or   
>>> not. It happens both on XP 32 bit and on W7 64 bit. 
>>>
>>> I prepared a new test version here: 
>>>
>>> http://users.ugent.be/~pbienst/pub/mnemosyne-20120709-setup.exe 
>>>
>>> I changed some small packaging/configuration options. I'm not sure if   
>>> they will have a big impact, but you never know :-) 
>>>
>>> If you still have hangs, it would be interesting to see if how the   
>>> frequency of hangs changes if you try e.g. 'autosave after 1 reps' vs   
>>> 'autosave after 20 reps'. 
>>>
>>> If you have a virus scanner like Microsoft security essentials   
>>> running, please try disabling it and see if it makes a difference.   
>>> Ditto for Windows desktop search. 
>>>
>>> If you have a separate version of Python installed on your machine,   
>>> please remove it. 
>>>
>>> Do a search for default.db on your file system, and check if   
>>> default.db has write permissions, together with all the folder levels   
>>> above it. 
>>>
>>> Do you have funny characters in your windows account name? 
>>>
>>> Is your database on the C drive? 
>>>
>>> Do you also have the problem if you never used the card browser after   
>>> starting the program? 
>>>
>>> If you're technically inclined, run Sysinternal process monitor while   
>>> running Mnemosyne, to see if anything suspect happens with database   
>>> access (filter to show only events in the 'file system' class) (   
>>> http://technet.microsoft.com/en-us/sysinternals/bb896645 ) 
>>>
>>> Make sure you have enough free disk space and try running a 
>>> defragmenter. 
>>>
>>> Any other pattern you observe or thought you might have to solve this,   
>>> is welcome! 
>>>
>>> Peter 
>>>
>>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "mnemosyne-proj-users" group.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msg/mnemosyne-proj-users/-/nMK7uOamiloJ.
>> 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.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"mnemosyne-proj-users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/mnemosyne-proj-users/-/HU6Vvx7aiWAJ.
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