We had a major storm through here recently and we suffered damage to the house roof and ceilings. I just received the quote to repair. I’m hoping that a small fraction of the 80,000 odd people that download SDIO and/or Desktop Info every month won’t mind chipping in a few dollars to help out. Click on the big blue button at the bottom of the page to help us keep a roof over our heads, literally!
Guests have read-only access to our forums. If you wish to participate you will need to register. Be sure to activate your account from the email sent to you when you register.
Seems the driverpacks themselves have been messed up. Tried on a laptop over the weekend and saw other incorrect drivers being offered - didn't manage to get a screenshot (was at someone else's place, with limited time), but will see if I can try again. It was some component of the system (ASUS laptop, intel 4th gen CPU) and the apparent driver update for it was named "HP <something>", so very clearly wrong.
Just for sanity, tried an older version of SDIO, same issue - so the appearance of this problem was a coincidence with the release of the latest SDIO as far as I can tell.
Seems the driverpacks themselves have been messed up.
<snip>
Further to this, all sorts of drivers are now completely wrong, and have suspicious driver sources with excessively long Chinese language names (that scroll off my 2560 wide monitor). Seems the packs are compromised?
Hrm, you may be right 🤨 I'll be looking closely at the next release. I'm tempted to re-release the 25000 set as a way to get as many people off the latest drivers as possible.Seems the driverpacks themselves have been messed up.
<snip>Further to this, all sorts of drivers are now completely wrong, and have suspicious driver sources with excessively long Chinese language names (that scroll off my 2560 wide monitor). Seems the packs are compromised?
Edit: In fact I just did.
@glenn as long as we avoid the yEXP packages which violently proposed themselves loudly asking to replace basically all drivers from other packages with theirs, is the 25010 safe? I mean, the Chipset, Sound Others, Sound Intel, etc etc, can I safely use the 25010 which I have already installed?
I believe so..@glenn as long as we avoid the yEXP packages which violently proposed themselves loudly asking to replace basically all drivers from other packages with theirs, is the 25010 safe? I mean, the Chipset, Sound Others, Sound Intel, etc etc, can I safely use the 25010 which I have already installed?
What process is in place to insure these driver packages are safe?
Are the driver packages just assumed to be safe before they are dumped for download?
It will be a while before I am able to trust this process again. I would like to see more quality control.
What do you have in mind?
