thefastone

ok..i found the place in the sourcecode... in core.js line 102 is detected the OSLanguage... i comment out some lines and hardcoded my language // var OSProps = GetObject("winmgmts:").InstancesOf("Win32_OperatingSystem"); // Language ID in Dec // sLang = new Enumerator(OSProps).item(); // Enum = sLang.OSLanguage; // DtoH = DecToHex(Enum); // while (DtoH.length<4) DtoH = "300a";

ok fine...no replies... well another question: Im getting "error on line102" (see my picture above) when i delete wbem folder... i think there is an unique WMI comannd elsewhere in scripts... who knows about it... i can close the error windows and everthing else works fine... Please i need shortly some constructive feedback

OK! You are making the right question!!! Why use WPI in preinstalation environment??? This same question i have made about 3 years before....well my question was: Why i cant select in an GUI in the first 5 minutes of contact with a n new PC all the components i want have installed onto the computer..???? WPI for me is more than Windows (why not Linux) Post (why not Pre...) Instalation (why not other thinks like Virus Scan or Bios Update or Imaging with Imagex?? ) If i create some new scripts (like now unattend Application installs) i can make WPI most powerfull than ever!!! Running from WInpe2 its possible to make in the first minute rescue and antivirus operations on existent Installation of a PC defining of wich operating system and applications will be installed (unattended WIndows script /unattended apllication scripts applied with imagex) and and and... ok all what in the year 2004 only was in my mind in this moment exists: File-based Imaging Solution!! and a powerfull GUI so that everbody can use it once configured... the end-user has only to know where to put the aplication and OS "source files"!!! Ok ...the only problem is: How to make it work from a Network Ressource after booting also the Winpe2 from Network.... i hope the developers will take my comments as an suggestion for improvements Oh, and i have made some improvements regarding slimming down Winpe2.. at this moment im using an only 80MB "small" WinPE2 winpe.wim wich is working fine (if wpi is installed in this file)...

After a couple of years im saying hello again! I must say the WPI community and special the developer have done a great job..!!! Im trying to run WPI from Winpe 2 wich is freeware if used from WAIK... 1. Winpe2 its running in Ram after deployment from PXE-Linux Server... 2. WPI is working fine if i run it from Ramdrive...also all aplications are running fine...if they also stay in RAM My biggest problem is i dont have enough RAM.... (Its also easier to update all thinks in the network share!!!) So im trying to run WPI and al the other stuff from network...and because its not working im now here..... I cant make run WPI from network share: Because the Winpe2 User "System" dont knows Driveletters like z: at other side i cant use the method running wpi from %share% because i must (beacuse of security settings in Winpe2???) start wpi.hta with x:\windows\system32\mshta.exe %share%\wpi.hta ...but this works only partially i get the errors shown in attached files: ..after the last error i see only a blank "mshta" window. I think there is (in my case) some problem with the wpipath variable... maybe the variable is not interpreted correctly in Winpe2?? My Question: Is there somebody out there who has running the combination WINPE2 and WPI with apllications from Network share? a lot of thanks for any answer!