Whistler Scanners and Windows 10

[Ed6698]

I am not driving at anything Dave, just trying to help people, this issue is being caused by the user I believe due to improper installation/ lack of information. Once there is enough information on this either Whistler needs to adjust the installation information, or correct the process of the driver. Sounds more like it is a user created issue due to not being clear setup procedures.

If I can do it with no issues and I am far from a computer expert.

 

[DaveIN]

Which makes me believe that the driver, model specific "inf" file has not been installed for those users. Something that may be important for the operation of updating CPU/DSP firmware and access of the SD card.

 

[Ed6698]

I just installed EZScan for the 1095 on my Win7 laptop, ran the PC Application update, plugged in scanner, works with no issues. This leads me to believe, people are plugging in the scanner before the EZscan installation and the EZScan update that fixes this issue. I am 3 for 3, with 2 different OS's and 3 different computers.

 

[darunimal]

DaveIN was your new TRX hooked upto the computer first?, before the download, installation and update of the EZ-Scan software, for the TRX Series. I'm not asking about the 1095 or 1098, just literally the TRX with a USB cable to the PC before anything else was done.

]

DaveIN, I'll ask the same question again, because apparently, no body installs software and drivers, before plugging in devices, for 25 years this is the way devices like it, in the correct order. If you can answer the question then we can really get to the bottom of the problem....

Proper Order of Installing (of most) Devices, on Windows machines, dating back to Windows 3.1:

1. Software
2. Drivers
3. Connect Device

Whether a company has a signed driver version is up-to Microsoft and could take over a year to be approved!!!

Updating the Wiki page before we get to the bottom of the problem isn't helpful to anyone. Despite some members thinking the Wiki's are useless, not everyone uses the forum to ask (numerous) questions (since there are 2 search features, one's inside the Wiki's). Some people like to educate themselves, with the Wiki. Some never ask a question publicly. Some haven't even signed-up to RadioReference, but still view pages here, then they consume as much info as they can: to inform themselves. So, once its set in stone, then, we should put it there. If we do it too early, we could dissuade numerous users from purchasing the scanners, even though realistically we meant to tell the 2-5 percent, they MAY have an issue. In the grandeur scheme of things, we all want both manufacturers to remain viable companies don't we? Also, shouldn't we try to be objective in what we put into the Wiki and leave subjective thoughts to the Forum?

 

[DaveIN]

Right... See post 60. Thank's for your comments. Moving on...

 

[Ed6698]

Dave can you answer darunimals question in post #58 about hooking up the scanner?

Just moving on is going to create more issues by leaving up a Wiki that is possibly incorrect as of now.

This is from Whistler after they updated EZScan with the fix for this issue.

•Changed the method used to detect the correct COM port for the scanner to take advantage of the Windows 10 feature that will automatically load the usbser windows driver for the scanner.


Whistler has fixed this issue. By me doing what I said on 4 different computers now on 2 different OSs shows this is probably going to be resolved for most people.

 

[03msc]

None of these steps should even need to be done anymore. There is no need even to download that other FTDI file or do a manual install of a driver. I installed EZScan and first thing ran the PC Application update, the latest update to EZScan takes care of the WIn10 issue. I have actually done this now on 2 Win 10 computers.

Same here for me with a 1095. Install EZScan and Windows 10 sees it fine. But as you said in another post, lots of different hardware and lots of different users factor in as well.

 

[Ed6698]

Same here for me with a 1095. Install EZScan and Windows 10 sees it fine. But as you said in another post, lots of different hardware and lots of different users factor in as well.

When you did the install of EZScan, did you install it and run the PC Application update before connecting the scanner?

 

[03msc]

When you did the install of EZScan, did you install it and run the PC Application update before connecting the scanner?

The first time I believe so, yes. Now it doesn't matter which order, whether I connect it first or open EZScan first.

 

[Ed6698]

The first time I believe so, yes. Now it doesn't matter which order, whether I connect it first or open EZScan first.

Thanks for letting me know, this is the pattern I am looking for. It does not matter after the initial install is done of EZScan when scanner is connected.

What I believe is happening, some users are connecting the scanner first before installing EZScan with the update, that allows Windows to install its own driver first, then users are installing EZScan, then the scanner will not communicate with pc.

 

[radio3353]

Not having bought a scanner in many years, do scanners today come with a quick start guide? From this post, seems like there is a specific sequence to follow when getting the new scanner ready for use. If there is no quick start guide, seems like the manufacturers have missed a crucial step.

 

[Ed6698]

Not having bought a scanner in many years, do scanners today come with a quick start guide? From this post, seems like there is a specific sequence to follow when getting the new scanner ready for use. If there is no quick start guide, seems like the manufacturers have missed a crucial step.

I took a look at the manuals. There is nothing on the Quick Start Guide at all about connecting scanner to PC.

Page 32 of the 1095 Manual it does mention to remove the card first when making a copy of the SD card.

What I believe is happening,some people are skipping this step and just connecting the scanner to pc first.

However the instructions later say to install the software by accessing the SD card via USB with scanner connected to PC. This is where the issue begins because Windows installs its own driver before the software is installed, causing the entire issue.

 

[freema22]

I am absolutely at my wits end with the Pro-668. I got one off of eBay for a great price. I followed all of the steps, but still can't get the damn thing to talk to my PC. I get the scanner to come up under "Ports" in the Device Manager, but it has an (!) on the icon. When I click it, it says that "This device cannot start (Code 10). When I run the RS software, it says "Unable to confirm the scanner has entered update mode. Please check to ensure that the USB cable is connected to your computer and your scanner and try again." But I try and I try and I try, and nothing works. Please help! And ideas are appreciated.

Mike

 

[wbswetnam]

I am absolutely at my wits end with the Pro-668. I got one off of eBay for a great price. I followed all of the steps, but still can't get the damn thing to talk to my PC. I get the scanner to come up under "Ports" in the Device Manager, but it has an (!) on the icon. When I click it, it says that "This device cannot start (Code 10). When I run the RS software, it says "Unable to confirm the scanner has entered update mode. Please check to ensure that the USB cable is connected to your computer and your scanner and try again." But I try and I try and I try, and nothing works. Please help! And ideas are appreciated.

Mike

Mike,

This forum is for Whistler scanners, but let me try to help you out...

I was having trouble updating my RS Pro-668, too, until I found this post: http://forums.radioreference.com/ra...-668-since-windows-10-update.html#post2431669

I followed the directions to the letter (don't skip any steps!) and my Pro-668 loaded the driver perfectly. Then I was able to use the EZ-Scan to check for updates, no problem.

 

[darunimal]

All GRE PSR-800 Based scanners to include Radio Shack RS-668, Whistler WS1080, WS1088, WS1095, WS1098, TRX-1 & TRX-2 need proper installation order (should you need an SD card reader to obtain Software, before connecting said device(s), one may well need to be purchased from a 3rd party source, that's if a copy of the corresponding software cannot be downloaded from official channels).

First and foremost BACKUP ORIGINAL SD CARD, Then Install Software, Afterward Update Software, Then after Install Drivers, And finally Connect your Scanner

The same is applicable to all scanner with heritage of the PSR-800, since Whistler bought out all Grecom intellectual property and real property, and as such is used for all those related products regardless of their respective Make or model Names. These are indemic problems associated to the whole line

 

[mrhermit]

WS1080 and WIndows 10.

I have always had trouble with the software working properly on my Windows 10 Pro 64 bit 6 month old desktop.
The other day I was updating to the latest software and firmware. It was not a smooth operation.
The firmware update choked a few times before It finally got it to update. Then the same thing happened with the software update. The scanner was recognized by the computer, but it kept telling me I had to unplugged the scanner cable and try again. Finally I got it updated. The next day I had it hooked up again and it started to do the Firmware update again without me doing anything. After a about 10 minuets, the firmware update froze the scanner. I unplugged it and the screen still was frozen with the update information on the scanner screen.
I tried to turn of the scanner, but I could not get it to do that. I thought that maybe somehow the firmware update bricked the scanner.
I the hooked it up to my 10 old Windows 7 32 bit laptop. Zip, Bam, Boom. The laptop recognized the scanner immediately. The screen that was stuck before was now working properly. I preformed a firmware update again. This time it was a smooth update and very fast compared to my new Windows 10 computer. Next I did the update of the database and again it was very smooth and fast.

So I am wondering. Is the EZ Scan software better suited to a 32 bit system and Windows 7 then it is to a 64 bit system running Windows 10? As I remember when I was running Windows 8.1 64 bit it also had a lot of hiccups.

I hope my old laptop does not die anytime soon.

Joe in Sarasota FL

 

[03msc]

I have always had trouble with the software working properly on my Windows 10 Pro 64 bit 6 month old desktop.
The other day I was updating to the latest software and firmware. It was not a smooth operation.
The firmware update choked a few times before It finally got it to update. Then the same thing happened with the software update. The scanner was recognized by the computer, but it kept telling me I had to unplugged the scanner cable and try again. Finally I got it updated. The next day I had it hooked up again and it started to do the Firmware update again without me doing anything. After a about 10 minuets, the firmware update froze the scanner. I unplugged it and the screen still was frozen with the update information on the scanner screen.
I tried to turn of the scanner, but I could not get it to do that. I thought that maybe somehow the firmware update bricked the scanner.
I the hooked it up to my 10 old Windows 7 32 bit laptop. Zip, Bam, Boom. The laptop recognized the scanner immediately. The screen that was stuck before was now working properly. I preformed a firmware update again. This time it was a smooth update and very fast compared to my new Windows 10 computer. Next I did the update of the database and again it was very smooth and fast.

So I am wondering. Is the EZ Scan software better suited to a 32 bit system and Windows 7 then it is to a 64 bit system running Windows 10? As I remember when I was running Windows 8.1 64 bit it also had a lot of hiccups.

I hope my old laptop does not die anytime soon.

Joe in Sarasota FL

Was it actually failing or was it just saying "not responding" and you ended it? Because mine sometimes says not responding but if I leave it alone it completes in the background successfully. Obviously some sort of glitch but it still works. Just wondering.

Interesting observation of the 32bit vs 64bit. Could be possible. Could be some other difference between your computers that is unrelated to the 32/64 thing, too. At least you did get it to complete for you, on a positive note.

 

[dmaria]

Was it actually failing or was it just saying "not responding" and you ended it? Because mine sometimes says not responding but if I leave it alone it completes in the background successfully. Obviously some sort of glitch but it still works. Just wondering.

Mine does this also. Just when i'm about to give up, it will respond and finish.

 

[SCPD]

There are a few things like this .. mostly when dealing with audio files. But I know it is working .. just needs patience. But .. poor-ish programming by the developers. I know a bit about that one .. as I am one of those developer types.

 

[mrhermit]

03msc.
At fist it seemed to be working. Win 10 recognized the scanner. Then it asked if it would like to update.
There was the update for EZscan, That seemed to work fine. Then it tried to update the firmware. It seemed to stumble a few times and the scanner was showing it was working, but it stalled out on me. I waited about 10 minuets and still nothing. I finally gave up. The screen on the radio was still locked up. I could not turn it off. That is when I pulled out my Windows 7 32 bit laptop. Everything worked as it should. Once the scanner was recognized, it briefly shut off, and then it turned itself on and started doing an update of the firmware, and also it did a CPU update, plus it also updated easy scan software and then the database files. It seems to be working fine now.