• Announcements

Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.

DriverForge v5.0! - An Automatic Driver Installer

148 posts in this topic

Is it just the image Amalux?

AFAIK but haven't fully tested; at times, dbl-clicking the .exe wouldn't produce a ui but I can't reproduce that now. Again, the only way (for others) to test this is if they have never had any earlier version installed. If installing 4.3 or 4.4 they get an image in the ui, then something else is at work here. I test this by restoring my HDD to a point previous to any DF install

Edited by amalux
0

Share on other sites
Perhaps I can integrate the Hwpnp utility for PE type installs?? Does anyone have a link to this?

Ed. Never mind I found it... I hope it's ok with Paraglider...

I'm going to write my app to use this program instead. Not only does it make my program faster but it also makes it smaller. We'll see I guess.

I decide it is better to write here.

as far as i understand,

* amulux wrote things to add driver to the existing os on harddisk by using pe environment with DriverForge.

* I do things to add driver to the existing pe in the pe environment with DriverForge.

NO need to add hwpnp to your app for pe, and there can be other utilites/methods to search and add device to different "pe1 os"'s (ex: in livexp there is no hwpnp but livexp already searchs for hardware and add if needed (i am new with livexp, i dont know how yet)).

But maybe you can use hwpnp to search for undefined drivers and add only the required files to os (as an option)???

example: DriverForge extract or look in and take hwids maybe in the drivers, hwpnp search for needed drivers in the environment, Driver forge extract only the needed ones.

i still have tests/trials, i wrote my foundings in bootland 'cause i couldnt make it work with the way i use using livexp yet.

amulux:

i had no problems in using driverforge4.4 in my os, also i tried on vmware/xp32 to make first time test, and it worked immediately.

But i remembered sth, at some point driverforge4.4 didnt work once when i wanted to see the gui of it (i double click on it (3 or 5 times) but it didnt work and i didnt see it on taskmanager too), i had things to do and after a while it worked nicely, but i cant remember when/how/why, and never happened again yet.

0

Share on other sites
amulux:

i had no problems in using driverforge4.4 in my os, also i tried on vmware/xp32 to make first time test, and it worked immediately.

Did you have any previous DF install (even if 'uninstalled') when you tested 4.4? Did you see the 'header art' image in the UI? Did you get any kind of 'Security warning' - 'Run' prompt?

But i remembered sth, at some point driverforge4.4 didnt work once when i wanted to see the gui of it (i double click on it (3 or 5 times) but it didnt work and i didnt see it on taskmanager too), i had things to do and after a while it worked nicely, but i cant remember when/how/why, and never happened again yet.

Same thing happened for me but can't reproduce this behavior. All other functions of the app seem to work fine other than those mentioned above.

Edited by amalux
0

Share on other sites
Did you have any previous DF install (even if 'uninstalled') when you tested 4.4? Did you see the 'header art' image in the UI? Did you get any kind of 'Security warning' - 'Run' prompt?
But i remembered sth, at some point driverforge4.4 didnt work once when i wanted to see the gui of it (i double click on it (3 or 5 times) but it didnt work and i didnt see it on taskmanager too), i had things to do and after a while it worked nicely, but i cant remember when/how/why, and never happened again yet.

Same thing happened for me but can't reproduce this behavior. All other functions of the app seem to work fine other than those mentioned above.

no i had never used or uninstalled DF install, v44 is the first one i use.

But here is a funny thing, before posting this message, i doubleclick on driverforge.exe again and vala, it didnt open. (tried many times with double clicking DriverForge.exe)

i put it in E:\1 folder with a name DriverForge.exe, and no it didnt open.

i also observed taskmanager, in taskm, DriverForge.exe shows up for a second (or less) and disappears.

BUT

as my main purpose is using this utility in livexp/bartpe, there never a problem like that yet. (i made many many test with them), this only happens when using my os. Maybe this bugy is about 2003x64 i am using so sometimes it works in 2003x64 and sometimes it doesnt work. (ps: i know this is not for x64 environment, i double click it just to see gui)

if i find a method to reproduce the problem, i will inform.

hahaha, at the end of this message, before i press send, i double click on DriverForge.exe and it started (driverforge.ini was deleted in previous trials) .

for a solution lets say, if it doesnt start, delete driverforge.ini (maybe not necessary) and deal with other things for a while, than try to start DriverForge.exe again.

0

Share on other sites
Did you have any previous DF install (even if 'uninstalled') when you tested 4.4? Did you see the 'header art' image in the UI? Did you get any kind of 'Security warning' - 'Run' prompt?
But i remembered sth, at some point driverforge4.4 didnt work once when i wanted to see the gui of it (i double click on it (3 or 5 times) but it didnt work and i didnt see it on taskmanager too), i had things to do and after a while it worked nicely, but i cant remember when/how/why, and never happened again yet.

Same thing happened for me but can't reproduce this behavior. All other functions of the app seem to work fine other than those mentioned above.

no i had never used or uninstalled DF install, v44 is the first one i use.

But here is a funny thing, before posting this message, i doubleclick on driverforge.exe again and vala, it didnt open. (tried many times with double clicking DriverForge.exe)

i put it in E:\1 folder with a name DriverForge.exe, and no it didnt open.

i also observed taskmanager, in taskm, DriverForge.exe shows up for a second (or less) and disappears.

BUT

as my main purpose is using this utility in livexp/bartpe, there never a problem like that yet. (i made many many test with them), this only happens when using my os. Maybe this bugy is about 2003x64 i am using so sometimes it works in 2003x64 and sometimes it doesnt work. (ps: i know this is not for x64 environment, i double click it just to see gui)

if i find a method to reproduce the problem, i will inform.

hahaha, at the end of this message, before i press send, i double click on DriverForge.exe and it started (driverforge.ini was deleted in previous trials) .

for a solution lets say, if it doesnt start, delete driverforge.ini (maybe not necessary) and deal with other things for a while, than try to start DriverForge.exe again.

Every once in a while it doesn't unload itself properly from memory and I don't know why. Amalux has the link to the new test version. If you want it Lance let me know. I haven't tested in x64 or 2003 so I'm unsure as to what processes are crashing. We'll see if I can change this error checking code I have that checks to see if it's already running. That seems to have been the issue in previous versions with it not starting up again.

A couple things 7zLoc and DriverExtract are now called Compressed_Driver_Location and Uncompressed_Driver_Location, so 7zloc and Driverextract won't work in versions coming. Both can use CD\ to specify the current folder DriverForge is being run from. The Uncompressed_Driver_Location can use option None to specify no driverpacks.

The new option is to use Windows native installation process using syssetup.dll or use HWPNP. It's possible I have a HWPnP command line error. Update_All_Hardware is now Use_Windows_Method_For_Driver_Install, setting Y or N.

I'm working on v4.4.4 so I'll turn that error checking off. I've also updated the changelog.

0

Share on other sites

v4.5 is out! Check the change log for all the changes!

0

Share on other sites

Is there something that clicks automatically on 'Start' to launch the install of drivers?

0

Share on other sites
Is there something that clicks automatically on 'Start' to launch the install of drivers?

Yes in the INI file you can edit the Automatic_Install to Y under the section AutoInstall.

So basically get your settings all the way you want it via the gui and then click on the Menu "INI File" > "Save INI" then "Edit INI". Edit it the way I said and then save and close the INI file (which opened in your text editor). Close out of DriverForge and the next time you run it it will install everything with the settings you chose automatically.

Edited by kickarse
0

Share on other sites
Is there something that clicks automatically on 'Start' to launch the install of drivers?

Yes in the INI file you can edit the Automatic_Install to Y under the section AutoInstall.

So basically get your settings all the way you want it via the gui and then click on the Menu "INI File" > "Save INI" then "Edit INI". Edit it the way I said and then save and close the INI file (which opened in your text editor). Close out of DriverForge and the next time you run it it will install everything with the settings you chose automatically.

Stupid question from me, I did the change already

HWPNP and Devcon doesn't work for me so it's using the windows native mode and there I sometimes have to click 'Continue Anyway' when the driver isn't signed.

Edited by Kingskawn
0

Share on other sites
Is there something that clicks automatically on 'Start' to launch the install of drivers?

Yes in the INI file you can edit the Automatic_Install to Y under the section AutoInstall.

So basically get your settings all the way you want it via the gui and then click on the Menu "INI File" > "Save INI" then "Edit INI". Edit it the way I said and then save and close the INI file (which opened in your text editor). Close out of DriverForge and the next time you run it it will install everything with the settings you chose automatically.

Stupid question from me, I did the change already

HWPNP and Devcon doesn't work for me so it's using the windows native mode and there I sometimes have to click 'Continue Anyway' when the driver isn't signed.

Ahh... There's a program that should be running to turn that off. I guess it didn't. I'll see about that in the next version! Thanks for the update!

0

Share on other sites

Hi,

I wondered if anyone can help. I've just stumbled onto this tool and it looks quite handy. I have two questions, if this is the wrong post I apologise and if these questions have come up before please forgive me as I am a noobie:

1. Does the tool (with the driverpacks) work under Windows 2000? The reason I ask is whenever I run the tool it doesn't seem to update / install any drivers.

2. When I run the tool it extracts all the drivers and then demonstrates the follwoing error:

"Error in Syssetup.dll"

"Missing entry:UpdatePnpDeviceDrivers"

Can anyone help? Thanks in advance

error1.bmp

0

Share on other sites

Are you looking for a resolution for the problem 'Continue anyway'?

0

Share on other sites
Hi,

I wondered if anyone can help. I've just stumbled onto this tool and it looks quite handy. I have two questions, if this is the wrong post I apologise and if these questions have come up before please forgive me as I am a noobie:

1. Does the tool (with the driverpacks) work under Windows 2000? The reason I ask is whenever I run the tool it doesn't seem to update / install any drivers.

2. When I run the tool it extracts all the drivers and then demonstrates the follwoing error:

"Error in Syssetup.dll"

"Missing entry:UpdatePnpDeviceDrivers"

Can anyone help? Thanks in advance

It doesn't seem to work in 2000 in it's current state. I'm working on that. It does say in the notes that I've only tested it on XP.

Are you looking for a resolution for the problem 'Continue anyway'?

My life is busy. But I am working on it.

0

Share on other sites

Hi kickarse,

Universal path name (like \\server\drivers) No longer work in v4.5, it was working in v4.1.2

[Drivers]

Compressed_Driver_Location=\\server\drivers

Uncompressed_Driver_Location=C:\Drivers

to go roung i have to create a batch file like this within same folder

@ECHO OFF

::This should be the path to WPI on the share

SET SHARE=\\server\drivers\

::mount share to a free drive and change directory to it. After Script it finished the drive will be unmounted

PUSHD "%SHARE%"

Start /Wait \DriverInstaller\driverforge.v4.5.exe

POPD

0

Share on other sites

How can I include environment variables like %systemdrive%

I want to extract the drivers to %systemdrive%\d

0

Share on other sites
How can I include environment variables like %systemdrive%

I want to extract the drivers to %systemdrive%\d

You can do @systemdrive I believe. I'll be adding the ability to use environment variables in the next release.

0

Share on other sites

Hi

its a great tool, but there is a bug: installing drivers via "windows native" damages the normal windows driver installation. when i plug in a normal usb mouse to a usbport where it was never connected before, it doesn't find hid driver in c:\windows\inf automaticly. i have to manually put in the path.

driverforge changes default driverpath in registry [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion] "DevicePath" from "%SystemRoot%\inf" to "".

is it possible to set a relative compressed file path?

larsm

Edited by larsm
0

Share on other sites

It should set it back to what it was originally. I'll check on that.

0

Share on other sites

oh and v4.5.1 is out

0

Share on other sites

thx!!!

another problem: i created a small driverpack myself. method two and three failed, method 1 was used instead on my laptop. the drivers are ok, i am able to install them manually. other driverpacks were successfully installed.

my driverpack

lars

0

Share on other sites

hi

version 4.5.1 is not much better: now it changes "DevicePath" to:

c:\d\c\a\1;c:\d\c\a\2;c:\d\c\am\1;c:\d\c\am\2;c:\d\c\am\3;c:\d\c\am\4;c:\d\c\am\5;c:\d\c\am\6;c:\d\c\am\7;c:\d\c\at;c:\d\c\au;c:\d\c\c\a\1;c:\d\c\c\a\2;c:\d\c\c\am\1;c:\d\c\c\am\2;c:\d\c\c\am\3;c:\d\c\c\am\4;c:\d\c\c\am\5;c:\d\c\c\am\6;c:\d\c\c\am\7;c:\d\c\c\at;c:\d\c\c\au;c:\d\c\c\d;c:\d\c\c\d\win9x;c:\d\c\c\f;c:\d\c\c\h;c:\d\c\c\i\1;c:\d\c\c\i\2;c:\d\c\c\i\2k;c:\d\c\c\i\2k3;c:\d\c\c\i\xp;c:\d\c\c\in;c:\d\c\c\it;c:\d\c\c\n\c51;c:\d\c\c\n;c:\d\c\c\n\smu51;c:\d\c\c\s\2k;c:\d\c\c\s\2k3;c:\d\c\c\s;c:\d\c\c\s\xp;c:\d\c\c\sm;c:\d\c\c\t;c:\d\c\c\v\2k;c:\d\c\c\v\2k3;c:\d\c\c\v;c:\d\c\c\v\xp;c:\d\c\d;c:\d\c\d\win9x;c:\d\c\f;c:\d\c\h;c:\d\c\i\1;c:\d\c\i\2;c:\d\c\i\2k;c:\d\c\i\2k3;c:\d\c\i\xp;c:\d\c\in;c:\d\c\it;c:\d\c\n\c51;c:\d\c\n;c:\d\c\n\smu51;c:\d\c\s\2k;c:\d\c\s\2k3;c:\d\c\s;c:\d\c\s\xp;c:\d\c\sm;c:\d\c\t;c:\d\c\v\2k;c:\d\c\v\2k3;c:\d\c\v;c:\d\c\v\xp;c:\d\cpu;c:\d\cpu\cpu;c:\d\g\3a;c:\d\g\3b;c:\d\g\3c;c:\d\g\3d;c:\d\g\a1\avs;c:\d\g\a1;c:\d\g\a2;c:\d\g\a3;c:\d\g\a4;c:\d\g\a5;c:\d\g\a5\wdm;c:\d\g\a6;c:\d\g\a7;c:\d\g\a8;c:\d\g\a9;c:\d\g\aa;c:\d\g\ab;c:\d\g\as1;c:\d\g\as2;c:\d\g\g\3a;c:\d\g\g\3b;c:\d\g\g\3c;c:\d\g\g\3d;c:\d\g\g\a1\avs;c:\d\g\g\a1;c:\d\g\g\a2;c:\d\g\g\a3;c:\d\g\g\a4;c:\d\g\g\a5;c:\d\g\g\a5\wdm;c:\d\g\g\a6;c:\d\g\g\a7;c:\d\g\g\a8;c:\d\g\g\a9;c:\d\g\g\aa;c:\d\g\g\ab;c:\d\g\g\as1;c:\d\g\g\as2;c:\d\g\g\i1\hdmi;c:\d\g\g\i1;c:\d\g\g\i2;c:\d\g\g\i3;c:\d\g\g\i4;c:\d\g\g\i5;c:\d\g\g\i6;c:\d\g\g\i7;c:\d\g\g\m1;c:\d\g\g\m2;c:\d\g\g\n1;c:\d\g\g\n2;c:\d\g\g\n3;c:\d\g\g\n4;c:\d\g\g\p;c:\d\g\g\s3a;c:\d\g\g\s3b;c:\d\g\g\s3c;c:\d\g\g\s3d;c:\d\g\g\s3e;c:\d\g\g\s3f;c:\d\g\g\s3g;c:\d\g\g\s3h;c:\d\g\g\sa;c:\d\g\g\sb;c:\d\g\g\sc;c:\d\g\g\sd;c:\d\g\g\se;c:\d\g\g\t;c:\d\g\g\v;c:\d\g\g\v1;c:\d\g\g\v2;c:\d\g\g\v3;c:\d\g\g\v4;c:\d\g\g\v5;c:\d\g\g\v6;c:\d\g\g\v7;c:\d\g\g\v8;c:\d\g\g\v9;c:\d\g\g\x;c:\d\g\g\x2;c:\d\g\i1\hdmi;c:\d\g\i1;c:\d\g\i2;c:\d\g\i3;c:\d\g\i4;c:\d\g\i5;c:\d\g\i6;c:\d\g\i7;c:\d\g\m1;c:\d\g\m2;c:\d\g\n1;c:\d\g\n2;c:\d\g\n3;c:\d\g\n4;c:\d\g\p;c:\d\g\s3a;c:\d\g\s3b;c:\d\g\s3c;c:\d\g\s3d;c:\d\g\s3e;c:\d\g\s3f;c:\d\g\s3g;c:\d\g\s3h;c:\d\g\sa;c:\d\g\sb;c:\d\g\sc;c:\d\g\sd;c:\d\g\se;c:\d\g\t;c:\d\g\v;c:\d\g\v1;c:\d\g\v2;c:\d\g\v3;c:\d\g\v4;c:\d\g\v5;c:\d\g\v6;c:\d\g\v7;c:\d\g\v8;c:\d\g\v9;c:\d\g\x;c:\d\g\x2;c:\d\l\3a;c:\d\l\3b;c:\d\l\3c;c:\d\l\3d;c:\d\l\3e;c:\d\l\3f;c:\d\l\ac1;c:\d\l\ac2;c:\d\l\ac4;c:\d\l\ac5;c:\d\l\ac6;c:\d\l\ac7;c:\d\l\ad1;c:\d\l\ad2;c:\d\l\ag;c:\d\l\al;c:\d\l\am1;c:\d\l\am2;c:\d\l\am3;c:\d\l\as1;c:\d\l\as2;c:\d\l\as3;c:\d\l\as4;c:\d\l\as5;c:\d\l\as6;c:\d\l\at1;c:\d\l\at2;c:\d\l\au;c:\d\l\b1;c:\d\l\b2;c:\d\l\b3;c:\d\l\b4;c:\d\l\be1;c:\d\l\bu1;c:\d\l\bu2;c:\d\l\bu3;c:\d\l\c1;c:\d\l\co1;c:\d\l\co2;c:\d\l\co3;c:\d\l\co5;c:\d\l\d1;c:\d\l\d10;c:\d\l\d2;c:\d\l\d3;c:\d\l\d4;c:\d\l\d5;c:\d\l\d6;c:\d\l\d7;c:\d\l\d8;c:\d\l\d9;c:\d\l\da1;c:\d\l\da2;c:\d\l\da3;c:\d\l\hp;c:\d\l\i1;c:\d\l\i2;c:\d\l\i3;c:\d\l\ic1;c:\d\l\ic2;c:\d\l\l\3a;c:\d\l\l\3b;c:\d\l\l\3c;c:\d\l\l\3d;c:\d\l\l\3e;c:\d\l\l\3f;c:\d\l\l\ac1;c:\d\l\l\ac2;c:\d\l\l\ac4;c:\d\l\l\ac5;c:\d\l\l\ac6;c:\d\l\l\ac7;c:\d\l\l\ad1;c:\d\l\l\ad2;c:\d\l\l\ag;c:\d\l\l\al;c:\d\l\l\am1;c:\d\l\l\am2;c:\d\l\l\am3;c:\d\l\l\as1;c:\d\l\l\as2;c:\d\l\l\as3;c:\d\l\l\as4;c:\d\l\l\as5;c:\d\l\l\as6;c:\d\l\l\at1;c:\d\l\l\at2;c:\d\l\l\au;c:\d\l\l\b1;c:\d\l\l\b2;c:\d\l\l\b3;c:\d\l\l\b4;c:\d\l\l\be1;c:\d\l\l\bu1;c:\d\l\l\bu2;c:\d\l\l\bu3;c:\d\l\l\c1;c:\d\l\l\co1;c:\d\l\l\co2;c:\d\l\l\co3;c:\d\l\l\co5;c:\d\l\l\d1;c:\d\l\l\d10;c:\d\l\l\d2;c:\d\l\l\d3;c:\d\l\l\d4;c:\d\l\l\d5;c:\d\l\l\d6;c:\d\l\l\d7;c:\d\l\l\d8;c:\d\l\l\d9;c:\d\l\l\da1;c:\d\l\l\da2;c:\d\l\l\da3;c:\d\l\l\hp;c:\d\l\l\i1;c:\d\l\l\i2;c:\d\l\l\i3;c:\d\l\l\ic1;c:\d\l\l\ic2;c:\d\l\l\l1;c:\d\l\l\l2;c:\d\l\l\l4;c:\d\l\l\l5;c:\d\l\l\l6;c:\d\l\l\l7;c:\d\l\l\l8;c:\d\l\l\m;c:\d\l\l\mi;c:\d\l\l\mo;c:\d\l\l\n1;c:\d\l\l\n10;c:\d\l\l\n2;c:\d\l\l\n3;c:\d\l\l\n4;c:\d\l\l\n5;c:\d\l\l\n6;c:\d\l\l\n7;c:\d\l\l\n8;c:\d\l\l\n9;c:\d\l\l\nd1;c:\d\l\l\ns1;c:\d\l\l\nv3;c:\d\l\l\nv3\prenrm\win2k;c:\d\l\l\nv3\prenrm\winxp;c:\d\l\l\nv4;c:\d\l\l\nv5;c:\d\l\l\nv5a;c:\d\l\l\nv6;c:\d\l\l\nv6a;c:\d\l\l\nv7;c:\d\l\l\o1;c:\d\l\l\o2;c:\d\l\l\o3;c:\d\l\l\o4;c:\d\l\l\o5;c:\d\l\l\o6;c:\d\l\l\o7;c:\d\l\l\o8;c:\d\l\l\r1;c:\d\l\l\r2;c:\d\l\l\r3;c:\d\l\l\r4;c:\d\l\l\sb1;c:\d\l\l\sb2;c:\d\l\l\sis;c:\d\l\l\sis2;c:\d\l\l\sm1;c:\d\l\l\sm2;c:\d\l\l\sm3;c:\d\l\l\sm4;c:\d\l\l\sm6;c:\d\l\l\sm7;c:\d\l\l\sm8;c:\d\l\l\sm9;c:\d\l\l\su1;c:\d\l\l\su2;c:\d\l\l\su5;c:\d\l\l\su7;c:\d\l\l\su8;c:\d\l\l\su9;c:\d\l\l\sua;c:\d\l\l\sub;c:\d\l\l\suc;c:\d\l\l\t3;c:\d\l\l\u1;c:\d\l\l\u3;c:\d\l\l\u4;c:\d\l\l\u5;c:\d\l\l\v1;c:\d\l\l\v2;c:\d\l\l\v3;c:\d\l\l\x1;c:\d\l\l\x2;c:\d\l\l\z;c:\d\l\l1;c:\d\l\l2;c:\d\l\l4;c:\d\l\l5;c:\d\l\l6;c:\d\l\l7;c:\d\l\l8;c:\d\l\m;c:\d\l\mi;c:\d\l\mo;c:\d\l\n1;c:\d\l\n10;c:\d\l\n2;c:\d\l\n3;c:\d\l\n4;c:\d\l\n5;c:\d\l\n6;c:\d\l\n7;c:\d\l\n8;c:\d\l\n9;c:\d\l\nd1;c:\d\l\ns1;c:\d\l\nv3;c:\d\l\nv3\prenrm\win2k;c:\d\l\nv3\prenrm\winxp;c:\d\l\nv4;c:\d\l\nv5;c:\d\l\nv5a;c:\d\l\nv6;c:\d\l\nv6a;c:\d\l\nv7;c:\d\l\o1;c:\d\l\o2;c:\d\l\o3;c:\d\l\o4;c:\d\l\o5;c:\d\l\o6;c:\d\l\o7;c:\d\l\o8;c:\d\l\r1;c:\d\l\r2;c:\d\l\r3;c:\d\l\r4;c:\d\l\sb1;c:\d\l\sb2;c:\d\l\sis;c:\d\l\sis2;c:\d\l\sm1;c:\d\l\sm2;c:\d\l\sm3;c:\d\l\sm4;c:\d\l\sm6;c:\d\l\sm7;c:\d\l\sm8;c:\d\l\sm9;c:\d\l\su1;c:\d\l\su2;c:\d\l\su5;c:\d\l\su7;c:\d\l\su8;c:\d\l\su9;c:\d\l\sua;c:\d\l\sub;c:\d\l\suc;c:\d\l\t3;c:\d\l\u1;c:\d\l\u3;c:\d\l\u4;c:\d\l\u5;c:\d\l\v1;c:\d\l\v2;c:\d\l\v3;c:\d\l\x1;c:\d\l\x2;c:\d\l\z;c:\d\m\3;c:\d\m\3b;c:\d\m\a;c:\d\m\a2;c:\d\m\a3;c:\d\m\a4;c:\d\m\a5;c:\d\m\a6;c:\d\m\a7;c:\d\m\a8;c:\d\m\ad;c:\d\m\ad1;c:\d\m\ad2;c:\d\m\ad3;c:\d\m\ad4;c:\d\m\ad5;c:\d\m\ad6;c:\d\m\ad7;c:\d\m\ad8;c:\d\m\ad9;c:\d\m\ada;c:\d\m\adb;c:\d\m\am;c:\d\m\ar;c:\d\m\at;c:\d\m\au;c:\d\m\au2;c:\d\m\au3;c:\d\m\c;c:\d\m\c1;c:\d\m\c2;c:\d\m\c3;c:\d\m\d;c:\d\m\d1;c:\d\m\d2;c:\d\m\d3;c:\d\m\e;c:\d\m\h;c:\d\m\h1;c:\d\m\h10;c:\d\m\h1s;c:\d\m\h2;c:\d\m\h3\h3k;c:\d\m\h3\h3s;c:\d\m\h3;c:\d\m\h4;c:\d\m\h5;c:\d\m\h6;c:\d\m\h6s;c:\d\m\h7;c:\d\m\h7s;c:\d\m\h8;c:\d\m\h9;c:\d\m\h9s;c:\d\m\i1;c:\d\m\i2;c:\d\m\i3;c:\d\m\i6;c:\d\m\ib1;c:\d\m\ib2;c:\d\m\ib3;c:\d\m\ib4;c:\d\m\ib5;c:\d\m\ib6;c:\d\m\it;c:\d\m\j;c:\d\m\l;c:\d\m\l1;c:\d\m\l2;c:\d\m\l3;c:\d\m\l4;c:\d\m\l5;c:\d\m\l6;c:\d\m\l7;c:\d\m\m\3;c:\d\m\m\3b;c:\d\m\m\a;c:\d\m\m\a2;c:\d\m\m\a3;c:\d\m\m\a4;c:\d\m\m\a5;c:\d\m\m\a6;c:\d\m\m\a7;c:\d\m\m\a8;c:\d\m\m\ad;c:\d\m\m\ad1;c:\d\m\m\ad2;c:\d\m\m\ad3;c:\d\m\m\ad4;c:\d\m\m\ad5;c:\d\m\m\ad6;c:\d\m\m\ad7;c:\d\m\m\ad8;c:\d\m\m\ad9;c:\d\m\m\ada;c:\d\m\m\adb;c:\d\m\m\am;c:\d\m\m\ar;c:\d\m\m\at;c:\d\m\m\au;c:\d\m\m\au2;c:\d\m\m\au3;c:\d\m\m\c;c:\d\m\m\c1;c:\d\m\m\c2;c:\d\m\m\c3;c:\d\m\m\d;c:\d\m\m\d1;c:\d\m\m\d2;c:\d\m\m\d3;c:\d\m\m\e;c:\d\m\m\h;c:\d\m\m\h1;c:\d\m\m\h10;c:\d\m\m\h1s;c:\d\m\m\h2;c:\d\m\m\h3\h3k;c:\d\m\m\h3\h3s;c:\d\m\m\h3;c:\d\m\m\h4;c:\d\m\m\h5;c:\d\m\m\h6;c:\d\m\m\h6s;c:\d\m\m\h7;c:\d\m\m\h7s;c:\d\m\m\h8;c:\d\m\m\h9;c:\d\m\m\h9s;c:\d\m\m\i1;c:\d\m\m\i2;c:\d\m\m\i3;c:\d\m\m\i6;c:\d\m\m\ib1;c:\d\m\m\ib2;c:\d\m\m\ib3;c:\d\m\m\ib4;c:\d\m\m\ib5;c:\d\m\m\ib6;c:\d\m\m\it;c:\d\m\m\j;c:\d\m\m\l;c:\d\m\m\l1;c:\d\m\m\l2;c:\d\m\m\l3;c:\d\m\m\l4;c:\d\m\m\l5;c:\d\m\m\l6;c:\d\m\m\l7;c:\d\m\m\m;c:\d\m\m\m2;c:\d\m\m\m3;c:\d\m\m\m4;c:\d\m\m;c:\d\m\m\n\123;c:\d\m\m\n\4;c:\d\m\m\n\4in;c:\d\m\m\n\5;c:\d\m\m\n\6;c:\d\m\m\n\tm;c:\d\m\m\p\k;c:\d\m\m\p;c:\d\m\m\p\s;c:\d\m\m\p1;c:\d\m\m\p1k;c:\d\m\m\p1s;c:\d\m\m\p2;c:\d\m\m\p2\k;c:\d\m\m\p2s;c:\d\m\m\p3;c:\d\m\m\p4;c:\d\m\m\p4k;c:\d\m\m\p4s;c:\d\m\m\p5;c:\d\m\m\p6;c:\d\m\m\p7;c:\d\m\m\p8;c:\d\m\m\p9;c:\d\m\m\pa;c:\d\m\m\pas;c:\d\m\m\pc;c:\d\m\m\q;c:\d\m\m\q2;c:\d\m\m\q3;c:\d\m\m\q4;c:\d\m\m\s;c:\d\m\m\s2;c:\d\m\m\s2a;c:\d\m\m\s3;c:\d\m\m\s4;c:\d\m\m\s5;c:\d\m\m\s7;c:\d\m\m\s7a;c:\d\m\m\s7b;c:\d\m\m\s8;c:\d\m\m\s9;c:\d\m\m\sa;c:\d\m\m\sa2;c:\d\m\m\sb;c:\d\m\m\sb2;c:\d\m\m\sb3;c:\d\m\m\sb4;c:\d\m\m\sb5;c:\d\m\m\sc;c:\d\m\m\sc2;c:\d\m\m\sc3;c:\d\m\m\sc4;c:\d\m\m\sc5;c:\d\m\m\sis;c:\d\m\m\sis1;c:\d\m\m\sis2;c:\d\m\m\v;c:\d\m\m\v2;c:\d\m\m\v3;c:\d\m\m\v4;c:\d

lars

0

Share on other sites

That's because that's what your device path was before! If you do driverpacks twice it'll use whatever you had last. Plus, if you didn't have anything in there to begin with it'll add what you scanned as default. At least, that's what I think

So if you could test by changing that value to the default value and then run DriverPacks and see what happens that would be great!

I think I have it setup so if you aren't using compressed drivers it'll keep the location of the drivers in the registry. However, as you've shown, it's probably better to always revert to the original.

That'll be fixed in 4.5.2

Edited by kickarse
0

Share on other sites

oh, btw, v4.5.2 is out! Check the help file for INI configuration and usage changes.

0

Share on other sites

v4.5.3 is out checks the Read Me for full change log.

Added some fixes for Driver Signing Policy and fixing inf locations after running the driver installation.

Edited by kickarse
0

Share on other sites

Sorry to ask, but where can I find the source code?

0

Create an account

Register a new account