MadBoy

Just noticed your EDIT: *EDIT: I realize why now, nicely done. Question though, devices I have intentionally disabled, (error code 22), will they be updated or skipped or what? Simply don't put code 22 in problem id's field in config and it will skip removal of that device. The problem ID's are only used if you want to 'remove' that device prior to drivers instalation. When using UpdateAll drivers feature the problems id's aren't taken into consideration.

Thanks for all the comments. I would advice you to wait for the new version which will have some "problems" resolved and some things fixed. However since you asked a lot of questions i will try to answer 1. And for the log file, how do you intend to write to the $programdir$ if this was burned on a CD? - It is up to you to set the path correctly. What i put there is default for using from PenDrive or any other device. However the code has error proof logging. It will check if it can write to the path specified in the config and if it can't do that it will try to write the log to $ProgramDir (in your case it would do exactly same thing) and if that errors out too it will write the log to C:\. If you have any suggestions how to make it work diffrent way feel free to advice how you would like it to be taken care of. However keep in mind that new version that will be out soon has some significant changes on this aswell. But that is another story. 2. "There are no devices marked for removal. If you think this is an error correct config file with proper PROBLEM ID's.". Why is this even comming up? Why does there even have to be a device marked for removal to begin with? - When the program started it was simple tool to remove devices that have no drivers. In Windows devices that have no drivers or have other kind of problems are marked with a problem ID. Program lists all devices and then checks for their Problem ID. Each problem ID has diffrent meaning. If i remember correctly of the top of my head Problem ID 1 and 22 are for missing driver. On the first page there's a link to Microsoft Web site explaining every problem id and possible match. The problem id's in example are the ones that i found out by experience Feel free to remove anything you wish However if you leave the field empty the default ones, hardcoded will be used. 3. Can't seem to get the 'update drivers' feature working. I run the app on a machine I know needs updates but it doesn't even do anything, comes up with the same error about no devices marked for removal. Im not trying to do that, I just want to update drivers... - As the program in the begining was mostly suppoed to fix devices that require driver and update feature was added recently you will have to use force_run option in the config file to ignore the check for devices that have errors only. This should make the program to skip the check and follow up doing other procedures. 4. EDIT: Does the 'drivers_copy_path' accept environment variables? I do not wish to hard code the path but rather have it %systemdrive% or %windir% etc - At the moment it doesnt. However new version will. 5. "...but it is looking for the C:\Drivers folder, not the C:\Test\UniversalDriverDisk\Drivers folder...." As you are using RELATIVE value it only means that drive letter is relative not the whole path. So the relative for your program means C: and then you have to enter the path which in your case would be \Test\UniversalDriverDisk\Drivers. I suggest waiting for new version which will be built a bit diffrently. As the program was started i had no knowledge at coding at all. I just simply found some batch file that was doing something and couldn't understand a thing and i needed some realy good solution for my work. So i started digging up and found AutoIt. Posted the batch and asked for porting the batch file to autoit. Noone helped Suprise suprise it wasn't such an easy job as it looked. So i started doing it by myself. Now after some time i am coding a bit better and understand basics so the coding is going much better and the features are good aswell. However in the code there are many things from the old code and it takes time to replace them. What seemed to be great solution at time now is just bad code that even i can't understand why i put it like that

It's almost done .. and would be done already if i hadn't included Modern Menu... now menu looks great however everytime you right click on the main listview you can see the menu showing up. ANd if you do a lot of left clicking on the listview you can also close the program. So i will have to either a) remove it and replace it again with old styled menu B) let it be and warn to not touch listview ;P

; Ready to install WinWaitActive("ACDSee Pro 2") Send("{ENTER}") [color="#FF0000"][b]Sleep(24000)[/b][/color] ; Finish WinWaitActive("ACDSee Pro 2") Send("{TAB}") Send("{SPACE}") Send("{TAB}") Send("{ENTER}") Since between one window and another you've got WinWaitActive you can simply remove Sleep. You will get more help on AutoIt related forum.

I am a bit lost on here? So who's program is it? Maybe you guys need to have 2 diffrent threads ?

There's only one XML wrapper and it's eltorro's one which will probably end up as autoit udf comming with autoit package. He also helped with the functions i use for having it in the format as kind of 'registry type'. Here's a link to XML dom wrapped on autoit page if you need it http://www.autoitscript.com/forum/index.php?showtopic=19848

As promised earlier to pSycho-Y2K i will implement Hardware Wizard managing in next version. Unfortunetly due to many languages it will have to be set in the .xml like this: <window_managing> <hardware_wizard> <wizard_use>Yes</wizard_use> <wizard_title>Found New Hardware Wizard</wizard_title> <wizard_button_cancel>Cancel</wizard_button_cancel> <wizard_button_next>Next</wizard_button_next> <wizard_button_finish>Finish</wizard_button_finish> </hardware_wizard> </window_managing> On diffrent language settings you will have to set diffrent settings.

If you don't mind, could you implement this? As long as we don't have a good solution for it, this can be a temporary workaround for the time being. Then we can have a fully unattended installation This will be implemented in the next version: - advanced drive mapping solution (DONE) - diffrent way of handling paths (internal changes mostly, nothing that will affect users) (DONE) - window managing of Hardware wizard (DONE) - prepare drivers database (DONE) - usage of driver database (to faster driver instalation) - usage of driver database on the fly (so it's created and used right after program is started to get rid of any Registry limits or Windows searching thru drivers for very long time). - better error proof listing of directories (completly autoit solution and not like today usage of DIR command and reading the output which can have some issues on foreign systems) (DONE) - probably something more (DONE) Now i only have to find time for all that and we're done Most likely will be done before end of the year but no promises!

I could (it's not a big deal realy - althought i would have to add in .xml options for entering Window name and what to press manually due to language issues. However the question is why it's popping out... If we could know why it's popping out in first place we could do something to prevent it. As designed Wizard should never popup.

I wrote function that scans all .inf's for DEVICE they support and put them in the following format (DEVICEID, PATH to INF). Not exactly what you need but still something to work with It will be released as part of greater project as soon as possible

Devcon is simply how everyone puts it in .batch files or any other files. Usually it's DEVCON RESCAN command and that's it. While the Internal is written purely in AutoIt using dllcalls. The diffrence? None. I've only added it because someone said the Internal was crashing for him at some stage of Windows Instalation so i added 'DEVCON' to be sure that it's not something that is problem of my code. So use one that suits you the most

The problem is with WMI so most likely you've corrupted WMI files or so. Maybe you removed it or somehow got it destroyed. Not sure how i can help you guys with this? Also have you tried the newest version or the one from first page. The newest version is somewhere in the last posts as i am too lazy to update the first post (and since i am preparing new version soon i don't see sense)! Can you explain exactly what you have in mind?

What you mean by add select directories for scanning. Do you mean to add Vernalex DriverScanner? I'm writting my own functions for "fast driver applying". Just being lazy on my side.

Put in registry device path path to drivers you want to have installed/updated and run this from command prompt: RunDll32.exe Syssetup.dll,UpdatePnpDeviceDrivers Or use Devcon.exe

It's gone a long way since i started it. I'm trying to find best possible solutions for this little proggy, to be as fast as possible, and this doesn't always goes as planned It takes a lot of time but i've got enough knowledge now to go thru includes and see how someone else wrote it and maybe use some of the code to write mine. I'm still learning AutoIt. Anyway it takes a lot of time to work on something i don't use myself Hardware Installer i have used in my ex-job. New job doesn't have multiple weird hardwares Latly i am more focused on Image Manager which i have developed for my job or PostDeployment installer which can be used to "configure/install" some stuff at the time of deployment when certain piece of hardware is used (Like Tablet HP TC4400 or Laptop HP NC6400). When it's desktop it removes VPN Client from the machien at the time of deployment When it's laptop it will stop some services and do something else Stuff like that. Also i will probably write Image Builder a script to produce build according to options choosen (as i have to support 30 countries or so with diffrent images).

This is something i have read about the limit but never was able to say that it is so. For me it usually went up to 12000 chars (so way over 4000 limit). The problem is i can't confirm if Windows is reading it correctly and using it correctly. I just know that in the end my program was reporting to me that the entry has over 12000 chars. It's for you to test whether it works or not

Try this solution then, it's a bit more direct: Here are the individual steps: 1. Open a cmd prompt. 2. Run the command: net stop winmgmt 3. Run the command: winmgmt /kill 4. change directories to c:\windows\system32\wbem 5. Run the command: for %i in (*.dll) do RegSvr32 –s %i 6. Run the commands: regsvr32 –s scrcons.exe regsvr32 –s unsecapp.exe regsvr32 –s wbemtest.exe regsvr32 –s winmgmt.exe regsvr32 –s wmiadap.exe regsvr32 –s wmiapsrv.exe regsvr32 –s wmiprvse.exe 7. Run the command: net start winmgmt

Can anyone with the COM with DOM! problems please test this solution: 1. http://www.computerperformance.co.uk/Logon...de_80041013.htm seems like it's a problem with WMI. So if anyone can confirm this is a solution i'll put it on a first page or in future documentation. It's not something i can realy prevent of happing i guess since it's working just fine on computers that are up to date!

I would check if you can run WMI calls or does it crashes aswell (can be any .vbs file with WMI call) as the function it's breaking is using WMI calls. Can't find anything else that would crash it.

Ye that's my point to create it. Problem is that after going thru all files from bashrat drivers pack the file with db output is 850kb in size!!! Putting it both at file/memory at same time takes around 662008.467556631ms = 6minutes. Depending if hdd/ram cache kicked in it might be longer. Also it will be hardware dependant. I'm wondering how much time it will take to load it from file to memory (at the time of using the app from earlier preparation) if it will be any faster then doing it all at the time of instalation. Anyway i'll do more testing, will try to remove some unnessecary code + put some additinal code how to handle it. I will probably introduce 2 options. One to use be used as created predb and then loading from at time of instalation or doing it straight at deployment time. One way or another it will take some time Then you have to load it with my program

Ye ye, the error seems to be there for a lot of ppl so i'll try to reproduce it why it happens. As for the Wizard comming up i'll check it out aswell. The Inf database is my priority after finishing up with the errors I've some working code for the db creation but it seems that getting thru a lot of .inf files takes a lot of time. It may be worth it thou as the RegistryDevicePath limit won't be the concern here anymore. I'll be trying to optimize the code. Just hold on.

I understand. The wizard shouldnt come up if the drivers are correctly found by Windows at locations that are applied to registry or by setupcopyoeminf. That's why i wonder if you press "next' next nexgt will it work

What does happen when the Wizard comes up and you just press next next next (just like you would normally do)? Does it works? Install drivers? Also when you integrated the drivers and you go to Device Manager (after closing my program) and you do "refresh" delete the devices manually and press 'refresh' does it also bring Hardware wizard. Also are you sure that the drivers that you integrated cover the drivers that you need? EDIT: removed the server question. don't know where i got that you're using the program on Win2003 :/

It would be that: <plug_and_play> <option>Internal</option> <time_to_wait>15</time_to_wait> </plug_and_play> But Smoke_N fixed the problem right away for me So just download this (http://pro-solutions.org/download.php?id=1234267699) and try again without that change. Change this thou: <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> To <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>Advanced</log_option> </log> Or even <log_option>Debug</log_option>

Change the Internal To Devcon in the config as suggested by me. It clearly crashes on the Plug & Play that i mentioned that's why it doesn't run anything. Do other WMI based scripts run on that windows without problem? Also: [16:47:43] - Integrating drivers with SetupCopyOemInf method. [16:49:26] - SetupCopyOemInf method completed. No drivers were integrated. Means somethng is wrong. Change Log from Simple to Advanced and try again posting the log file. Eventually then run it again and change Advanced to Debug and post it too