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

Michael Lees <michael.groups-z6eOKc0IOiNWk0Htik3J/[email protected]>
Newsgroups gmane.editors.poedit.user
Message-ID <[email protected]>
Monday, February 21, 2005, 12:45

Dear Vaclav,

Regarding your message dated 21/02/05 01:18,
subject "Re: DB_RUNRECOVERY with TM (Vaclav Slavik)",

purlsn>> Are you saying that it doesn't matter how many files are there? Does=20
purlsn>> it happen if there are _no_ files scanned for inclusion in the TM?

If I choose to generate the database, but don't select any files, then
no error occurs, but three DB files are created anyway (three for each
language  I  had  selected, EN and PT). The files are translations.db,
strings.db and words.db.

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.

And when I close poEdit, it happens (the error) again.

If I erase the TM files (for EN and PT), **while** running poEdit, the
error  continues.  But once I close and re-run poEdit, no errors occur
anymore.

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>>  If=20
purlsn>> some files are needed, could you please prepare some (as small as=20
purlsn>> possible) example and submit a bug report with these files attached,=20
purlsn>> and with instructions on how to use them to reproduce the bug?

OK. I'll send the generated DB files.

purlsn>> You aren't running out of disk space by any chance, are you?

4.51 Gb free space at the moment.

purlsn>> Other than that, the only idea I have is that it's somehow related to=20
purlsn>> being used on win98, but I don't think Berkeley DB requires=20
purlsn>> Unicode...

I  searched  the  web for this error message, and I find it related to
the Berkeley DB (which I know nothing about), but always in some other
context.  Often,  the  solution  is  to  erase the DB and recreate it.
Didn't help me, though.

I installed Windows Unicode support, and tried putting the UNICOWS.DLL
file in different folders/paths, but it didn't make any difference.

Do other Windows 98 SE users have any problems?

purlsn> 
purlsn>> Regards,
purlsn>> Vaclav
  

Regards,

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

-------------------
Random quote:
A notebook is a device for taking work to a place where you would rest.
-Unknown


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

purlsn> Hi,

purlsn> Michael Lees wrote:
>>    I  tried  excluding/including  PO and MO files to try and track
>> the problem to a specific file, but it makes no difference.=20

purlsn> Are you saying that it doesn't matter how many files are there? Does=20
purlsn> it happen if there are _no_ files scanned for inclusion in the TM? If=20
purlsn> some files are needed, could you please prepare some (as small as=20
purlsn> possible) example and submit a bug report with these files attached,=20
purlsn> and with instructions on how to use them to reproduce the bug?

purlsn> You aren't running out of disk space by any chance, are you?

purlsn> Other than that, the only idea I have is that it's somehow related to=20
purlsn> being used on win98, but I don't think Berkeley DB requires=20
purlsn> Unicode...

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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.