Winlog32 Forums

<t>Hi Gerald<br/> In order to update the log without printing, you must still go through the print procedure. Press the print button (with printer off if necessary), after an aborted attempt at printing it can update the Log proving you answer 'Yes' to the prompts after pressing the update button.<b...

<t>OK Guys I can take a hint!<br/> <br/> I am looking into the possibilities, you guys can help by letting me know what rigs you are looking to hook-up, this will give me some ideas on which to work on first.<br/> <br/> I do not expect that the rig control will be more than simple freq/mode exchange...

<t>Hi<br/> Although Mark has resolved this particular problem, for other readers with similar problems I include the following comments:<br/> <br/> Winlog32 gets data from the "Radio Amateurs Callbook" (RAC) via their propriety DLL file, I am bound by its restrictions.<br/> <br/> Make sure that you ...

<t>Hi David<br/> <br/> Well I had to go back and check this out myself as I remember there was a bug in this area which I can't recall, anyway it is working as expected now - tested on RAC, obviously if auto-date-time is ON cursor will advance to Band select though. Otherwise cursor will return to D...

<t>Hi David<br/> <br/> If this has always been a problem, then are you sure that you are updating the database correctly - using the toolbar 'Update' button?<br/> <br/> After which check that the Log QSLOut field has been updated with the current date, this prevents QSO's being selected for the 'to ...

<t>As good as it is, the Prefix database used in Winlog32 struggles with certain call prefixes, in particular and regularily reported is KG4, the KG4xx calls allocated to Guantanamo Bay whilst the KG4xxx calls are allocated to U.S.A.<br/> Other prefixes like K5K (Kingman Reef) also cause trouble to ...

<t>Hi Guys.<br/> <br/> Thanks for the comments.<br/> <br/> I had several similar suggestions over a period of time, the only problem with this is that on next prefix database update, you will loose these assigned calls/countries as they would be stored inside the prefix database file.<br/> <br/> I h...

<t>Further to the above comments, and in a mad moment, I have now revised the Prefix database further.<br/> You can now store callsigns directly into the Prefix database, this means that you can allocate any Country designator to any callsign. <br/> This new procedure takes place directly from the L...

<t>Hi<br/> <br/> The prefix database allocates the country to each prefix, it's always difficult with the FO0's as they are sometimes working with the same callsign from different island groups/entities. In any case there seems to be a slight hiccup in the prefix database which is ignoring FO/A (it ...

<t>Thanks for the interesting comments.<br/> <br/> It's great to hear that someone can work more than few sqaures at SHF! <br/> <br/> The problem facing me at SHF, is the frequency allocations may not be the same world-wide, Winlog translates frequencies from a broad range of Log frequencies e.g. 23...