开云体育

I just installed all the programs on Windows 7. It is in an administrator
account but not the hiddened administrator. All so far seems to work

QRZ.COM call lookup. HTat no longer works. It does work if you go to
Pathfinder to do it but not if you click CBA or Lookup. I think they may
have finally enforced direct lookup at QRZ but not sure. Anyhow so faer is
so good fpor Windows 7. I did tuoff UAC by turning it to the Never prompt
level. I shou;ld have tried installing in a Standard user I suppose just

see. J

I just installed all the programs on Windows 7. It is in an administrator
account but not the hiddened administrator. All so far seems to work

QRZ.COM call lookup. HTat no longer works. It does work if you go to
Pathfinder to do it but not if you click CBA or Lookup. I think they may
have finally enforced direct lookup at QRZ but not sure. Anyhow so faer is
so good fpor Windows 7. I did tuoff UAC by turning it to the Never prompt
level. I shou;ld have tried installing in a Standard user I suppose just

see. J

I just installed all the programs on Windows 7. It is in an administrator
account but not the hiddened administrator. All so far seems to work exceptr
QRZ.COM call lookup. HTat no longer works. It does work if you go to
Pathfinder to do it but not if you click CBA or Lookup. I think they may
have finally enforced direct lookup at QRZ but not sure. Anyhow so faer is
so good fpor Windows 7. I did tuoff UAC by turning it to the Never prompt
level. I shou;ld have tried installing in a Standard user I suppose just to
see. J

Dave and the group,

I now have the correct info showing for JD1BMM, after having entered the
grid, zone etc.

Prior to this, I had never entered any data in the line, other than call and
country. I guess maybe it has been sheer coincidence that all other calls
have worked OK, but I connect to a DXSpider cluster, which does append grids
to most calls, but not all.

I tried "local" spots for a few other calls that were in the overrides
panel, but didn't have grid, zone etc specified, and they all appeared to
work as expected. Among others.
I will now complete ALL the boxes when I enter an override!

Thanks for the help, as always, and it is appreciated.

73 de Phil GU0SUP


---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 090910-0, 10/09/2009
Tested on: 11/09/2009 17:52:11
avast! - copyright (c) 1988-2009 ALWIL Software.

Just worked TT8FC, sent-requested qsl = -R- but when I generate 'add

Will add needed also generate an entry in the qsl-queue for a qso for

Just worked TT8FC, sent-requested qsl = Y but when I generate 'add needed'

With 'add requested' the qso is added, but not the old, not yet confirmed

73,

Aart PA3C

I have version 7.7.8 Dx Lab commander install unable to download and upgrade to 7.9.2 error message unable to download?

A workspace is just a folder that contains a file (containing registry settings) for each DXLab application. Workspaces live in the Launcher's Workspace folder.

73,

Dave, AA6YQ

--- In dxlab@..., "n8wrl" <n8wrl@> wrote:

One more question - where are the 'workspaces' stored? I have my log files stored under my user files so they get backed up and will be migrated to Win7. Where are the workspaces so i can back them up and migrate them as well?

-Brian n8wrl

--- In dxlab@..., "Dave AA6YQ" <aa6yq@> wrote:

AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
n8wrl
Sent: Wednesday, September 09, 2009 3:21 PM
To: dxlab@...
Subject: [dxlab] Two (or more) users/logs?


My daughter passed her Tech and got her call yesterday!

Congratulations to both of you!

I would like to set up a fresh log for her in dxlab so we can track her
awards, progress, etc, and 'do something' when it starts so we can pick the
log to work in - hers or mine.

You can create an empty new log for Olivia using the "Log file" panel at

the top of Config window's Log tab. If the pathname for your log file shown
in this panel is

C:&#92;Program Files&#92;DXLab Suite&#92;DXKeeper&#92;Logs&#92;N8WRL.mdb

change this to

C:&#92;Program Files&#92;DXLab Suite&#92;DXKeeper&#92;Logs&#92;KJ4OTY.mdb

and then click the Create button. DXKeeper will create an empty new log, and
open it. To switch back to your log, Brian, you'd click the "Log file"
panel's Select button and double-click N8WRL.mdb in the "select existing
log" window.

At minimum, you'll also need to change the default "Station callsign"

(Config window, Defaults tab) whenever you change operators so that the
correct station callsign will be recorded with each QSO. If you don't mind
sharing the rest of the settings, this will be the fastest approach. If
you'd like to maintain separate settings, you could either direct the
Launcher to setup a pair of Workspaces, save your settings to your
Workspace, and then after Olivia establishes her settings save those to her
Workspace. Switching operators would then entail terminating all DXLab
applications except the Launcher, switching workspaces, and then restarting
your DXLab applications. Alternatively, you could create a separate Windows
user for Olivia, and switch Windows users whenever you switch operators.

I spent some quality time searching this group and the docs to no avail. Any
hints?

See

< Tab>


73,

Dave, AA6YQ

Brian,

I will play with this a bit to see if it will work. It would be a fun
challenge :)

73 es God Bless de KK1L...Ron Rossi (kk1l@...) <><
QTH: Jericho, Vermont
My page:



Ron Rossi wrote:

Brian,

This sounds like a perfect job for AutoHotKey switching the windows and
filling in the fields for you.

73 es God Bless de KK1L...Ron Rossi (kk1l@...) <><
QTH: Jericho, Vermont
My page:



aa6yq wrote:

I can't test it at the moment, but I'm fairly certain that switching Windows users means shutting down all applications and then restarting them. Even if it doesn't, you can't have two different instances of Commander running and connected to the same serial port. So if you're looking for rapid switching in the short-term, I'd perform the switch by loading the new user's log file and changing the default Station Callsign to that of the new user. Eventually, the Launcher will let you switch all settings without having to terminate and restart applications, but this capability is not imminent.

73,

Dave, AA6YQ

--- In dxlab@..., "n8wrl" <n8wrl@> wrote:

Hi Dave!

Long time - hope all is well. Thank you so much for the quick reply. I will try the log-file approach. I also like the seperate windows accounts idea because we're getting ready for a Windows 7 migration here and plan to have seperate accounts for everyone in the family. things are getting a bit cluttered on the default/common acocunt now. One thing I will have to experiment with is how easily I can switch between acocunts - I log in and fire up DXkeeper, we switch users and she logs in and also fires it up. I wonder if we can just use Windows to switch back and forth as we take turns in a pileup. I suspect there will be issues with talking to the radio but will the two programs interoperate ok? We'd each have our own log files but I suspect we'd be sharing the common DB's - DXCC, lotw, etc?

73 everyone!

-Brian n8wrl


--- In dxlab@..., "Dave AA6YQ" <aa6yq@> wrote:

AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
n8wrl
Sent: Wednesday, September 09, 2009 3:21 PM
To: dxlab@...
Subject: [dxlab] Two (or more) users/logs?


My daughter passed her Tech and got her call yesterday!

Congratulations to both of you!

I would like to set up a fresh log for her in dxlab so we can track her
awards, progress, etc, and 'do something' when it starts so we can pick the
log to work in - hers or mine.

You can create an empty new log for Olivia using the "Log file" panel at

the top of Config window's Log tab. If the pathname for your log file shown
in this panel is

C:&#92;Program Files&#92;DXLab Suite&#92;DXKeeper&#92;Logs&#92;N8WRL.mdb

change this to

C:&#92;Program Files&#92;DXLab Suite&#92;DXKeeper&#92;Logs&#92;KJ4OTY.mdb

and then click the Create button. DXKeeper will create an empty new log, and
open it. To switch back to your log, Brian, you'd click the "Log file"
panel's Select button and double-click N8WRL.mdb in the "select existing
log" window.

At minimum, you'll also need to change the default "Station callsign"

(Config window, Defaults tab) whenever you change operators so that the
correct station callsign will be recorded with each QSO. If you don't mind
sharing the rest of the settings, this will be the fastest approach. If
you'd like to maintain separate settings, you could either direct the
Launcher to setup a pair of Workspaces, save your settings to your
Workspace, and then after Olivia establishes her settings save those to her
Workspace. Switching operators would then entail terminating all DXLab
applications except the Launcher, switching workspaces, and then restarting
your DXLab applications. Alternatively, you could create a separate Windows
user for Olivia, and switch Windows users whenever you switch operators.

I spent some quality time searching this group and the docs to no avail. Any
hints?

See

< Tab>


73,

Dave, AA6YQ

------------------------------------

Yahoo! Groups Links

------------------------------------

Yahoo! Groups Links

Those settings are reasonable, Ken.

The FX-5700LE is a reasonably powerful video card. It sounds like your system is intermittently entering a mode in which the CPU rather than the video card is doing the pixel management. You might try downloading the latest driver from nVidia.

73,

Dave, AA6YQ

--- In dxlab@..., "Kenneth D. Grimm, K4XL" <grimm@...> wrote:

Dave AA6YQ wrote:

I am running a Intel Core Duo 6600 CPU clocked at 2.4 GHz. I see little to
no increase in Commander's CPU consumption when scrolling a bandspread full
of spotted callsigns, and that scrolling is smooth (i.e. no disappearances).
If you're seeing a big increase, then your CPU is doing the work instead of
your video adapter.

What version of Windows are you running, Ken?

XP Pro SP3

Assuming its XP, please open the Windows Control Panel's System applet,
select its Advanced tab, and click the Performance panel's Settings button.
In the "Performance Options" window,

- on the "Visual Effects" tab, what option is selected?

Adjust for best performance

- on the Advanced tab, what options are selected in the "Processor
Scheduling" and "Memory Usage" panels?

Programs on both

What sort of video adaptor are you using? If you're not certain, run the
Windows Control Panel's Display applet, select the Settings tab, and click
the Advanced button in the lower-right corner. The resulting window is
adaptor-specific, but should at least indicate the manufacturer and model
number.

nVidia GeForce FX-5700LE

73,

Dave, AA6YQ

The frustrating part is that the behavior is intermittent. This morning as I was checking the settings per your request, I could rapidly QSY with no disappearing calls and yet, last evening, if I were to move the dial only slightly they were gone! I've opened a bunch of programs including my virus scanner to load the CPU and it is currently behaving as it should. Occasionally, when I spin the dial, the marker on the Bandspread window doesn't keep up but rather lags behind in updating. The more I think about this, I'm beginning to think that the problem may well be with the video card.
73,

Ken - K4XL

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Kenneth D. Grimm, K4XL
Sent: Thursday, September 10, 2009 12:32 AM
To: dxlab@...
Subject: [dxlab] Disappearing calls on bandspread dial


What is the best guess for the cause of the calls on the bandspread dial
of Commander disappearing as I tune up or down the band? Insufficient
memory or insufficient computer power? I'm running a 3 GHz P4 with 1
Gig of memory (2 x 512MB) on my DXLab computer.

From looking at the Windows Task Manager window, the CPU usage
increases rather dramatically when tuning and the memory usage stays
fairly constant which probably answers the question for me. :-)
Still, I wonder if others with similar computers notice the calls
disappear as they tune and reappear when you stop. More to the point,
do those of you running duo or quad core Intel computers notice the same
thing.

73,

--
Ken K4XL
k4xl@...