Re: incorect XLAT tables

2001-01-08 Thread Michal Kozusznik
Hello Andrey, Monday, January 08, 2001, 1:32:15 AM, Andrey G. Sergeev (AKA Andris) wrote: The XLAT tables are stored in the registry under HKCU\SOFTWARE\RIT\The Bat!\XLT. Hmm. That's no so good. I hate soft which stores all unnecessary stuff into registry. Such files like XLAT tables could

Re[2]: incorect XLAT tables

2001-01-08 Thread Marek Mikus
Hello all, Monday, January 08, 2001, Michal Kozusznik wrote: They are updated only as needed. The setup file contains a lot of stuff. Of course, it must contain verything, as this is the file the new user runs; so it is possible that your complete registry key is overwritten with exactly

incorect XLAT tables

2001-01-07 Thread Michal Kozusznik
Hello I've noticed incorect XLAT tables for Central European encoding (ISO 8859-2) in TB! v1.48. I replaced these with old tables (some time ago I've saved it for somebody) and now everything is OK. Additional question: how TB! updates it self? Do every time overwrites all files

Re: incorect XLAT tables

2001-01-07 Thread Andrey G. Sergeev (AKA Andris)
Hello! Monday, January 08, 2001, 1:51:59 AM, Michal Kozusznik [EMAIL PROTECTED] wrote: MK I've noticed incorect XLAT tables for Central European encoding (ISO MK 8859-2) in TB! v1.48. I replaced these with old tables (some time MK ago I've saved it for somebody) and now everything

Re: incorect XLAT tables

2001-01-07 Thread Thomas Fernandez
Hi Andrey, On Mon, 8 Jan 2001 03:32:15 +0300GMT (08/01/2001, 08:32 +0800GMT), Andrey G. Sergeev (AKA Andris) wrote: MK Additional question: how TB! updates it self? Do every time MK overwrites all files (XLAT tables)? Maybe some older version had MK bad tables and it was not replaced?

Re: incorect XLAT tables

2001-01-07 Thread Michal Kozusznik
Hello Thomas, Monday, January 08, 2001, 4:54:41 AM, Thomas Fernandez wrote: They are updated only as needed. The setup file contains a lot of stuff. Of course, it must contain verything, as this is the file the new user runs; so it is possible that your complete registry key is overwritten