开云体育

Helo all. I have install the 1.01 version of PropView. I have the next problem. 1. When i click the Predict button the next mesagge show: Error 13 Run time error. 2. If i click the help button i have a screen for DOS and and must put a filename????? 3. I have also if i click the Config button the same error 13 4. I can not save my Antenna degrees and my output power. 5. The DXView give the long and lat super on DXProp. Who can help me. Ron

This release corrects the runtime error occuring on systems with a locale that doesn't use the period character as a decimal separator. (Ron, this should correct the problem you are encountering with 1.0.1). If you already have PropView 1.0.1 installed, you can upgrade by downloading and running www.qsl.net/propview/PropView102Update.exe -- it will update your online help and install PropView102.exe, which you can then run. 73, Dave, AA6YQ

Dave, Entering a callsign in DXKeeper's capture window and clicking on the question mark next to it causes the callsign to be placed into the filter window and looked up. If the callsign exists in the log, the information is also transferred to DXView which then provides beam heading and progress information. However, if the callsign does not exist in the log, nothing goes to DXView. I could click "lookup" to get the call into DXView but that does other things including noting the start time and I haven't started a QSO yet. ----- 73, Rich - W3ZJ www.w3zj.com

Dave, Now that the solar flare activity seems to have settled a bit, PathView is providing some very nice and accurate information. I think however that it is not always reading the clock. When I first bring it up and do a prediction it shows the vertical time bar in the correct location. However, it never seems to change as I do more predictions at a later time unless I close and reopen it again. ----- 73, Rich - W3ZJ www.w3zj.com

When PropView starts, it initializes the Time field to the then current UTC time. This won't change unless you change it -- either by double-clicking (to set the current time), or by keying in a time. Clicking the "Predict" button does not update the time to the current time, as that would preclude times other than the current time. Since time doesn't play a role in the computation -- its just used to position the vertical time bar -- perhaps it would be more useful to eliminate the "Time" text box (in the Conditions panel of the Parameters tab) and instead make the vertical time bar in the Prediction display "draggable". A prediction would initially position the vertical time bar to the current time, but one could drag it around to serve as an index. Double-clicking the vertical time bar would return it to the current time. Note that a prediction could be for some day other than today, in which case double-clicking the vertical time bar would be positioning it to "the current time on that day". Comments? Better ideas? IonCAP does not consider geomagnetic conditions in its prediction computation. I'm currently scanning the literature for the statistical relationship between the K index and the dimensions of the auroral oval, which would enable DXView to plot the oval and report the extent to which a path experiences polar absorption. I know of at least one propagation program that does this, and therefore assume that documentation of the relationship exists. If anyone is has this information or a reference to it, please send it my way. 73, Dave, AA6YQ

This release - adds an "Import from MMTTY" checkbox to the Import tab, which when checked extracts transmit and receive sequence numbers from imported RST sent and rcvd fields respectively - adds a "Start" button to the QSO Capture window, which when activated designates the QSO start time When you click the Start button, it is replaced by a display of the QSO start time. Clicking the Log or Clear buttons un-hides the Start button. When the QSO Capture window's Callsign textbox has focus, striking the "Insert" key is equivalent to clicking the Start button. Clicking the Lookup button no longer designates the QSO start time. If you've already installed DXKeeper 1.1.1 or later, you can upgrade to version 1.1.9 by downloading and then running http://www.qsl.net/dxkeeper/DXKeeper119Update.exe -- your online help will be updated by this process. 73, Dave, AA6YQ -----Original Message----- From: Dave, AA6YQ [mailto:dhb@...] Sent: Thursday, March 29, 2001 1:31 AM To: dxlab@... Subject: [dxlab] DXLab 1.1.8 is available This release - corrects a defect that produced a crash if you tried to close DXKeeper while it was iconified - in the QSO Capture window, clearing all fields leaves the text entry cursor in the callsign field If you've already installed DXKeeper 1.1.1 or later, you can upgrade to version 1.1.8 by downloading and then running www.qsl.net/dxkeeper/DXKeeper118Update.exe -- your online help will be updated by this process. 73, Dave, AA6YQ Yahoo! Groups Sponsor To unsubscribe from this group, send an email to: dxlab-unsubscribe@... Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

I just worked BX7AA on 21.016. I ran the propagation forecast for him using the current solar flux of 228 (not too shabby) and it showed that I should have propagation but it was between the 10% and 50% MUF lines. I managed to work him but the interesting thing was that the charts showed that propagation to him on that frequency should improve over the next two hours and then begin to drop off. Of course there is no guarantee that he would still be there in two hours but the message to me was that if I had trouble working him at this time I should keep trying because the conditions should be improving. Nice job Dave, this is really useful! ----- 73, Rich - W3ZJ www.w3zj.com

Ron, are you still having problems with PropView settings like Power and TakeOff not being saved between sessions? Is anyone else encountering this? 73, Dave, AA6YQ http://docs.yahoo.com/info/terms/

I have resized DXKeeper already as you had described but I was running 600 x800 resolution. I have up 1024 x 768 It is a little better. The font is smaller but I fortunately have my eyesight. My thought on resizing DXView was to use a similar function that you have on the side and bottom of the log file in DXKeeper to view the list of QSO's that is too large for the window. I have found that I run both DXview and DXkeeper together all of the time. When I hear a DX station I type the call sign in DXKeeper hit enter then look over to DXView to see where the station is. Then I either pass on the QSO or try to make contact. Of course this may change as I do more DXing but for now this is the procedure I have gotten into without even thinking about it. >>>That's how I run DXView and DXKeeper as well. Have you tried the new QSO Capture window in DXKeeper? It lets you work the same way, but consumes much less screen space. The full DXKeeper window need only used when you query for previous QSOs with a station, or for general log maintenance (QSLing, etc). I can certainly give DXView a resizable border, but the result would be to "cut off" information -- there is nothing analogous to DXKeeper's log where I can simply show fewer log entries. Maybe there should be two DXView window sizes -- "full" (displaying all information as you see it now) and "reduced", showing a subset of the information in a smaller window. What would you see as the essential fields in the "reduced" window? I have tried to print QSL cards and have come upon a problem which I think is with my printer. I have and HP 550C which is pretty old. When I tried printing 2 cards the end of the second card was cut off a little. I tried printing the same cards at work on an Epson 740 and had no problem. I cannot find a way to adjust the print area with the HP printer. Any suggestions? >>>I use an HP 895CSE without difficulty, but am unfamiliar with the 550C. All I can suggest is to manipulate the Printer Setup options in the standard Windows way. On another subject... I have DSL at work and a cable modem at home. I use PCanywhwere to do a lot of file transfer and to check my home weather station etc. I would love to be able to work my Icom IC-746 from my laptop at work. Have you heard of anything like this being done? >>>That's certainly feasible given the 746's extended CI-V command set, and there may well be software out there that supports this mode of operation. I'm not aware of any, but you might try posting your question on the Icom reflector, or doing some Internet searching with Alta Vista or Google. >>>By the way, Tom, there's now an email reflector for the DXlab suite (DXKeeper, DXView, WinWarbler, etc.). I've copied the reflector on this message, as your comments and suggestions are quite relevant to the evolution of these applications. If you care to join, you can do so via http://www.qsl.net/dxlab/reflector.htm . 73, Dave, AA6YQ -----Original Message----- From: Bernstein, Dave [mailto:dhb@...] Sent: Tuesday, April 03, 2001 1:06 AM To: me2u@... Subject: RE: Just more stuff. I have been playing around more with your software and I thought that it would be handy to be able to adjust the size of the window for DXview and DXkeeper. I think that I would like to be able to fit both windows in my monitor so I can view the information easier. >>>The only way to make the DXView window smaller would be to shift to smaller fonts; I'm a little reluctant to do that given that I occasionally get feedback that the fonts are already too small! >>>The DXKeeper main window is already resizable in two ways: you can specify which "panels" are visible (using the checkboxes on the Config window), showing nothing but the basic QSO information if desired. And you can drag the window's lower right-hand corner to control the depth of the log display. >>>I'm not sure what version of DXKeeper you are running, but the latest development feature now includes an optional QSO Capture window, which occupies much less screen space and allows you to capture the key QSO information. Give it a try and let me know what you think. >>>What display resolution are you running? Where do you get the postcard paper to print the QSL cards? I cant seem to find them locally. >>>I use 8.5" by 11.5" card stock, which is available in Staples, OfficeMax, or most stationary stores. Card stock is available in different "weights" -- the heavier the weight, the stiffer the card. Your printer documentation should state the maximum weight it can handle. I'm sure this is a lot of extra work but have you thought about enhancing the software so that QSL cards can be customized with pictures, different fonts etc? >>>Adding the ability to superimpose a bitmap graphic on the card would be easy, and is "on the list". Allowing the user to control font selection, font size, and font color is also not hard, though the addition of significantly more "knobs" would require a "print preview" operation. 73, Dave, AA6YQ

Hi Dave, Have just started using PropView and it seems to work well at this QTH. What would make it very quick to use would be the ability to use Country prefixes instead of Latitude and Longitude. All of that information must exist already in DXView...is there any way in which PropView could access that database? Robin gw3zcf

This release adds a "Display Previous QSOs on Lookup" checkbox to the "QSO Capture window" panel of the General configuration tab. When this box is checked, clicking the QSO Capture window's "Lookup" button filters the Log to only display previously logged QSOs with the captured callsign. While looking at the code associated with the "Lookup" button, I noticed that the DXCC prefix associated with the callsign would not be updated (via a DXView query) if some DXCC prefix was already specified. One could always click "Clear" before "Lookup", but why require the extra mouse gesture? So in this release clicking "Lookup" always queries DXView (if running) and updates the DXCC prefix. If you've already installed DXKeeper 1.1.1 or later, you can upgrade to version 1.2.0 by downloading and then running http://www.qsl.net/dxkeeper/DXKeeper120Update.exe -- your online help will be updated by this process. 73, Dave, AA6YQ

Dave, Try the following. In the capture window, enter a callsign of a station that "is" in your log, press enter. All looks fine so far, does the lookup - great. Now click log to log it. Whacky!! If you need more detail let me know, but I think you'll see it. ----- 73, Rich - W3ZJ www.w3zj.com

In the release - there is no longer a "current time" setting - when the Prediction tab's "Show Current Time" box is checked, the Vertical Time Index automatically tracks the current time - you can drag the Vertical Time Index anywhere within the Prediction graph; doing so unchecks the "Shot Current Time" box To drag the Vertical Time Index 1. position the mouse over it 2. press and hold the left mouse button 3. move the mouse left or right 4. release the left mouse button If you already have PropView 1.0.1 installed, you can upgrade by downloading and running www.qsl.net/propview/PropView103Update.exe -- it will update your online help and install PropView103.exe, which you can then run. 73, Dave, AA6YQ

I noted two QSO Capture window defects in the scenario outlined below: #19: clicking the Log button failed to unfilter the log #20: the recorded QSO start time is bogus Was there something else? Both above the above defects are corrected in DXKeeper 1.2.1; when no QSO start time is established (by clicking the Start button), the QSO start time is set to the QSO end time. If you've already installed DXKeeper 1.1.1 or later, you can upgrade to version 1.2.1 by downloading and then running http://www.qsl.net/dxkeeper/DXKeeper121Update.exe -- your online help will be updated by this process. 73, Dave, AA6YQ -----Original Message----- From: Richard B Drake [mailto:rich@...] Sent: Friday, April 06, 2001 18:37 PM To: Dxlab Subject: [dxlab] DXKeeper 1.2.0 Dave, Try the following. In the capture window, enter a callsign of a station that "is" in your log, press enter. All looks fine so far, does the lookup - great. Now click log to log it. Whacky!! If you need more detail let me know, but I think you'll see it. ----- 73, Rich - W3ZJ www.w3zj.com Yahoo! Groups Sponsor To unsubscribe from this group, send an email to: dxlab-unsubscribe@... Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

The title bar UTC clock does not function in this release -- I disabled it while debugging something, forgot to restore it, and failed to notice its condition during pre-release testing. I'll correct it in the next release. Any comments on the proposal to create an alternative DXView window that consumes less screen space by presenting less information and by displaying a smaller map? What fields should be retained in this window? 73, Dave, AA6YQ

Hi Dave, I have upgrade DXView to 1.2.3 and DXKeeper 1.1.7 and will install the latest updates as soon as my work schedule calms down. Having the capture window is exactly what I was looking for. I don't feel a need to have the option to resize DXview any longer. I have never used any sort of reflector before and I find it very effective. Thank You 73 de KB2VNB

Dave, I have used V121 this afternoon to log several contacts and it seems to be working well now. One thing that seems strange is that after logging a contact it picks up the callsign of the previous contact and puts it into DXView. Not a big deal it just seems odd. I am also appreciating the contest fields this afternoon. When I am serious about a contest, I will set up WriteLog which is specifically designed for contesting and has many special contesting features. But if I am just dabbling with a contest such as this weekends SPDX contest (i.e. if I hear an SP calling CQ contest, I'll call him and give him a contact) the additional contest fields and keeping track of sequence number are very nice. ----- 73, Rich - W3ZJ www.w3zj.com

Hi Dave, Is it necessary to install each update individually or does the latest one encompass all updates befor it. I am not able to install each update as they become available. Instead, I have to pile them up and do them all at once when I get my "Ham Time". Thank You 73 de KB2VNB

I hope that SpotCollector is next on your to do list. I find that absence of that is the major reason that I keep reverting to Logger. I think that once the bugs are worked out and SpotCollector implemented this will become my main modus operandi! NetCluster -- obtains spots from Telnet packetclusters PacketCluster -- obtains spots from VHF packetclusters via a TNC connected to a com port CQDX -- obtains DXS spots via the #CQDX IRC channel SpotCollector -- aggregates and displays spots collected from multiple instances of NetCluster, PacketCluster, and CQDX This design makes it possible to simultaneously collect spots from multiple sources and intelligently merge them into a single database. I've implemented NetCluster and SpotCollector and have them basically working. SpotCollector currently lacks DXKeeper's database sort and filter capabilities, and you can't yet configure the presentation of the database fields to your taste. I am having second thoughts about forcing the user to deal with so many different applications . Realistically, the most anyone will do is run two or three NetClusters, one PacketCluster, and one CQDX. So I'm now thinking of packaging these within SpotCollector. While NetCluster, PacketCluster, and CQDX each maintain a window that monitors their respective source, in practice one focuses on the merged database display maintained by SpotCluster. Anyone see a problem with this simplified packaging? > the space is taken up > with control labels and associated whitespace; would an > lacking this nicety be a reasonable alternative? > Hmm! I don't think id like it without any control labels some of them could be abbreviated and made smaller. Let's see .... We don't need the Go button, that could be performed by double clicking the callsign. Prefix could be abbreviated and that field made smaller, Country could be smaller. Lat/Lon can be made slightly smaller, distance can be smaller, grid can be eliminated (put that in the title bar instead of Lat/Lon), Region and Time can be eliminated. The DXCC button could be eliminated and become a tab in the config dialog, help could be reduced to a "?". How does it lay out now? I'd have to see it. Maybe there are a few other economies that could be applied without affecting the functionality. You already have a Map button there. If the main map were hidden by default, clicking that button would display it, clicking on the map itself could toggle between the large scale map and the more detailed ones. The traditional "x" in the title bar would hide the map again. How are we doing? Yahoo! Groups Sponsor To unsubscribe from this group, send an email to: dxlab-unsubscribe@... Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

The "lookup last log entry" blemish is fixed, and clicking Lookup (in the Capture window) now restores input focus to the Callsign textbox. If nothing else shows up for a few hours, I'll release these in DXKeeper 1.2.2 tonight. I'd like to release PropView 1.0.3 and DXView 1.2.7 (with the working title bar clock) to a larger audience, probably via announcement to several DX and propagation reflectors. Any comment on the recent Vertical Time Bar change before I reduce flexibility by adding users? 73, Dave, AA6YQ -----Original Message----- From: Richard B Drake [mailto:rich@...] Sent: Saturday, April 07, 2001 16:10 PM To: Dxlab Subject: [dxlab] DXKeeper 121 Dave, I have used V121 this afternoon to log several contacts and it seems to be working well now. One thing that seems strange is that after logging a contact it picks up the callsign of the previous contact and puts it into DXView. Not a big deal it just seems odd. I am also appreciating the contest fields this afternoon. When I am serious about a contest, I will set up WriteLog which is specifically designed for contesting and has many special contesting features. But if I am just dabbling with a contest such as this weekends SPDX contest (i.e. if I hear an SP calling CQ contest, I'll call him and give him a contact) the additional contest fields and keeping track of sequence number are very nice. ----- 73, Rich - W3ZJ www.w3zj.com Yahoo! Groups Sponsor To unsubscribe from this group, send an email to: dxlab-unsubscribe@... Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.