Почему виндовс блокирует snappy driver installer
Перейти к содержимому

Почему виндовс блокирует snappy driver installer

  • автор:

Почему виндовс блокирует snappy driver installer

Snappy Driver Installer R477

Номер версии: Revision 477
Разработчик: BadPointer
Язык интерфейса: Мультиязычный, включая русский
Системные требования: Windows 2000
Лицензия: GNU GPL v3
Сайт: https://sdi-tool.org

R513 — последний релиз, собранный лично BadPointer’ом. Далее программа контролируется третьими лицами.

Описание:
Snappy Driver Installer — программа предназначенная для установки и обновления драйверов с использованием драйверпаков из сборки SamDrivers. Является лидером среди программ этого класса по точности подбора драйверов и скорости работы. При ранжировании драйверов отдает приоритет более подходящим драйверам(невзирая на наличие более новых версий), чтобы минимизировать риски для рядовых пользователей. Специалисты могут оценить большой объем информации выдаваемый о драйверах и возможность выбрать альтернативный драйвер.

  • Язык программирования: C/C++.
  • Наиболее совершенный алгоритм подбора драйверов среди аналогов.
  • Программа весит менее мегабайта и не требует никаких сторонних программ.
  • Высокое быстродействие при индексации, поиске драйвера, установке.
  • Поддержка работы с распакованными драйверами.
  • Создание снимков системы, позволяющими эмулировать чужую систему на другом ПК.
  • Предупреждения о возможных попытках вирусов заразить флешку с программой.
  • Возможность обновить программу и драйверпаки через интернет(технология торрентов).
  • Щелчок на кнопке драйвера устанавливает/снимает галку.
  • Кнопка “Установить” запускает установку выбранных драйверов.
  • Щелчок на кнопке драйвера при удерживании Shift запускает установку данного драйвера.
  • Во время установки можно добавлять/исключать драйверы к установке.
  • Отменить установку драйвера возможно до его окончательной распаковки.
  • Щелчек на общем прогрессбаре останавливает установку.
  • Удерживание пробела при наведении на драйвер отображает таблицу со всеми альтернативными драйверами для данного устройства. Список отсортирован от самых подходящих к менее подходящим. Строка с рамкой выделяет драйвер, на который наведен указатель мыши.
  • Иконка с треугольником раскрывает полный список альтернативных драйверов для устройства.
  • Отобразить альтернативные драйверы можно также используя фильтры в режиме эксперта.
  • Удерживание Ctrl при наведении на драйвер отображает подсказку с сравнением установленного драйвера с предлагаемым к установке. Зеленым цветом подсвечиваются предпочтительные характеристики. Чем ниже оценка драйвера, тем лучше он подходит.
  • По щелчку правой кнопки над драйвером открывается контекстное меню.
  • Щелчок на панели “Информация о системе” открывает “Диспетчер устройств“.
  • Окно программы можно перетаскивать за любую его часть.
  • Прокручивать список драйверов можно нажатым колесиком мыши.
  • Программа поддерживает работу с распакованными драйверами.
  • В случае добавления/удаления устройства, программа сама обновит список драйверов.
  • При попытке записать файл autorun.inf на флешку появляется предупреждение о возможном вирусе.

Это сообщение посчитали полезным следующие участники:

Сообщения: 1158
Благодарности: 382

BadPointer , как утилита ведет себя при установке Touchpad.
Второй вопрос , почему утилита создала папки dev_db1 и dev_db2?
dev_db1 — оказалось пустой , а в dev_db2 лежат индексы

Для отключения данного рекламного блока вам необходимо зарегистрироваться или войти с учетной записью социальной сети.

Сообщения: 106
Благодарности: 33

:333 отличное начало!!

особенно нравятся эти мелочи:

Во время установки можно добавлять/исключать драйверы к установке.
Отменить установку драйвера возможно до его окончательной распаковки.

возможно ли вкратце рассказать в чем заключается отличие?

Наиболее совершенный алгоритм подбора драйверов среди аналогов.

неустановленный ASUS ATK0110 ACPI Utility почему-то не определила и обновление для NVIDIA nForce PCI System Managment

Последний раз редактировалось Smokie_BlahBlah, 27-02-2014 в 12:16 .

Сообщения: 593
Благодарности: 222

Цитата Painkiller:

как утилита ведет себя при установке Touchpad. »

Программа определяет является компьютер десктопом или ноутбуком на основе наличия аккумулятора и размера экрана(наведи на панель «информация о системе»). На настольных ПК драйверы для татчпадов не предлагаются.

Цитата Painkiller:

Второй вопрос , почему утилита создала папки dev_db1 и dev_db2?
dev_db1 — оказалось пустой , а в dev_db2 лежат индексы »

dev_db1 — папка для индексов в человекочитаемом формате, который можно открыть любым редактором.
Программа может создать эти файлы при запуске с ключами

SDI_R4.exe -reindex -index_hr

Цитата Smokie_BlahBlah:

возможно ли вкратце рассказать в чем заключается отличие? »

Позже я более подробно сравню с DPS И DIA.
Если коротко, это учет пустых секций в inf файлах, подбор оптимального драйвера по всем драйверпакам(а не просто лучший драйвер в каждом драйверпаке), учет подписей. Я раньше работал над DPS, и изначально
Snappy Driver Installer разрабатывался как переписывание DPS с нуля с устранением тех хронических проблем, из-за которых мне пришлось ввести систему маркеров в качестве временного решения проблем подбора драйвера. И вот эти проблемы наконец решены в Snappy Driver Installer.

Цитата Smokie_BlahBlah:

неустановленный ASUS ATK0110 ACPI Utility почему-то не определила в DP_Vendor и обновление для NVIDIA nForce PCI System Managment (DP_Chipset) »

Выложи лог и снимок со своей системы(snp файл), чтобы я смог посмотреть что там не так. Это находится в режим эксперта->открыть логи.

Последний раз редактировалось BadPointer, 09-02-2014 в 15:52 .

Сообщения: 1159
Благодарности: 540

Smokie_BlahBlah, думаю понравиться еще больше если сказать что программа само достаточна не нуждается в использовании дополнительных библиотеках , дот нетов и пр , не нуждается в костылях типо: девкона , дп инсталлера и даже в семь зип все делает сама !
сам алгоритм определения драйверов подобен анализу виндовс и настолько универсален что даже при наличии в будущем win 9 или win 10 скорее всего не потребует переписывания кода парсинга

важно:
вы должны знать, в случае если программа что то делает не так по вашему мнению с установкой обновлением драйверов в папке logs храниться необходимая информация , выглядит вот так:
2014_02_09__15_03_10__MYCOMP_log.txt
2014_02_09__15_03_10__MYCOMP_state.snp
Кликни «Режим эксперта->открыть логи» и выложи эти файлы (при необходимости)

если у программы происходят какие то непредвиденные сбои в самой работе (вылеты) используйте запуск через батник : SDI_safemode.bat в этом случае включается защищенный режим (некое подобие safemode для виндовс)

——-
я нерусский потому пишу с ошибками!

Это сообщение посчитали полезным следующие участники:

Сообщения: 106
Благодарности: 33

quarq, ну самодостаточность да, я заметил. а еще молниеносное индексирование! в общем надежды у меня на эту прогу большие)

Последний раз редактировалось Smokie_BlahBlah, 09-02-2014 в 21:19 .

Сообщения: 593
Благодарности: 222

а еще молниеносное индексирование! в общем надежды у меня на эту прогу большие

Snappy Driver Installer индексирует все драйверпаки быстрее чем DIA подбирает драйверы с уже созданными индексами, и это еще далеко не предел возможностей по оптимизации скорости индексации.

Чтобы отобразился NVIDIA nForce PCI System Management нужно снять галку «Только оптимальные». В драйверпаках есть более новые версии драйверов, но они не предлагаются поскольку подпись драйвера не действительна(выделено красным) для Windows 8.1, как ты можешь видеть при удерживании Ctrl над драйвером.

Устройство ASUS ATK0110 ACPI Utility работает нормально и установленный драйвер является самым новым. Нужно установить галку «Неизвестные» чтобы увидеть его.

DeviceInfo Name: ATK0110 ACPI UTILITY Status: Driver is running. Manufacturer: ATK HWID_reg \0040 Class: Location: ConfigFlags: 0 Capabilities: 48 DriverInfo Name: ATK0110 ACPI UTILITY Provider: ATK Date: 11-5-2012 Version: 1043.6.0.0 HWID: acpi\atk0110 inf: C:\Windows\inf\oem2.inf,DriverInstall Score: 00FF0001 0001 1 | 00FF0001 | 16.07.2009 | 100 | 2 | 82 | atk.ntamd64 | drivers\DP_Vendor_14022.7z | 1B9FB| Asus\ATK\FORCED\NTx64\0110_1043.6.0.0\AsAcpi.inf | ATK | 1043.6.0.0 | ACPI\ATK0110 | ATK0110 ACPI UTILITY 1 | 00FF0001 | 16.07.2009 | 1 | 0 | 82 | atk | drivers\DP_Vendor_14022.7z | 1A733| Asus\ATK\FORCED\NTx86\0110_1043.5.0.0\AsAcpi.inf | ATK | 1043.5.0.0 | ACPI\ATK0110 | ATK0110 ACPI UTILITY 1 | 00FF0001 | 21.01.2008 | 100 | 0 | 82 | atk.ntamd64 | drivers\DP_Vendor_14022.7z | 1B9E1| Asus\ATK\FORCED\5x64\0110_1043.5.0.0\AsAcpi.inf | ATK | 1043.5.0.0 | ACPI\ATK0110 | ATK0110 ACPI UTILITY 1 | 00FF0001 | 19.10.2006 | 100 | 0 | 82 | atk.ntamd64 | drivers\DP_Vendor_14022.7z | 1B9EA| Asus\ATK\FORCED\6x64\0110_1043.4.0.0\AsAcpi.inf | ATK | 1043.4.0.0 | ACPI\ATK0110 | ATK0110 ACPI UTILITY 1 | 00FF0001 | 11.10.2006 | 1 | 0 | 82 | atk | drivers\DP_Vendor_14022.7z | 1A70F| Asus\ATK\FORCED\6x86\0110_1043.1.0.0\AsAcpi.inf | ATK | 1043.1.0.0 | ACPI\ATK0110 | ATK0110 ACPI UTILITY 1 | 00FF0001 | 13.08.2004 | 1 | 0 | 82 | atk | drivers\DP_Vendor_14022.7z | 1A761| Asus\ATK\FORCED\5x86\0110_1043.2.15.37\Atk2000.inf | ATK | 1043.2.15.37 | ACPI\ATK0110 | ATK0110 ACPI UTILITY 0 | 00FF0001 | 16.07.2009 | 1 | 2 | 8A | atk | drivers\DP_Vendor_14022.7z | 1B9FB| Asus\ATK\FORCED\NTx64\0110_1043.6.0.0\AsAcpi.inf | ATK | 1043.6.0.0 | ACPI\ATK0110 | ATK0110 ACPI UTILITY 0 | 00FF0001 | 21.01.2008 | 1 | 0 | 8A | atk | drivers\DP_Vendor_14022.7z | 1B9E1| Asus\ATK\FORCED\5x64\0110_1043.5.0.0\AsAcpi.inf | ATK | 1043.5.0.0 | ACPI\ATK0110 | ATK0110 ACPI UTILITY 0 | 00FF0001 | 19.10.2006 | 1 | 0 | 8A | atk | drivers\DP_Vendor_14022.7z | 1B9EA| Asus\ATK\FORCED\6x64\0110_1043.4.0.0\AsAcpi.inf | ATK | 1043.4.0.0 | ACPI\ATK0110 | ATK0110 ACPI UTILITY

Snappy Driver Installer (Page 2 of 3)

Not a hijack, this is the right place to ask.
Am i correct that SDI can leverage DriverPacks.net DriverPacks?

edit: If not, i would humbly request the choice of driver packs, or direction as to where to place them. Thank you.

nlinecomputers wrote:

@ BadPointer :

«I have SPI version 02 R142. It is prompting me to update driverpacks. 15 of them and the index. When I try and do so, nothing happens. The logs imply that this is done via bittorrent? If that is so it is likely that my router will be blocking that.

What ports do I need to open on my router to get this to properly update. I can’t find any information that discusses that.»

quoted from previous post

Last edited by TechDud (2014-12-04 17:20:41)

http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/5NQ1BpqvDa_0vDwtHeoZCcSJjOVNuvMXSp4i7SE7DQA/perpetual:forever/userbar/moderator-1.png

Forum Rules & Guidelines HWID’s tool Unknown Devices (Win7-max) LatencyMon — NT6.x
MemTest86+ Video Memory Stress Test D-P-C Driver Latency Tester (Win7-max)

27 Reply by BadPointer 2014-12-09 05:06:58

  • BadPointer
  • Snappy Driver Installer(SDI) Dev
  • Offline
  • Registered: 2009-07-17
  • Posts: 66
Re: Snappy Driver Installer

nlinecomputers wrote:

First post on this forum or about this topic. Not sure if it needs it’s own topic. If so my apologies for the hijack.

I have SPI version 02 R142. It is prompting me to update driverpacks. 15 of them and the index. When I try and do so, nothing happens. The logs imply that this is done via bittorrent? If that is so it is likely that my router will be blocking that.

What ports do I need to open on my router to get this to properly update. I can’t find any information that discusses that.

With thanks,
Nathan Williams
N-Line Computers

The port is 50171.

TechDud wrote:

Am i correct that SDI can leverage DriverPacks.net DriverPacks?

edit: If not, i would humbly request the choice of driver packs, or direction as to where to place them. Thank you.

SDI should work with driverpacks from DriverPacks.net just fine. You need to drop them inside the folder «Drivers».

28 Reply by nlinecomputers 2014-12-09 05:13:17

Re: Snappy Driver Installer

Thanks. That got it rolling for me. You should include that in your documentation. Most routers block bittorrent traffic and that has to be manually set up as a port forward. I’m sure others will question it.

29 Reply by symbios24 2014-12-30 07:17:48

Re: Snappy Driver Installer

very good program outperfomed the driverpacks solution fast and reliable.

30 Reply by Stoner 2015-02-01 02:22:07

  • Stoner
  • DriverPacks newbie and Hero of the day 12/15/08
  • Offline
  • From: England
  • Registered: 2008-07-09
  • Posts: 90
Re: Snappy Driver Installer

I have been using this now for about 2 months and to say it is superb would be an understatement! Thank you soooooo much for taking the time to create this wonderful piece of software and of course to all the folks who update the driver packs!

31 Reply by OverFlow 2015-02-01 17:13:59

  • OverFlow
  • DriverPacks Administrator & BASE Developer
  • Offline
  • From: Cincinnati
  • Registered: 2006-12-02
  • Posts: 6,729
Re: Snappy Driver Installer

Always nice to see one of our veterans give a big thumbs up.

http://driverpacks.net/userbar/admin-1.png

DP BartPE Tutorial DP_BASE Tutorial HWID’s Tool Read BEFORE you post UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.

32 Reply by symbios24 2015-02-01 21:00:21

Re: Snappy Driver Installer

can i slipstream this to windows setup?

Last edited by symbios24 (2015-02-03 19:42:28)

33 Reply by hardware_failure 2015-02-08 08:00:54

Re: Snappy Driver Installer

Just wow! This is FANTASTIC. How did I just now find out about SDI?

Its so fast.. so easy.. ability to update and snapshot.. As far at I can tell, so far garbage free. Obviously the «meat» is in the driver packs but I have never seen a tool this awesome.

The way that its organized and can access unpacked drivers or driver packs is just brilliant and so smooth
Running from a central network location (and always being updated).. excellent
Ability of silently running from a login script or pushing with gpo.. stellar
Ability of silently running with a windows automated install. absolutely amazing (I have yet to do this, will try next image I make)

I would bet there has to be millions of IT people (and some general geeks too) out there that would fall out of their chair if they new that this package existed and saw it in action. (SDI + driver packs)

This is going to forever change how I deploy systems.

Kudos to you BadPointer (and obviously to the driver packs too)

symbios24 wrote:

can i slipstream this to windows setup?

RyperX shared doing exactly this on page 1.

34 Reply by OverFlow 2015-02-08 19:39:35

  • OverFlow
  • DriverPacks Administrator & BASE Developer
  • Offline
  • From: Cincinnati
  • Registered: 2006-12-02
  • Posts: 6,729
Re: Snappy Driver Installer

Welcome to DriverPacks hardware_failure,
So. was that a vote for, or against SDI? . LOL

Thanks for taking the time to stop by, we do value the feedback.

Have you personally tested all of the features you listed above? That is not made clear except on installs which you admit is not yet tested.

It is more helpful to everyone if you can report on what you tested personally. Including an outline report of how you achieved success would definitely benefit others.

BP has been around a long time and I am cautiously optomistic about SDI.

Keep the feedback flowing people!

http://driverpacks.net/userbar/admin-1.png

DP BartPE Tutorial DP_BASE Tutorial HWID’s Tool Read BEFORE you post UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.

35 Reply by raimon93 2015-02-15 02:28:47

Re: Snappy Driver Installer

after some time using Snappy Driver as auto installer for our clients, some employee start aking me why it became slower after some updates,

We using a SMB share and its running on a Dell poweredge 2950 with some other stuff on it.

could it be possible that the decompress takes a bit and meby its better to let it be unpacked so clients could read it faster?

36 Reply by BadPointer 2015-02-15 23:31:12

  • BadPointer
  • Snappy Driver Installer(SDI) Dev
  • Offline
  • Registered: 2009-07-17
  • Posts: 66
Re: Snappy Driver Installer

Are you talking about the long extraction times?

It must have to do with the fact that driverpacks are growning in size.

I plan to improve extraction times, eventually. It involves creating tools that optimize driverpacks for SDI by repacking them in a special way. It will result in at least fourfold decrease of extraction time and also reduce the size of driverpacks. Even when it’s fully automatized it would still take many hours to process driverpacks each time they are updated, so I might have to get a SSD to speed up things.

In the meantime, you can repack biggest driverpacks with the solid block size set to 256 MB.

37 Reply by GMAC 2015-03-14 08:05:46

Re: Snappy Driver Installer

I registered to thank you for taking the time to create such a brilliant tool. Simply put, it kicks ass.

Do you accept any form of donation? I would love to support this project in a more tangible way.

38 Reply by electropica 2015-04-13 18:34:39

Re: Snappy Driver Installer

Hello,
I have worked to move from SAD to SDI but I have some questions.

I want to use a network drive mount on Z to install driver and if the server can be reach, i want to use a local directory that will contain only the important drivers (LAN, WLAN and CHIPSET).

I have write this script that i want to use from he sysprep and it looks to works.

@echo off PING fogserver IF %ERRORLEVEL% EQU 1 GOTO local NET USE z: \\fogserver\Drivers Z: FOR /F "tokens=*" %%G IN ('DIR /B *.exe') do (%%G -autoinstall -autoclose -license "-finish_cmd:%systemroot%\System32\shutdown -r -t 15") NET USE /delete /yes Z: goto end :local FOR /F "tokens=*" %%G IN ('DIR /B *.exe') do (%%G -autoinstall -autoclose -license "-finish_cmd:shutdown -r -t 15") :end

any advise to make it better ?

My second question is, it looks like that SDI unpack all drivers from a packs that contain needed driver, is this normal ?

Last edited by electropica (2015-04-13 18:36:04)

39 Reply by OverFlow 2015-04-13 20:25:40

  • OverFlow
  • DriverPacks Administrator & BASE Developer
  • Offline
  • From: Cincinnati
  • Registered: 2006-12-02
  • Posts: 6,729
Re: Snappy Driver Installer

answer to second question.

DriverPacks are solid archives. Meaning that the entire stream must be extracted from start to finish. However if you are only extracting part of the archive (Let’s say one driver) there is a huge pick up in not copying the unneeded files, they are «skipped». So even though the entire pack is processed only specified files are written / output during the process. Skipping is quicker than copying, go figure.

http://driverpacks.net/userbar/admin-1.png

DP BartPE Tutorial DP_BASE Tutorial HWID’s Tool Read BEFORE you post UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.

40 Reply by electropica 2015-04-27 17:48:44

Re: Snappy Driver Installer

If SDI, running from the network, install or update network driver, will it crash or will it handle the temporay lost of connection ?

I have review my script to this to have a debug command lline windows and install network driver from local SDI if needed for the net use.

start cmd /k SET curdir=%~dp0 FOR /F "tokens=*" %%G IN ('DIR /B %curdir%*.exe') do (start wait %curdir%%%G -autoinstall -autoclose -license) NET USE z: \\fogserver\Drivers Z: FOR /F "tokens=*" %%G IN ('DIR /B *.exe') do (%%G -autoinstall -autoclose -license) C: NET USE /delete /yes Z:

Last edited by electropica (2015-04-28 20:01:14)

41 Reply by SuprSurfr 2015-05-05 01:44:08

Re: Snappy Driver Installer

Is there a way to auto install Unsigned Drivers?

42 Reply by gmk1212 2015-05-05 14:05:15

Re: Snappy Driver Installer

43 Reply by nadeem Behwar 2015-05-15 22:05:15

Re: Snappy Driver Installer

i was facing some issues with my hardware drivers and search from google and download the SDI from the
http://softlay.net/drivers/best-driver-updaters.html it downloaded and working like charm thanks

Last edited by nadeem Behwar (2016-10-22 18:31:11)

44 Reply by nadeem Behwar 2015-05-18 20:16:38

Re: Snappy Driver Installer

gmk1212 wrote:

Hi gmk you can download latest version of SNAPPY DRIVER INSTALLER FROM HERE. i HAVE DOWNLOADED IT WORKS LIKE CHARM
http://softlay.net/drivers/snappy-drive … -r199.html

45 Reply by SuprSurfr 2015-05-22 02:46:21

Re: Snappy Driver Installer

Does anyone know how I can get it to install unsigned drivers without prompting?

46 Reply by electropica 2015-06-18 19:42:37

Re: Snappy Driver Installer

SuprSurfr wrote:

Does anyone know how I can get it to install unsigned drivers without prompting?

I used AutoIt to click on «do not install» when i run a loop on a pnputil command.
As i use French OS, as it’s maybe not the same window and as you want to accept them,
I’m not sure if this will help a lot without editing the code but you have a start.

While 1 if WinActive("C:\windows\system32\cmd.exe") = 0 then if Winactive("Sécurité de Windows") = 0 Then ;use the au3info tool to check the actual name of the window Winactivate("Sécurité de Windows") Endif ControlClick("Sécurité de Windows","","[TEXT:Ne pas installer ce pilote]") sleep(2000) Else Exit EndIf Wend

Last edited by electropica (2015-06-18 19:45:05)

47 Reply by cheche 2015-07-23 10:48:34

Re: Snappy Driver Installer

Hi,
you have been commented out by the sourceforge twitter https://twitter.com/sourceforge/status/ … 7555048452

It would be nice if those users could report back to missing drivers on driverpacks.net

48 Reply by techsup1983 2015-08-20 08:47:24

Re: Snappy Driver Installer

Hello. I have recently got this working from a USB. The OS installs sliently using unattend.xml from a fully updated gold image.
I’m by no means a master of this, or scripting, but through trial and error I got it working. I tested all the examples in the previous posts and none seemed to work. This is the only thing that worked for me.
For the rest of the people wanting to do do what i’ve done. This is how I did it.
Hopefully this may save someone some time.
I used this for a Win7x64 based image.

Copied all the source files and drivers to:
.\sources\$oem$\$1\Setup\SDI_R317

——SetupComplete.cmd
@echo off
del /Q /F c:\windows\system32\sysprep\unattend.xml
del /Q /F c:\windows\panther\unattend.xml
pushd %systemdrive%\Setup\SDI_R317\
DP_Install_tool.cmd
exit

——DP_Install_tool.cmd
%systemdrive%\Setup\SDI_R317\SDI_x64_R317.exe -autoinstall -autoclose -license «-finishrb_cmd:Shutdown.exe -r -t 15»
pause
RD C:\Setup /S /Q

«-finish_cmd:RD C:\Setup /S /Q»
«-finishrb_cmd:Shutdown.exe -r -t 15»
«-finish_upd_cmd:RD C:\Setup /S /Q»

Last edited by techsup1983 (2015-08-20 09:21:26)

49 Reply by Flow 2015-12-05 07:09:37

Re: Snappy Driver Installer

Hello all, I am a bit confused, this script from electropica works great when running manually, the whole SDI folder is on a smb share and kind of wonder, if I want to integrate this in an unattend setup, shouldnt I just call this .bat file or use the whole _Drivers.bat and SDI.bat files? I prefer this method as it automagically launch the proper .exe without having to name it, so when an update changes the name i.e. SDI_x64_423.exe it still works!

If the proper way of doing this in unattend has to be using the SDI.bat and _Drivers.bat, how would I then name the set wdir= option for smb. ? It seems to me like both ways would work but prefer to ask.

I do not have much experience with the unattend.xml, I guess I could just add whats needed to mine using what’s provided on here?

electropica wrote:

If SDI, running from the network, install or update network driver, will it crash or will it handle the temporay lost of connection ?

I have review my script to this to have a debug command lline windows and install network driver from local SDI if needed for the net use.

start cmd /k SET curdir=%~dp0 FOR /F "tokens=*" %%G IN ('DIR /B %curdir%*.exe') do (start wait %curdir%%%G -autoinstall -autoclose -license) NET USE z: \\fogserver\Drivers Z: FOR /F "tokens=*" %%G IN ('DIR /B *.exe') do (%%G -autoinstall -autoclose -license) C: NET USE /delete /yes Z:

Last edited by Flow (2015-12-09 00:42:20)

Snappy Driver Installer

If something goes wrong, you can go back to the latest restore point.
If installed driver doesn’t work properly, you try installing another from dropdown lists. It would be nice if you let me know when you have to pick
the second/third best match, so that I could see if can do something to improve driver ranking.

SDI creates log files in the folder named «logs». You should be able to find the relevant log file, granted that you recall when it happened.

BadPointer
Active Member

Reaction score 90
My real question is, if I just keep the torrent seeded, am I automatically going to get updates?

Each time you run SDI, it downloads http://driveroff.net/SDI_Update.torrent and checks for new binaries/driverpacks. SDI can download them with an internal torrent client but it stops seeding as soon as it’s done downloading.

If you want to help other people download faster, you can seed the current torrent via uTorrent or any other client. There’s no point in seeding old torrent once new is uploaded at http://driveroff.net/SDI_Update.torrent. In order to populate new torrent, seeders are given the following instruction:

  1. Delete the old .torrent + Data.
  2. Download the updated torrent and start downloading.
  3. .
  4. PROFIT.
  1. Delete the old .torrent while keeping Data.
  2. Download the updated torrent.
  3. Uncheck “Start downloading” or stop it if it’s already started.
  4. Right click on the torrent in your torrent client and choose “Force re-check”.
  5. Start downloading.
  6. Clear readonly attribute on files in the Drivers folder.
  7. Run del_old_driverpacks.bat.
NJW
Well-Known Member

Reaction score 1,009 Location Deux-Sèvres, France
Right click on the torrent in your torrent client and choose “Force re-check”.

In Transmission, there is no explicit ‘Force recheck’ option.
4. Right-click and select ‘Verify Local Data’. When the check is complete:
5. Right-click again and select ‘Start Now’.

LifelineIT
Member

Reaction score 24 Location Fairmont, WV

Thanks. In this particular case system restore wasn’t an option, and no big deal. The system has since been reimaged but it was a Dell Inspiron 7450, I suspect it was the USB3x drivers in particular that caused the issue.

cbsnyder87
Member

Reaction score 12 Location Helendale, CA
Is there ever a need to unpack the compressed drivers, or does SDI do this itself?

bertie40
Well-Known Member

Reaction score 415 Location Leeds, UK
Is there ever a need to unpack the compressed drivers, or does SDI do this itself?

I’m sure you can unpack the individual drivers if you want, but no. SDI performs the entire operation, inc unpacking, itself.

With respect, have you actually tried SDI ?

glennd
Well-Known Member

Reaction score 2,526 Location South West Victoria Australia

I used it yesterday. Customer brought in a partially functioning laptop. I went to device manager and noticed some devices missing drivers. I immediately plugged in SDI, it picked the missing drivers and installed them. It was all over in about 5 minutes. Almost magical to watch. The sad part was I don’t think the customer understood the significance of what just happened.

glennd
Well-Known Member

Reaction score 2,526 Location South West Victoria Australia

  • Delete the old .torrent + Data.
  • Download the updated torrent and start downloading.
  • .
  • PROFIT.

me thinks you spent too much time on slashdot?

cbsnyder87
Member

Reaction score 12 Location Helendale, CA

I’m sure you can unpack the individual drivers if you want, but no. SDI performs the entire operation, inc unpacking, itself.

With respect, have you actually tried SDI ?

I had just used it on my own machine right before writing my question. It functioned flawlessly. but I was baffled because I’ve never seen a program run off of compressed files. So my first inclination was, «Wait a minute. I was connected to the internet. Did this thing just download the drivers and install them, or did it unpack the files already in the folder?» My next question was, «What if I am not connected to the internet when I use SDI? Would I need to unpack all of these files to be used in that case?»

So, rather than unpacking 8 Gigs of data. which after 25 minutes was only at 6% and 27 Gigs, I decided to just ask somebody.

BadPointer
Active Member

Reaction score 90

SDI doesn’t download drivers from the Internet. It downloads driverpacks. Once you have driverpacks, you don’t need the Internet.

Each driver is installed in two steps:
Stage 1: Extracting. You can see the progressbar going from 0% to 90%.
Stage 2: Installing. It might appear installation stuck on 90% but the driver is being installed. There’s just no way to tell how much it progressed and it just jumps from 90% to 100% as soon as driver installed.

I was baffled because I’ve never seen a program run off of compressed files.

Actually a lot of programs work with compressed data. For example videogames often have their resources packed. However sometimes it’s faster to read uncompressed data than to read compressed data and unpack it the fly. It depends on the hardware so it’s difficult to optimize for every possible case. Most PCs at my workplace are somewhat old(Pentium 4, Radeon x1600, 1 GB RAM, 120 GB) so I have a great opportunity to optimize SDI for worst cases. SDI works even on Windows 2000 even though it takes an additional effort to keep support for this OS. Thankfully I don’t have to deal with PCs with 256MB RAM anymore because they tended to run out of virtual memory during extracting.

Driverpacks are optimized for minimal size. It resulted in the loss of random access to the files, so SDI has to treat them like magnetic tapes. In order to reach a file at the end of archive, it has to extract all files preceding it and discard unwanted files without writing on disk. SDI is intelligent enough to extract all needed files in a single pass. This is why SDI sometimes skips the first state(extracting) for some drivers.
The point is you don’t have to worry about it, SDI does all the heavy lifting in the most efficient way possible.

cbsnyder87
Member

Reaction score 12 Location Helendale, CA

SDI doesn’t download drivers from the Internet. It downloads driverpacks. Once you have driverpacks, you don’t need the Internet.

Each driver is installed in two steps:
Stage 1: Extracting. You can see the progressbar going from 0% to 90%.
Stage 2: Installing. It might appear installation stuck on 90% but the driver is being installed. There’s just no way to tell how much it progressed and it just jumps from 90% to 100% as soon as driver installed.

Actually a lot of programs work with compressed data. For example videogames often have their resources packed. However sometimes it’s faster to read uncompressed data than to read compressed data and unpack it the fly. It depends on the hardware so it’s difficult to optimize for every possible case. Most PCs at my workplace are somewhat old(Pentium 4, Radeon x1600, 1 GB RAM, 120 GB) so I have a great opportunity to optimize SDI for worst cases. SDI works even on Windows 2000 even though it takes an additional effort to keep support for this OS. Thankfully I don’t have to deal with PCs with 256MB RAM anymore because they tended to run out of virtual memory during extracting.

Driverpacks are optimized for minimal size. It resulted in the loss of random access to the files, so SDI has to treat them like magnetic tapes. In order to reach a file at the end of archive, it has to extract all files preceding it and discard unwanted files without writing on disk. SDI is intelligent enough to extract all needed files in a single pass. This is why SDI sometimes skips the first state(extracting) for some drivers.
The point is you don’t have to worry about it, SDI does all the heavy lifting in the most efficient way possible.

This might be nearly the most awesome tech tool I’ve ever seen, seconded only to Sysinternal’s suite of tools.

(I had no idea video games unpacked compressed files on the fly. Can you tell I’m not a programmer? lol)

A severe bug

Hey bro, this software is amazing and I’ve been using it for years. It used to work fine, but about 1 year ago it sometimes began to raise std::bad_cast exception (see attachments below) and crushed when initiating. Then in 2022 the problem deteriorated and happened every time. I’ve googled this error but found nothing. I also tried switching to Snappy Driver Installer (SDI-RUS) and faced same issue. Windows version
Windows 8.1 64-bit
Product version
1.12.7.747 Steps to reproduce
1. Extract SDIO_1.12.7.747.zip
2. Open SDIO_x64_R747.exe
3. Accept ToS
4. Download any driverpacks or index
5. Error occurs
The expected output
The program start to download selected driverpacks after step 4
The actual output
See ‘std::bad_cast’ exception window Additional info
I currently live in China. The network here is very slow. In my opinion it’s network and ISP that cause this bug. If I run SDIO offline the error won’t occur. Also if I change Wi-Fi to mobile hotspot (they belong to different ISPs), the bug will be gone too, but I don’t have enough mobile traffic to download the driverpacks.
I’m using a proxy to boost surfing experience. I’m thinking that if SDIO can support connecting to a proxy, the bug will be solved too. Please fix the issue asap, thanks ��

Attachments:

21 August, 2022 at 12:35 pm #5464

Glenn

It feels like it’s going down a path in the torrent code that it doesn’t normally go. I’ll look into it this week.

Добавить комментарий

Ваш адрес email не будет опубликован. Обязательные поля помечены *