BadPointer
Active Member
- Reaction score
- 90
I'm not aware of these problems. I suggest trying to install alternative drivers from the dropdown menu till you find the best fit, put aside log files and submit a bug report.
Snappy Driver Installer
- Thread starter JustInspired
- Start date
Bingo, thanks for that.
Is there a way in the sdi.cfg to use current directory for drp_dir:? I tried %~dp0 and * didn't work. This would help with running it with different driver folders. If not I'll just make sure to put them in a "drivers" folder.
Last edited:
BadPointer
Active Member
- Reaction score
- 90
Currently only the -log_dir switch supports environment variables.
For example: -log_dir:%WINDIR%\Logs\SDILog
Altster
Well-Known Member
- Reaction score
- 1,394
- Location
- Indianapolis, Indiana, USA
I'm curious about all of this - why are you trying to run this silently?
I just plug in my USB stick with the current (or almost current) updates for SDI, make my selections and away it goes.
If need be I have another copy of SDI on another USB stick so I can do more than 1 at a time. I don't run it from a network share - not saying you can't but I don't. I don't have a huge amount of units that need to done w/ SDI. If it comes down to having a great deal of units I'll get one all updated (including O/S updates) then make an image of it then deploy it - all with Clonezilla for image manipulation.
I just plug in my USB stick with the current (or almost current) updates for SDI, make my selections and away it goes.
If need be I have another copy of SDI on another USB stick so I can do more than 1 at a time. I don't run it from a network share - not saying you can't but I don't. I don't have a huge amount of units that need to done w/ SDI. If it comes down to having a great deal of units I'll get one all updated (including O/S updates) then make an image of it then deploy it - all with Clonezilla for image manipulation.
I am trying to use SDI with setupcomplete.cmd, which runs after sysprepping a computer to install drivers. For the last few years I have been using DPINST, which has become less reliable for installing the correct drivers in Windows 10. I have been successful at using SDI in this context but not always 100%. It has to be silent because it is run in the background before the first login prompt. If I had to run SDI manually everytime I re-image 100+ machines at a time that would be a nightmare and I would just stick to the hit or miss DPINST.
Hmmm...... SDI failed for me yesterday for the first time. Did a Win10 N&P on a Dell laptop. After confirming activation I ran SDI and it replaced the mouse and touch pad drivers with something that didn't work. Can't do much of anything without a working mouse/touch pad. Did another N & P on that machine and unchecked the mouse drivers this time in SDI and all went well.
River Valley Computer
Well-Known Member
- Reaction score
- 782
- Location
- Russellville, AR
Would an external USB mouse work?
Larry Sabo
Well-Known Member
- Reaction score
- 3,325
- Location
- Ottawa, Canada
That's why I do a restore point before SDI updates; I've had the odd update go wrong, too, but it's rare.
Understood, but that's built into SDI and for some reason also failed..... Like I said, It's been the only time I have had an issue.
Larry Sabo
Well-Known Member
- Reaction score
- 3,325
- Location
- Ottawa, Canada
Oh! I'd better check that from now on! Thanks for the heads-up.
Seems it does get it wrong sometimes. I've had SDI install the wrong drivers for the USB 3.0 host. Removed driver and Windows auto-installed an MS driver and all was good.
EDIT: This was observed on my personal desktop. I just tried SDI again and it seems this may have been fixed as it doesn't recommend this driver anymore.
EDIT2: I was wrong, it is still there. Submitted a ticket.
EDIT: This was observed on my personal desktop. I just tried SDI again and it seems this may have been fixed as it doesn't recommend this driver anymore.
EDIT2: I was wrong, it is still there. Submitted a ticket.
Last edited:
BadPointer
Active Member
- Reaction score
- 90
The accuracy of picking the right drivers depends on users reporting problems and proposing solutions. This is why it's important to collect all relevant information about the problem(log files) and verify the proposed solution(which drivers should've been installed?) before returning the PC to the client.
nlinecomputers
Well-Known Member
- Reaction score
- 8,566
- Location
- Midland TX
New installs of Windows 10 have System Restore TURNED OFF! You have to actively turn it on. SDI does not do this nor does it report that it can't create a system restore point.
Ahhh - that explains it. Thanks @nlinecomputers . Actually SDI does report a problem in that the System Restore indicator bar in SDI does not turn green.
nlinecomputers
Well-Known Member
- Reaction score
- 8,566
- Location
- Midland TX
Yes but it reports it after the fact. There is no halt on system restore failure that I am aware of in SDI. (Will gladly eat crow if someone can point out one if I have missed it.)
Do we know the rationale behind this? I hadn't connected it to Win10 yet as I had seen more than ever systems coming through with restore space set to zero. We check system restore settings and defrag settings on every computer that comes through. (Defrag every week? Really Microsoft? This is NTFS not FAT32. Old habits die hard. Even once a month - the minimal setting - is still a bit strong.)
A very good point. I don't want drivers installed until I have at least a restore point in place.
BadPointer
Active Member
- Reaction score
- 90
SDI doesn't halt installation but you should have enough time to cancel installation by clicking on the main progressbar before SDI completed extracting drivers from the first driverpack.
nlinecomputers
Well-Known Member
- Reaction score
- 8,566
- Location
- Midland TX
I would guess because of the prevalence of SSD drives. It is just one more thing writing to the drive. Also, such drives typically are small and SR takes up valuable real estate. And there is also tablets which can have even less space. It's defaulting to the lowest common denominator of settings.
Similar threads
