Snappy Driver Installer Origin

[Volya]

What's the problem you're trying to solve here?

Some of our coporate windows images needed a network driver to be installed prior to first user/desktop login. We copied SDI to the C drive and executed only the network drivers install. Upon succesfull installation, we required the SDI folder and its content deleted from the system because it had no more use to be there. This command will be useful for sys admins that do unattend setups, it sure would've been for me.

 

[glricht]

Some of our coporate windows images needed a network driver to be installed prior to first user/desktop login.

Before SDI came onto the scene, if we couldn't get a machine on the Internet due to no network driver, we used 3DP Net (http://www.3dpchip.com/3dpchip/index_eng.html). It contains the drivers for a LOT of network adapters. Run it, it would detect the needed driver and install it.

 

[glennd]

Some of our coporate windows images needed a network driver to be installed prior to first user/desktop login. We copied SDI to the C drive and executed only the network drivers install. Upon succesfull installation, we required the SDI folder and its content deleted from the system because it had no more use to be there. This command will be useful for sys admins that do unattend setups, it sure would've been for me.

added to the TODO list.

 

[fincoder]

if we couldn't get a machine on the Internet due to no network driver, we used 3DP Net

I use one of those USB3-to-gigabit ethernet adapters with built-in flash storage containing the driver (got from ebay). Years ago I had an SMC USB-ethernet adapter (only 10mbps) that didn't need a driver on XP systems as the driver was built into the OS. Unfortunately in later OS versions the driver was no longer built in!

 

[Volya]

I'd like to understand why the options -PATH -nogui -autoupdate -autoclose -autoinstall will be deprecated.


Also, the following code will automatically update the drivers even though it is not asked. I'm running SDIO in a WinPE environment so there is no need to update drivers. How do I set it to never update?

-license -hidepatreon -expertmode -nostop -autoinstall -autoclose

The autoupdate on -install should be disabled by default and only work when specifying a parameter.

 

[glennd]

I'd like to understand why the options -PATH -nogui -autoupdate -autoclose -autoinstall will be deprecated.


Also, the following code will automatically update the drivers even though it is not asked. I'm running SDIO in a WinPE environment so there is no need to update drivers. How do I set it to never update?

-license -hidepatreon -expertmode -nostop -autoinstall -autoclose

The autoupdate on -install should be disabled by default and only work when specifying a parameter.

all the command line automation arguments are being deprecated. You should start looking at the scripting tool, it is much more powerful and flexible and easier to understand. There are several examples in the package as well as a detailed explanation in the reference manual of how to use it.

However, I'll have a look to see if it's a simple fix that can be done for the next release but by definition, 'deprecated' means it's no longer supported.

 

[Volya]

I actually looked at the scripting syntax last night. It's very impressive and more flexible than before.
I think you should remove the config file entirely and have the application settings and parameters to the script file. It's cleaner this way.

install
Install the selected drivers. If drivers are not found locally they will be automatically
downloaded if checkupdates previously completed successfully. You don't need to do a 'get'
command, just the 'select' and 'install'.

This was the reason why it downloaded the updates in WinPE. You see, In WinPE SDIO has only Network* driverpacks, but SDIO also finds other hardware for which it has no driverpacks, so it downloads them automatically. This behavior should immediately be disabled. SDIO should install the drivers for which it has driverpacks and not automatically download them.
You could add the options

install available (from available driverpacks)
install all (if driverpacks do not exist, download and then install)

Here are some minor tips you could do:

• keep all code references, syntaxes and examples in one .txt file. it's easier to find, read, and copy from. don't use pdf as when copying certain lines will have non-printable and can cause issues to unsuspecting users. one changelog.txt and one reference.txt, and one manual.pdf for storing pictures and full guides
  
• ditch the autorun.inf because 1) the execution will not work on any os passed windows xp and 2) nobody actually uses a usb drive only for sdio, they use it with more apps so the icon is not really useful
• append all your batch scripts with _ so they will always appear before the executables SDIO_R658.exe / SDIO_x64_R658.exe. you can use _install_auto, _run, _cleanup_driverpacks
  
• it probably would be best to find someway to name the executables SDIO.exe and SDIO_x64.exe instead of SDIO_R658.exe / SDIO_x64_R658.exe. With a static name, it's much easier for the averange joe to execute and use.

Congratulations on yet another significant improvement.

 

[Porthos]

nobody actually uses a usb drive only for sdio, they use it with more apps so the icon is not really useful

I do. I have a 16gig usb3 drive dedicated to it.

 

[glennd]

You see, In WinPE SDIO has only Network* driverpacks, but SDIO also finds other hardware for which it has no driverpacks, so it downloads them automatically. This behavior should immediately be disabled. SDIO should install the drivers for which it has driverpacks and not automatically download them.

the drpfilter in the select command is for exactly this purpose. it allows you to select only the lan drivers to be installed from your PE. the command would be something like: "select missing better lan" followed by the install command.

Here are some minor tips you could do:

some interesting ideas there, i'll see what can be done.

nobody actually uses a usb drive only for sdio

I do. I'd rather have a bag full of thumb drives than a single point of failure for all my tools.

believe it or not i still have end users working on XP boxes.

Congratulations on yet another significant improvement.

thank you.

 

[GTP]

I too use a USB for SDIO.

 

[glennd]

I'd like to understand why the options -PATH -nogui -autoupdate -autoclose -autoinstall will be deprecated.


Also, the following code will automatically update the drivers even though it is not asked. I'm running SDIO in a WinPE environment so there is no need to update drivers. How do I set it to never update?

-license -hidepatreon -expertmode -nostop -autoinstall -autoclose

The autoupdate on -install should be disabled by default and only work when specifying a parameter.

The code looks fine so I guess you had the -checkupdates switch on in the cfg file.

I think you should remove the config file entirely and have the application settings and parameters to the script file. It's cleaner this way.

the cfg file is ignored when running in script mode, all configuration is done within the script

 

[glennd]

For those interested, I've given SDIO a Christmas present, a brand new web site. I've also set up a more complete alternative to Patreon using PayPal for those that want to help out but don't like Patreon.

Have a look: www.snappy-driver-installer.org

 

[Dean2]

Looks good, cheers

 

[overburnz]

Redownloanding it again thanks

 

[fincoder]

@glennd is there are reason why the 'Updates are available' thing at the top no longer specifies that there is an index or application update? Before when I was using the non-origin version it used to say whether index or app udpates were available, so for normal usage where driver packs are downloaded on demand, I only needed to go into the update window if I had to. No I have to go into updates every time I run it, to make sure there's no app/index updates.

 

[glennd]

@glennd is there are reason why the 'Updates are available' thing at the top no longer specifies that there is an index or application update? Before when I was using the non-origin version it used to say whether index or app udpates were available, so for normal usage where driver packs are downloaded on demand, I only needed to go into the update window if I had to. No I have to go into updates every time I run it, to make sure there's no app/index updates.

Check which update torrent you're on. Only the first one, SDIO Updates, shows the app and index updates.

 

[fincoder]

I've no idea how you got that menu in your pic. I only see what's in the pic attached.

I can still update to the latest app/indexes once I go into the update window, but I only get notified of driver pack updates on the main screen.

 

[glennd]

I've no idea how you got that menu in your pic. I only see what's in the pic attached.

I can still update to the latest app/indexes once I go into the update window, but I only get notified of driver pack updates on the main screen.

Right click on the title bar

 

[glennd]

I've no idea how you got that menu in your pic. I only see what's in the pic attached.

I can still update to the latest app/indexes once I go into the update window, but I only get notified of driver pack updates on the main screen.

are you asking why the front screen doesn't say "48 driver packs, indexes and application updates available" ?

 

[fincoder]

are you asking why the front screen doesn't say "48 driver packs, indexes and application updates available" ?

Yes, I'm asking why there is no indication on the front screen that app/index updates are available, which it used to. On one of my recovery drives with SDIO it currently says 'Updates are Available: 48 driver packs'. If I click on that I see there's also Application and Index updates available, which I would have missed if I didn't click on it.

I, and I assume most others, don't need to know about updated driver packs. They download on demand if needed anyway. But the app and index updates need to be installed, they're the most important update but there's no notification. It did that in earlier versions (possibly before 'origin').

For a while now I've been going into the update screen every time I run SDIO, because it's the only way of knowing. I've lived with this for a while now so if you can't figure out the issue, don't worry.