Date   

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




locked Re: 2.50 Like It

WB8ASI Herb
 

Sweet........JTA was great to start with and now getting better all the time.   Can't imagine operating WSJTX without it.  Thanks for all your dedication. 73, Herb WB8ASI


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

Gilles beaulieu
 

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




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

Michael Black
 

Check these settings in JTAlert.

Inline image





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




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

Gilles beaulieu
 

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




locked Re: Version 2.50.0 F5 Text Message window

Steve, N3SL
 

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

On Wed, Apr 14, 2021 at 4:24 PM John C <vk7xx.radio@...> wrote:

thanks Laurie.   I was hoping that there was a "clear messages' button that I had missed that was similiar to the old versions.    

 

Thanks again

John


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

Michael Black
 

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


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

Phil Cooper
 

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


locked Re: 2.50.0 with WSJT-X 2.3.1 crashes

John, DK9JC / AK9JC
 

I can not find any other topics on this issue so far.

Is there anything I can do or can I provide any other data/info?


locked Re: Version 2.50.0 F5 Text Message window

John C
 

thanks Laurie.   I was hoping that there was a "clear messages' button that I had missed that was similiar to the old versions.    

 

Thanks again

John


locked Re: Version 2.50.0 F5 Text Message window

HamApps Support (VK3AMA)
 

On 15/04/2021 6:51 am, John C wrote:

I cannot find a way of clearing the F5 Text Message window.  Can anyone help with this please ??

 

John
VK7XX


Wait 7 days, that is the threshold for removing old messages.
Alternatively, delete the message manually via the right-click context menu.
A function to delete all messages is currently unavailable, its on the todo list.

de Laurie VK3AMA


locked Version 2.50.0 F5 Text Message window

John C
 

I cannot find a way of clearing the F5 Text Message window.  Can anyone help with this please ??

 

John
VK7XX

3681 - 3700 of 37666