MSGID: 2:240/1120.29 ed41a801
CHRS: IBMPC 2
TZUTC: 0100
Dear All,

As it turned out, that version contains a bug that causes the location of the
configuration information in the registry to change while the configuration is
read. As a result, Version 369 will fail to read half of the configuration and
afterwards store ALL configuration information DIRECTLY under HK
Y_CURRENT_USER rather than (as intended) under the respective WinPoint Key in
the Software section. Afterwards, it will continue to use the new location and
thuss work essentiall as intended. However, that location is wrong and the
fixed version will again read from the correct location. 

*Thus I strongly recommend _not to use Version 369_. I will provide an updated
test version very shortly that does not have this issue*

Good news: The *old configuration information is still there. So the next
version of WP can still use it*. 

Sorry for the inconvenience
Tim

PS: It is actuall version 369, not build 360 (adding to the confusion) ;)

>-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-<
> Diese Nachricht wurde _weitergeleitet_! Die Originalmail war:               <
>-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-<
> Area: *WINPOINT*
>  Von: *Tim Schattkowsky(2:240/1120.29)*
>   An: *Martin Foster*
> Betr: *Build 369 changes*
> Zeit: *06.11.21* *19:36:18*
>-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-<

Hello Martin,

on 05.11.21 at 11:54:43 You wrote in Area WINPOINT
a message to Tim Schattkowsky 
about "Build 369 changes".

 TS>> BTW: Did you experience any problems with lost settings (e.g., Mailboxes
 TS>> or textgroups gone)?

 MF> Yes, I "lost" the mailbox settings completely but after re-configuring
 MF> the mailbox, it hasn't disappeared since. Something else strange
 MF> happened: the second time I fired up 369.0, it had mysteriously changed
 MF> to the German language but after manually changing back to English, it
 MF> hasn't happened again.

Exactly what happened to me. There must be one "old" setting that causes the
issue on first start, that is overwritten by valid (new) data on exit so it
never pops up again. Will try to find that ... 

Nasty :(

Regards,
Tim

-+- WinPoint 370.1
 @ Origin: Original WinPoint Origin! (2:240/1120.29)
>-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-<
>                    Ende der weitergeleiteten Nachricht                    <
>-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-<
--- WinPoint 371.0
 * Origin: Original WinPoint Origin! (2:240/1120.29)
SEEN-BY: 30/0 221/1 6 229/426 428 664 700 240/1120 261/38 280/464
SEEN-BY: 282/464 1038 292/854 301/0 1 101 113 335/364 341/66 371/0
SEEN-BY: 920/1 2452/250 5020/1042 5058/104
PATH: 240/1120 301/1 229/426