Stephen G4SJP said: > I don't >remember the firmware version where this started but it was certainly not >always the case The problem first appeared last September with "production release" 2.38/1.90. The previous "production release", which I believe was 2.02, was stable. 73 to all Trevor G0KTN