开云体育

+ AA6YQ comments below Perhaps it's just my memory failing or me not reading enough posts here but I see that I have a lot of "C" in the DXView matrix for QSO that are fully verified on LoTW. The QSO

Perhaps it is an LOTW bug after all. If I pick one of the "strange" QSO which show up as C rather than V in spite of being verified I see that if I look up the QSO in "My QSO" and click on its QSL

Perhaps it's just my memory failing or me not reading enough posts here but I see that I have a lot of "C" in the DXView matrix for QSO that are fully verified on LoTW. The QSO in question show up as

Perplexity offers this comment about Graphics card memory and system memory: A graphics card primarily uses its own dedicated memory, known as Video RAM (VRAM), for handling graphics-related tasks

+ AA6YQ comments below + Any interface from a reputable supplier that supports your chosen monitor's resolution, refresh rate, and video connector (HDMI or DisplayPort) will be fine. 73, Dave,

I'm continuing to try to define the graphics card requirements for ham radio work specifically like the DXLab suite, N1MM, WSJT-X and such. I am wondering whether a 2D system like AutoCAD might

+ AA6YQ comments below Regarding Spot collector hardware needs, I think they relate to the motherboard hardware and not to the graphics card unless the graphics card uses motherboard resources and

+ AA6YQ comments below I keep getting this error message in DXKeeper. 2025-03-26 23:37:04.549 > Common.Terminate: DXKeeper shutdown 2025-03-27 12:48:23 > DXKeeper version 17.9.9 2025-03-27

Regarding Spot collector hardware needs, I think they relate to the motherboard hardware and not to the graphics card unless the graphics card uses motherboard resources and then a limitation in

I keep getting this error message in DXKeeper. 2025-03-26 23:37:04.549 > Common.Terminate: DXKeeper shutdown 2025-03-27 12:48:23 ? ? > DXKeeper version 17.9.9 2025-03-27 12:48:23 ? ? > App.Path

+ AA6YQ comments below + I did not design SpotCollector or any other DXLab component to detect and exploit the presence of multiple cores. However, testing revealed that SpotCollector's performance

+ AA6YQ comments below + There are two supported forms of interoperation between WSJT-X and DXLab: direct, and via JTAlert. Both forms provide options that direct DXKeeper to perform eQSL and LoTW

I might have spoken prematurely. It seem the if I use the Capture window in DXK the LoTW and eQSL colors come across fine.? However, if the QSO is entered vie WSJT-X the colors are ignored and

So Tom, a related question.? What about the case where I would like log requests going to DXKeeper on one machine to also be logged in the database of a primary copy of DXKeeper on another? In this

Use port 12060 and the latest gateway. Tom NY4I 813-205-6388 ny4i@...

moreover, I have seen that all running processes have affinity set to all CPUs. 73 de Salvatore (I4FYV)

correction: the Task Manager still has the Affinity option, but it is accessible only in "Details" view. Sorry. 73 de Salvatore (I4FYV)

hello, is SpotCollector multi-processor or multi-core aware? I have found a link on a very old article

I'm reviewing various graphics cards and seeing many costing well over $300-400. I'm also seeing various 4K NUC mini computers with 3-4 video outputs (HDMI) that are apparently 4K or even 8K and

The other argument against buying the absolute high end CPU (more CPU than necessary for the purpose) is that Moore's Law still holds when it comes to CPU performance vs. price. By the time the