Date   

locked Re: Version 2.50.0 F5 Text Message window

Steve, N3SL
 

Outstanding....  Learn something every day!  

Thanks again for an outstanding app!  Can't fully operate FTx without it!

73,
Steve

On Wed, Apr 14, 2021 at 7:50 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 15/04/2021 7:49 am, Steve, N3SL wrote:
One observation (and request) I'd like to add to this:  In the previous version, when I received a text message, the reply button left the texter's callsign in the address box.  Not so with the new version.  But I will say, in general, the new version is a vast improvement - and thanks, Laurie, for taking feedback/suggestions from all of us!

Steve
I wont go into the complexities why that is not implemented. But, the workaround is simple, but didn't get documented. Click the received message, a single-left click. That automatically populates the Callsign entry window with the Callsign sender of that message and will also perform an online check. You can also click one of your previously sent messages and the recipient callsign will populate the Callsign field.

Also Callsigns that have been messaged (in the current JTAlert session) are listed in the drop-down list below the Callsign entry field so you can find a previously messaged station there if there are no messages to click.


de Laurie VK3AMA


locked Re: api-ms-win-crt-runtime-l1-1-0.dll missing ->> try reinstalling the program to fix

Jim
 

OK NOW WE ARE TALKING... it seems to be working now but had to download the Microsoft Visual C++ 2015 Redistributable as well as two lower .net packages. This was a new install and the first time everything has been working together and it is windows and the never install everything you need.

Now the only problem is I am fighting to learn the organization of the set up now.... specifically I cant find out to scan the .mdb file in dxKeeper but its probably in the docs so I am off to find the info...


thanks again

Jim K3YBN


locked Re: Version 2.50.0 F5 Text Message window

HamApps Support (VK3AMA)
 

On 15/04/2021 7:49 am, Steve, N3SL wrote:
One observation (and request) I'd like to add to this:  In the previous version, when I received a text message, the reply button left the texter's callsign in the address box.  Not so with the new version.  But I will say, in general, the new version is a vast improvement - and thanks, Laurie, for taking feedback/suggestions from all of us!

Steve
I wont go into the complexities why that is not implemented. But, the workaround is simple, but didn't get documented. Click the received message, a single-left click. That automatically populates the Callsign entry window with the Callsign sender of that message and will also perform an online check. You can also click one of your previously sent messages and the recipient callsign will populate the Callsign field.

Also Callsigns that have been messaged (in the current JTAlert session) are listed in the drop-down list below the Callsign entry field so you can find a previously messaged station there if there are no messages to click.


de Laurie VK3AMA


locked Re: Getting fed up..... #FT8

HamApps Support (VK3AMA)
 

On 15/04/2021 9:11 am, Joe Subich, W4TV wrote:
I completely disable the power saving features
of Windows; 2) I disable "fast boot" (A.K.A. "hybrid sleep")

Same here.

Disabling USB power saving should be standard operating practice when operating any of the sound-card modes,
in my opinion. For me it is a mandatory setup on all PCs. Just like having a reliable and accurate NTP source when operating the the JT modes, it is not an option, again IMO.

de Laurie VK3AMA


locked Re: Ver 2.50.0 issues

Russ Ravella
 

An assignable window sounds like a great idea to me, Laurie  !

As it is, the more I use this the more I love it - again, thanks so much  !

Russ KR6W


On Apr 14, 2021, at 4:52 PM, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:

On 15/04/2021 9:26 am, Bill Barrett wrote:
Or one window with multiple partitions? Okay, hope you get a laugh [or at least a giggle] out of this.

73. Bill W2PKY

Not as far-fetched as you think. Are you aware the Callsigns window already has an additional partition that display Stations calling you?

Rather than multiple partitions, perhaps one additional partition with the ability for the user to assign what sort of decodes appear there, say CQs or 73s or a specific Alert type (like Dxcc or State) with the ability for the Callsigns to persist for a period of time (ie they don't automatically get cleared at the end of a period like the main display partition).

The beauty with the new code and desktop UI creation tools is the flexibility it gives me in adding new functionality with minimal fuss, aka headaches. Not that this is an acknowledgement of what you propose will happen, but I am not apposed to the idea.

de Laurie VK3AMA



locked Re: Getting fed up..... #FT8

HamApps Support (VK3AMA)
 

On 15/04/2021 8:16 am, Gilles beaulieu wrote:

Mike, I forgot to mention that I get them but only in the callsign window of JTAlert, but can't click on them if I want to chase some DX callsign for example.

Gilles
Non-coloring of decodes in WSJT-X by JTAlert and non-response to JTAlert Callsigns clicks is a classic problem that is more common in recent months with the new WSJT-X releases.

The fix is simple, enable the "UDP Accept requests" in WSJT-X, Settings window, Reporting tab.

For some reason, this setting is getting unchecked for many users with recent WSJT-X releases. I don't know if it is a defect in WSJT-X or the user setting up new configs in WSJT-X which will by default not have that setting enabled. I suspect the latter scenario.

de Laurie VK3AMA


locked Re: Ver 2.50.0 issues

HamApps Support (VK3AMA)
 

On 15/04/2021 9:26 am, Bill Barrett wrote:
Or one window with multiple partitions? Okay, hope you get a laugh [or at least a giggle] out of this.

73. Bill W2PKY

Not as far-fetched as you think. Are you aware the Callsigns window already has an additional partition that display Stations calling you?

Rather than multiple partitions, perhaps one additional partition with the ability for the user to assign what sort of decodes appear there, say CQs or 73s or a specific Alert type (like Dxcc or State) with the ability for the Callsigns to persist for a period of time (ie they don't automatically get cleared at the end of a period like the main display partition).

The beauty with the new code and desktop UI creation tools is the flexibility it gives me in adding new functionality with minimal fuss, aka headaches. Not that this is an acknowledgement of what you propose will happen, but I am not apposed to the idea.

de Laurie VK3AMA


locked Re: api-ms-win-crt-runtime-l1-1-0.dll missing ->> try reinstalling the program to fix

Jim
 

awesome first piece of good news I have heard in the last two days Laurie.... thank you thank you thank you. I will download 
the Microsoft Visual C++ 2015 Redistributable  and install it.  What I have been worried about is that I need to have a medical procedure done next thursday and I want to let another ham use my system while I am laid up. He is not very knowledgeable about digital no DXlab so I wanted everything working correctly for him. He has not been on the air in about 25 years.

In any way thanks and please dont ever stop supporting windows 7 64 bit.... the later versions have too much government spy ware in it.

Jim 


locked Re: Ver 2.50.0 issues

Bill Barrett
 

Hello Laurie-

Yes sorting multiple sets of data would be unacceptable of course. After thinking about it, I came up with this brainstorm.
How about multiple Callsigns windows where one contains CQ calls, second has 73 calls and a third with all the rest?
These windows could be re-sizeable. Or one window with multiple partitions? Okay, hope you get a laugh [or at least a giggle] out of this.

73. Bill W2PKY

On Tue, Apr 13, 2021 at 9:26 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 14/04/2021 10:41 am, Bill Barrett wrote:
Moved over to Multicast and all is well now.

Couple of "Nice to Haves"

1. Filter USA calls only. I run HF - 6M on my 6700 so want to see: Caribbean, Mexico, Canada which are filtered out by the N.A. filter. 
   Filtering out USA calls in the Callsigns window would reduce the number of entries on busy bands like 40 & 20M. 
   Finally, it would be nice if each Callsigns window could have it's own filters.

2. Sort Callsigns window by 1, CQ  2. 73 3. DX 4. all others.

Thanks, could not operate FT8 without this app.

Bill W2PKY

Good stuff!

1. USA only filtering is on the todo list along with every other Country. It's unlikely to happen in the near future however. The same applies for Filtering at the Callsigns window level. Everything displayed in the Callsigns window is still coming from the old JTAlert code and there are issues with trying to implement this currently.

2. Sorting, very unlikely to happen. Sorting by its nature consumes extra CPU resources, depending on the algorithm used adding to a slowdown of the Callsigns display. The biggest problem however is that to sort a list of decodes, by any criteria (frequency, db, message type, country, etc) requires that all the decodes are available prior to sorting which means hanging onto the decodes and waiting till they have all been received and then applying the sort.  That would add seconds to the time to display the Callsigns. With WSJT-X now supporting early decoding and up to 3 passes, holding off the Callsigns display until all have been received is a show-stopper, IMO.

There are alternate solutions to sorting in batches but they will result in a continuous shuffling of the Callsigns in the display as each is received from WSJT-X, with the shuffling ending only after all decodes have been received.


de Laurie VK3AMA




locked Re: Win10 updates and USB device reassignments. I have a theory.

Robie - AJ4F
 

Laurie,

I do the same as you and I have not had any issues so far.

Robie - AJ4F 

On Wed, Apr 14, 2021, 5:47 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
I noted the recent flurry of messages today after the most recent Win10 update causing USB device reassignments. Both my Win10 PCs were updated today without the USB reassignments. In fact, I have never encountered the devices being reassigned as many others have. That got me thinking.

I always keep my PCs updated, I don't permanently postpone Windows updates as some have advocated to avoid the problem. Having an un-updated PC connected to the Internet is asking for trouble, likely more trouble than that caused by device reassignments, IMO. At most I postpone updates for a couple of hours.

Why don't I get these reassignment problems? My theory is that it is due to not allowing Windows to update itself while the PC is in an idle state, like 2 or 3 in the morning, as it typically wants. I have windows set to notify that updates have been download and are ready to apply. I then allow the updates while I am watching the PC, and importantly, all my connected devices are active. That is none of my connected USB devices are asleep or hibernating during the update.

I wonder if Windows is reassigning devices because during its update, devices that it was previously aware of are not found, so reassigns. If all device are connected I suspect Windows will not reassign.

Comments?

de Laurie VK3AMA


locked Re: .NET 5 and W7 home premium

Brian D
 

Installed OK here, W7 Home premium (64 bit) sp1


"John" <ve3kkqve3kkq@gmail.com> wrote:

Dave,

Easiest way to find out is to install .NET5. It'll let you know.

John VE7KKQ

On Wed, Apr 14, 2021 at 9:10 AM David Gould <dave@g3ueg.co.uk> wrote:

I have seen some postings that .NET 5 has installed OK with W7 Pro, but
I have not seen anything regarding W7 Home premium (64 bit)

I am a computer user not a technician, I would appreciate any guidance
on whether I can upgrade and if so how? or am I stuck with the current
version of JT Alert.

I know I can go back to previous versions of JT Alert, but can I go back
to my current version of .NET (4.8) if I encounter any problems with the
upgrade?

73, Dave G3UEG







--
Brian D
G3VGZ G8AOE G3T
IO94im


locked Re: Win10 updates and USB device reassignments. I have a theory.

Joe Subich, W4TV
 

On 2021-04-14 6:47 PM, HamApps Support (VK3AMA) wrote:

Why don't I get these reassignment problems? My theory is that it is
due to not allowing Windows to update itself while the PC is in an
idle state, like 2 or 3 in the morning, as it typically wants. I have
windows set to notify that updates have been download and are ready
to apply. I then allow the updates while I am watching the PC, and
importantly, all my connected devices are active. That is none of my
connected USB devices are asleep or hibernating during the update.
I find the same. I do not leave my computers run 24 x 7. Windows will
download (and install) updates while the computers are running. When I
shutdown at the end of the day, the updates will automatically install.

In addition, I completely disable the "power saving" features of Windows
- specifically USB Selective Suspend and allowing Windows to turn off
devices (serial ports, etc.) to "save power" - *AND* I disable "fast
boot" (A.K.A. "Hybrid sleep") which forces Windows to load kernel
drivers (sound cards, serial ports, network ports, etc.) *FROM DISK*
rather than reload a snapshot of the saved kernel *on every boot-up*.

The only time I have ever had an audio problem after a Windows Update
is when one of the external devices was physically disconnected *or*
when all of the cables had become disconnected from the RealTek sound
card in the computer (the "Windows default device"). In both cases,
reconnecting the device(s) and REBOOTING (RESTARTING) Windows returned
my normal operation.

73,

... Joe, W4TV


On 2021-04-14 6:47 PM, HamApps Support (VK3AMA) wrote:
I noted the recent flurry of messages today after the most recent Win10 update causing USB device reassignments. Both my Win10 PCs were updated today without the USB reassignments. In fact, I have never encountered the devices being reassigned as many others have. That got me thinking.
I always keep my PCs updated, I don't permanently postpone Windows updates as some have advocated to avoid the problem. Having an un-updated PC connected to the Internet is asking for trouble, likely more trouble than that caused by device reassignments, IMO. At most I postpone updates for a couple of hours.
Why don't I get these reassignment problems? My theory is that it is due to not allowing Windows to update itself while the PC is in an idle state, like 2 or 3 in the morning, as it typically wants. I have windows set to notify that updates have been download and are ready to apply. I then allow the updates while I am watching the PC, and importantly, all my connected devices are active. That is none of my connected USB devices are asleep or hibernating during the update.
I wonder if Windows is reassigning devices because during its update, devices that it was previously aware of are not found, so reassigns. If all device are connected I suspect Windows will not reassign.
Comments?
de Laurie VK3AMA


locked Re: the .NET 5 Desktop Runtime 64bit (x64)

Jim
 

Russ,
this is the problem with Microsoft. They have all these cryptic errors and no way to tell what is actually wrong and half the time if you ask them what that error means they give you some kind of BS for an answer.  Its annoying.  I wish DXLab and All the WSJT-x software (some may already be) was able to run under Linux so we could get away from Windows.  

Jim K3YBN


locked Re: Getting fed up..... #FT8

Joe Subich, W4TV
 

On 2021-04-14 6:54 PM, Ron / W4MMP via groups.io wrote:
Hum, OK. How do you know that is not likely to help? Have you tried
what I have suggested and found that it does not help?
Good grief! Phil asked my opinion, I gave it along with my experience
with more sound devices that anyone else here (except a Flex user with
no limits on DAX devices) is likely to encounter.

Like Laurie, I do not allow my systems to update in the middle of
the night *AND* 1) I completely disable the power saving features
of Windows; 2) I disable "fast boot" (A.K.A. "hybrid sleep") to force
Windows to load kernel drivers (including sound/USB devices) from
the hard drive on every boot.

As I said, I have not had significant issues with audio endpoint
scrambling and have only seen it when one or more devices has been
physically disconnected during an update. In that case, reconnecting
the missing device and *REBOOTING WINDOWS* generally returns the
proper configuration.

73,

... Joe, W4TV


On 2021-04-14 6:54 PM, Ron / W4MMP via groups.io wrote:
Hum, OK.   How do you know that is not likely to help?  Have you tried
what I have suggested and found that it does not help?
At any rate, I find naming devices to something that is more
recognizable helps when configuring applications.
73,
Ron / W4MMP
On 4/14/2021 18:38, Joe Subich, W4TV wrote:
On 2021-04-14 5:21 PM, Phil Cooper via groups.io wrote:
>
Also, I use a microHAM MK11 as a connection between the PC and my
radio (IC7800) and I wonder if Joe W4TV can confirm whether it is
> permissible to change the name of the microHAM sound devices?

Yes, it is permissible to change the names (Line, Headset earphone,
Headset microphone) but is not likely to provide any more resistance
to Windows' messing with assignments for the other sound cards in
the system. Changes to the other cards, particularly arbitrary
changes in the "Default Device" and "Default Communications Device"
for both recording (receive) and playback (transmit) are more often
responsible for audio problems.

Perhaps I've been lucky but I have seven Playback devices (Line
[MK III], Line [MK II], Speakers [computer], Speakers [USB Audio
CODEC - MK2R+], Speakers [USB Voice CODEC - MK2R+], and 2 x VAC)
and 11 Recording devices (Microphone [MK III], Line [MK III],
Headset mic [MK II], Line [MK II], Line [computer], mic [computer],
microphone [USB Audio CODEC - MK2R+], microphone [USB Voice CODEC -
MK2R+], 2 x VAC, "Stereo Mix" [computer]) and have not had any
significant problem with scrambling of audio endpoints as a result
of Windows Updates.

73,

... Joe, W4TV


On 2021-04-14 5:21 PM, Phil Cooper via groups.io wrote:
Hi all,



I am in the process of getting a new Win10Pro box set up for the shack, and one of the “horrors” of Win10 that I am aware of (especially relating to radio software) is the fact that audio devices often end up being messed up.



This idea sounds really good, so is it really true? Can others confirm that this is correct?



Also, I use a microHAM MK11 as a connection between the PC and my radio (IC7800) and I wonder if Joe W4TV can confirm whether it is permissible to change the name of the microHAM sound devices?



Any advice would be welcomed….



I am not even going to try and install v2.5.0 or .NET5 on my old Win7pro (32bit) PC, as it is struggling already, and I would like to be able to network it so that I can retrieve files, check ini files etc once I have swapped them out.



73 de Phil GU0SUP





From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Ron / W4MMP via groups.io
Sent: 14 April 2021 17:02
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Getting fed up..... #FT8



Hi,

I never have this problem with any Windows update. This I believe is due to the fact that I give a name to the sound devices I care about. It appears that Windows updates don't mess with named sound devices. Do a similar naming operation for any USB/Serial adapters you care about. That is performed in the device manager. Give the USB/Serial device a com port number away from the default com port number (com1,com3,etc) such as com14.







73,
Ron / W4MMP

On 4/14/2021 11:25, Michael Black via groups.io wrote:

Yeah...I had the same problem and so did a friend of mine with the latest update.



Had to uninstall all sound devices (make sure you select View/Show hidden devices too) and reboot to let them install again...



Mike W9MDB









On Wednesday, April 14, 2021, 10:23:23 AM CDT, Paul <mailto:w2ec@arrl.net> <w2ec@arrl.net> wrote:





Are you running windows 10? Tuesday they did an update, it has scrambled many usb drivers to different ports, changed parameters etc. Took me over an hour to recover all mu USB attachments. Just one more of the windows features they keep forcing on us.



W2EC Paul



On Wednesday, April 14, 2021, 11:17:49 AM EDT, Michael Black via groups.io <mailto:mdblack98=yahoo.com@groups.io> <mdblack98=yahoo.com@groups.io> wrote:





What "same messages" ??



Mike W9MDB









On Wednesday, April 14, 2021, 10:15:34 AM CDT, Gilles beaulieu <mailto:ve3npi@outlook.com> <ve3npi@outlook.com> wrote:





Hi Laurie, really getting fed up with this FT* stuff. I have done many contacts in the past. Here's what I have here: Yaesu FTDX-1200, scu-17, running ACLog, WSJT-X (ver. 2.3.0) and the latest JTAlert. I had it running perfectly without any hassles yesterday. Today I rebooted my PC and started JTAlert and try to make a few contacts. I keep getting errors with the sound card. No matter what I change in the setup it keeps crashing on me with the same messages. Not impressed at all.
Gilles - ve3npi











locked Re: Getting fed up..... #FT8

John Petrocelli
 

Hello,

  I think someone mentioned that actually "Naming" the devices may mitigate this.  Perhaps it was only for the COM ports

John
John R. Petrocelli - WA2HIP
¶¶¶¶¶¶¶¶¶¶
Primary Home Page:
   http://wa2hip.com
On 2021-04-14 21:48, Michael Black via groups.io wrote:
Microsoft likes to mess with the USB device every few updates.
All you have to do if you have a problem is uninstall all your audio devices and reboot.

I (and many others) have had to do this multiple times over the last several years.

It's not every update...but seems like it's the major ones that tend to mess with USB devices.
Can happen to both audio and COM ports.

Mike W9MDB




On Wednesday, April 14, 2021, 04:43:40 PM CDT, Phil Cooper via groups.io <pcooper@...> wrote:


Hi all,

 

I am in the process of getting a new Win10Pro box set up for the shack, and one of the “horrors” of Win10 that I am aware of (especially relating to radio software) is the fact that audio devices often end up being messed up.

 

This idea sounds really good, so is it really true? Can others confirm that this is correct?

 

Also, I use a microHAM MK11 as a connection between the PC and my radio (IC7800) and I wonder if Joe W4TV can confirm whether it is permissible to change the name of the microHAM sound devices?

 

Any advice would be welcomed….

 

I am not even going to try and install v2.5.0 or .NET5 on my old Win7pro (32bit) PC, as it is struggling already, and I would like to be able to network it so that I can retrieve files, check ini files etc once I have swapped them out.

 

73 de Phil GU0SUP

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Ron / W4MMP via groups.io
Sent: 14 April 2021 17:02
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Getting fed up..... #FT8

 

Hi,

I never have this problem with any Windows update.  This I believe is due to the fact that I give a name to the sound devices I care about.  It appears that Windows updates don't mess with named sound devices.  Do a similar naming operation for any USB/Serial adapters you care about.  That is performed in the device manager.  Give the USB/Serial device a com port number away from the default com port number (com1,com3,etc) such as com14.  

 

73,
Ron / W4MMP

On 4/14/2021 11:25, Michael Black via groups.io wrote:

Yeah...I had the same problem and so did a friend of mine with the latest update.

 

Had to uninstall all sound devices (make sure you select View/Show hidden devices too) and reboot to let them install again...

 

Mike W9MDB

 

 

 

 

On Wednesday, April 14, 2021, 10:23:23 AM CDT, Paul <w2ec@...> wrote:

 

 

Are you running windows 10? Tuesday they did an update, it has scrambled many usb drivers to different ports, changed parameters etc. Took me over an hour to recover all mu USB attachments. Just one more of the windows features they keep forcing on us. 

 

W2EC Paul

 

On Wednesday, April 14, 2021, 11:17:49 AM EDT, Michael Black via groups.io <mdblack98@...> wrote:

 

 

What "same messages" ??

 

Mike W9MDB

 

 

 

 

On Wednesday, April 14, 2021, 10:15:34 AM CDT, Gilles beaulieu <ve3npi@...> wrote:

 

 

Hi Laurie, really getting fed up with this FT* stuff. I have done many contacts in the past. Here's what I have here: Yaesu FTDX-1200, scu-17, running ACLog, WSJT-X (ver. 2.3.0) and the latest JTAlert. I had it running perfectly without any hassles yesterday. Today I rebooted my PC and started JTAlert and try to make a few contacts. I keep getting errors with the sound card. No matter what I change in the setup it keeps crashing on me with the same messages. Not impressed at all.
Gilles - ve3npi



Virus-free. www.avast.com


locked Re: Getting fed up..... #FT8

Ron / W4MMP
 

Hum, OK.   How do you know that is not likely to help?  Have you tried
what I have suggested and found that it does not help?

At any rate, I find naming devices to something that is more
recognizable helps when configuring applications.

73,
Ron / W4MMP

On 4/14/2021 18:38, Joe Subich, W4TV wrote:
On 2021-04-14 5:21 PM, Phil Cooper via groups.io wrote:
>
Also, I use a microHAM MK11 as a connection between the PC and my
radio (IC7800) and I wonder if Joe W4TV can confirm whether it is
> permissible to change the name of the microHAM sound devices?

Yes, it is permissible to change the names (Line, Headset earphone,
Headset microphone) but is not likely to provide any more resistance
to Windows' messing with assignments for the other sound cards in
the system. Changes to the other cards, particularly arbitrary
changes in the "Default Device" and "Default Communications Device"
for both recording (receive) and playback (transmit) are more often
responsible for audio problems.

Perhaps I've been lucky but I have seven Playback devices (Line
[MK III], Line [MK II], Speakers [computer], Speakers [USB Audio
CODEC - MK2R+], Speakers [USB Voice CODEC - MK2R+], and 2 x VAC)
and 11 Recording devices (Microphone [MK III], Line [MK III],
Headset mic [MK II], Line [MK II], Line [computer], mic [computer],
microphone [USB Audio CODEC - MK2R+], microphone [USB Voice CODEC -
MK2R+], 2 x VAC, "Stereo Mix" [computer]) and have not had any
significant problem with scrambling of audio endpoints as a result
of Windows Updates.

73,

... Joe, W4TV


On 2021-04-14 5:21 PM, Phil Cooper via groups.io wrote:
Hi all,



I am in the process of getting a new Win10Pro box set up for the shack, and one of the “horrors” of Win10 that I am aware of (especially relating to radio software) is the fact that audio devices often end up being messed up.



This idea sounds really good, so is it really true? Can others confirm that this is correct?



Also, I use a microHAM MK11 as a connection between the PC and my radio (IC7800) and I wonder if Joe W4TV can confirm whether it is permissible to change the name of the microHAM sound devices?



Any advice would be welcomed….



I am not even going to try and install v2.5.0 or .NET5 on my old Win7pro (32bit) PC, as it is struggling already, and I would like to be able to network it so that I can retrieve files, check ini files etc once I have swapped them out.



73 de Phil GU0SUP





From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Ron / W4MMP via groups.io
Sent: 14 April 2021 17:02
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Getting fed up..... #FT8



Hi,

I never have this problem with any Windows update. This I believe is due to the fact that I give a name to the sound devices I care about. It appears that Windows updates don't mess with named sound devices. Do a similar naming operation for any USB/Serial adapters you care about. That is performed in the device manager. Give the USB/Serial device a com port number away from the default com port number (com1,com3,etc) such as com14.







73,
Ron / W4MMP

On 4/14/2021 11:25, Michael Black via groups.io wrote:

Yeah...I had the same problem and so did a friend of mine with the latest update.



Had to uninstall all sound devices (make sure you select View/Show hidden devices too) and reboot to let them install again...



Mike W9MDB









On Wednesday, April 14, 2021, 10:23:23 AM CDT, Paul <mailto:w2ec@arrl.net> <w2ec@arrl.net> wrote:





Are you running windows 10? Tuesday they did an update, it has scrambled many usb drivers to different ports, changed parameters etc. Took me over an hour to recover all mu USB attachments. Just one more of the windows features they keep forcing on us.



W2EC Paul



On Wednesday, April 14, 2021, 11:17:49 AM EDT, Michael Black via groups.io <mailto:mdblack98=yahoo.com@groups.io> <mdblack98=yahoo.com@groups.io> wrote:





What "same messages" ??



Mike W9MDB









On Wednesday, April 14, 2021, 10:15:34 AM CDT, Gilles beaulieu <mailto:ve3npi@outlook.com> <ve3npi@outlook.com> wrote:





Hi Laurie, really getting fed up with this FT* stuff. I have done many contacts in the past. Here's what I have here: Yaesu FTDX-1200, scu-17, running ACLog, WSJT-X (ver. 2.3.0) and the latest JTAlert. I had it running perfectly without any hassles yesterday. Today I rebooted my PC and started JTAlert and try to make a few contacts. I keep getting errors with the sound card. No matter what I change in the setup it keeps crashing on me with the same messages. Not impressed at all.
Gilles - ve3npi











locked Re: Getting fed up..... #FT8

HamApps Support (VK3AMA)
 

On 15/04/2021 7:21 am, Phil Cooper via groups.io wrote:
I use a microHAM MK11 as a connection between the PC and my radio (IC7800) and I wonder if Joe W4TV can confirm whether it is permissible to change the name of the microHAM sound devices?

Phil,

Exact same setup here, 7800 & MKII. None of my Microham audio devices have been renamed. They are still using factory default naming. I never encountered the audio device reassignments after a Windows10 update that others have. See my theory on why in this message https://hamapps.groups.io/g/Support/message/34216

To be safe I suggest you wait for some authoritative feedback from MicroHam, aka Joe W4TV.

de Laurie VK3AMA


locked Win10 updates and USB device reassignments. I have a theory.

HamApps Support (VK3AMA)
 

I noted the recent flurry of messages today after the most recent Win10 update causing USB device reassignments. Both my Win10 PCs were updated today without the USB reassignments. In fact, I have never encountered the devices being reassigned as many others have. That got me thinking.

I always keep my PCs updated, I don't permanently postpone Windows updates as some have advocated to avoid the problem. Having an un-updated PC connected to the Internet is asking for trouble, likely more trouble than that caused by device reassignments, IMO. At most I postpone updates for a couple of hours.

Why don't I get these reassignment problems? My theory is that it is due to not allowing Windows to update itself while the PC is in an idle state, like 2 or 3 in the morning, as it typically wants. I have windows set to notify that updates have been download and are ready to apply. I then allow the updates while I am watching the PC, and importantly, all my connected devices are active. That is none of my connected USB devices are asleep or hibernating during the update.

I wonder if Windows is reassigning devices because during its update, devices that it was previously aware of are not found, so reassigns. If all device are connected I suspect Windows will not reassign.

Comments?

de Laurie VK3AMA


locked Re: Getting fed up..... #FT8

Joe Subich, W4TV
 

On 2021-04-14 5:21 PM, Phil Cooper via groups.io wrote:

Also, I use a microHAM MK11 as a connection between the PC and my radio (IC7800) and I wonder if Joe W4TV can confirm whether it is permissible to change the name of the microHAM sound devices?
Yes, it is permissible to change the names (Line, Headset earphone,
Headset microphone) but is not likely to provide any more resistance
to Windows' messing with assignments for the other sound cards in
the system. Changes to the other cards, particularly arbitrary
changes in the "Default Device" and "Default Communications Device"
for both recording (receive) and playback (transmit) are more often
responsible for audio problems.

Perhaps I've been lucky but I have seven Playback devices (Line
[MK III], Line [MK II], Speakers [computer], Speakers [USB Audio
CODEC - MK2R+], Speakers [USB Voice CODEC - MK2R+], and 2 x VAC)
and 11 Recording devices (Microphone [MK III], Line [MK III],
Headset mic [MK II], Line [MK II], Line [computer], mic [computer],
microphone [USB Audio CODEC - MK2R+], microphone [USB Voice CODEC -
MK2R+], 2 x VAC, "Stereo Mix" [computer]) and have not had any
significant problem with scrambling of audio endpoints as a result
of Windows Updates.

73,

... Joe, W4TV


On 2021-04-14 5:21 PM, Phil Cooper via groups.io wrote:
Hi all,
I am in the process of getting a new Win10Pro box set up for the shack, and one of the “horrors” of Win10 that I am aware of (especially relating to radio software) is the fact that audio devices often end up being messed up.
This idea sounds really good, so is it really true? Can others confirm that this is correct?
Also, I use a microHAM MK11 as a connection between the PC and my radio (IC7800) and I wonder if Joe W4TV can confirm whether it is permissible to change the name of the microHAM sound devices?
Any advice would be welcomed….
I am not even going to try and install v2.5.0 or .NET5 on my old Win7pro (32bit) PC, as it is struggling already, and I would like to be able to network it so that I can retrieve files, check ini files etc once I have swapped them out.
73 de Phil GU0SUP
From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Ron / W4MMP via groups.io
Sent: 14 April 2021 17:02
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Getting fed up..... #FT8
Hi,
I never have this problem with any Windows update. This I believe is due to the fact that I give a name to the sound devices I care about. It appears that Windows updates don't mess with named sound devices. Do a similar naming operation for any USB/Serial adapters you care about. That is performed in the device manager. Give the USB/Serial device a com port number away from the default com port number (com1,com3,etc) such as com14.
73,
Ron / W4MMP
On 4/14/2021 11:25, Michael Black via groups.io wrote:
Yeah...I had the same problem and so did a friend of mine with the latest update.
Had to uninstall all sound devices (make sure you select View/Show hidden devices too) and reboot to let them install again...
Mike W9MDB
On Wednesday, April 14, 2021, 10:23:23 AM CDT, Paul <mailto:w2ec@arrl.net> <w2ec@arrl.net> wrote:
Are you running windows 10? Tuesday they did an update, it has scrambled many usb drivers to different ports, changed parameters etc. Took me over an hour to recover all mu USB attachments. Just one more of the windows features they keep forcing on us.
W2EC Paul
On Wednesday, April 14, 2021, 11:17:49 AM EDT, Michael Black via groups.io <mailto:mdblack98=yahoo.com@groups.io> <mdblack98=yahoo.com@groups.io> wrote:
What "same messages" ??
Mike W9MDB
On Wednesday, April 14, 2021, 10:15:34 AM CDT, Gilles beaulieu <mailto:ve3npi@outlook.com> <ve3npi@outlook.com> wrote:
Hi Laurie, really getting fed up with this FT* stuff. I have done many contacts in the past. Here's what I have here: Yaesu FTDX-1200, scu-17, running ACLog, WSJT-X (ver. 2.3.0) and the latest JTAlert. I had it running perfectly without any hassles yesterday. Today I rebooted my PC and started JTAlert and try to make a few contacts. I keep getting errors with the sound card. No matter what I change in the setup it keeps crashing on me with the same messages. Not impressed at all.
Gilles - ve3npi


locked Re: Getting fed up..... #FT8

Gilles beaulieu
 

Mike, I forgot to mention that I get them but only in the callsign window of JTAlert, but can't click on them if I want to chase some DX callsign for example.

Thanks again

Gilles

On 4/14/2021 6:12 PM, Gilles beaulieu wrote:

Hi Mike, that's what I thought, they are both check but don't get the color highlights.

Guess I'll have to read some more...

Thanks


On 4/14/2021 6:04 PM, Michael Black via groups.io wrote:
Check these settings in JTAlert.







On Wednesday, April 14, 2021, 04:58:55 PM CDT, Gilles beaulieu <ve3npi@...> wrote:


Thanks Mike I'll keep that in mind for next time.

Another small problem is on WSJT-X Band Activity used to get some callsign were highlighted different color. I don't get that anymore... Did I miss something along the way? any ideas?

Thanks

Gilles - VE3NPI

On 4/14/2021 5:48 PM, Michael Black via groups.io wrote:
Microsoft likes to mess with the USB device every few updates.
All you have to do if you have a problem is uninstall all your audio devices and reboot.

I (and many others) have had to do this multiple times over the last several years.

It's not every update...but seems like it's the major ones that tend to mess with USB devices.
Can happen to both audio and COM ports.

Mike W9MDB




On Wednesday, April 14, 2021, 04:43:40 PM CDT, Phil Cooper via groups.io <pcooper@...> wrote:


Hi all,

 

I am in the process of getting a new Win10Pro box set up for the shack, and one of the “horrors” of Win10 that I am aware of (especially relating to radio software) is the fact that audio devices often end up being messed up.

 

This idea sounds really good, so is it really true? Can others confirm that this is correct?

 

Also, I use a microHAM MK11 as a connection between the PC and my radio (IC7800) and I wonder if Joe W4TV can confirm whether it is permissible to change the name of the microHAM sound devices?

 

Any advice would be welcomed….

 

I am not even going to try and install v2.5.0 or .NET5 on my old Win7pro (32bit) PC, as it is struggling already, and I would like to be able to network it so that I can retrieve files, check ini files etc once I have swapped them out.

 

73 de Phil GU0SUP

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Ron / W4MMP via groups.io
Sent: 14 April 2021 17:02
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Getting fed up..... #FT8

 

Hi,

I never have this problem with any Windows update.  This I believe is due to the fact that I give a name to the sound devices I care about.  It appears that Windows updates don't mess with named sound devices.  Do a similar naming operation for any USB/Serial adapters you care about.  That is performed in the device manager.  Give the USB/Serial device a com port number away from the default com port number (com1,com3,etc) such as com14.  

 

73,
Ron / W4MMP

On 4/14/2021 11:25, Michael Black via groups.io wrote:

Yeah...I had the same problem and so did a friend of mine with the latest update.

 

Had to uninstall all sound devices (make sure you select View/Show hidden devices too) and reboot to let them install again...

 

Mike W9MDB

 

 

 

 

On Wednesday, April 14, 2021, 10:23:23 AM CDT, Paul <w2ec@...> wrote:

 

 

Are you running windows 10? Tuesday they did an update, it has scrambled many usb drivers to different ports, changed parameters etc. Took me over an hour to recover all mu USB attachments. Just one more of the windows features they keep forcing on us. 

 

W2EC Paul

 

On Wednesday, April 14, 2021, 11:17:49 AM EDT, Michael Black via groups.io <mdblack98@...> wrote:

 

 

What "same messages" ??

 

Mike W9MDB

 

 

 

 

On Wednesday, April 14, 2021, 10:15:34 AM CDT, Gilles beaulieu <ve3npi@...> wrote:

 

 

Hi Laurie, really getting fed up with this FT* stuff. I have done many contacts in the past. Here's what I have here: Yaesu FTDX-1200, scu-17, running ACLog, WSJT-X (ver. 2.3.0) and the latest JTAlert. I had it running perfectly without any hassles yesterday. Today I rebooted my PC and started JTAlert and try to make a few contacts. I keep getting errors with the sound card. No matter what I change in the setup it keeps crashing on me with the same messages. Not impressed at all.
Gilles - ve3npi

--


Gilles - VE3NPI

Prescott-Russell Amateur Radio Club

www.prarc.ca



--


Gilles - VE3NPI

Prescott-Russell Amateur Radio Club

www.prarc.ca



--


Gilles - VE3NPI

Prescott-Russell Amateur Radio Club

www.prarc.ca



3201 - 3220 of 37197