polemos

Hey guys, am I missing something? I searched a lot in the forum and I haven't found an answer to this. The answer is so obvious that nobody cares to take a look? There are a lot of bright minds participating in this forum, I really can't believe they don't have an answer for this, I am starting to believe that I really miss something to obvious!!!

Thank you for your response, yes it is indeed a problem with the driver. It is not a problem with WPI. If I follow the regular path and I install manually the driver, after the system boots etc., the installation proceeds without flaws. The problem arises when I try to install the bluetooth driver unattended with the help of WPI. Even though the driver supports silent mode by itself, it fails to accomplish the installation since it asks for administrative privileges, (which it already has, since WPI starts the install process after it logs on in a chosen account, which in my case is an administrator account). After I googled for a solution, I found out this not the only driver with this kind of problematic behaviour and that there are many more people with the same problem (drivers installers asking for administrative privileges). There are many solutions for installing these drivers in an unattended setup (example RunOnceEX) but I haven't found any solution for using it with the WPI alone. This is a hole in using the WPI, of which no answer has came yet. Even though many people are asking about it. As I understand from watching WPI in action, it starts to function in a free of programs and processes enviroment. This makes me suspect that the above mentioned installers are searching for some certain processes or programs in memory, to validate if the account which they are being installed to, is an administrative account. In short, how is it possible to make installers, asking for administative privileges when they are in an administration account and by fault identify the account as a not being an administrative one, to... install when they are executed from WPI? Thank you.

Greetings, I don't know your level of expertise concerning the whole subject so I'll try to offer you a brief list as a follow up guide. Tell me if you need more details for any of the steps below: 1. AFter you configure the WPI you need to enable it to autorun after the XP installation is over. There are many methods available for this, here is my preffered one (this is from the official WPI site): i) inside the $OEM$ folder create a file named: cmdlines.txt, the file contents have to be like this: [COMMANDS] "rundll32 advpack.dll,LaunchINFSection RunWPI.inf,,1,N" ii) inside the $OEM$ folder create another file named runWPI.inf, the file contents have to be like this: [Version] Signature="$CHICAGO$" [DefaultInstall] AddReg=Run.AddReg [Run.AddReg] HKLM,"%RUN%","%WPI%",,"RunDll32 advpack.dll,LaunchINFSection ""%01%\%INF%"",Execute" [Execute] RunPreSetupCommands=Launch.WPI:1 DelReg =Run.DelReg [Launch.WPI] CMD /Q /C CD /D """%01%\..\WPI""" & START /WAIT /B WPI.hta [Run.DelReg] HKLM,"%RUN%","%WPI%" [strings] RUN="SOFTWARE\Microsoft\Windows\CurrentVersion\RUN" WPI="Windows Post Install" INF="RunWPI.inf" 2. Afterwards you need to make an image and burn it to a preffered media, avoid using programs like UltraISO or WinImage etc. you will find difficulties which you don't need. I suggest you use nLite. This is the web address for it: www.nliteos.com inside their website you will find details for using it. ALSO NOTE THAT THE ABOVE IS A SIMPLE GUIDELINE FOR YOU TO USE, THERE ARE MORE STEPS NEEDED FOR MANY MANY MORE STUFF YOU MAY NEED! I also suggest that you visit this (kind of encyclopedia) which is going to explain you everything step by step, study it if you haven't already done yet: http://unattended.msfn.org/unattended.xp/

Greetings, After the 23450,25th time of reinstalling XPs, I 've recently decided to make my own unattended version for it. My problem arised when WPI autostarted to install the Broadcom bluetooth drivers in my laptop. The wizard stopped working after complaining that it needs "administrative privileges" for completing the installation. This happened in an administrative account. Any info? thanks. p.s:And offcourse, I really googled the planet for an answer, no answers for the WPI though.