开云体育

Found something interesting about that. If you make a change to a contact in the main QSO window then click save, it adds the info to the progress window. Might help narrow it down a bit. ---- 73,

This release - correctly updates the progess table when QSOs are logged from the Capture window - contains more instrumentation aimed at isolating the "persistent hourglass" problem - if

Dave, I have been running V 1.2.4 most of the day and so far I have been unable to break it. I created a new error log before installing it and so far it's empty. Looking good :-) ----- 73, Rich -

This is a defect, Joe -- PropView's Transmitter Latitude and Longitude are not being properly initialized when DXView is installed. This has been corrected in PropView version 1.0.6, which can be

This release - eliminates several possible causes of the "Cannot open any more tables or queries" error log entry that occurs after many log filter operations - accepts callsigns from DXView

This release - supports rotators controlled by ARSWIN (see http://www.ea4tx.com/inde.htm) - logs the contents of the Prefix texbox (presumably a callsign) in DXKeeper (if running) when you

The correct URL for ARSWIN is http://www.ea4tx.com/inde.htm

I am having a problem getting "DxView to work. When I go to bring it up, I get a "Runtime Error 340 Control array Element '0' Doesn't Exist". Does anyone know what that means. Thanks in advance for

That's certainly a defect, Mark, but you're the first to report it. What version of DXView are you running? On which operating system are you running? Does this failure occur right away, or after you

Dave, So far the new versions of DXKeeper and DXView are running smoothly but we'll run them a little longer before giving a clean bill of health :-) I like the new functionality. One thing, I would

You meen a special button for this Richard that likes great not mistakes to the put two buttons good idea. Ron -----Oorspronkelijk bericht----- Verzonden: vrijdag 20 april 2001 17:49 Aan:

I understand Rich's suggestion to be "striking CTRL-Enter in any QSO Capture Window textbox logs the current information and clears all fields for the next QSO". Should the same behavior apply in

i do not know i have the control box on the printer poort with a switch i must put him on the com poort voor DXview. special button i meen 1 more to to that ctrl and go sorry my poor

-I have it works Dave there is one smal problem but i think thats a calibration problem if i ask JA6 that is 35 degrees he going to 129 so that is it with LOGGER no problem then he is o.k. perhaps i

Yes, that's what I meant Dave. Yes, I think it would work well in the main window as well and would also maintain consistency of the command keys in the different windows. ---- 73, Rich - W3ZJ

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

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

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 >

Not out of the woods yet, obviously. When this happens again, please note the Windows resources levels before terminating DXKeeper. 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