Jump to content

Drivers Instalation in Post-Install stage (New Method)


MadBoy

Recommended Posts

  • 2 weeks later...

This is an awesome program, but I am having problems configuring it.

I have tried various combinations with the XML settings, sometimes the Found New Hardware wizard comes up asking for files like "sbsetup.exe" (Sound Blaster file) and other times, this doesn't pop up but it seems no drivers install.

I am using Bashrats driverpacks, so no drivers are compressed (all are broken down to their SYS and INF files, the driverpacks 7z files are already decompressed off the CD and onto the hard drive with the RELATIVE setting in the XML config file and a pre-prepared folder full of drivers.

I have always used the SetupCopyOemInf method because I know using all Bashrats driverpacks goes well over the 4096 character limit for the Registry.

Still, I don't think my XML file is right!

If anyone else is using Bashrats packs and this program, can you please post your XML file in code tags? It doesn't matter if your path to the driver folder is different to what I would use - my main problem is... not knowing if devices are installing, because I am testing in VMware and it always has a perfect Device Manager with no devices that need any drivers installing!

I don't know if the XML should have the "forced" setting on "Yes". I think when I set that, devices do install but I get the Found New Hardware wizard popping up... eeeeek! Can anyone post an XML configuration that they KNOW is tried and tested with Bashrats (unpacked) drivers?

Well, here is what I think is my final XML file but I still don't know if drivers are installing. I will have to try to set the time aside to do a real install on my real system and do it for real...

<?xml version="1.0" encoding="utf-8"?>
<settings>
<basic_configuration>
<choice>automatic</choice>
<drivers>
<drivers_drive>RELATIVE</drivers_drive>
<drivers_directory>\D</drivers_directory>
<drivers_packed>No</drivers_packed>
<drivers_copy>No</drivers_copy>
<drivers_copy_path></drivers_copy_path>
<drivers_copy_delete>No</drivers_copy_delete>
<options>
<method>SetupCopyOemInf</method>
<registry_path>Begin</registry_path>
<problem_ids>01,10,18,24,28,37,39</problem_ids>
<update_all>No</update_all>
<plug_and_play>
<option>Internal</option>
<time_to_wait>15</time_to_wait>
</plug_and_play>
<shutdown>
<auto_reboot_when_nessecary>No</auto_reboot_when_nessecary>
<auto_reboot_when_done>No</auto_reboot_when_done>
<auto_login>Yes</auto_login>
<notify_when_done>Yes</notify_when_done>
</shutdown>
<time_to_run>0</time_to_run>
<force_run>No</force_run>
<device_manager>No</device_manager>
</options>
</drivers>
<log>
<log_overwrite>No</log_overwrite>
<log_to_file>Yes</log_to_file>
<log_filename>hardware.log</log_filename>
<log_path>$ProgramDir</log_path>
<log_option>Simple</log_option>
</log>
<gui>
<hide_legacy_devices>No</hide_legacy_devices>
<fade_in_effect>No</fade_in_effect>
</gui>
</basic_configuration>
</settings>

i wrote the above lines in my hardware.xml and test it with my usb stick. program start but it gives an unknown error then it continues normally it finds my driver packs (unpacked) and it discovers the unknown devises and it starts to detect them and install drivers. but when it detects a device the wizard "found new hardware" starts and the program just freezes and waits me to press cancel or search. how do we turn off the "found new hardware wilard" ?

i cant post my log file because it doesnt create one.

the program is great and very usefull if u have to set drivers in many pc in short time so i neeeeeeed it to make it work

EDIT i use the Bashrats packs uncompressed from my usb stick

the hardware.exe and hardware.xml are in same folder as my drivers in my usb stick \drivers i start it from there.

my Bashrats pack drivers are decompressed in there \drivers and they are in folders for example wan,chipset,vga

what do i do wrong and why my log doesnt show anything so i can post it here :( arg i ll try again in a few minutes

Edited by herc2k
Link to comment
Share on other sites

It would be easier if you explained the error? ;) Maybe post a screen shot? The Wizard comes up because it can't find drivers so somewhere here is a mistek. Also you're using SetupCopyOemInf. Was this intended or you just choose it because someone else did?

Link to comment
Share on other sites

i used SetupCopyOemInf method because LeveL said that all Bashrats driverpacks goes well over the 4096 character limit for the Registry.

so SetupCopyOemInf is a must i suppose with the Bashrats driverpacks.

can someone else post his xml if it works for him so we can compare them? and try different configurations?

EDIT the errors say something like this

Com Error with DOM

err.description is:

err.windescription is : evises..

err.number is: 80041013

err.lastdllerror is : 0

err. scriptline is: -1

err.sourse is:

err helpfile is:

err.helpcontext is:

my opperating system is win 2k3 server

Edited by herc2k
Link to comment
Share on other sites

I've just read your EDIT.

EDIT i use the Bashrats packs uncompressed from my usb stick

the hardware.exe and hardware.xml are in same folder as my drivers in my usb stick \drivers i start it from there.

my Bashrats pack drivers are decompressed in there \drivers and they are in folders for example wan,chipset,vga

what do i do wrong and why my log doesnt show anything so i can post it here sad.gif arg i ll try again in a few minutes

If your drivers are on pendrive in directory lets say E:\Drivers\Wan E:\Drivers\Lan etc you should use:

<drivers_drive>RELATIVE</drivers_drive>

<drivers_directory>\Drivers</drivers_directory>

As for the XML settings try:

<?xml version="1.0" encoding="utf-8"?>

<settings>

<basic_configuration>

<choice>manual</choice>

<drivers>

<drivers_drive>RELATIVE</drivers_drive>

<drivers_directory>\Drivers</drivers_directory>

<drivers_packed>No</drivers_packed>

<drivers_copy>No</drivers_copy>

<drivers_copy_path>C:\DriversTest</drivers_copy_path>

<drivers_copy_delete>No</drivers_copy_delete>

<options>

<method>RegistryDevicePath</method>

<registry_path>Begin</registry_path>

<problem_ids>01,10,18,24,28,37,39</problem_ids>

<update_all>No</update_all>

<plug_and_play>

<option>Internal</option>

<time_to_wait>15</time_to_wait>

</plug_and_play>

<shutdown>

<auto_reboot_when_nessecary>No</auto_reboot_when_nessecary>

<auto_reboot_when_done>No</auto_reboot_when_done>

<auto_login>Yes</auto_login>

<notify_when_done>Yes</notify_when_done>

</shutdown>

<time_to_run>0</time_to_run>

<force_run>No</force_run>

<device_manager>No</device_manager>

</options>

</drivers>

<log>

<log_overwrite>No</log_overwrite>

<log_to_file>Yes</log_to_file>

<log_filename>hardware.log</log_filename>

<log_path>$ProgramDir</log_path>

<log_option>Simple</log_option>

</log>

<gui>

<hide_legacy_devices>No</hide_legacy_devices>

<fade_in_effect>No</fade_in_effect>

</gui>

</basic_configuration>

</settings>

Don't worry that it's over 4096. Just test it if it's a bit better.

About the error. Can you tell me at which point it happens? What currently is shown in the log window?

Edited by MadBoy
Link to comment
Share on other sites

yes i changed these lines as u said

<drivers_drive>RELATIVE</drivers_drive>

<drivers_directory>\Drivers</drivers_directory>

since my drivers on pendrive are G:\drivers

there seems to be no problem with finding the drivers from my usb stick.

the log says : directory with drivers exists (G\drivers)

Discovering basic information about all system devises

Discovering advanced information about system system

then it shows those errors that i wrote in previous post and if i hit ok it continues noramlly the force detect and force plug and play but the wizard "found new hardware starts" that my main problem. i press cancel but no drivers aer installed from the program (even if i press search aytomatically)

EDIT i also changed the method to RegistryDevicePath nothing happened its the same as before mu xlm is this now

<?xml version="1.0" encoding="utf-8"?>

<settings>

<basic_configuration>

<choice>automatic</choice>

<drivers>

<drivers_drive>RELATIVE</drivers_drive>

<drivers_directory>\drivers</drivers_directory>

<drivers_packed>No</drivers_packed>

<drivers_copy>No</drivers_copy>

<drivers_copy_path></drivers_copy_path>

<drivers_copy_delete>No</drivers_copy_delete>

<options>

<method>RegistryDevicePath</method>

<registry_path>Begin</registry_path>

<problem_ids>01,10,18,24,28,37,39</problem_ids>

<update_all>No</update_all>

<plug_and_play>

<option>Internal</option>

<time_to_wait>15</time_to_wait>

</plug_and_play>

<shutdown>

<auto_reboot_when_nessecary>No</auto_reboot_when_nessecary>

<auto_reboot_when_done>No</auto_reboot_when_done>

<auto_login>Yes</auto_login>

<notify_when_done>Yes</notify_when_done>

</shutdown>

<time_to_run>0</time_to_run>

<force_run>No</force_run>

<device_manager>No</device_manager>

</options>

</drivers>

<log>

<log_overwrite>No</log_overwrite>

<log_to_file>Yes</log_to_file>

<log_filename>hardware.log</log_filename>

<log_path>$ProgramDir</log_path>

<log_option>Simple</log_option>

</log>

<gui>

<hide_legacy_devices>No</hide_legacy_devices>

<fade_in_effect>No</fade_in_effect>

</gui>

</basic_configuration>

</settings>

Edited by herc2k
Link to comment
Share on other sites

yes i changed these lines as u said

<drivers_drive>RELATIVE</drivers_drive>

<drivers_directory>\Drivers</drivers_directory>

since my drivers on pendrive are G:\drivers

there seems to be no problem with finding the drivers from my usb stick.

the log says : directory with drivers exists (G\drivers)

Discovering basic information about all system devises

Discovering advanced information about system system

then it shows those errors that i wrote in previous post and if i hit ok it continues noramlly the force detect and force plug and play but the wizard "found new hardware starts" that my main problem. i press cancel but no drivers aer installed from the program (even if i press search aytomatically)

EDIT i also changed the method to RegistryDevicePath nothing happened its the same as before mu xlm is this now

For sure there's a bug in creating log :P But lets skip it for now. After you see that com errror when you browse thru the 3 tabs DeviceSimpleView, DeviceAdvancedView and ErrorDeviceView do you see on all tabs some devices?

Just like on the screens below?

post-44662-1194794616_thumb.png

post-44662-1194794624_thumb.png

post-44662-1194794632_thumb.png

Link to comment
Share on other sites

yes after i skip the error i see all these images it detects teh devises that needs driver sand the unknown ones it tries to force detect them and install the drivers just like the images that u post but then the wizard starts...

post-161963-1194795682_thumb.jpg

post-161963-1194795840_thumb.jpg

Edited by herc2k
Link to comment
Share on other sites

yes after i skip the error i see all these images it detects teh devises that needs driver sand the unknown ones it tries to force detect them and install the drivers just like the images that u post but then the wizard starts...

Try this version. I may have introduced other bugs as this is open code release but at least logging is fixed so you should have easier way to report problems :P

http://pro-solutions.org/download.php?id=3284911232

Link to comment
Share on other sites

ill try it in a few seconds

hmm i use teh same xml with this version and it pop up an error

configuration file doesnt exist g:\drivers

but i havent change anything in xml it worked with previus version. my drivers are still i my usb stick

g:\drivers and i run the hardware.exe from that folder

post-161963-1194797322_thumb.jpg

Edited by herc2k
Link to comment
Share on other sites

ill try it in a few seconds

hmm i use teh same xml with this version and it pop up an error

configuration file doesnt exist g:\drivers

but i havent change anything in xml it worked with previus version. my drivers are still i my usb stick

g:\drivers and i run the hardware.exe from that folder

hardware_config.xml

pro-s_hardware_installer_2.0.0.12.exe

Works fine here

Link to comment
Share on other sites

oups its hardware_config.xml not hardware.xml

noe it gives autoit error and the wizard still pops up

and the log says

16:27:02] - Started program on computer HOME-84C113F3A7.

[16:27:02] - Detecting Windows version - Windows 2003 x32

[16:27:02] - Directory with drivers (G:\drivers) exist.

[16:27:03] - Discovering basic information about all system devices..

[16:27:12] - Discovering advanced information about all system devices..

[16:27:17] - Cleaning up devices list from non-essential devices...

[16:27:20] - Building up simple devicelist...

[16:27:25] - Building up advanced devicelist...

[16:27:36] - Building up error devicelist...

[16:27:36] - Found process rundll32.exe with PID 1828. Ignoring that process!

[16:27:37] - Setting path into registry using RegistryDevicePath method.

[16:27:50] - Device Path in registry currently has 36669. Maximum path is 4096 characters.

[16:27:50] - It is suggested, that if Device Path is longer then 4000 characters you should use SetupCopyOemInf method.

[16:27:50] - If you don't want to do so you can cut some dirnames so those will be shorter, cutting down the number of characters overall.

[16:27:50] - Drivers path was set successfully into registry.

[16:27:51] - Removing unknown hardware from system.

[16:27:51] - Removing hardware ID: PCI\VEN_10DE&DEV_0064&SUBSYS_57001462&REV_A2\3&13C0B0C5&0&09

[16:27:53] - Removing hardware ID: PCI\VEN_10DE&DEV_006A&SUBSYS_57001462&REV_A1\3&13C0B0C5&0&30

[16:27:53] - Unknown devices were removed successfully.

[16:27:54] - Forcing system to detect Plug & Play Devices.

post-161963-1194798696_thumb.jpg

Edited by herc2k
Link to comment
Share on other sites

oups its hardware_config.xml not hardware.xml

noe it gives autoit error and the wizard still pops up

But the other error is gone? Or still there? Due to upgrade to newest beta of AutoIt some things are probably broken still that's why i didn't released new version officially :P

Link to comment
Share on other sites

so i need to put SetupCopyOemInf first and retest it

after the autoit error the program closes

Well the new version crashes on detecting Plug and Play devices which uses dll call and if i am right autoit changed something in that command. But to be realy sure it's that you can

Change <plug_and_play> <option>Internal</option>

to <plug_and_play><option>Devcon</option>

and see. If that works and you won't get that Autoit error then i'll check the DllCall with some autoit mastah :P

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...