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.
is v2.0.2 behaving itself?@rdwells It was slow and kept stopping for me. But Glenn has fixed it (for me) with R878.
Downloading drivers now. So far, so good.
Just one question. I notice that it does "checking files" before downloading even if I hadn't previously started a new download. Is that normal behavior? I can't remember.
Hi, I wanted to ask if v2.0.2 will be available via torrent too? (only 1.18 available atm) Thanks
Yes. As soon as I'm convinced it's stable and ready to be pushed out to the unsuspecting.Hi, I wanted to ask if v2.0.2 will be available via torrent too? (only 1.18 available atm) Thanks
Hello
I have installed and launch all the V2.0 last versions and rarely I have the bubble help when the pointer is on a driver line.
Actually, with the last version, there are no bubble-help.
(Windows 11 last version with 4k screenmode).
About this problem, It's resolved. Another program I use cause this problem (taskSlinger 0.8.27 actual beta).
can't the application register itself as a proper name e.g SDIO rather than the executable name which is what other apps seem to do?
The firewall gets the application name from version resource of the executable. The same info you see when you select properties from the Explorer context menu.
BLOCK "StringFileInfo"
BEGIN
BLOCK "040904E4" // Lang=US English, CharSet=Windows Multilingual
BEGIN
VALUE "CompanyName", "Glenn Delahoy\0"
VALUE "FileDescription", "Snappy Driver Installer Origin\0"
VALUE "LegalCopyright", "GNU GPL v3\0"
VALUE "OriginalFilename", "SDIO_R" SVN_REV_STR ".exe\0"
VALUE "ProductName", "Snappy Driver Installer Origin\0"
VALUE "FileVersion", VER_FILEVERSION_STR
VALUE "ProductVersion", VER_FILEVERSION_STR
VALUE "SpecialBuild", SVN_BUILD_NOTE
END
END
Specifically the FileDescription field. That info has been in the application for a very long time so it's a mystery why Windows Firewall sometimes uses the executable file name as the application name.
As an experiment, I deleted all related entries in my firewall and ran the latest sdio. It created the expected two entries, both with the correct name.
The multiple entries is due to each version update has a new executable file name, eg SDIO_x64_R886.exe. The only solution to that is to ensure each update results in the same file name. eg SDIO_x64_R886.exe => SDIO_x64.exe. Some people like to keep older versions in case the latest version sux. We could add an option that renames the new executable as it moves it into the main directory and perform an exe restart.
The only solution to that is to ensure each update results in the same file name. eg SDIO_x64_R886.exe => SDIO_x64.exe. Some people like to keep older versions in case the latest version sux. We could add an option that renames the new executable as it moves it into the main directory and perform an exe restart.
Yeah personally I would prefer the executable to be always the same and I can understand the need to keep older versions. Perhaps rename the previous release or place it in a subfolder, though for me I wouldn't require it as I can simply restore from backups which of course everyone will be doing 😜 Also, what if the newer version changes something that the older version cannot handle, having just the old executable wouldn't help.
Agreed. I'll work on it.The only solution to that is to ensure each update results in the same file name. eg SDIO_x64_R886.exe => SDIO_x64.exe. Some people like to keep older versions in case the latest version sux. We could add an option that renames the new executable as it moves it into the main directory and perform an exe restart.
Yeah personally I would prefer the executable to be always the same and I can understand the need to keep older versions. Perhaps rename the previous release or place it in a subfolder, though for me I wouldn't require it as I can simply restore from backups which of course everyone will be doing 😜 Also, what if the newer version changes something that the older version cannot handle, having just the old executable wouldn't help.
Have you ever looked at this option?personally I would prefer the executable to be always the same
rem 32-bit if exist SDIO.exe.bak del SDIO.exe.bak if exist SDIO.exe ren SDIO.exe SDIO.exe.bak if exist SDIO_R*.exe ren SDIO_R*.exe SDIO.exe rem 64-bit if exist SDIO_x64.exe.bak del SDIO_x64.exe.bak if exist SDIO_x64.exe ren SDIO_x64.exe SDIO_x64.exe.bak if exist SDIO_x64_R*.exe ren SDIO_x64_R*.exe SDIO_x64.exe rem XP 32-bit if exist SDIO-XP.exe.bak del SDIO-XP.exe.bak if exist SDIO-XP.exe ren SDIO-XP.exe SDIO-XP.exe.bak if exist SDIO-XP_R*.exe ren SDIO-XP_R*.exe SDIO-XP.exe rem XP 64-bit if exist SDIO-XP_x64.exe.bak del SDIO-XP_x64.exe.bak if exist SDIO-XP_x64.exe ren SDIO-XP_x64.exe SDIO-XP_x64.exe.bak if exist SDIO-XP_x64_R*.exe ren SDIO-XP_x64_R*.exe SDIO-XP_x64.exe
Have you ever looked at this option?
I've seen it but never had anything to use it for. Not sure how it would help - after downloading what for example?
after downloading what for example?
after downloading updates. see previous edited msg.
Version 2:
rem process_update.bat rem take a backup of the current executables rem then rename latest updates to something rem sensible so the firewall rules don't rem fill up with duplicates @echo off :32bit if not exist SDIO_R*.exe goto :64bit if exist SDIO.exe.bak del SDIO.exe.bak if exist SDIO.exe ren SDIO.exe SDIO.exe.bak if exist SDIO_R*.exe ren SDIO_R*.exe SDIO.exe echo Updated SDIO.exe :64bit if not exist SDIO_x64_R*.exe goto :XP32bit if exist SDIO_x64.exe.bak del SDIO_x64.exe.bak if exist SDIO_x64.exe ren SDIO_x64.exe SDIO_x64.exe.bak if exist SDIO_x64_R*.exe ren SDIO_x64_R*.exe SDIO_x64.exe echo Updated SDIO_x64.exe :XP32bit if not exist SDIO-XP_R*.exe goto :XP64bit if exist SDIO-XP.exe.bak del SDIO-XP.exe.bak if exist SDIO-XP.exe ren SDIO-XP.exe SDIO-XP.exe.bak if exist SDIO-XP_R*.exe ren SDIO-XP_R*.exe SDIO-XP.exe echo Updated SDIO-XP.exe :XP64bit if not exist SDIO-XP_x64_R*.exe goto :done if exist SDIO-XP_x64.exe.bak del SDIO-XP_x64.exe.bak if exist SDIO-XP_x64.exe ren SDIO-XP_x64.exe SDIO-XP_x64.exe.bak if exist SDIO-XP_x64_R*.exe ren SDIO-XP_x64_R*.exe SDIO-XP_x64.exe echo Updated SDIO-XP_x64.exe :done