Atheros

ensure that the driver inf that you are using contains the hardware id and is of the correct architecture for the winpe that your using. if you installed the WMIC package into your winpe you can get the VEN and DEV from the "WMIC NIC" command within PE. also veryify your winpe startup actually enables networking: manual command: "wpeutil initializenetwork"

if i ever have problems with drivers, i just rebuild the image completely with the new drivers set. injecting 1.2GB of drivers then trying to reverse engineer the problem has always failed for me even upon driver removal (**** you 20 versions of intel HECI!!!!) (ok the censorship is way OTT, it makes it look worse than what i actually said!)

as trip said, Networking driver should be injected into the image. however if your not in a DHCP enviorment (i do tests with a winpe with a mounted ISO on a VM). in this instance i need to set a static address by firstly getting the adaptor name using ipconfig then by using the folowing command netsh interface ipv4 add address "Wired Ethernet Connection" 192.168.x.x 255.255.255.0 ?where "Wired Ethernet Connection" is the name of your adaptor you may or may not have to put the work "static" between the adaptor name and the network address depending on what PE you are using.

yes using winpe 3. i think it could be something to do with running 2 diskpart scripts from the same sub, maybe it is storing an error somewhere. ah well ill keep trying, once i get a little more time and let you know how i get round it.

nice thought Trip. i do have a diskpart script running on window_onload but the cardreader seems to retain the letter unless i close and re-open the HTA application: this is what i currently have: Sub Window_OnLoad Document.body.style.cursor = "Wait" If ObjFSO.driveexists("c:") Then Objapp.run "Diskpart /s remc.txt",0,true objapp.run "ping 127.0.0.1",0,true END IF IF ObjFSO.driveexists("D:") Then Objapp.run "Diskpart /s remd.txt",0,true objapp.run "ping 127.0.0.1",0,true END IF Document.body.style.cursor = "Auto" End Sub diskpart scrips are as follows: Sel Vol C: Remove Letter=C NOERR Exit any further ideas,,,, not only that i sent a support request to MS about the drive lettering that WinPE allocates when system is booted with multiple drives.... but thats another nightmare in itself. if you are not aware of this letting issue then this is how it goes. drives have partitons configured on them: Disk(0)Partition(1) = C: Disk(1)Partition(1) = D: Disk(0)Partition(2) = E: Argh! hopefully they will send me a fix for this. ignore the lack of object declarations and types.... i didn't bother adding them on here but do exist on the program

does any one know if there is a fast and simple way to remove UFD support from WinPE... a certain cardreader is becoming a Nuisance... i dont use UFD as everything is blasted over a gigalan. so any quick ideas would be appreciated.

you use the winpeshl.ini file to launch your custom app. by creating an entry it should automatically override startnet.cmd.

just a quick question, something that seems to have been a pain in my side since the dawn of winpe 3.0. does any1 know how to get winpe to display scripting errors rather than just a big white square box? been making diagnostics very ardious and if there is a way of displaying them, a solution or an idea would be greatly appreciated.

compression. 1000MB is a bit large though... mine is only 786MB, but all depends on your customisations etc.

change your deployment method. Use a custom tool along with WinPE to deploy Custom WIM's... you will still run into the space issue. maybe have 2 dual DVDR9's on with x86arch wimfiles and the other with x64 arch files.

all drivers are installed during the generalize phase. as far as i know you cannot add them after. Both Network and DVD install copys a folder that is injected to the system during the installation (just before process generalize phase) personally i just BLAAT them into the Custom WIMfile. that way the image remains HAL free and can be installed on ANY system.

wouldn't it be easier to leave outlook running and minimize it to the systray?

On the HDD config Screen, click "Load Additional Drivers" option. take the win7 dvd out and insert you mainboard drivers cd. select load and navigate to the corresponding folder where your raid driver is installed. load it. reinstert the Win7 product DVD and click next. you HDD should now be seen by the HDD config page. failing that get a copy of the latest driver from the manufacturures website. if you are unsure of what it is. press shift + F10 to open a command prompt. type WMIC DiskDrive >> X:\temp.txt. use notepad to read temp.txt (Notepad x:\temp.txt) in here it will give you a list of the available storage devices and hardware ID's. then use PCIdatabase.com to lookup what hardware you have.

Ok so long time sine i've needed help with much but now i am dabbling with things that i do not fully understand (Exchange 2010). This is the setup: Router 1 (xx.xx.201.1) is L2TP tunneled to Router 2 (xx.xx.1.1) (communication both way confirmed working) Server 1 Attached to Router 1 has 2 LAN adaptors (xx.xx.201.3 - External) and (xx.xx.101.7 - Internal). both AD & Exchange is hosted on this machine and serves everyone in the 101 subnet. OWA internal and external address is working fine at both sites. File and printers hosted by AD are available. just users on router 2 cannot connect to Exchange via Outlook 2007. i think the problem is because the exchange client connector is hosted on the 101 subnet and not the 201... i do not know how to make it available to both.. any ideas? Please just ignore this POST. It does work was just an interference between the users keayboard and chair!!

air duster time ^^

Very impressed with your work Kullenen_Ask. its about time something like this came around. all i ever see is winbuilder or builder that. "I don't want the end result i want to understand how to get the end result". Which is provided by your information. 100% thanks, and hope to hear more from you in the future.

you could always try injecting the xxx.XML file directly into the image. guidelines on how to do it are in the waik. also i think WDS uses the unattend file on wds server and ignopre that in the image. try it there.

CD's and UFD's boot differently with NTLDR. what version of windows PE are you using, as this will help with diagnosis.

just to simplify your task a bit. you should use WDS to boot wim images and use WDS to load RIS if need be, it has a legacy section.

open the catalog file instead of the image for now. i had the same issue and thats what worked for me.

open a command prompt windows and load the program from the CD in there to see what its saying/doing.

i think you'll find that it doesn't. it just uses a generic one that setup uses and the HAL is built during setup. /minint switch is Winpe

ok so i couldn't find your issue using my winpe, but now i have made one from scratch, and window.confirm most definetly isn't working. im gonna look into it as MS don't respond easily, as i need this function also. you could use the winpe built on the windows disk as this works fine (install.wim 1 \windows\system32\recovery\winre.wim..... until we see whats really going wrong or find a fix. [EDIT] OK GOT IT WORKING [/EDIT] OPEN DEPLOYMENT TOOLS COMMAND PROMPT COPYPE AMD64 C:\WINPE IMAGEX /MOUNTRW WINPE.WIM 1 MOUNT DISM /IMAGE:MOUNT /ADD-PACKAGE /PACKAGEPATH:"C:\PROGRAM FILES\WINDOWS OPK\TOOLS\PETOOLS\AMD64\WINPE_FPS\WINPE-HTA.CAB" DISM /IMAGE:MOUNT /ADD-PACKAGE /PACKAGEPATH:"C:\PROGRAM FILES\WINDOWS OPK\TOOLS\PETOOLS\AMD64\WINPE_FPS\WINPE-MDAC.CAB.CAB" DISM /IMAGE:MOUNT /ADD-PACKAGE /PACKAGEPATH:"C:\PROGRAM FILES\WINDOWS OPK\TOOLS\PETOOLS\AMD64\WINPE_FPS\WINPE-SCRIPTING.CAB" DISM /IMAGE:MOUNT /ADD-PACKAGE /PACKAGEPATH:"C:\PROGRAM FILES\WINDOWS OPK\TOOLS\PETOOLS\AMD64\WINPE_FPS\WINPE-WDS-TOOLS.CAB" DISM /IMAGE:MOUNT /ADD-PACKAGE /PACKAGEPATH:"C:\PROGRAM FILES\WINDOWS OPK\TOOLS\PETOOLS\AMD64\WINPE_FPS\WINPE-WMI.CAB" DISM /IMAGE:MOUNT /ADD-PACKAGE /PACKAGEPATH:"C:\PROGRAM FILES\WINDOWS OPK\TOOLS\PETOOLS\AMD64\WINPE_FPS\EN-US\LP_EN-US.CAB" DISM /IMAGE:MOUNT /ADD-PACKAGE /PACKAGEPATH:"C:\PROGRAM FILES\WINDOWS OPK\TOOLS\PETOOLS\AMD64\WINPE_FPS\EN-US\WINPE-HTA_EN-US.CAB" DISM /IMAGE:MOUNT /ADD-PACKAGE /PACKAGEPATH:"C:\PROGRAM FILES\WINDOWS OPK\TOOLS\PETOOLS\AMD64\WINPE_FPS\EN-US\WINPE-MDAC_EN-US.CAB" DISM /IMAGE:MOUNT /ADD-PACKAGE /PACKAGEPATH:"C:\PROGRAM FILES\WINDOWS OPK\TOOLS\PETOOLS\AMD64\WINPE_FPS\EN-US\WINPE-SCRIPTING_EN-US.CAB" DISM /IMAGE:MOUNT /ADD-PACKAGE /PACKAGEPATH:"C:\PROGRAM FILES\WINDOWS OPK\TOOLS\PETOOLS\AMD64\WINPE_FPS\EN-US\WINPE-WDS-TOOLS_EN-US.CAB" DISM /IMAGE:MOUNT /ADD-PACKAGE /PACKAGEPATH:"C:\PROGRAM FILES\WINDOWS OPK\TOOLS\PETOOLS\AMD64\WINPE_FPS\EN-US\WINPE-WMI_EN-US.CAB" XCOPY MOUNT\WINDOWS\SYSTEM32\MSHTA.EXE MOUNT\WINDOWS\SYSWOW64 IMAGEX /UNMOUNT MOUNT /COMMIT Now that is everything exactly what i have done to the letter no deviations, nothing. and its working.... give it a go

yes i noticed it too. i could no long do answers unless i specified the true value forgive me as this is prolly gonna be messy. sub startbutton_OnClick blnanswer "do you want to install XP apps" if blnanswer = "true" then diskpart if blnanswer = "false" then exit sub 'next function if true msgbox "About to deploy image, a window will popup to confirm when the process is complete. this can take upto 30 mins" set objapp = createobject(wscript.shell") objapp.run "imagex /apply" & " %path%\%imagename%" & " %index%" & " %pathtodeploy%",0,true blnanswer "image apply complete, would you like to reboot now?" if blnanswer = "true" then shutdown if blnanswer = "false" then exit sub end sub sub diskpart set objapp = createobject("wscript.shell") objapp.run "diskpart /s script.txt",0,true 'hides that **** command prompt window end sub sub shutdown set objapp = createobject("wscript.shell") objapp.run "wpeutil -reboot",0,true end sub problem is from there it will process that sub and continue down the original sub so i had to stop it by using the exit sub command if the value was false.

odd because when i was testing the code it was pointing to my syswow64 folder (vistax64). i ran your script and yest it does seem to return system32 folder. also the \1.txt = root\1.txt thats why i said to remove the "\". so it calls systemfolder\1.txt. check it out, this is the code i used and although the variable is calling system32 folder, it fails even though the file is in system32, but if you put the file in syswow64 it returns with the working value. Sub Window_Onload Dim fso, tempfile, tfolder, tname, tfile Set fso = CreateObject("Scripting.FileSystemObject") Set tfolder = fso.GetSpecialFolder(1) MsgBox(tfolder) Set objfso = CreateObject("Scripting.FileSystemObject") If objFso.FileExists(Sysfolder & "1.txt") Then msgbox "moo" else msgbox "baa" end if End Sub