MadBoy

Well if you would do a lot of small packs (not like bashrat huge packs) that would be small ones (5MB per pack or even less) and the program would only have to unpack 3 packs from 50-70 packs, considering amount of space saved it may be worth it. And since the packs would be small the speed of unpacking wouldn't be killer for the the time it would take It's a nice idea but like you said mostly Post install stage

Not quite It's doable and actually wouldn't be that hard to achieve. I guess i could add that option to my little proggy if i get time (not very soon). I could tell my program to scan for .7z or other archived packages, then unpack one (scan all inf's and add them to db - this is already part of the program), then unpack another and so on. After that delete all files except the .7z ones and the .db would have format like HW_ID,INF_PATH,IN_WHICH_PACK. Then it would only unpack what's nessecary and point only windows to correct inf's The only draw back is it's in the post install stage (noone tried using my program in other stage i guess). And i would actually have to do some work on it Not a biggy, nice idea and maybe some day

Switches: GDisk Question/Issue: This document describes the switches that can be used with the GDisk utilities, GDisk.exe, and GDisk32.exe. Solution: GDisk is a DOS program with seven main operations. This document describes the options available for each operation. The seven operations are: * Display partition information (/STATUS) * Create a partition (/CRE) * Delete a partition (/DEL) * Activate or deactivate a partition (/ACT and /-ACT) * Hide or unhide a partition (/HIDE and /-HIDE) * Reinitialize the master boot record (/MBR) * Wipe the disk surface (/DISKWIPE) So maybe /MBR option will do for you?

Spl1 it's not yet done. If my company wouldn't push me too much to write documentation (it's heavy documented envirovment) for new Image Manager (which i need to updated on MSFN aswell) version and uni wouldn't give me more exams i would be focused on that WinPE Customizer. The good thing is i am about 50% into coding this. Shouldn't take much time. Maybe 2 weeks with testing and checking everything works as designed Currently the work is focused on doing proper saving / loading configuration so things can be saved for later reproduction without much hassle. Need to add support for multiple config files and then the whole PE creation which should be simple All in all - 2 weeks

Open XML file in Internet Exploer (in non modified default setting pressing enter on .xml should open it in Internet Explorer by default). If you open it in IE you will see that most likely IE will tell you that you typed in something wrong in the .xml that causes the .xml to "crash". Fix it by going thru errors that IE shows up. Unless no errors then as always "send me the .xml" My .xml is correct, even I have the same error with your original .xml. But this happens in a BartPE instaled in harddisk. Sure fails because this system... With my XP your tool works ok. BartPE is diffrent then XP. The program is designed to work only on XP. You can probably try to use it on BartPe but my guess is that it won't realy work

Open XML file in Internet Exploer (in non modified default setting pressing enter on .xml should open it in Internet Explorer by default). If you open it in IE you will see that most likely IE will tell you that you typed in something wrong in the .xml that causes the .xml to "crash". Fix it by going thru errors that IE shows up. Unless no errors then as always "send me the .xml"

Changelog for 2.0.0.20 (public) - Fixed bug where some .inf's would be ignored (tnx GrandCat), nasty typo - Fixed bug where database wouldn't be recreated if one already existed and $variables were used @GrandCat please test this. Thanks for your report (however next time please be more descriptive ;P Had to think a bit what you mean and found another bug when fixing your problem.

I have DC7800. DC7700 drivers work straight away with standard WinPE. For Dc7800 i have downloaded drivers from HP sp36743.exe. Unpacked it. Then went to dir C:\sp36743\PRO1000\Win32 Then for each .inf i have did: echo Adding the driver %1 peimg /inf=%1 %PEMNT%\Windows>NUL IF errorlevel 1 echo INF File %1 failed>>%ERRFLE% Where %1 = path to .inf file. I am writting currently program that will allow easy winpe creation along with easy adding drivers and removing some stuff. Just need some time and i will probably release it on forum. Actually here's a little screenshot for adding drivers: You simply browse for directory or enter path, press enter and tell it to scan for .inf's then you select drivers to integrate and that's it. You will just have to install WAIK, prepare some minor things first and then go thru simple configuration Program will create Usb aswell as .iso for CD-ROM. This will have built in support for adding Image Manager which has gone thru a lot of changes and additions

The thing is that there are far a lot of possiblities to use the tool. Depending on what you want to achieve you have to set diffrent settings. I was thinking of creating help file with all kind of scenarios on what settings to use for each scenario. However i don't have much time to play with this. The most important part of the .xml file that is attached on the first page is: <drivers_method>New</drivers_method> <drivers_database_use>No</drivers_database_use> <drivers_database_recreate>No</drivers_database_recreate> <drivers_database_path>$ProgramDir\hardware_database.db</drivers_database_path> <drivers_directory_path>RELATIVE:\PenDrive\Drivers</drivers_directory_path> <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> Rest can left as default. Scenario 1. Lets say you want to put all your drivers on USB Pen (drive letter H:). The drivers need to be unpacked for fast deploy. The directory with drivers that you want to use is stored on C:\Drivers directory. Things to do: 1. Copy drivers from C:\Drivers to directory on USB Pen to directory H:\D 2. Copy pro_s-hardware.exe along with .xml file to the root of H:\ 3. Modify the .xml file to either <drivers_directory_path>H:\D</drivers_directory_path> or <drivers_directory_path>RELATIVE:\D</drivers_directory_path>. Of course the H:\D will only work on your computer. While the RELATIVE means RELATIVE drive letter to the pro_s-hardware.exe. Which means it doesn't matter under what letter you will have your drive detected on other computer. The drive letter will always be the same for your D directory as long as pro_s-hardware.exe is on same place as your drivers. 4. If you just wanted standard functionality that's all you have to do. Scenario 2. Lets say you want to put all your drivers on USB Pen (drive letter H:). The drivers need to be packed as the size matters. The directory with drivers (packed) that you want to use is stored on C:\Drivers (.7z or .rar archives) directory. The drivers should be unpacked by program to C:\DriversUnpacked Things to do: 1. Copy drivers from C:\Drivers to directory on USB Pen to directory H:\D 2. Copy pro_s-hardware.exe along with .xml file to the root of H:\ 3. Modify the .xml file to either <drivers_directory_path>H:\D</drivers_directory_path> or <drivers_directory_path>RELATIVE:\D</drivers_directory_path>. Of course the H:\D will only work on your computer. While the RELATIVE means RELATIVE drive letter to the pro_s-hardware.exe. Which means it doesn't matter under what letter you will have your drive detected on other computer. The drive letter will always be the same for your D directory as long as pro_s-hardware.exe is on same place as your drivers. 4. Modify the following .xml entries to - <drivers_packed>Yes</drivers_packed> - <drivers_copy>Yes</drivers_copy> - <drivers_copy_path>C:\DriversUnpacked</drivers_copy_path> 5. Now if you want to leave the directory DriversUnpacked to be left intact after program is done working leave entry <drivers_copy_delete>No</drivers_copy_delete> intact. However if you want program to delete the drivers as those will be no longer in use set <drivers_copy_delete>Yes</drivers_copy_delete> Now the things that will work for both scenarios and that are for you to experiment with whether you want to use them or not are: - <drivers_method>New</drivers_method> - <drivers_database_use>No</drivers_database_use> - <drivers_database_recreate>No</drivers_database_recreate> - <drivers_database_path>$ProgramDir\hardware_database.db</drivers_database_path> Those are described on the first page. Maybe i'll spend some more time later on to explain all 4 entries again with full description but i realy don't have that much time If someone wants to make .chm file for my program and help me out with creating a lot of scenarios and add at the end help me with creating this a MAJOR package with all that let me know

Changelog for 2.0.0.19 (public) - Added workaround for devices with &REV_ (tnx hoolie) @hoolie please test if it works for you. @pSycho-Y2K turn on debug as logging option. and try the program again. I've moved the function up a bit in the code and added some debug lines to see where it doesn't work. Report back with .xml file and log file attached if it's not fixed please.

Yes it is possible. Read helpfile on the first page how to do it. @hoolie, i'll take a look probably my program is not removing last part &REV when it should. @pSycho-Y2K, not yet found :| no time + too many things on my head

Lovely! Had the same problem. Tnx SKiNNiEH.

Thank you for your report. I will need the log file, .xml and the screenshot (so i can see my program GUI). This will give me ability to know when the Hardware Window showed up. Might be that i've put the Hardware Closing function in wrong place. What about the NEW aproach to drivers. Database working? Is it finding the drivers and working fine other then the Hardware windows showing up?

Gah, Changelog for 2.0.0.18 (public) - Changed amounts of elements from 30000 to 8300000 (my bad) Sorry guys. Value of array in special function was increased from 30000 to 8300000. This is hardcoded value so the speed of program can be fast. Hopefully it will be enough. I left 30000 value as i was doing some tests and showing array with 8300000 elements with ArrayDisplay isn't something fast So pSycho-Y2K and everyone else please redownload.

Preety sure it is. Can you please send me the log file? and screenshot of application (so i can see Image Manager GUI along with error, not the error alone). EDIT: also please send me the .xml file.

I'm using the Dutch version, and we don't use apostrophes in our language. But unfortunately the latest version of the tool generates the following error: Method must be set: SetupCopyOemInf or RegistryDevicePath. Terminating! In the logwindow I see the following line: [16:37:48] - [CONFIGURATION] Wrong settings for Plug And Play Option. Setting method to INTERNAL. I used the new default configuration supplied in the zip, and altering the requested values did not help Is this a bug? Press ENTER on .xml. It should open up in Internet Explorer. If it opens up without problems then send me .xml file + eventually log. If it doesn't open up you should be notified with errors that are in .xml. If there is any inconsistency with XML format my program won't have ability to read it and therefore the function that checks .xml doesn't work.

There's no way to encrypt the code. You can use obfuscator but that won't slow people down much. So i kinda gave up And yes i still use AutoIt

I have just found out that some chars can't be properly used in .xml file. For example i tried to use some french apostrophes in window name and it wouldn't let me. So i have to find another way to store the information that is required for Window managing. Unless noone is using other language then English ...

Geek, why don't you use Pro-S Hardware Installer, it has the features you ask for It's a bit more advanced thou and requires some settings

All is fine i just need the log file now and possibly a screenshot of application showing that error (whole application with gui). This way i can see at which point of program it crashes and fix it asap).

Here it comes Sooner or later you will end up like me Having so many features you can hardly track where is what ;P BTW. Your CHECKFORWIZARD() function isn't the best considering that you hardcoded english title, also WinActive isn't nessecary i think. Also why do you put both 7zip.dll and un7zip.exe into the .exe shouldn't one be enough?

Send me your config file please and log..

Well unfortunetly what you have to do is to write .bat file that will be starting the .exe and first mapping the drive etc then with mapping drives turned of in my proggy do the rest. Or just put everything on server. Start it from \\share\sharedir\pro_s-hardware.exe and just make it map the drive (again just this time it will have letter) as you require. Can't seem to find a problem with that?

No. You have to map drive to be able to use shares of any kind. Otherwise it would be too dificult to 'verify'. EDIT: this is because most likely some kind of connection (with credentials) would have to be made first. I am curious where you would prefer to use the share path instead of mapping the drive (which will unmap itself on reboot). I could probably add unmap option to program when quiting program but that will follow up in next version.

This is it. The day has come. 2.0.0.17 was released today with new options and heavily redesigned core. This will most likely bring bugs not seen before and so i advice you to test this program heavily on test envirovment before running on production. I didn't had much chance to test it so it may not even work *SIGH* so i advice you to keep backup of old version and configs. Reread the first page for changes in .XML. You won't be able to use old one as the changes are preety significant. Please ask if something is unclear or needs additional description. When reporting bugs try to make screenshot, send a log and describe what happens. To do list: - Fix _UpdateStatusBar icons (wth is going on) - Fix any bugs that come in a way - Add window managing for Ignore Unsigned drivers - Add application updater (to update itself) - Add database online support to download drivers from the WEB - Add timers to execute some stuff simultaneously (where possible) Changelog for 2.0.0.17 (public) - First release since a while (expect lots of bugs ) Changelog for 2.0.0.16 (non-public) - Changes to listing of directories for RegistryDevicePath (better/optimized) - Changes to listing of files for SetupCopyOemInf (better/optimized) - Updated version of 7zip to 4.57 - Added window managing of Hardware wizard Changelog for 2.0.0.15 (non-public) - Added drive mapping (supported in LOGS/DRIVERS DB/DRIVERS PATH/DRIVERS COPY PATH) - Changes to _DetectInfrastructure(), warning for Windows Vista added (vista is not supported as far as i can tell). - Changes to hardware_config.xml (update your configuration!!): ===> REPLACED: <drivers_directory> AND <drivers_drive> WITH <drivers_directory_path> ===> REPLACED: <log_filename> AND <log_path> WITH <log_filename_path> ===> ADDED: <drivers_database> with subkeys added ===> ADDED: <drivers_method> added ===> ADDED: <share_configuration> with subkeys added ===> ADDED: <window_managing> with subkeys added - Added Modern Menu look - Added prepare drivers database Changelog for 2.0.0.14 (non-public) - Updated settings check to be more informative in case config file wasn't found. Was missleading back then. - Updated settings check msgboxes to ones with icons - Changed config file name from hardware.xml to hardware_config.xml (update your configuration!!) - Fixed default log file names when the correct one cannot be created Changelog for 2.0.0.13 (non-public) - Fixed logging problem where log file was created but no data was populated - Fixed flickering when data was populated to SimpleDeviceListView - Updated code to newest beta of AutoIT v3 (some GUI functions were broken) - Fixed DllCall for Plug and Play Rescan (tnx to Smoke_N) (Changed: DllCall() new method of passing types by reference using *.) (Changed: DllCall(): short_ptr, long_ptr, int_ptr types deprecated. Use short*, long* and int* respectively.)