开云体育

Give de freq where you use the dipool o.k. -----Oorspronkelijk bericht----- Verzonden: dinsdag 24 april 2001 21:04 Aan: dxlab@... Onderwerp: RE: [dxlab] PropView Question Hi Ron, I have

Hi Ron, I have the same questions that Ted has. I have a Windom TNT2X dipole at about 45 feet. I would like to have the formula for calculating the take off as well. Thank you Tom KB2VNB

Deleting a log entry in DXKeeper 1.2.5 does not automatically remove the data from the progress table. ----- 73, Rich - W3ZJ www.w3zj.com

Ted Give me your antenna and high from ground i can calculate your take off if you will Ron -----Oorspronkelijk bericht----- Verzonden: dinsdag 24 april 2001 16:39 Aan: dxlab@...

Hi, I'm new to PropView and DXView and I have a couple of questions on PropView. First, under Conditions is Avail %. Can someone fill me in on what this is and where the information comes from.

This release - corrects the regression introduced in version 1.2.9, in which rotor control enable is not saved between DXView sessions - hides the rotor's Serial Port Interface panel if you select an

Thanks - I'll fix it in the next rev. Dave, AA6YQ

V1.2.9 disables rotor control when closed so that it has to be enabled each time it is brought up. ----- 73, Rich - W3ZJ www.w3zj.com

My pleasure, Mark. Extending Commander to support Yaesu and Kenwood radios is on th list, but behind the Telnet/IRC Cluster interface, KAM support, and some things DXKeeper needs to support

Hello Dave: Your fix worked perfectly. I am back up and running again. Thank you very much for the help. I really appreciate it. I am looking forward to trying the other programs you have. They look

Warning>>> Deleting or modifying the wrong registry entry can result in a corrupt or un-bootable system! <<<Warning The following sequence will remove all registry entries for DXView. When you run

Dave: I have not used REGEDIT before, but I could give it try. Thanks, Mark...

Mark, I'm not sure what's happened exactly, but the program failure is definitely the result of some latent defect. Since I'm unlikely to replicate it here, tracking it down would require me to add

Hello Dave: I am running 98 Second Edition on a PII system. The problem is not in the program. I originally had the DXView version just before your latest release of DXView 1.28 working with Rotor EZ

While 13% is low, its unlikely to be responsible for this problem. Thanks! 73, Dave, AA6YQ

Well, it just so happens that I took a snap shot of my system information at the time of the hang up. Here it is. Note system resources are at 13% free which I felt was insignificant. Microsoft

Not out of the woods yet, obviously. When this happens again, please note the Windows resources levels before terminating DXKeeper. 73, Dave, AA6YQ

Occurred while trying to log a contact with an empty filtered window. The contact was not logged. Error log extract: 20-Apr-2001 09:07:06 > DXKeeper version 1.2.5 startup 20-Apr-2001 15:28:56 >

It works i forget the 0 degrees offset i make always problems they are not there sorry sorry bud it keeps you wake up IT WORKS FINE NOW> Ron

Ron, Assuming that Dave has maintained the same functionality with the Arswin rotor as he has with the Yaesu, you should be able to fix that by defining an appropriate "Rotor offset" in the config