We appreciate the contributions many of you have been able to make towards repairing the storm damage and keeping a roof over our heads. With your help we’ve been able to complete much of the critical work. There is still work to be done to secure the house and your continued support will be a huge help.
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.
Version 1.17.8.829
07 March 2026
* SamLab Driver Packs 26.02.2
* SDIO Driver Packs 26.03.1
Hi Glenn, I updated to this new version and for whatever reason, it downloaded into my system32 folder. Which then resetup all of the folders and config files inside the system32 directory. I moved the update back to my normal SDIO install folder but maybe you should fix this, if you can reproduce it.
i figured it out more. if you open SDIO using the taskbar search, it will generate a new config file in the system32 directory. If I open SDIO by navigating to the folder in my file explorer, it will open it using the correct config file inside the SDIO folder. So weird, i've never had this issue before.
I'm glad you figured it out. You discovered the joys of Windows default "current directory" or "working directory". Running from the taskbar search will cause a default working directory of system32. Your best bet is to create a shortcut to SDIO and make sure the "Start in" directory is set to the SDIO folder.i figured it out more. if you open SDIO using the taskbar search, it will generate a new config file in the system32 directory. If I open SDIO by navigating to the folder in my file explorer, it will open it using the correct config file inside the SDIO folder. So weird, i've never had this issue before.
Hello, how can I restrict the ports (local) for SDIO that it can access? I've restricted it through the Windows 10 firewall, but it still accesses 64XXX (even though the allowed port range was specified differently. I did the same as with my configured torrent client – there are no problems in this regard). My mobile operator charges me if I use file-sharing networks, so I have to route the traffic through a proxy.
The utility starts accessing the entire port range, and I can't find it in the Mikhomo proxy kernel. In the torrent client (qBitTorrent), I solved a similar problem by specifying a proxy server in the settings (router address:listening port) and listening on the specified port in the kernel (listeners). I don't understand how to find your program here. For example, I specified port 55555 in the settings (it accessed this port once, and then it goes through the entire range).
That's a part of torrents I've never explored. A brief look in the code suggests that when we set the torrent port in SDIO we are actually setting the incoming port, the listening port. The outgoing ports apparently are unrestricted with the possible exception of <1024. I'll see if we can do anything about that. Meanwhile you can make use of Windows Resource Monitor to see what it's up to.Hello, how can I restrict the ports (local) for SDIO that it can access? I've restricted it through the Windows 10 firewall, but it still accesses 64XXX (even though the allowed port range was specified differently. I did the same as with my configured torrent client – there are no problems in this regard). My mobile operator charges me if I use file-sharing networks, so I have to route the traffic through a proxy.
The utility starts accessing the entire port range, and I can't find it in the Mikhomo proxy kernel. In the torrent client (qBitTorrent), I solved a similar problem by specifying a proxy server in the settings (router address:listening port) and listening on the specified port in the kernel (listeners). I don't understand how to find your program here. For example, I specified port 55555 in the settings (it accessed this port once, and then it goes through the entire range).
Hey, Glenn! That AMD bug returned recently. This time, I noticed there's a screenshot option. Is there a way to maybe hide the update using the settings? Thanks!!
Maybe a driver ignore list would be useful or a device ignore list or something?Hey, Glenn! That AMD bug returned recently. This time, I noticed there's a screenshot option. Is there a way to maybe hide the update using the settings? Thanks!!
Yes, that would be nice! The AMD Install Manager used to install the same driver with the same result, but has long since been fixed.
@camfarrsuperstar Can you provide more information on the driver in question?
