[poedit-users] Re: [3] DB_RUNRECOVERY with TM (Vaclav Slavik)

Wednesday, February 23, 2005, 12:21

Dear Vaclav Slavik,

Regarding your message dated 22/02/05 01:16,
subject "Re: [3] DB_RUNRECOVERY with TM (Vaclav Slavik)",

>> OK. I'll send the generated DB files.
purlsn> 
purlsn> Please don't, they are useless, the important thing is *how* it=20
purlsn> happens, not how the corrupted files look afterwards.
purlsn>

OK.

>> Do other Windows 98 SE users have any problems?
purlsn> 
purlsn> I don't know. Nobody reported it before, but that may well be because=20
purlsn> nobody else is using 98 or because you're the first to bother=20
purlsn> reporting the bug. It's worth trying on different win version with=20
purlsn> same data, if you have access to any.

Hmmmm... not right now, at least not this week... but I'll check ASAP.

Meanwhile, I'll just not use the TM. It's still a great tool, anyway.


Regards,

Michael Lees
michael.groups-z6eOKc0IOiNWk0Htik3J/[email protected]

-------------------
Random quote:
A fool with a tool is still a fool. With a tool.
- Unknown


---8<---Your original message starts here (or part of it)--------

purlsn> Message: 2
purlsn> From: Vaclav Slavik <[email protected]>

purlsn> Hi,

purlsn> Michael Lees wrote:
>> But then the error still occurs when using poEdit. While I
>> right-click on  an item, the context menu appears OK, but as soon
>> as I LEFT click, then  the error occurs. I Click OK and I can
>> continue. But NOTICE: the error occurs when I left-click ONLY AFTER
>> I RIGHT-CLICK. If I continue to left-click, no problem apparently.

purlsn> Yes, because that's when TM is used.

>> And when I close poEdit, it happens (the error) again.
>>
>> If I erase the TM files (for EN and PT), **while** running poEdit,

purlsn> Bad idea...

>> the error  continues.  But once I close and re-run poEdit, no
>> errors occur anymore.

purlsn> Because there's no TM it could break on.

>> Monitoring  the file access, I notice that the error begins as soon
>> as the DB files are accessed (translations.db and strings.db), so
>> it must be something to do with the TM.

purlsn> Yes, that much is obvious from the error message that says it's a=20
purlsn> database error: it only happens when accessing the TM database.

>> OK. I'll send the generated DB files.

purlsn> Please don't, they are useless, the important thing is *how* it=20
purlsn> happens, not how the corrupted files look afterwards.

>> Do other Windows 98 SE users have any problems?

purlsn> I don't know. Nobody reported it before, but that may well be because=20
purlsn> nobody else is using 98 or because you're the first to bother=20
purlsn> reporting the bug. It's worth trying on different win version with=20
purlsn> same data, if you have access to any.

purlsn> Regards,
purlsn> Vaclav




---8<------------Your original message ends here-----------------



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click