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.
I think I found the issue. I may have been the only one getting the emails :-/I put it in the v2.0.1 zip. Maybe check your spam folder. I know I'm getting the emails. The v2 releases are not on the auto updates yet until I know it's stable.
Nope, nothing in spam - I suspect it just doesn't like my email address
I think I found the issue. I may have been the only one getting the emails :-/I put it in the v2.0.1 zip. Maybe check your spam folder. I know I'm getting the emails. The v2 releases are not on the auto updates yet until I know it's stable.
Nope, nothing in spam - I suspect it just doesn't like my email address
Thanks I just received one 👍
Has anyone worked out what "Keep sharing new driver packs after downloads are finished" means?
@glenn Quick question, I've been seeding the application and driver packs from my server to support the project and would love to keep contributing that way. Will this still be possible in the future?
Absolutely. The more seeders we have, the better. I've added a new function to encourage people to share. So now there's a choice of seeding via a torrent client or from within SDIO itself. You may have noticed when SDIO v2 downloads the SDIO_Update.torrent file, it puts it in a sub-folder called "torrent" so you can use that in a client if you prefer.@glenn Quick question, I've been seeding the application and driver packs from my server to support the project and would love to keep contributing that way. Will this still be possible in the future?
I'm downloading updates again now. All good.
But I just have to say, that Clean theme is lovely. I just love the colors. 🙂
@glen is it possible for the hardware-ignore list to be machine specific, rather like the log and state files? I share my SDIO install from a server so that it's accessible to my two workstations and some exclusions are only relevant to the specific machine e.g. on the server itself which is a VM it thinks I need some updates to the PCI Bus drivers but if I exclude it, it will also be excluded on the workstations where it's more relevant. I never actually update anything on the server as it's a VM, but just use it as an example.
You mean like put the host name into the file name? eg: HOST_hwid-ignore.txt@glen is it possible for the hardware-ignore list to be machine specific, rather like the log and state files? I share my SDIO install from a server so that it's accessible to my two workstations and some exclusions are only relevant to the specific machine e.g. on the server itself which is a VM it thinks I need some updates to the PCI Bus drivers but if I exclude it, it will also be excluded on the workstations where it's more relevant. I never actually update anything on the server as it's a VM, but just use it as an example.
or possibly hwid-ignore_HOST.txt