Snappy Driver Installer

[Sergio3]

Oh boy I found this thread and after many years of fighting with DRP I tried SDI and will never go back !!
The only plus side (if you want to be optimistic) is their hta software was easy to mod to remove all the included spywares by only removing a few lines of codes. But god it's so slow and it's getting worse over years.

 

[Kyle Bradley]

What an awesome tool this is! keep up the great development!

 

[pcpete]

I need to see log files from these sessions.

here they are

 

[BadPointer]

As far as I can tell the extraction was canceled by the UserBreak event as if the user removed the checkbox or clicked on the main progressbar. I think I'll extend logging of these events, so it'll be easier to investigate it when it happens next time.

Can you consistently reproduce the issue? Do you know any specific conditions/actions that might cause the issue to manifest?

 

[pcpete]

As far as I can tell the extraction was canceled by the UserBreak event as if the user removed the checkbox or clicked on the main progressbar. I think I'll extend logging of these events, so it'll be easier to investigate it when it happens next time.

Can you consistently reproduce the issue? Do you know any specific conditions/actions that might cause the issue to manifest?

I can consistently reproduce it, because it happens every time. I think it happens on all versions of Windows from Vista through 10.

Would you like for me to post more log files as they come?

 

[BadPointer]

Would you like for me to post more log files as they come?

Use this debug build
http://rghost.net/7WqF5Gl8V

 

[pcpete]

Use this debug build
http://rghost.net/7WqF5Gl8V

here are some with the debug build

 

[BadPointer]

It looks like you somehow started installation before SDI finished indexing newly downloaded driverpacks.
The extraction was canceled because the list became stale during extraction.

 

[TechLady]

Windows 7x64 with SDI 390, I'm seeing "Exception: std::bad_aloc. The program will terminate now."

 

[BadPointer]

Windows 7x64 with SDI 390, I'm seeing "Exception: std::bad_aloc. The program will terminate now."

That's an old build.
32-bit applications cannot allocate more than 2 GB of RAM per process even if Windows has plenty of RAM available. Some old 32-bit builds of SDI used to run out of available RAM but this issue has been resolved rather a long time ago and 64-bit versions of SDI were never affected.

Let me know if the problem persists in the latest build: R423. Also additional information(such as logs and a more detailed description of the problem) would be helpful.

 

[pcpete]

It looks like you somehow started installation before SDI finished indexing newly downloaded driverpacks.
The extraction was canceled because the list became stale during extraction.

i will try and send some logs from other machines. This happens to us everytime, I would think this would be happening to everyone. I can't imagine what my employees and I are doing different every single time.

 

[BadPointer]

i will try and send some logs from other machines. This happens to us everytime, I would think this would be happening to everyone. I can't imagine what my employees and I are doing different every single time.

By the way, why did you download all drivers instead of relaying on SDI to download updated driverpacks and replace the old ones?

You must be doing something unusual and that may cause SDI to malfunction. This is why it's important to figure out which steps lead to the problem. I also suggest taking screenshots.

 

[pcpete]

By the way, why did you download all drivers instead of relaying on SDI to download updated driverpacks and replace the old ones?

You must be doing something unusual and that may cause SDI to malfunction. This is why it's important to figure out which steps lead to the problem. I also suggest taking screenshots.

We may be doing it incorrectly, I would love to hear some advice. Here is our procedure
1. first we click at the top "click here to start download"
2. then we choose, "only needed for this pc"
3. then after it displays needed drivers, we choose on the left column, "select all"
4. then we choose on the left column, "install"

 

[Larry Sabo]

You didn't wait for those drivers to download first?

 

[BadPointer]

We may be doing it incorrectly, I would love to hear some advice. Here is our procedure
1. first we click at the top "click here to start download"
2. then we choose, "only needed for this pc"
3. then after it displays needed drivers, we choose on the left column, "select all"
4. then we choose on the left column, "install"

I mean If you use SDI often, it would make make more sense to keep SDI on a USB flash drive or external HDD instead of downloading driverpacks for each PC.

Downloading driverpacks as needed is more suited for users who want to install drivers on their PCs and aren't likely to be using SDI again.

Both use case are valid.

I still can't reproduce the problem. I suggest running SDI with -showconsole and record a video via your mobile phone. You can start recording just before you start installing. Try to keep both windows in the frame.

 

[Larry Sabo]

... or use MS's Problem Steps Recorder (psr) that's part of Windows.

 

[myleso]

We dont use "the only needed for this pc" option, we download everything and update it once a week on our server, that way we have everything and do not need an internet connection to update drives on customers pc's and its fast. We also have a syncback pro script on our server that will load a techs usb with the latest SDI and WSUS files if they prefer using a usb.

 

[pcpete]

we are experimenting with changing up our procedure by having all the driver packs on a flash drive instead of redownloading them per pc. Am I correct to assume it looks in the default driver folder? The reason I ask is it is not detecting any downloaded drivers and I have to go into expert mode and manually point to the default driver folder. Is this normal? I have enclosed some log files if they may help

 

[pcpete]

we are experimenting with changing up our procedure by having all the driver packs on a flash drive instead of redownloading them per pc. Am I correct to assume it looks in the default driver folder? The reason I ask is it is not detecting any downloaded drivers and I have to go into expert mode and manually point to the default driver folder. Is this normal? I have enclosed some log files if they may help

I think I see what I was doing wrong, I need to copy the cfg file also, which referenced the driver folder

 

[Xaff]

Still testing it out, but so far, I really like the tool I wish the UI was better though :/