<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:tahoma,new york,times,serif;font-size:12pt"><div style="font-family: tahoma,new york,times,serif; font-size: 12pt;">Hi Larry et all<br><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><br><div>>1/ Before the computer restarted (1st paragraph), was the "Sticky <br>>setting" enabled or not ?<br><br>Paul has already provided answer to this one. The "Sticky setting" was not originally<br>enabled. After the problem was observed, however, enabling "Sticky Setting" would<br>not enforce the R1/R2 designator after restarting Win-Test.<br> In other words - it had no effect at this point. <br><br><br>>2/ When you restarted this computer, you say you were "R2". Had you <br>>entered a QSO on the band you restarted on, at that time, as R2 ? I have <br>>an idea but I have to dig... ;-)<br><br>If I understand
your question correctly, the offending radio continued<br>to operate on the same band it was on before, after the radio designator got changed. <br><br>Before the problem: <br>R1 was logging on 20m<br>R2 was logging on 40m<br><br>Win-Test then got restarted. Radio bearing R2 designator is now renamed R1:<br>R1 remains on 20m<br>R1 (originally R2) remains on 40m<br><br><br>I wonder if it would be possible to implement some sort of control <br>for M/2 setups to warn the operators if computers on the network<br>have been found to have the same radio designator?<br><br> 73, Nick<br>ve3ey <br><br><br><br> </div></div><br></div></div></body></html>