superbikkel

I posted the solution here

With Recource Hacker. Really simple.

I solved that problem. My PE loads a menu that connects to a server. When it's not able to connect to the server, the tools menu appears with some functions disabled, preinstallation is also disabled. It also compares the version of the CD with the minimum allowed version approved by the server. If I don't want a certain version to be used, I disable it by incrementing the minimum version on the server. The techs can still use the old version with degraded functionality, but because of that, they all upgrade the CD .

How did you get Computer Management working?? It refused to load when I tried it.

Did that. No go.

It seems possible to burn with BartPE, but I'd like to know if it is possible to burn with the "real" WinPE. I tried Nero5 and CDBurnerXPPro. Both fail. Nero gives me "SCSI errors" and CDBurner won't load, it can't find a file it needs.

I disagree with Chris. We use PE to preinstall systems (with network connection), to test systems, to virusscan systems, to reque data etc (with or without network connection). I would classify myself as a corparate user, but I have a lot packed on the PE disc: * Preinstall functionality * McAfee virusscan * Total Commander * Nero * Filescavenger * Partitionmagic * Ghost * CPU-Z/AIDA * Memtest * HD-Tune * CPU stability test * Nero CD Speed * PC Angel * PCI bus scan

I started with WinPE before I ever heard of BartPE. When I found out about BartPE, I wouldn’t give up my version anymore It does most of what I want it to do, and so far I could always get everything (well, it's not that much) to work. APE is really used in an industrial environment. We use it to preinstall systems, to refresh test-systems (with Ghost32), to do basic tests and Anti-Virus runs on systems from customers. I want to make sure my PE is legal, and working perfectly so therefore I stick with the official WinPE.

Very nice work Troglodyte. I'm looking forward to the releases of your plugins. Maybe we can also use them in real WinPE.

Nope. There will always be programs that won't work I'm afraid. Example: I have not seen any indication that it is possible to include Direct-X into WinPE.

No worries my boy, however not much use posting your so called creation if you cannot part your knowledge on how you made this for everyone else here? Topic is "Post your screenshots", not "Post your knowledge". I cannot post APE but I can help anyone with a specific question on how to get something working (if I know how). So: want to know something: ask! Only if it compromises intelectual property of my employer, or it can cause economical damage to my employer I will not answer.

To get WMI support, you need at least the XP SP2 OPK CD. It has updated tools to build the source for WinPE. If you have this OPK CD, just add /WMI to the MKIMG command.

Got it working already. Just copy all the files SoftThink added to the original OPK to your PE and start it with the START.EXE from the system32 directory. Be pacient as it takes a while before the Angel menu appears.

I have a XP SP2 RC1 including the OPK CD to test, and I got a lot of info along with it. From the manual on the SP2 OPK CD: Adding Plug and Play Device Driver Support to Windows PE You must first add Plug and Play device driver support to your Windows PE image before you can add drivers to that image. If you add only network adapter drivers, you do not need to enable Plug and Play device driver support in Windows PE. When you enable Plug and Play device driver support in Windows PE, you can directly access any Plug and Play device through the corresponding Windows device driver from within Windows PE. For example, if you copy the associated .inf and driver files for the computer's video card, the video performance of Windows PE is much faster because Windows PE uses the actual Windows video driver instead of the standard VGA driver that Windows PE usually loads.

You can´t add anything else to PE than NIC and mass/storage drivers with the current versions of PE. With the PE based on XP SP2 (soon te be released) it will be possible to add more drivers, like sound and graphiccard drivers.

Some of you might be using PC Angel LE (PCALE) as restore utility. Then you know that it runs of its own custom PE CD. I just hate to waste CD's on 2 versions of PE (my preinstall PE and the PCALE PE), so I'm trying to run PCALE from my custom PE. I copied all the files they added to my PE, but it refuses to work properly. I think they employ some registry hacks, en I know they use a ramdrive (which I also use, on a different letter though, mine is R:, theirs is Z:). Dis somebody get this to work?

Did it take a long time???? Between the first version and the last version is about 1,5 years. Everytime my collegues or I came up with something that we wanted in PE, and I integrated it. It is coded in Visual Basic, and it uses no plugins like Bart does. Before you all think I'm just bragging here: I have on occasion looked how Bart did it.

APE is not a plugin. I think it will be hard to implement at any other location that where we use it. It heavily interacts with a server to store some data for example. Also, as I made this partially during working time, and for my company, I think they will be less then pleased when I distribute APE. Some of our competititors would like to have it (in fact: have asked me for it). But I'd like to hang on to my job for a little while longer BTW: It's based on plain WinPE 1.2, not BART's.

Here are my screens. I made this WinPe for the company I work. I Photoshopped the name from the company, so it's unreadable....... Boot Screen Init Main Menu Tool Menu About Screen Edit: Changed Images to links.

The Marvel Yukon is a tricky card. yukonwxp.inf -> \I386\INF yukonwxp.sys -> I386\SYSTEM32\DRIVERS gewmi.mof -> I386\SYSTEM32\WBEM\MOF (create the directory!) mrvdlg.dll -> I386\SYSTEM32 I couldn't get this one to work at first, but I placed the gewmi.mof file in the wrong dir.

I have that Intel driver working in XP PE. Couldn't get it to work in the beginning, gave up in the end. Later, I created a new revision of PE for some other card (without removing the Intel NIC files) and to my surprise, the Intel NIC worked, and it still does several PE revision further....... I am playing with XP PE SP2 RC1 at the moment, and it has a new tool to inject drivers into PE (before creating the ISO). I think this tool also works with the current PE, as it only copies the files to the right locations. I'd like to supply the file to you, but I think that violates the copyrights...

The problem is, that the location of files is uncertain. With most NIC drivers, you put the .INF file in I386\INF, the .SYS file in I386\SYSTEM32\DRIVERS and all other files in I386\SYSTEM32. But some drivers, like the nVidia or Intel NIC drivers, put the files in other locations. What you can do to find the right locations, is install Windows, install the NIC, and search the files. Write down where the files are found, and put them in the same location on the WinPE CD. This works almost all the time, I only have a problem with the new nForce3-250 chipset.

nvenet.cat -> delete jedih2rx.bin -> delete ramsed.bin -> delete jedireg.pat -> delete nvenet.sys -> system32 and system32\drivers nvenetxp.inf -> inf Works for me. BUT: anyone got the nForce3/250 drivers working?