Driver Signing Certificates On Sale -- Please Eliminate Installation Issues
- Thread starter AggieCon
- Start date
- Status
DonS
Member
The only explanation I have for that is that people are trying to run the OLDER versions of the various PC apps on Windows 10.
Posts #44 and #47 in this thread indicate that the .INF file is no longer needed on Windows 10 in order to get Windows to "see" the serial port. The screen shots in post #47 clearly show that Windows 10 is installing the required driver and assigning a COM port to the scanner's communication device without the .INF. Yes, that user (DaveIN) describes difficulties updating CPU firmware, but he says in post #82 that he was able to set the clock - indicating that the PC app and Windows saw the scanner's serial port.
In May 2016, Whistler released new versions of the PC apps. Before that, the apps were looking for specific "Friendly name" for the COM port - for the WS1080/88, that was "Whistler WS1080 Serial Device". The new versions merely look for a USB serial device where the "Device instance path" contains matching VID/PID info. For example, the WS1080/88 app looks for "VID_2A59&PID_000D".
My post #81 in that thread describes my experience connecting a WS1088 to three different Windows 10 machines (two desktops running Window 10 Pro and a Surface 3 running Windows 10 Home). I never installed the Whistler .INF file, nor was I prompted to do so. The old version of the PC app that I had on the scanner's uSD card (1.9.5.305 from July 2014) could not see the scanner's COM port - that was expected. As soon as I ran the PC app and installed the latest version, it could see the scanner, set the time, update firmware, etc. And the scanner still shows up in Device Manager as "USB Serial Device (COMx)", not "Whistler WS1080 Serial Device (COMx)", since the Whistler .INF file was never installed.
Want it to work? 1) Reformat 2) Don't Download Driver 3) Update Software
Okay. I get it. We are liars and incompetent. Good to know. That's the nail in the coffin. No more Whistler products for me.
You can continue to listen to the echo chamber of a few 'Whistler defenders' and feel great inside, or, listen to hundreds, if not thousands, who have problems and respond by make modifications instead of marginalizing your own customers. Obviously, the orientation is to defend and market rather than to fess up and fix.
To be clear to anyone reading this in the future, "Post 81" referenced above was just posted...
The post describes 21 specific steps that must be followed in order. Hardly "EZ".
Oh, and you have to have a "virgin" computer that never had the Whistler inf file downloaded or installed.
It is plainly admitted that before May of this year, there was no expectation for the software to work.
Now, if you want it to work, you better reformat your computer or go buy a new one (if you previously tried to use your scanner on the computer).
And you have to have the latest software version... That's right, after you download the software straight from the marketer's website, make sure you update it again or it will not work.
I posted a number of links and substantial key quotes and commentary. Was it even read? I already described why the scanners will be more likely to work if users do not download the Whister driver first. It is because your device subclass is not correct (2). But as long as Whistler's chicken driver isn't on the computer, the OS will look for "compatibility drivers" that do work in many instances (but not all). That's exactly why I listed 5 shorter steps previously. I oftentimes forget to tell people to update the software first, because it escapes my mind that people post old versions of software online.
If you had read my material, you would already know why this behavior is occurring, not merely that it is occurring.
I too have been through all the mess described in posts 47 and on. Even though the device appears with the Windows driver, it does not always work.
Who do you think is helping people with these problems, anyways? The Whistler support generally can't figure it out.
Documentation for this product is almost non-existent. There are a number of nuanced steps regular (or even advanced) users aren't going to naturally do or know, including the following:
Okay. I get it. We are liars and incompetent. Good to know. That's the nail in the coffin. No more Whistler products for me.
You can continue to listen to the echo chamber of a few 'Whistler defenders' and feel great inside, or, listen to hundreds, if not thousands, who have problems and respond by make modifications instead of marginalizing your own customers. Obviously, the orientation is to defend and market rather than to fess up and fix.
To be clear to anyone reading this in the future, "Post 81" referenced above was just posted...
The post describes 21 specific steps that must be followed in order. Hardly "EZ".
Oh, and you have to have a "virgin" computer that never had the Whistler inf file downloaded or installed.
It is plainly admitted that before May of this year, there was no expectation for the software to work.
Now, if you want it to work, you better reformat your computer or go buy a new one (if you previously tried to use your scanner on the computer).
And you have to have the latest software version... That's right, after you download the software straight from the marketer's website, make sure you update it again or it will not work.
I posted a number of links and substantial key quotes and commentary. Was it even read? I already described why the scanners will be more likely to work if users do not download the Whister driver first. It is because your device subclass is not correct (2). But as long as Whistler's chicken driver isn't on the computer, the OS will look for "compatibility drivers" that do work in many instances (but not all). That's exactly why I listed 5 shorter steps previously. I oftentimes forget to tell people to update the software first, because it escapes my mind that people post old versions of software online.
If you had read my material, you would already know why this behavior is occurring, not merely that it is occurring.
I too have been through all the mess described in posts 47 and on. Even though the device appears with the Windows driver, it does not always work.
Who do you think is helping people with these problems, anyways? The Whistler support generally can't figure it out.
Documentation for this product is almost non-existent. There are a number of nuanced steps regular (or even advanced) users aren't going to naturally do or know, including the following:
- You must update the software that came with your new scanner or that you just downloaded before it will work correctly.
- You should not download the Whistler drivers in most instances.
- You have to reformat your computer or buy a new one if you want the Whistler recommended steps to work (if you used your scanner with the computer before today).
- There are two device types and both must be correct. Merely a drive showing up in Windows Explorer does not necessarily mean it is installed correctly.
- And more.
And, once again here I am tip-toeing thru the tulips. I don't mean to break in, but my TRX 2 arrived today. Its still in the shipping box next to my 436 which came today also.
Last week I downloaded the Whistler EZ Scan software. I assume I just need to update it before connecting the TRX2 to it?
Second, and I cannot remember, if I downloaded the driver as well. A look thru my device manager and nothing stood out.
(Reformat my PC ?) That's not going to happen.
If I have the updated software before I connect, must I worry about this driver issue? Or, any other help would be great. I've read every post here on the subject, and I have terrible migraine now?
Thank you.
Last week I downloaded the Whistler EZ Scan software. I assume I just need to update it before connecting the TRX2 to it?
Second, and I cannot remember, if I downloaded the driver as well. A look thru my device manager and nothing stood out.
(Reformat my PC ?) That's not going to happen.
If I have the updated software before I connect, must I worry about this driver issue? Or, any other help would be great. I've read every post here on the subject, and I have terrible migraine now?
Thank you.
Just to be perfectly clear, having a "Signed Certificate" means only that the person seeking the certification is in fact who he or she claims to be. In other words, they can be "trusted." That is all!
Having WHQL certification is an ancillary process that may be undertaken at the same time but that only guarantees that the file being certified isn't going to do anything stupid or dangerous to the OS, not that it will necessarily work properly... :lol:
For many years I had to digitally sign dynamic link library (gauge) files for use in MS Flight Simulator X because of MS's silliness. It was a complicated and time consuming process that added no value whatsoever to the end product save that of not having a popup pester the customer if they wanted to "Trust" each individual .dll file when installing for the first time... :roll:
Having WHQL certification is an ancillary process that may be undertaken at the same time but that only guarantees that the file being certified isn't going to do anything stupid or dangerous to the OS, not that it will necessarily work properly... :lol:
For many years I had to digitally sign dynamic link library (gauge) files for use in MS Flight Simulator X because of MS's silliness. It was a complicated and time consuming process that added no value whatsoever to the end product save that of not having a popup pester the customer if they wanted to "Trust" each individual .dll file when installing for the first time... :roll:
The reformat/buy a new PC wasn't a serious suggestion. I was pointing out the ludicrous situation and "perfect conditions" used for the tests when it all just works right.
So, certainly, update the software by going to Updates -> Check for PC Application Updates. There should be a newer version.
It wouldn't hurt to look through your downloads. If the driver is there, go ahead and delete it so there will be no way for Windows to find it.
Otherwise, hope it works, and, if not, there are (difficult) ways around that too.
And, yea, I know what you mean.
So, certainly, update the software by going to Updates -> Check for PC Application Updates. There should be a newer version.
It wouldn't hurt to look through your downloads. If the driver is there, go ahead and delete it so there will be no way for Windows to find it.
Otherwise, hope it works, and, if not, there are (difficult) ways around that too.
And, yea, I know what you mean.
Not having the driver signed isn't just a pop-up. It is an involved process to work around.
I should think correcting it would add much value.
I am not sure they are receptive to their customer base. They might find that their customer base does not purchase again and ceases to recommend the product. They might even find that the customer base actively persuades against their product. I will say that it is not too late for them to apologize, admit wrongdoing, and correct the problem. But it's not looking like that will happen.
I should think correcting it would add much value.
I am not sure they are receptive to their customer base. They might find that their customer base does not purchase again and ceases to recommend the product. They might even find that the customer base actively persuades against their product. I will say that it is not too late for them to apologize, admit wrongdoing, and correct the problem. But it's not looking like that will happen.
I predict that if they don't give driver signing a single thought, there will not be more than one customer lost. That dead horse is now leather. Give it up.
mike
D
darunimal
Guest
Once again an Admin or Moderator should not be deciding the validity of a posters problem when it recognized as a problem that has yet to be fixed/mitigated. This isn't him saying he wants the paint on his Ford fixed, this is a scanner issue on a scanner forum, if you hate the premise that's cool, don't post comment or read, it's the same as whats on TV, you don't like it "change the channel." But publicly flogging him for bring up a KNOWN issue, surely won't solve the ISSUE, may be a private message might dissuade him, but until the problem is resolved by the manufacturer, any OP has the right to comment on a known issue. We finally don't have to read 40 post a day about, "when are manufacturer's are going to support DMR?," I think I only commented on that dead horse twice, when "it wasn't likely", the other 8000 times I, "changed the channel."
I knew that! I deleted the EZ Scan software anyhow. I had downloaded the software for the TRX-1; I bought the TRX-2 however.
(Besides, my wife would not buy my argument that I need a TRX-1 now because I downloaded the software for it)
I know you knew but I reconsidered that perhaps not everyone will know, so I wanted to clear it up.
Yea, always have to listen to the boss lady. Let me know how you like the TRX-2 and if you are able to get it working easily without having the Whistler driver ever downloaded and installed.
Yea, always have to listen to the boss lady. Let me know how you like the TRX-2 and if you are able to get it working easily without having the Whistler driver ever downloaded and installed.
I looked thru my device manager, but did not see anything sticking out at me. That does not mean it is not there.
Also I deleted the TRX-1 program and will download the TRX-2 EZ scan before I start. Thanks for the help.
Also I deleted the TRX-1 program and will download the TRX-2 EZ scan before I start. Thanks for the help.
- Joined
- Jan 5, 2003
- Messages
- 13,953
- Reaction score
- 9,744
- Location
- Retired 40 Year Firefighter NW Tenn
You will not see it in device manager unless it is hooked up.
Try to do a search of your downloads folder or wherever you might have downloaded a driver file, just incase Windows for some reason tries to search your computer for it. Also, be sure to update the EZ Scan software once you install it, even if you just downloaded it from their website.
It would seem that with the MAY release of EZScan, that differs in how it handles Windows 10, worked in DonS 3 PC's that never had the program installed in it is great. Others will most likely experience the same results with a first time installation. but just like Windows 7 there are going to be some users that will have issues. The issues are east to fix, they just have to use the Win8-10 driver work-around to get the scanner to be seen by the PC.
If they have issues, that is what this forum is for to help others,... right?
If they have issues, that is what this forum is for to help others,... right?
- Joined
- Jan 5, 2003
- Messages
- 13,953
- Reaction score
- 9,744
- Location
- Retired 40 Year Firefighter NW Tenn
Wendy just posted to not ask bug questions or request or ask DonS anything open here they are busy use the whistler email address. Here is her post
Hi everyone -
The Whistler Engineering team and Don S. are very busy right now so we would greatly appreciate it if you would submit any suggestions (or bug reports) to the scannersuggestions@whistlergroup.com email rather than posting them in the forum or directing them to Don. That way we can monitor them and log them. You may not receive a response to your email directly but please know that we are looking at every single one of them and logging them and discussing within the team.
We appreciate you all!
Thanks,
Whistler Wendy
Hi everyone -
The Whistler Engineering team and Don S. are very busy right now so we would greatly appreciate it if you would submit any suggestions (or bug reports) to the scannersuggestions@whistlergroup.com email rather than posting them in the forum or directing them to Don. That way we can monitor them and log them. You may not receive a response to your email directly but please know that we are looking at every single one of them and logging them and discussing within the team.
We appreciate you all!
Thanks,
Whistler Wendy
D
darunimal
Guest
We can monitor and log them just fine here, that is: until we can't.
WhistlerWendy
Member
Sorry guys, it wasn't that we don't want it discussed. That post was actually from the Update thread. I'm just trying to keep up with the thread and make sure we get everyone's issues addressed and the email is an easier way of doing that. That's all. Definitely not closing the thread or trying to stifle any conversation!
- Status
