Date   

locked Re: WSJT-X suddenly deaf?

John V
 

Guys, sheesh, 90% of these "soapbox gripes" posts do nothing to answer the OP question.

Possibly someone needs to start their own topics like "OS gripes" or "Covid-19 frustration"  to lessen the unrelated  QRM to valid questions? 

Tad, you may have already done this -- SignaLink has an excellent and extensive installation and troubleshooting section on their website for your soundcard. The guide goes into great detail for SW and OS soundcard/audio settings. Many of the settings pertain to all soundcards and I have suggested that people review it when they are having issues even with other brands other than SignaLink.  

Be well, John NA6L 


locked Re: WSJT-x

Arthur Petteway
 

Roger,

Thank you for the reply.

How do I setup the sound card input?

In the audio tab sound card is showing 
Input: Microphone(USB Audio CODEC)
Output: Speakers(USB Audio CODEC)

I am using Windows 10 and the IC-7300

73,
Art WB4MNK


locked Re: WSJT-X suddenly deaf?

Al Groff
 

Dave,
  I think the portion beginning "One of Windows most annoying habits... " should be required reading for anyone using Windows with amateur radio apps interfaced to a radio and/or station accessories.

AL, K0VM

On 3/26/2020 5:51 AM, Gilbert Baron wrote:
Thanks for a post that I am flagging in Outlook. You are telling the truth here.

Outlook Desktop Gil W0MN
Hierro Candente Batir de Repente
44.08226 N 92.51265 W EN34rb

-----Original Message-----
From: WSJTX@groups.io <WSJTX@groups.io> On Behalf Of Dave_G0WBX via Groups.Io
Sent: Thursday, March 26, 2020 04:33
To: WSJTX@groups.io
Subject: Re: [WSJTX] WSJT-X suddenly deaf?

Hi.

There was indeed one windows update  KB4532693  that only partly completed the job, it did the update bit, but failed to restore normal operating profiles, so many users found that all their data had been moved off into an oddly named folder, or in some cases was indeed completely removed.

Some of that action, may, MAY, have been due to users not heeding the "do not turn off your computer" warnings, or not letting it complete the (sometimes two automatic reboots) when the machine was powered on the first time after that update.

This was a problem about a month or more ago.  The Security Now transcripts at grc.com  <https://www.grc.com/sn/sn-754.txt>  has some details if you want to dig them out.

But yes, owning a computer these days, is like owning an car 10 to 15 years ago.  You shouldn't "need to know" what goes on under the hood, but it can certainly help a lot if you do.  If just to know what not to go fiddling with!

And before anyone else comments, Apple, Google and Linux systems have similar issues at times, they are just "different" that is all.

Also.  When debugging such issues.  Make only ONE CHANGE at a time, and re-test.  Keep notes too as to what you changed and if it had any effect, good or bad.  Unless it was a good change, revert it back to what you had and check again, BEFORE making the next change.   Learn and understand what you've got, don't just blindly poke and hope.

One of Windows most annoying habits, is that any HID class of device, (Human Interface Device) that is suddenly introduced, iMS assumes you want it to use as the default device of that type.  For our needs, that is not always the case, so you have to tell it not to do that, and that is where the trouble lies.

If you later unplug something, and plug it back into THE SAME port, it's likely to stay as what you want.  If however, you plug it back into ANOTHER port, Windows will see it as a "New" device, and around you go again.  This behaviour IS documented, but not anywhere you can eaisily find.   Play with USB<>Serial devices*, and their settings in device mangler, to see what is going on.  You can train your system to use what you have, how you want, but it is a long chore when you have many such devices.   (Hint!  A "device" identity, consists of not only it's own information, but also the "path" to it, that includes how to navigate through the entire USB subsystem to reach it.

* And that includes rigs with embedded USB<>Serial devices for CAT control, all hiding behind yet another USB Hub!

So, unless you want a lot more work, make a not of what hole in the PC something was plugged into, and ONLY plug it in that same port next time.

Use USBview to discover what you have connected.   (Google for it, but ONLY obtain it direct from Microsoft, or the much easier to find FTDI site, they are the only versions to trust.) https://www.ftdichip.com/Support/Utilities/usbview.zip

USBDView, is something similar and very useful, but ONLY get it direct from the authors site. <https://www.nirsoft.net/utils/usb_devices_view.html>  It is not a MS product.

Explore, learn and understand how all this works, because you need to.

73.

Dave G0WBX.


--
Created on and sent from a Unix like PC running and using free and open source software:






    


locked Re: WSJTX Log

Jay Lijoi
 

Check out gridtracker. I'm not a contester by nature, so this fit the bill for me. It logs LOTW automatically, but it also give beam heading and grey line map. Just a very good utilitarian program.
Good luck,
Jay wb2qqj


locked Re: WSJT-X suddenly deaf?

Reino Talarmo
 

So back to my WSJT deafness problem, I have no reason to assume that it is related to an OS update.

 

Tad,

Have you tried to rename or remove WSJT-X.ini file, when you re-installed wsjt-x? In some cases removal of it and restart on wsjt-x (and possibly re-booting PC) have solved that kind of problems; no need to re-install wsjt-x. Unfortunately all your settings are also gone, but…

Also the order you power-up your rig and PC affects, but you should know that by now.

73, Reino  oh3mA

 


locked Re: WSJT-x

n5qs
 

It is really not an error just a statement that the input device is not set up yet.
Roger

On 3/26/2020 12:09 PM, Arthur Petteway wrote:
Just installed WSJT-x and when i open WSJT-x an error pops up saying error in sound input opening the audio input has occurred

How do I correct this error?

73,
Art WB4MNK

    


locked WSJT-x

Arthur Petteway
 

Just installed WSJT-x and when i open WSJT-x an error pops up saying error in sound input opening the audio input has occurred

How do I correct this error?

73,
Art WB4MNK


locked Re: WSJT-X suddenly deaf?

K7RA Tad Cook
 

So back to my WSJT deafness problem, I have no reason to assume that it is related to an OS update.




On Thu, Mar 26, 2020 at 8:16 AM Dave_G0WBX via Groups.Io <g8kbvdave=googlemail.com@groups.io> wrote:
Re:-

Except, I challenge anyone to show me a MS manual on any update; ever!
They don't exist!

Oh they do, but they do take a lot of digging and unearthing to find out
the full official details, but the info is out there.  It is even
published BEFORE the updates are shipped!

Likewise at home (and on this laptop) I've 99% abandoned Windows, in
favor of Linux.  Mint 19.3 64 bit in my case.  There are plenty of
distributions out there, some more suitable for niche applications than
others, or for general use.

Pick up a Raspberry Pi, and have a play, you might just find you like
it, to the point where you want to try it on a bigger more general
purpose system.

Frankly, there is not a lot you can do on Windows, that you can't do on
Linux.  Other than some manufacturer provided device
programming/configuration tools.  For that, just setup and use a dual
boot system, Linux by default, but if you *Need* it, you can boot into
Windows.  Over a short time, you'll find you need Windows less and less
for day to day tasks.

But, as previously said...  RTFM!  Has to be said too, that the
"quality" of "community support" online for Linux, far outstrips that
available for Windows, where poke-n-hope seems the norm.

73.

Dave G0WBX.


--
Created on and sent from a Unix like PC running and using free and open source software:




--
Tad Cook - K7RA
Seattle, WA
k7ra@...


locked Re: OT: Virtual comport software

John
 

Dennis,

If you are replying to my post about naming com ports, then thanks, I hadn't
thought of using com0com for this.

I think after this weekend's CQ WPX contest I'll give it a try, can't really go
anywhere for a few weeks as we are in self-isolation, good time to lower the
items in the shack "job jar".

John
VE3KKQ

---------- Original Message ----------
From: Dennis - WU6X <wu6x@...>
Date: March 26, 2020 at 12:23 PM


I'm using com0com with good results. http://com0com.sourceforge.net/
Dennis, WU6X


locked Re: OT: Virtual comport software

Dennis - WU6X
 

I'm using com0com with good results. http://com0com.sourceforge.net/
Dennis, WU6X


locked Re: WSJT-X suddenly deaf?

Dave_G0WBX
 

Re:-

Except, I challenge anyone to show me a MS manual on any update; ever!
They don't exist!

Oh they do, but they do take a lot of digging and unearthing to find out
the full official details, but the info is out there.  It is even
published BEFORE the updates are shipped!

Likewise at home (and on this laptop) I've 99% abandoned Windows, in
favor of Linux.  Mint 19.3 64 bit in my case.  There are plenty of
distributions out there, some more suitable for niche applications than
others, or for general use.

Pick up a Raspberry Pi, and have a play, you might just find you like
it, to the point where you want to try it on a bigger more general
purpose system.

Frankly, there is not a lot you can do on Windows, that you can't do on
Linux.  Other than some manufacturer provided device
programming/configuration tools.  For that, just setup and use a dual
boot system, Linux by default, but if you *Need* it, you can boot into
Windows.  Over a short time, you'll find you need Windows less and less
for day to day tasks.

But, as previously said...  RTFM!  Has to be said too, that the
"quality" of "community support" online for Linux, far outstrips that
available for Windows, where poke-n-hope seems the norm.

73.

Dave G0WBX.


--
Created on and sent from a Unix like PC running and using free and open source software:


locked Re: MSK144 Works, FT4, FT8, JT9, JT65 do not.

john ni0k
 

Here is another article on how to set app permissions in Windows 10 (pay particular attention to the Microphone!):
https://www.howtogeek.com/368598/how-to-manage-app-permissions-on-windows-10/

-NI0K

Danny Riggsbee wrote on 3/25/2020 2:18 PM:

Thanks John,

 

Settings->Sound->Advanced Settings options->App volume and device preferences is where I did most of my poking around.   I saw the drop down boxes in the form associated with each app using a sound card device.  In my case the only Apps displayed are; System Sounds, HRD Rig Control & WSJT-X.  Additionally, there is a Master Volume that I adjusted the settings on.  I changed the value in these drop downs back and forth from “Default” to “USB AUDIO CODEC”.  My poking around with these settings did seem to randomly and temporary fix the problem.  But after a few minutes of operation, the problem always came back.  I never could get WSJT-X to behave in a consistent enough manner to do proper troubleshooting.   BTW after the Win10 patch revert, all of these settings are set to “Default” and WSJT-X is now working as expected. 

 

However, there is one thing that leads me to believe that your theory around privileges and permissions is correct.    When WSJT-X was not functioning correctly, the slider control for WSJT-X in the aforementioned settings form was grayed out.  The HRD Rig Control slider control was not.  And as I mentioned in the previous post, DM780 was working fine while WSJT-X was not.  I thought the WSJT-X slider control being grayed out was suspicious, but I didn’t know what was proper state.   Now after the Win10 upgrade revert, the WSJT-X slider control is enabled which adds more circumstantial evidence.

 

Working from your theory that this is a privileges or permissions issue, (which I think likely) where else might we look in Win10 to find that WSJT-X is being denied access to the sound card?

 

Looking forward to your response as I am uncomfortable running around the internet with an unpatched Win10 OS.

 

 

Thanks,

Dan

 

 

From: <WSJTX@groups.io> on behalf of "john ni0k via Groups.Io" <jasimmons@...>
Reply-To: "WSJTX@groups.io" <WSJTX@groups.io>
Date: Tuesday, March 24, 2020 at 5:01 PM
To: "WSJTX@groups.io" <WSJTX@groups.io>
Subject: Re: [WSJTX] MSK144 Works, FT4, FT8, JT9, JT65 do not.

 

WIN10 is changing privileges on your sound devices. Right-click on the speaker icon on the right side of your task bar and select "Open Sound Settings". Scroll to the bottom of the window and click on "Advanced sound options". Go through all the settings carefully and it should solve your problem(s).

-de John NI0K

Danny Riggsbee wrote on 3/24/2020 3:39 PM:

Hi Harv,

 

Earlier this week, I allowed Win10 to update overnight and had a similar problem the next day.   The WSJT-X to USB audio device connection began intermittently functioning. (mostly not functioning).  I have HRD & DM780, which still worked fine.   Thrashed around for a couple of hours looking for the problem to no avail.

 

Finally reverted the Win10 update and everything went back to normal.   The Win10 update revert took about 45 minutes on my cheapy puck device, but it did the trick.

 

However, am more than a little concerned about not updating Win10.  It is a jungle out there on the internet and don’t want to be exposed.  Hopefully the WSJT-X authors will run across this issue and fix it.

 

 

73s,

Dan WA4WZR











locked Re: WSJTX Log

 

Trevor,

 

For one my private logger works on the following  algorithm:

 

  1. Check the wsjtx.adi and fl-digi logbook.adi every 20 seconds.
  2. If the timestamp has changed since the previous time, import it.
  3. If the time on the QSO is earlier than that previous time, ignore it.
  4. If it is later add the QSO to the log maintained by the logger.

 

Phil GM3ZZA

 

Sent from Mail for Windows 10

 

From: trevor via Groups.Io
Sent: 25 March 2020 21:08
To: WSJTX@groups.io
Subject: Re: [WSJTX] WSJTX Log

 

If you're importing into TQSL, it will automatically exclude duplicates (unless you tell it not to), so no need to copy new QSOs out. I would hope other log programs have similar features in their importing.

- Trevor, AG7GX

On 3/25/2020 3:03 PM, Anthony Luscre wrote:

Yes, they are in ADIF format and most logging programs will let you important ADIF.

I actually kept a small to-import file and copy just new QSO from full log.

Paste them into to-import file and then save and import into logging program.

 

Some logging programs will automatically copy files from WSJT-X log (my LOGic9 just added this feature).

 

Anthony

 

On Wed, Mar 25, 2020 at 4:28 PM Richard <raitchd@...> wrote:

I am new to FT8 and have questions. The WSJTX software has an automatic
logging function that saves the QSO's in comma delineated rows in
Notepad. Is there any way to save those QSO's directly to a logging
program for transfer to LBoTW? Also it would be nice if the program
updated (while on screen) after each QSO while working other stations so
repeats could be avoided.

Dick KC9UB


 

--

Anthony Luscre

 

K8ZT

Ohio Section Section Youth Coordinator & Education Outreach

ARRL - The National Association For Amateur Radio™

 

k8zt@... (best for Amateur Radio)

 

The Web Resource Hoarder- www.ZTLearn.com

 

K8ZT Radio Website- www.k8zt.com

 

Amateur Radio Resources for Students/Youth - www.k8zt.com/hry



 

 


--

Ham Radio Podcasts Free for Android

https://play.google.com/store/apps/details?id=com.andromo.dev5592.app509392

 


--
73 Phil GM3ZZA


locked WSJTX autostart with Slicemaster

Ken
 

I'm sure this is a config problem but not sure if it is WSJTX or slicemaster. I had to reinstall everything on a new computer and now I cant get slicemaster to autostart WSJTX by mode (DIGU). It use to work for me but I obviously am missing something. I do get n error on slicemaster that says 
" NoSectionError: No section: 'Configuration'" . It seems like it might be a permissions problem but I tried running slicemaster as admin with the same results.

My config is;
Flex 6600
WSJTX  2.1.2
Slicemaster 0.10.7c

What am I missing?
Ken


locked Re: WSJTX Log

Glen - G0SBN
 

Hello Richard

As Jim says, N1MM main job in life is contesting, but as well as contesting I also use it for other logs.

Another option if you want a more general logger is Log4OM. I don't use it, but It appears to have interlinks with WSJT-x, real-time upload to LotW, and general logging. 

Log4OM https://www.log4om.com/integrated/ 
Forum http://forum.log4om.com/viewtopic.php?f=10&t=4109

Glen G0SBN


locked Re: WSJT-X suddenly deaf?

Brian KN4RDF
 

Go to URL time.is in a web browser and check your local system clock if you haven’t already. If it is more than +/- 1 or 2 seconds off, the decoder software won’t work. Perhaps your time synchronization software isn’t starting up and running correctly?

-Brian Dotson, KN4RDF 

On Thu, Mar 26, 2020 at 6:33 AM <careyfisher@...> wrote:
In my experience, the people that have problems with Windows are people that fancy themselves computer geniuses but, in reality, have never worked with computers in a professional capacity.
I've been running WSJTX on Windows 10 ever since Joe and company first released the software and I have never had Windows change any port settings during updates.
73, Carey,WB4HXE

On Wed, Mar 25, 2020 at 6:47 PM Russ Ravella via Groups.Io <rus5=me.com@groups.io> wrote:
Gotta pipe in here on John’s behalf.  There is absolutely no question whatsoever that updating Windows whenever microsoft decides to assault the world with their next disaster is a terrible idea unless there is some special driving need to do so.  This forum and countless others along with endless news and journal articles over the last several years recount horror story after horror story brought on by updates from the flaming idiots at microsoft.  The fact that some people have been lucky so far doesn’t negate that fact that very very many haven’t. It just is what it is.  And trying to pretend it isn’t doesn’t help anyone.

However, from what I can see, allowing just the routine security updates that, for example, refresh WD’s database don’t seem to cause these problems and probably can be be performed safely.  So “performing updates” can mean several things.  And I think the case most people are advising against here are version updates.

There are many guidelines on-line and some on Dave Bernstein’s excellent DXLab Suite website for “dealing with Windows”.  They can be easily googled up.  For my own part I’ve been successful at preventing version updates and allowing routine security updates for the nearly two years I’ve been forced to use microsoft garbage for ham radio purposes.  It is also possible to disable just the device portion an update might have which, at least for me, spared me the port scramble/loss misery being described once I decided enough “fix our last screwup” updates had occurred that a particular version update might finally be safe (still always a risk).

Anyway, I just wanted to weigh in with some support for the “avoid the microsoft morons whenever possible” side of the discussion because it is very real.

Russ, KR6W 



On Mar 25, 2020, at 2:59 PM, JP Tucson, AZ <samcat88az@...> wrote:


Hassan,

Perhaps I wasn't completely clear, when win10 updated, it blew out my profiles, my saved passwords, etc.

It took me nearly 5 freaking hours just to get back to where I was!

Sorry, but you and others are wrong! Recent win10 upgrades have proven to be nearly complete disasters that even MS "experts" are dumbfounded by... 

Just like the recent time after time screwups by Boeing!

Frankly, I think it's just more proof that Washington state's pot(head) acceptance is just stupid!

Let me be more clear... the last "good" & working version of Windows was XP Pro!  7 was workable but not as good.  Office 2003 worked great, and since then MS has done everything wrong & screwed up the works.

Seriously, I would still use XP Pro today, except most of the software writers stopped supporting it.

FYI, Yes! I still have an HP & two other computers that run XP Pro!  The HP gas only had to have the failed hard drive replaced, and that took 8 minutes, not 5 hours! (I kept an up to date spare HD on the side).




73 - John - N7GHZ

On Wed, Mar 25, 2020, 2:32 PM Hasan Schiers N0AN <hbasri.schiers6@...> wrote:
Turning off Windows Updates is a Terrible Idea

If a person doesn't have the technical competence to make Windows Audio Devices work properly after an Update munges them, just how well do they think they are going to do avoiding getting and giving virus's and Trojans when their Security Patches are so out of date that they become a nesting area for the bad actors?

Work through the audio setup from top to bottom. If needed, uninstall all your audio devices and start over. Windows audio can be very daunting.

Simply plugging and unplugging something from the Sound Card inputs and outputs can drive you crazy!

However, turning off Windows Updates is NOT the solution, unless you are quite accomplished with the O/S in the first place. ...and if you are, then you shouldn't need to turn off Updates to solve and audio device or serial port enumeration issues.

Worst case, uninstall all the audio devices (non-motherboard ones) and disconnect them. Then reboot. Plug the audio devices in one at a time and find them in Device Manager when Windows recognizes them. Test them one at a time. Rename them once you have identified them.

If that doesn't work, uninstall even the motherboard audio device....you won't lose it.

Shut the computer down, power back up and Windows will find the motherboard audio. Test it out. Unless it's gone bad, it will work. Then add each additional device one at a time. Review them in Device manager and then test them. Eventually you will have them all working again.

If you are using another audio device besides the motherboard one (and you should be for WSJT-X), then once you get it working, RENAME it, so you won't get confused next update. I  have not had Update change an Audio Device Name that I changed, and I get updates nearly weekly.

Windows Update is a PITA, to be sure, I have had it brick a laptop, but most of the time I don't have those kinds of issues. With Audio Devices since I renamed them, and also wrote out notes on every serial port (plus labled the cables on both ends), my problems become very easy to solve.

When things get messed up, it's a big help.

Good luck!

73, N0AN



Hasan


On Wed, Mar 25, 2020 at 9:32 AM Gilbert Baron <w0mn00@...> wrote:

Turning off update is NOT the answer. You will be sad about this when you miss something critical ,especially a security thing. Find out what the real -problem is. I have ZERO problems with audio after update.

 

Outlook Laptop Gil W0MN

Hierro candente, batir de repente

44.08226N 92.51265W EN34rb

 

From: WSJTX@groups.io <WSJTX@groups.io> On Behalf Of Andrew O'Brien
Sent: Wednesday, March 25, 2020 07:45
To: WSJTX@groups.io
Subject: Re: [WSJTX] WSJT-X suddenly deaf?

 

John, I argue ... always update Windows 

Andy K3UK 

 

On Wed, Mar 25, 2020 at 5:32 AM JP Tucson, AZ <samcat88az@...> wrote:

Ted - did your Windows 'update'?  (Never update Windows!)

 

Win10 updates have a nasty habit of screwing up your audio mixer & your codec settings!

 

Recheck those & TURN OFF Win10 update; by going into the windows icon in bottom left corner - type ser(vices); which brings up a list; go down to Windows update & disable it!  NOTE: you have to check it on a regular basis because update will turn itself back on... (stupid windows & microsoft) (seriously, we need to all file a class action lawsuit against MS to force them to provide a permanently turn off windows/stop "forced" updates!)

73 - John - N7GHZ

 

On Wed, Mar 25, 2020, 12:30 AM K7RA Tad Cook <k7ra@...> wrote:

I've been using the software on FT8 with a Tigertronics SignalLink, but suddenly a few days ago it has gone deaf.  Nothing appears in Band Activity, and the Receiving nomograph stays at zero, which is odd because normally in the past even when the USB connection from the SignalLink hardware was not attached, the Receiving field is jumping around. For instance, right now I am not at the radio and on another computer, and when I run WSJT here with no audio input, that Receiving window acts as if there are signals present.

 

I*'ve been through everything. I am able to transmit OK.

 

Any suggestions? Everything worked fine til very recently.


--

Tad Cook - K7RA
Seattle, WA
k7ra@...

 

 



--

Andy


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop





--
Carey Fisher


--
73, Carey, WB4HXE
--
Brian Dotson

In a gentle way, you can shake the world!  
-Mahatma Ghandi
 


locked Re: WSJT-X suddenly deaf?

careyfisher@...
 

In my experience, the people that have problems with Windows are people that fancy themselves computer geniuses but, in reality, have never worked with computers in a professional capacity.
I've been running WSJTX on Windows 10 ever since Joe and company first released the software and I have never had Windows change any port settings during updates.
73, Carey,WB4HXE

On Wed, Mar 25, 2020 at 6:47 PM Russ Ravella via Groups.Io <rus5=me.com@groups.io> wrote:
Gotta pipe in here on John’s behalf.  There is absolutely no question whatsoever that updating Windows whenever microsoft decides to assault the world with their next disaster is a terrible idea unless there is some special driving need to do so.  This forum and countless others along with endless news and journal articles over the last several years recount horror story after horror story brought on by updates from the flaming idiots at microsoft.  The fact that some people have been lucky so far doesn’t negate that fact that very very many haven’t. It just is what it is.  And trying to pretend it isn’t doesn’t help anyone.

However, from what I can see, allowing just the routine security updates that, for example, refresh WD’s database don’t seem to cause these problems and probably can be be performed safely.  So “performing updates” can mean several things.  And I think the case most people are advising against here are version updates.

There are many guidelines on-line and some on Dave Bernstein’s excellent DXLab Suite website for “dealing with Windows”.  They can be easily googled up.  For my own part I’ve been successful at preventing version updates and allowing routine security updates for the nearly two years I’ve been forced to use microsoft garbage for ham radio purposes.  It is also possible to disable just the device portion an update might have which, at least for me, spared me the port scramble/loss misery being described once I decided enough “fix our last screwup” updates had occurred that a particular version update might finally be safe (still always a risk).

Anyway, I just wanted to weigh in with some support for the “avoid the microsoft morons whenever possible” side of the discussion because it is very real.

Russ, KR6W 



On Mar 25, 2020, at 2:59 PM, JP Tucson, AZ <samcat88az@...> wrote:


Hassan,

Perhaps I wasn't completely clear, when win10 updated, it blew out my profiles, my saved passwords, etc.

It took me nearly 5 freaking hours just to get back to where I was!

Sorry, but you and others are wrong! Recent win10 upgrades have proven to be nearly complete disasters that even MS "experts" are dumbfounded by... 

Just like the recent time after time screwups by Boeing!

Frankly, I think it's just more proof that Washington state's pot(head) acceptance is just stupid!

Let me be more clear... the last "good" & working version of Windows was XP Pro!  7 was workable but not as good.  Office 2003 worked great, and since then MS has done everything wrong & screwed up the works.

Seriously, I would still use XP Pro today, except most of the software writers stopped supporting it.

FYI, Yes! I still have an HP & two other computers that run XP Pro!  The HP gas only had to have the failed hard drive replaced, and that took 8 minutes, not 5 hours! (I kept an up to date spare HD on the side).




73 - John - N7GHZ

On Wed, Mar 25, 2020, 2:32 PM Hasan Schiers N0AN <hbasri.schiers6@...> wrote:
Turning off Windows Updates is a Terrible Idea

If a person doesn't have the technical competence to make Windows Audio Devices work properly after an Update munges them, just how well do they think they are going to do avoiding getting and giving virus's and Trojans when their Security Patches are so out of date that they become a nesting area for the bad actors?

Work through the audio setup from top to bottom. If needed, uninstall all your audio devices and start over. Windows audio can be very daunting.

Simply plugging and unplugging something from the Sound Card inputs and outputs can drive you crazy!

However, turning off Windows Updates is NOT the solution, unless you are quite accomplished with the O/S in the first place. ...and if you are, then you shouldn't need to turn off Updates to solve and audio device or serial port enumeration issues.

Worst case, uninstall all the audio devices (non-motherboard ones) and disconnect them. Then reboot. Plug the audio devices in one at a time and find them in Device Manager when Windows recognizes them. Test them one at a time. Rename them once you have identified them.

If that doesn't work, uninstall even the motherboard audio device....you won't lose it.

Shut the computer down, power back up and Windows will find the motherboard audio. Test it out. Unless it's gone bad, it will work. Then add each additional device one at a time. Review them in Device manager and then test them. Eventually you will have them all working again.

If you are using another audio device besides the motherboard one (and you should be for WSJT-X), then once you get it working, RENAME it, so you won't get confused next update. I  have not had Update change an Audio Device Name that I changed, and I get updates nearly weekly.

Windows Update is a PITA, to be sure, I have had it brick a laptop, but most of the time I don't have those kinds of issues. With Audio Devices since I renamed them, and also wrote out notes on every serial port (plus labled the cables on both ends), my problems become very easy to solve.

When things get messed up, it's a big help.

Good luck!

73, N0AN



Hasan


On Wed, Mar 25, 2020 at 9:32 AM Gilbert Baron <w0mn00@...> wrote:

Turning off update is NOT the answer. You will be sad about this when you miss something critical ,especially a security thing. Find out what the real -problem is. I have ZERO problems with audio after update.

 

Outlook Laptop Gil W0MN

Hierro candente, batir de repente

44.08226N 92.51265W EN34rb

 

From: WSJTX@groups.io <WSJTX@groups.io> On Behalf Of Andrew O'Brien
Sent: Wednesday, March 25, 2020 07:45
To: WSJTX@groups.io
Subject: Re: [WSJTX] WSJT-X suddenly deaf?

 

John, I argue ... always update Windows 

Andy K3UK 

 

On Wed, Mar 25, 2020 at 5:32 AM JP Tucson, AZ <samcat88az@...> wrote:

Ted - did your Windows 'update'?  (Never update Windows!)

 

Win10 updates have a nasty habit of screwing up your audio mixer & your codec settings!

 

Recheck those & TURN OFF Win10 update; by going into the windows icon in bottom left corner - type ser(vices); which brings up a list; go down to Windows update & disable it!  NOTE: you have to check it on a regular basis because update will turn itself back on... (stupid windows & microsoft) (seriously, we need to all file a class action lawsuit against MS to force them to provide a permanently turn off windows/stop "forced" updates!)

73 - John - N7GHZ

 

On Wed, Mar 25, 2020, 12:30 AM K7RA Tad Cook <k7ra@...> wrote:

I've been using the software on FT8 with a Tigertronics SignalLink, but suddenly a few days ago it has gone deaf.  Nothing appears in Band Activity, and the Receiving nomograph stays at zero, which is odd because normally in the past even when the USB connection from the SignalLink hardware was not attached, the Receiving field is jumping around. For instance, right now I am not at the radio and on another computer, and when I run WSJT here with no audio input, that Receiving window acts as if there are signals present.

 

I*'ve been through everything. I am able to transmit OK.

 

Any suggestions? Everything worked fine til very recently.


--

Tad Cook - K7RA
Seattle, WA
k7ra@...

 

 



--

Andy


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop





--
Carey Fisher


--
73, Carey, WB4HXE


locked Re: WSJT-X suddenly deaf?

Gilbert Baron
 

Thanks for a post that I am flagging in Outlook. You are telling the truth here.

Outlook Desktop Gil W0MN
Hierro Candente Batir de Repente
44.08226 N 92.51265 W EN34rb

-----Original Message-----
From: WSJTX@groups.io <WSJTX@groups.io> On Behalf Of Dave_G0WBX via Groups.Io
Sent: Thursday, March 26, 2020 04:33
To: WSJTX@groups.io
Subject: Re: [WSJTX] WSJT-X suddenly deaf?

Hi.

There was indeed one windows update KB4532693 that only partly completed the job, it did the update bit, but failed to restore normal operating profiles, so many users found that all their data had been moved off into an oddly named folder, or in some cases was indeed completely removed.

Some of that action, may, MAY, have been due to users not heeding the "do not turn off your computer" warnings, or not letting it complete the (sometimes two automatic reboots) when the machine was powered on the first time after that update.

This was a problem about a month or more ago. The Security Now transcripts at grc.com <https://www.grc.com/sn/sn-754.txt> has some details if you want to dig them out.

But yes, owning a computer these days, is like owning an car 10 to 15 years ago. You shouldn't "need to know" what goes on under the hood, but it can certainly help a lot if you do. If just to know what not to go fiddling with!

And before anyone else comments, Apple, Google and Linux systems have similar issues at times, they are just "different" that is all.

Also. When debugging such issues. Make only ONE CHANGE at a time, and re-test. Keep notes too as to what you changed and if it had any effect, good or bad. Unless it was a good change, revert it back to what you had and check again, BEFORE making the next change. Learn and understand what you've got, don't just blindly poke and hope.

One of Windows most annoying habits, is that any HID class of device, (Human Interface Device) that is suddenly introduced, iMS assumes you want it to use as the default device of that type. For our needs, that is not always the case, so you have to tell it not to do that, and that is where the trouble lies.

If you later unplug something, and plug it back into THE SAME port, it's likely to stay as what you want. If however, you plug it back into ANOTHER port, Windows will see it as a "New" device, and around you go again. This behaviour IS documented, but not anywhere you can eaisily find. Play with USB<>Serial devices*, and their settings in device mangler, to see what is going on. You can train your system to use what you have, how you want, but it is a long chore when you have many such devices. (Hint! A "device" identity, consists of not only it's own information, but also the "path" to it, that includes how to navigate through the entire USB subsystem to reach it.

* And that includes rigs with embedded USB<>Serial devices for CAT control, all hiding behind yet another USB Hub!

So, unless you want a lot more work, make a not of what hole in the PC something was plugged into, and ONLY plug it in that same port next time.

Use USBview to discover what you have connected. (Google for it, but ONLY obtain it direct from Microsoft, or the much easier to find FTDI site, they are the only versions to trust.) https://www.ftdichip.com/Support/Utilities/usbview.zip

USBDView, is something similar and very useful, but ONLY get it direct from the authors site. <https://www.nirsoft.net/utils/usb_devices_view.html> It is not a MS product.

Explore, learn and understand how all this works, because you need to.

73.

Dave G0WBX.


--
Created on and sent from a Unix like PC running and using free and open source software:




--
W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop


locked Re: WSJT-X suddenly deaf?

Dave_G0WBX
 

Hi.

There was indeed one windows update  KB4532693  that only partly
completed the job, it did the update bit, but failed to restore normal
operating profiles, so many users found that all their data had been
moved off into an oddly named folder, or in some cases was indeed
completely removed.

Some of that action, may, MAY, have been due to users not heeding the
"do not turn off your computer" warnings, or not letting it complete the
(sometimes two automatic reboots) when the machine was powered on the
first time after that update.

This was a problem about a month or more ago.  The Security Now
transcripts at grc.com  <https://www.grc.com/sn/sn-754.txt>  has some
details if you want to dig them out.

But yes, owning a computer these days, is like owning an car 10 to 15
years ago.  You shouldn't "need to know" what goes on under the hood,
but it can certainly help a lot if you do.  If just to know what not to
go fiddling with!

And before anyone else comments, Apple, Google and Linux systems have
similar issues at times, they are just "different" that is all.

Also.  When debugging such issues.  Make only ONE CHANGE at a time, and
re-test.  Keep notes too as to what you changed and if it had any
effect, good or bad.  Unless it was a good change, revert it back to
what you had and check again, BEFORE making the next change.   Learn and
understand what you've got, don't just blindly poke and hope.

One of Windows most annoying habits, is that any HID class of device,
(Human Interface Device) that is suddenly introduced, iMS assumes you
want it to use as the default device of that type.  For our needs, that
is not always the case, so you have to tell it not to do that, and that
is where the trouble lies.

If you later unplug something, and plug it back into THE SAME port, it's
likely to stay as what you want.  If however, you plug it back into
ANOTHER port, Windows will see it as a "New" device, and around you go
again.  This behaviour IS documented, but not anywhere you can eaisily
find.   Play with USB<>Serial devices*, and their settings in device
mangler, to see what is going on.  You can train your system to use what
you have, how you want, but it is a long chore when you have many such
devices.   (Hint!  A "device" identity, consists of not only it's own
information, but also the "path" to it, that includes how to navigate
through the entire USB subsystem to reach it.

* And that includes rigs with embedded USB<>Serial devices for CAT
control, all hiding behind yet another USB Hub!

So, unless you want a lot more work, make a not of what hole in the PC
something was plugged into, and ONLY plug it in that same port next time.

Use USBview to discover what you have connected.   (Google for it, but
ONLY obtain it direct from Microsoft, or the much easier to find FTDI
site, they are the only versions to trust.)  
https://www.ftdichip.com/Support/Utilities/usbview.zip

USBDView, is something similar and very useful, but ONLY get it direct
from the authors site. 
<https://www.nirsoft.net/utils/usb_devices_view.html>  It is not a MS
product.

Explore, learn and understand how all this works, because you need to.

73.

Dave G0WBX.


--
Created on and sent from a Unix like PC running and using free and open source software:


locked Re: WSJT-X suddenly deaf?

Russ Ravella
 

Yeah, gotta agree with John here again. RTFM is obviously important.  However it has about as much to do with the subject at hand as making sure your front door is locked at night does.

The decades long inexcusable stupidity at microsoft currently has folks computer forcibly “updated” resulting in huge problems for many people. And the idiots do it over and over and over again. Yes, they used to be even worse.  I was there from before the beginning so I am well aware.  But that’s like saying being 0.01 on a scale of 0-10 is better than being 0.001.  So what?  I’m not trying to pick a totally pointless fight here but how anyone can POSSIBLY defend those criminally ignorant hacks is beyond comprehension.

Very bad day here too.  My member-of-the-family cat just got bit in the face by a rattlesnake and I’ve been up non-stop for just under 48 hours.

Russ, KR6W 



On Mar 25, 2020, at 9:49 PM, K7RA Tad Cook <k7ra@...> wrote:


Thanks for all the comments.

The WSJT deafness problem is only on the laptop I have dedicated to WSJT.

My main laptop (both are Lenovo) does not have this problem.

I tried re-installing Win10 on the WSJT laptop, and that was quite an ordeal. I thought this would be easy, taking it back to factory defaults and a clean install, but there were complications. Re-installed WSJT and it is still deaf.  I will look at the OS sound options.

73



On Wed, Mar 25, 2020 at 8:39 PM JP Tucson, AZ <samcat88az@...> wrote:
Hi Bill, 

We"ve met at Quartzfest last year & @ Yuma.

I agree, RTFM is a good thing!

Except, I challenge anyone to show me a MS manual on any update; ever! They don't exist!

Worse, today - MS doesn't even tell you what a new update is for, or ask permission! 

My view: it is MY computer, not  MS's! If they ruin my computer, or wreck it to the point I have to start over with a new computer or hard drive; then they should be libel. 

That win10 updates scramble port settings and such is unprofessional & unacceptable.

As for not using windows, I have irreplaceable purpose driven software that isn't supported by MS & new versions (it runs only on XP) & the software mfr. went under in the great recession. Nobody makes anything to perform those tasks.



73 - John - N7GHZ

On Wed, Mar 25, 2020, 8:09 PM Bill Mader <billamader@...> wrote:
As a former computer tech support/IT guy in commercial broadcasting, my experience has show until a recent Windows Update, MS has done a "fairly" good job compared to a decade or two ago.  I had to deal with hundreds of PC's in a school environment and thousands of customers on the phone.  Now I read stories of hams who complain without having taking appropriate precautions like back-ups and good docmentation.

Then, when someone gives them hints, they just complain about Windows.  If it's that bad, don't use it!  Of course, most of the best ham radio software is written for Windows because, that's were the overwhelming majority of users are.

Like radios, RTFM is a useful acronym.  Of course, like radios, too few read those manuals who learn the ins and outs of the O/S.  I had the same problem with telephone users and electronic switches.  Learn to use your tool, drink some beer, and have a happier life.  Plus, shelter in place and maintain a safe social (or unsocial) distance.  Most importantly, stay safe and healthy!

If I sound grumpy, I have had a long day at this EOC!

--
73, Bill Mader, K8TE
W6H NM Coordinator, Route 66 On-the-Air 4-13 Sep 2020
Duke City Hamfest BoD Vice-Chairman www.dukecityhamfest.org 18-20 Sep 2020
Secretary and Past President, Albuquerque DX Association 




--
Tad Cook - K7RA
Seattle, WA
k7ra@...