MadBoy

Yeah, i encountred this problem several times too. Usually it happens when there is more then one driver on CD/Directories that matches the criteria. In cases where things weren't doubled up the Wizard didnt come up.

New version out. A lot of changes including hardware.ini so read first post carefully. Ideas, suggestions, bugs are welcome

The project still alive although i kinda stopped developing last few weeks/months due to enormous time i had to spend on other things. It's kinda ready just one little bug that makes the program crash + i need to fix/add minor things but that can be done later on. I kinda stopped developing it due to hardly any interest from ppl (you know, when it's free and you don't see ppl wanting that you don't do it ). Anyway i plan to release it since i noticed few ppl want it so it will come. @Bashrat: problem id column is what Device Manager states as device error code. When you go to devices that are unknown or with problems there's always a number next to error that it states. The error list can be found here. Only some "errors" are fixable by just removing device from device manager and are drivers related. Other problems usually are more serious problems that shouldn't and won't be solved just by device removal. But for maybe "future" features i added it to show the problem id number. @LDST - my program if it would be ready and fully working can do that for you ;p devcon -remove =Unknown is one thing but it sometimes doesn't work as the device may have been marked as "problematic" and not realy unknown. I solved it by doing a lot of reasearch on how devcon works and what changes. So my program usually check for that "problem id" that i explained to bashrat and when it founds the right codes (only 2-3 of them are drivers related) it takes device id and removes them. Then devcon rescan and woila xboxhaxorz - my first version was only looking for Unknown devices indeed. Problem with it is that after first devices removal they are no longer marked unknown. Also like you stated some device have just drivers problem. Well the new version works diffrently as i stated in this post. I'll try to release 0.4.* version during this week or so. Chears!

From Microsoft: So in other words HCL is just a list of devices that meet Microsoft requirements and can be used on Windows system without problems. They will still require drivers from CD in most cases. List of built-in drivers for cameras/scanners is here.

If it realy has 32KB limit then i would suggest to use that method. And yes it's always better to reset the path to drivers, unless you keep them on your hdd (like C:\Drivers) then you could leave it as it is. The orginal path %systemroot%\inf is also in registry so you shouldn't worry.

BOOL SetupUninstallOEMInf( PCWSTR InfFileName, DWORD Flags, PVOID Reserved ); Now since the SetupOemInf is working maybe SetupUninstall should be done too. Just not sure how the script should know what's the name of script to unninstall inf's. Maybe i should run it on all Oem.inf's and if those aren't used it would unninstall them?

Here's the log output from file. Even thou the @error isn't 0 (that's why it says FAILED there) i can still see OEM files created in Windows\Inf. Seems to work just weird that error isn't 0 [10:30:53] - Detecting Windows version - Windows XP x32 [10:30:53] - Detecting number of devices in system. [10:30:53] - Found 134 devices without any problems. [10:30:53] - Checking for drivers directory existance. [10:30:53] - Drivers directory (e:\Drivers) exist. [10:30:54] - Manual start used - Waiting for orders. [10:30:55] - Integrating drivers with SetupCopyOemInf method. [10:31:00] - Advanced Output: Inf integrated failed: e:\Drivers\1SA207WW\SMAXWDM\SE\SMWDMALI.INF [10:31:00] - Advanced Output: Inf integrated failed: e:\Drivers\1SA207WW\SMAXWDM\W2K_XP\SMWDMALI.INF [10:31:02] - Advanced Output: Inf integrated failed: e:\Drivers\1SRO15WW\WIN2K\B57W2K.INF [10:31:03] - Advanced Output: Inf integrated failed: e:\Drivers\1SRO15WW\WINXP\B57XP32.INF [10:31:04] - Advanced Output: Inf integrated failed: e:\Drivers\1YG409WW\tp4win2k.inf [10:31:09] - Advanced Output: Inf integrated failed: e:\Drivers\70CN23WW\RSTRCLMG.INF [10:31:11] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\EKEYAGT\dk.inf [10:31:13] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\EKEYAGT\fi.inf [10:31:15] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\EKEYAGT\fr.inf [10:31:16] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\EKEYAGT\gr.inf [10:31:17] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\EKEYAGT\it.inf [10:31:18] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\EKEYAGT\jp.inf [10:31:19] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\EKEYAGT\ne.inf [10:31:20] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\EKEYAGT\no.inf [10:31:21] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\EKEYAGT\sp.inf [10:31:22] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\EKEYAGT\sv.inf [10:31:23] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\EKEYAGT\us.inf [10:31:25] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\EZBTNS\JP\EZBTNS.INF [10:31:26] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\FLPTOUCH\Flptouch.inf [10:31:28] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\OSD\DK.INF [10:31:29] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\OSD\FI.INF [10:31:30] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\OSD\FR.INF [10:31:31] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\OSD\GR.INF [10:31:32] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\OSD\IT.INF [10:31:34] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\OSD\JP.INF [10:31:35] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\OSD\NE.INF [10:31:36] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\OSD\NO.INF [10:31:37] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\OSD\SP.INF [10:31:38] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\OSD\SV.INF [10:31:39] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\OSD\US.INF [10:31:41] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\ZOOM\TpScrEx.inf [10:31:42] - Advanced Output: Inf integrated failed: e:\Drivers\AUDIO\SMWDMALI.INF [10:31:44] - Advanced Output: Inf integrated failed: e:\Drivers\MODEM\AGRMDWXP.INF [10:31:45] - Advanced Output: Inf integrated failed: e:\Drivers\NETWORK\AEIWLNIC.INF [10:31:46] - Advanced Output: Inf integrated failed: e:\Drivers\NETWORK\WIN2K\B57W2K.INF [10:31:49] - Advanced Output: Inf integrated failed: e:\Drivers\NETWORK\WINXP\B57XP32.INF [10:31:50] - Advanced Output: Inf integrated failed: e:\Drivers\OTHER\BLUTOOTH.INF [10:31:51] - Advanced Output: Inf integrated failed: e:\Drivers\OTHER\IBMPMDRV.INF [10:31:52] - Advanced Output: Inf integrated failed: e:\Drivers\OTHER\IBMTPLCD.INF [10:31:53] - Advanced Output: Inf integrated failed: e:\Drivers\OTHER\TP4WIN2K.INF [10:31:54] - Advanced Output: Inf integrated failed: e:\Drivers\VIDEO\CX_06991.INF [10:31:55] - Advanced Output: Inf integrated failed: e:\Drivers\VIDEO\CX_06992.INF [10:31:56] - Advanced Output: Inf integrated failed: e:\Drivers\VIDEO\PHILDECN.INF [10:31:58] - Advanced Output: Inf integrated failed: e:\Drivers\VIDEO\WIN2K\GARTNT.INF [10:31:59] - Advanced Output: Inf integrated failed: e:\Drivers\VIDEO\WINXP\GARTNT.INF [10:32:00] - Advanced Output: Inf integrated failed: e:\Drivers\1OMA23WW\nt4\agrmdnt4.inf [10:32:00] - Advanced Output: Inf integrated failed: e:\Drivers\1OMA23WW\w2kxp\AGRMDwxp.inf [10:32:05] - Advanced Output: Inf integrated failed: e:\Drivers\1OMA23WW\w98\AGRMDvxd.inf [10:32:06] - Advanced Output: Inf integrated failed: e:\Drivers\1OMA23WW\wme\AGRMDMEE.inf [10:32:11] - Advanced Output: Inf integrated failed: e:\Drivers\1OMA23WW\wme\AGRMDMEM.inf [10:32:13] - Advanced Output: Inf integrated failed: e:\Drivers\1RD631WW\DRIVER\2KXP_INF\C2_21425.INF [10:32:15] - Advanced Output: Inf integrated failed: e:\Drivers\1RD631WW\DRIVER\2KXP_INF\CX_21425.INF [10:32:16] - Advanced Output: Inf integrated failed: e:\Drivers\1RD631WW\PHILDEC\WDM_2K\PHILDEC.INF [10:32:17] - Advanced Output: Inf integrated failed: e:\Drivers\1RD631WW\PHILDEC\WDM_XP\PHILDECN.INF [10:32:17] - TheENd Hehe fixed it.. call me id*** ;p Timeings for this log are for inf's that are already integrated. But timeings in my last post gives like 1 inf per second (keep in mind that i have USB 1.1 with drivers so it slows down the whole process a lot i think). Anyway it needs testing [10:42:39] - Integrating drivers with SetupCopyOemInf method. [10:42:42] - Advanced Output: Inf integrated ok: e:\Drivers\1SA207WW\SMAXWDM\SE\SMWDMALI.INF [10:42:42] - Advanced Output: Inf integrated ok: e:\Drivers\1SA207WW\SMAXWDM\W2K_XP\SMWDMALI.INF [10:42:43] - Advanced Output: Inf integrated ok: e:\Drivers\1SRO15WW\WIN2K\B57W2K.INF [10:42:43] - Advanced Output: Inf integrated ok: e:\Drivers\1SRO15WW\WINXP\B57XP32.INF [10:42:44] - Advanced Output: Inf integrated ok: e:\Drivers\1YG409WW\tp4win2k.inf [10:42:44] - Advanced Output: Inf integrated ok: e:\Drivers\70CN23WW\RSTRCLMG.INF [10:42:45] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\EKEYAGT\dk.inf [10:42:45] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\EKEYAGT\fi.inf [10:42:45] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\EKEYAGT\fr.inf [10:42:45] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\EKEYAGT\gr.inf [10:42:45] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\EKEYAGT\it.inf [10:42:45] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\EKEYAGT\jp.inf [10:42:46] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\EKEYAGT\ne.inf [10:42:46] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\EKEYAGT\no.inf [10:42:46] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\EKEYAGT\sp.inf [10:42:46] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\EKEYAGT\sv.inf [10:42:46] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\EKEYAGT\us.inf [10:42:46] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\EZBTNS\JP\EZBTNS.INF [10:42:46] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\FLPTOUCH\Flptouch.inf [10:42:46] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\OSD\DK.INF [10:42:47] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\OSD\FI.INF [10:42:47] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\OSD\FR.INF [10:42:47] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\OSD\GR.INF [10:42:47] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\OSD\IT.INF [10:42:47] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\OSD\JP.INF [10:42:47] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\OSD\NE.INF [10:42:47] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\OSD\NO.INF [10:42:47] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\OSD\SP.INF [10:42:47] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\OSD\SV.INF [10:42:48] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\OSD\US.INF [10:42:48] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\ZOOM\TpScrEx.inf [10:42:48] - Advanced Output: Inf integrated ok: e:\Drivers\AUDIO\SMWDMALI.INF [10:42:48] - Advanced Output: Inf integrated ok: e:\Drivers\MODEM\AGRMDWXP.INF [10:42:48] - Advanced Output: Inf integrated ok: e:\Drivers\NETWORK\AEIWLNIC.INF [10:42:49] - Advanced Output: Inf integrated ok: e:\Drivers\NETWORK\WIN2K\B57W2K.INF [10:42:49] - Advanced Output: Inf integrated ok: e:\Drivers\NETWORK\WINXP\B57XP32.INF [10:42:49] - Advanced Output: Inf integrated ok: e:\Drivers\OTHER\BLUTOOTH.INF [10:42:49] - Advanced Output: Inf integrated ok: e:\Drivers\OTHER\IBMPMDRV.INF [10:42:50] - Advanced Output: Inf integrated ok: e:\Drivers\OTHER\IBMTPLCD.INF [10:42:50] - Advanced Output: Inf integrated ok: e:\Drivers\OTHER\TP4WIN2K.INF [10:42:50] - Advanced Output: Inf integrated ok: e:\Drivers\VIDEO\CX_06991.INF [10:42:50] - Advanced Output: Inf integrated ok: e:\Drivers\VIDEO\CX_06992.INF [10:42:50] - Advanced Output: Inf integrated ok: e:\Drivers\VIDEO\PHILDECN.INF [10:42:51] - Advanced Output: Inf integrated ok: e:\Drivers\VIDEO\WIN2K\GARTNT.INF [10:42:51] - Advanced Output: Inf integrated ok: e:\Drivers\VIDEO\WINXP\GARTNT.INF [10:42:51] - Advanced Output: Inf integrated ok: e:\Drivers\1OMA23WW\nt4\agrmdnt4.inf [10:42:51] - Advanced Output: Inf integrated ok: e:\Drivers\1OMA23WW\w2kxp\AGRMDwxp.inf [10:42:51] - Advanced Output: Inf integrated ok: e:\Drivers\1OMA23WW\w98\AGRMDvxd.inf [10:42:52] - Advanced Output: Inf integrated ok: e:\Drivers\1OMA23WW\wme\AGRMDMEE.inf [10:42:52] - Advanced Output: Inf integrated ok: e:\Drivers\1OMA23WW\wme\AGRMDMEM.inf [10:42:52] - Advanced Output: Inf integrated ok: e:\Drivers\1RD631WW\DRIVER\2KXP_INF\C2_21425.INF [10:42:52] - Advanced Output: Inf integrated ok: e:\Drivers\1RD631WW\DRIVER\2KXP_INF\CX_21425.INF [10:42:53] - Advanced Output: Inf integrated ok: e:\Drivers\1RD631WW\PHILDEC\WDM_2K\PHILDEC.INF [10:42:53] - Advanced Output: Inf integrated ok: e:\Drivers\1RD631WW\PHILDEC\WDM_XP\PHILDECN.INF [10:42:53] - TheENd

Maybe i am too tired but everytime i call it @error is always = 0 which means everything is great ;p It's always fine even if i change $dll_exe = DllOpen("setupapi.dll") to $dll_exe = DllOpen("setupapi11.dll") ;p DllCall($dll_exe, "int","SetupCopyOEMInf", $full_path_to_inf, "", 1, 8, "", 0, 0, "") I'll try to work it out tommorow but any suggestions are welcome ;p

YEah i knew there is dllcall but never realy used it and didn't knew where to start As for SetPathDevice in autoit for now it jsut adds every dir it finds.. even those without .ini files but i'll change it soon, shouldn't be too hard (i even have idea right now how to do it so should be done soon). Was developing something else meanwhile in my script I also found that there is SetupUninstallOEMInf so maybe if Install will work i can do Uninstall also ;p So even if it will a bit slower it should be better. Calling external program from autoit makes it harder for me to control. Btw since you seems to be good with dllcalls, maybe you know a way for dllcall that will change driver signing the way it's done by hand with Properties/Hardware/DriverSigning/ignore. I tried to search a lot about it but no good way. It can be done in autoit using it's capabilities but it will be language dependant. BOOL SetupUninstallOEMInf( PCWSTR InfFileName, DWORD Flags, PVOID Reserved );

Well i already rewrote SetDevicePath in AutoIt and added support for 64bit (since the regirstry changes). But i don't know how do SetupCopyOemInf. That's why if you can pls upload those .bat files so i can learn more about the way you did it. It's easier for me to see the way it was done by you in .bat way then by pyron in C++. If i'll get the idea maybe it will be quick enough.

I could try rewritting SetupCopyOemInf in autoit and add the backup/recover procedures but i don't realy see option how to modify those files.. (as they are not clean text) - update the Signature Catalogs %windir%\system32\CatRoot2\....... - update the %windir%\inf\INFCACHE.1 maybe there are some dllcalls or so? If i remember right shalti you had some .bat files that were doing the SetupCopyOemInf procedure that was later on taken by pyron with his program. @shalti Hope you can give us much info as you can on this. Maybe then i could implement it in my Hardware Installer program.

Go to AutoIt forum / Scripts and Scraps and search for Scriptomatic.au3. This program is AutoIt version of Microsoft program that gives you same capabilities. Althought in some cases it crashes for me but it should give you good start since it works great for showing how/what/when http://www.autoitscript.com/forum/index.ph...pe=post&id=5862 --> CODE of scriptomatic.au3

Just to keep you guys posted.. i decided to add some screenshot. Not best quality but will give you *HINT* on new features that will be implemented in newest version. New features: - Full support for 7zip/Rar packed drivers - Optional backup of c:\Windows\Inf directory before applying drivers - New look - Ability to configure .ini file thru GUI (not realy sure i need it but i'll try to implement it if i get time ;p) - Possibility to copy drivers to for example C:\Drivers for later use (a must to set when using packed_drivers) - Optional output to log_file (usefull for debugging) - Optional output_option = Full/Simple - with Full mode on 99% of what's happening including output from external programs will be placed in log. (usefull for debugging but might slow down program a lot) - Information if Windows require reboot to use drivers or not - Automatic or Manual start (by pressing button). - Auto autorun file creator for easy deployment on CD. Suggestions are welcome as i haven't done everything yet so i can change things. Later on it will be much harder (althought with log window instead of preset GUI it's much easier to change things. Hope you guys will like the changes in new version. Hopefully out sometime soon.

So far everything i wanted to create in AutoIt was possible Sometimes you just have to look for it, and the forum response is always fast and great. Eventually you can use external programs that you can include in .exe. And simplicity (at some stage of course...new version of my hardware.exe is far from being simple ;p) is great!

@RougeSpear - nice script. I also noticed there is very little response in Hardware forum Which makes it hard also for me to focus on developing my app further. Producing something just for yourself is nice, but much better if you have users who will use it Would be nicer if ppl would post results if they like it or not :> If they tried it, if it works on other systems You should try learning AutoIt. It has huge advantage over batch files. Things you can do with it are amazing and with proper system knowledge you can do great tools I'm currently preparing final version of my hardware.exe app that i will release hopefully before May ;p Chears,

You can do conversion anytime. It is supposed to go without problems but as always backup your documents and other stuff your mom might need in case something goes wrong. As it is laptop power outage isn't problem here but better to be safe then sorry. Especially that it will be usefull later on since laptopt hdd's need special care and they often get broken. Now to the point.. You can either use the script provided by notebook vendor or just do 1. Click START. 2. Choose Run. 3. Write 'cmd' (without ' '). 4. Black window should open up. Type 'convert /?' and read what results you have Should give you idea. I would do it like convert C: /FS:NTFS /V. Although i am not sure if V is realy needed for you

@IceMan .. it's exactly what Hardware.exe should do for liquidator. Unless he is doing something wrong. He can also have drivers in some other, non pure .inf format. Then that won't realy work.

Sure, it will give you an error You haven't been carefull reader. REMOVABLE should be used when drivers are on USB DEVICE. For example i have a USB PEN that i insert to computer. It has Drivers dir on it. On each computer USB device can be mounted on diffrent letter. When you set Drivers_drive to REMOVABLE it will autodetect that letter. IN your case you should probably use like where E:\Drivers is a directory where you have driver for your device. Drivers_drive=E Drivers_dir=\Drivers U can also use CDROM if drivers are on CDROM (and the path is CDROM:\Drivers) .. remember that you have to set that corretly. Else it won't realy make sense.

Np, just report errors New version is there. Little mistake on my side ;/ And can anyone report problem with redetection of devices? I mean like you had to do it manually in device manager to see the process started? Changelog for 0.3.7 - Fixed multiple Device Manager instances being started

You can use my program. You could use it like 'hardware.exe Install' in "Unattended On" mode (it's use is for unattended cds but it will fit your case) it should set the path to drivers (where you have drivers for your unplugged device) into registry.. so when Windows detects new device it will first try to find drivers by itself. So if you have drivers in pure format in that dir Windows shouldn't ask you about it. If Windows have problems with those drivers it asks you about it. Hope that helps.

New version is out. I rushed it a bit but thought i would share it before i end up starting a lot of changes to GUI and other stuff. So without further ado... Download version 0.3.6 (Current with GUI) Problems to solve: - Signing of drivers isn't 100% working. Unfortunetly Microsoft implemented it the way it can't be realy done just by registry. Tests shown that also during change from Warn to IGNORE mode (My Computer -> Properties -> Hardware -> Driver Signing) besides standard registry keys that can be found all over the internet this key below also changes. On my computer it has 2 values (one for IGNORE and one for WARN). So unless i'll find a way to fix it.. Bummer. Maybe someone has some nice idea? Each computer has their own diffrent keys so it's not that simple as i seen on other forums in some posts - HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\PrivateHash 15 CA EF C3 34 E8 C8 78 - HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\PrivateHash 01 32 A3 68 55 C2 D2 00 Problem of signing drivers on unnatended cd doesn't exist because you can set the right value in winnt.sif or sysprep.inf. Or so i have read on Microsoft pages Oh well, we will see.. Possible changes in next versions: - Option to have copied drivers to C:\Drivers (or other dir you choose) and then using it as the main driver directory. Mighty be usefull for ppl who like to leave the drivers on hdd, and for use with pyron's method. - Completly redo of GUI. As someone said GUI isn't good enough which i knew on begining, but wanted to have something easy and done fast so i could see the progress going on. So the project will have new GUI soon. Better, nicer. Maybe special GUI for congfiguration. - Waiting for other ideas and problems. Changelog for 0.3.6 - Added REMOVABLE drives to be autodetected (you can use it instead of CDROM or drive letter) - Added function that will create hardware.ini automagically if there is no hardware.ini present (usefull ;p) - Added option that opens Device Manager while devices are being removed/detected. - Added option to use either RegistryDevicePath or SetupCopyOemInf by pyron Would be nice if someone would give his opinion about this, especially about Driver Signing. Couldn't realy found good solution.

Care to read some of posts on FORUM. YOu can surely find an answer for your question.

Switches for 7za.exe -aoa Overwrite All existing files without prompt. -aos Skip extracting of existing files. -aou auto rename extracting file (for example, name.txt will be renamed to name_1.txt). -aot auto rename existing file (for example, name.txt will be renamed to name_1.txt).

There are lots of methods for creating unnattended CD but it's just not as simple as you write it. You can use nlite (you can find it here in forum or just google for it). The app does all the work for you. You can also read the topics on the top of this forum .. they are there for a reason. You can also try my way of instaling drivers. But it's not the same as you want it to be.

This TAG is to detect under which letter you have CDROM driver. On all XP CD's with SP2 integrated WIN51IP.SP2 file is in the root of the cd. So first and second line are for setting the drive letter of your windows CD. IF EXIST %OEM%\7za.exe Copy %OEM%\7za.exe %SYSTEMROOT%\system32\7za.exe This code makes sure the 7za.exe exists in %OEM% dir on CD.. if it does it copies the right things into right dirs. If it doesn't it just skips it. It's to make sure that if you don't use the 7za.exe or you're not going to include it you don't have to change any code here. The rest i don't realy wanna predict what author had in mind