Jump to content

p4ntb0y

Member
  • Posts

    237
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United Kingdom

Everything posted by p4ntb0y

  1. Alan you may want to have a look at "wsname.exe" great little app helped us with our offline mode deployment by USB and DVD/CD using WINPE 2.0
  2. If your in the UK and you PM me I could send the BDD2005 / 2007 Training virtual labs used by Microsoft for training Gold Partners. It covers everything including Biztalk for zero provisioning Regards
  3. Ok I made a mistake creating loads of silent installs with a post here on how to create a silent install with 7zip, anyhows I got carried away and made all my "Core Apps" into 7zip exe's but I want to deploy these by Group Policy... So can you convert an exe to msi? or can you create a simple MSI to go with the exe? I am new to packaging so sorry if its a dumb question
  4. Why can you not just do a ipconfig /all and pipe this to a file??
  5. It fails at the F6 text mode part? If you go thru the install and you select F6 and then load the drivers by floppy it should work fine so now you need to add this into your textmode folder within the $oem$ or use nilite to intergrate or look at a previous post on how to add intell chipset drivers in 15 steps
  6. Just saw in your post you installed the WAIK this contains winpe 2.0 The OSD FP Contains winpe 2005 winpe 2.0 contains imagex.exe for version 1.0 WIM's OSD FP contains ximage for Version 0.9 WIM's untill you update to the latest patch which will the give you ximage version 1.0 WIM's Imagex can open mount etc ximage WIM's but ximage can not open imagex WIM's ximage is wrapped up within the Image Capture Wizard
  7. Alan can you PM me I have just done a massive rollout with SMS OSD FP and the BDD 2.5 Enterprise. First off you are using the OSAD FP with the latest update? as the old version of the OSD creates 0.9 version WIMS where the new update creates version 1.0 WIMS. How are you creating you WINPE within the SMS Distro point? if you are then your Winpe image will not have WMI support. The best way is to download the BDD 2.5 go into the Computer Imaging System into CONFIG.HTA set you paths for your OS and winpe. Set you settings up for how you want to build your Reference PC. once you have done that go to the Winpe Tab of the Config.hta, add any extra NIC drivers etc with the handy "Add extra Nic Drivers" buttton and then create you winpe the config.hta will do this automatically for you. You actually get a choice of the type of winpe disk you would like to make.... Deploy winpe disk. Lab winpe disk. Once you have your "winpe.iso" you can then extract this out (Ultra iso or something) and point the SMS DP to update your winpe within SMS to include the additional files required. Your can the use the sms capture cd to capture your WIM back to your SMS DP. You can then set up your zerotouchinstallation.vbs by using the customsettings.ini file man you can anything in that puppy! are you using SQL or are you going to set everything within the custosettings.ini? When you PM me I will send you a link to a very good site for OSD FP and the BDD it would be rude to post it here.
  8. how are you building your winpe 2005 image? are you using the windows 2003 sp1 source or xpsp2?
  9. Yes you can add the drivers in offline mode by using "peimg /inf=Inf_path" or load the drivers in Online mode by using "drvload.exe inf_path " No if your using any of the broadcom drivers that have a the virtual bus ie Multifuction types like the nc373i you will need to load the ris drivers and not the normal drivers. As said before all of this is in the Winpe.chm within the windows aik dir. You can get the ris drivers either from an earlier post or head over to the broadcome site (depending if you have broadcom) not sure what card you have you can run devon or driverquery
  10. how do you want to boot the ram drive CD? RIS? or USB? I have a usb pen booting to ram and its allways letter x: easy to do and works well
  11. Thats inrestesting I have to check this out, does this still apply if all my USB ports are USB 2.0?
  12. It can be but it can load any drivers you like. IE I have to load the ris drivers for my Broadcom NetXtreme 2 Network drivers for Networking. So let me get this right your going to deploy vista by using winpe 2 then load your vista image onto your box , but you need support for you LOM "Lan On Board" so are you deploying your winpe image by RIS? Whats your setup?
  13. Does you old "box" boot at all with either winpe 1.6 or bartspe? How about use winpe 2.0 and have a speaical lite touch cd/dvd for this box?
  14. Ok what is the Nic your trying to install and what version of winpe are you using?
  15. p4ntb0y

    Winpe 2.0

    @ bjorne78 Are you using the HP Scripting toolkit ie conrep and the acu? I have not be able to get this running yet as winpe 2 can not install the sysmgmt service required for HP tools. I be intrested if you have any input on this matter?
  16. Are you doing a diskpart first? I would do a diskpart either in wimbom.ini or thru the startup script first before you format and install.
  17. Most drivers are support out of the box for vista pe. To install additional drivers in the offline mode you would use peimg /inf="location of you inf" to do this by the online mode you use drvload. Its all in the CHM that come with the WAIK. Why would you want to use the WSIM? Or do you want to create a base image of vista that goes on all you hardware? Have a look at the BDD2007.
  18. Hi I have a winpe 2 on a USB Flash pen usb 2.0. Now when I boot the usb on a nc6400 its fast I mean 20 secs. When I Boot on a nc6220 or dc7600 its very slow? All the kit is USB 2.0 and I have plugged the pen drive into the root usb. Its kind of wierd? anyone had or has a workaround for this problem?
  19. Does anyone know how to add a service to winpe 2.0? I need to add the sysmgmt service to my winpe 2.0 for the HP scripting toolkit as I get "Health Driver not loaded error" I belive these are system device drivers that work in winpe 2005 but do not load in winpe 2.0. I really hope HP get on the case and release there win32 drivers for winpe 2.0 :-) Its a shame I have to go back to the winpe 2005. I take it if I want to takee out imagex from winpe 2.0 all I need is the winfltr.inf, winfltr.sys,wimgapi.dll and imagex.exe?
  20. Yeah did some more tests the bus emulator is not supported so I downloaded the The NetXterme II monolithic drivers which are just for the network drivers and not the bells and whistles. link here Drivers this works great! Many thanks Jazkal you were on the right track!
  21. I did read somewhere that it could be the ndis drivers not knowing alot about this I can not be sure.. Has anyone got any broadcom 2 ndis drivers working in winpe 2 or vista?
  22. Ahhhh this is driving me crazy! I just tried the same disk on a D510 compaq evo and I get the same thing!
  23. Ok I have tested the network using winpe 2005 with the hp drivers and this works ok. I made another winpe 2 disc with the drivers for winpe 2005 and again no go. I noticed that there are a some dll winsock2 files within an i386 dir I suspect that these need to be placed somewhere within the winpe 2 disc (I am thinking system32) Somehow the network loading part has changed somehow within winpe 2 as they are the same drivers but handled another way, I dont really understand it at the moment. I burn another disc off and try and place the dll,s files within system32. I wonder if HP are doing aa support pack for winpe 2 like they did for winpe 2005?
  24. The Network card is a NC373i
  25. Hi the Driver is the HP NC-Series Multifunction Driver for Windows Server 2003. I have extracted the drivers and there is an i386 folder with 2 sys files and 3 dll files. The normal sys, inf and cat files I will check with devcon when I am in work next and see what driver is actually loaded on my Windows 2003 Server. I suspect that I require some these dll's to go somewhere on the winpe disc. can you manually add drivers to winpe 2? instead of using peimg /inf? Can I copy all of the inf files to \winpe\inf and all the sys files to \winpe\drivers and the cats to \winpe\catroot and then drop the dll's into system32, I will do some tests as always...... thanks guys
×
×
  • Create New...