Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

About EvilGuinness

  1. 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. Thanks a lot for your answer, it's just what I wanted to hear Hum, last question : I have problems with 32 bits programs that don't work under PE for unknow reasons...is there anything new in the next version that says "all the 32 bits progs will work"?
  2. Thanks for your answer, I'm now sure that I didn't miss anything. Just a question : where do you find the changes for the next release of PE? I can't find it on the Microsoft website.
  3. It seems you simply can't do something like this...I tried lots of things, I read lots of docs, but I found nobody who worked on this, no docs (except for network/mass storage drivers), no help. It never worked. edit : I'm working on the official PE, I don't know BartPE. The only "light Windows" that can do this seems to be Windows Embedded...
  4. That's impressive! I didn't know that someone could do something like that with PE. Did this take a long time? Erf, too bad for me, I'm not working on PE for something the users could use, just for something that does all the work automatically...so I just don't need something beautiful and user-friendly like APE.
  5. Oh...I found it...you can read all the doc coming with PE, you won't find the word "ram drive"...yeah, you can hit me with 17'' screens, I work on it since some months, and I didn't see something as "big" as this all this time. (last "off-topic") PE is a good product, they just forgot something : the documentation. For all what I did, I found the informations I needed on this forum, and never on Microsoft website or documentation. Thanks a lot!
  6. Him, I read here that ram drives will only be supported in the next release and I found nothing about it in my PE documentation...did I do a mistake? Where can I find information about this? I don't know how to activate it! Nevertheless, it's only a little part of my problems Edit : oh, well... http://www.msfn.org/board/index.php?showtopic=16886 I don't know if it's official, but it's something that uses only Microsoft products...I'll try. And sorry for the off-topic But it seems these methods don't work each time...It will be hard to say that to my boss : "I will use a method that can work...no, it doesn't come from Microsoft..."
  7. Maybe with BartPE or with plugins for BartPE which work with the official PE. But when you can only use the official PE...you must wait for the next release! I work in a firm that uses only Microsoft products, and the technical service/hotline is something very important (and expensive..) here. If we use programs that are not in PE, Microsoft won't give the technical support. I think you understand the problem I have... Shortly, my problem is "if it's not official, I can't use". And officially, there's no ram drive in PE for the moment, and the only drivers that are supported are network and disk drivers. We have to many PC's and different configurations, we can't take any risk.
  8. That's just what I'm trying to do : replace DOS with PE for preinstallation tasks...you're the first person I "meet" who does something like this, and I work on this since three months now I'm working with the official PE. I don't know if PE could solve your "reboot problem" but with PE, I've LOTS of problems related with drivers, for example (although PE is a very good OS for tasks like configuring installation, you can't do anything with PE itself, it's heavyly "protected"...). Now if you use BartPE, I don't know if it would be better. Using PE as replacement of DOS is something very...I don't find the word...I mean there's VERY few people that do it now, even specialised firms are just beginning to work with PE like that. Even Microsoft can't answer, for some questions about PE, and there's just one person knowing WinPE who works in HP....and we hope we don't know more about PE than him. It's very useful for OEM and simple preinstallation tasks (configuration of the sysprep/riprep image, for example), but if you want to go further with PE itself (adding drivers, or test the hardware), it will be hard for the moment (PE doesn't yet support the RAM drives for example). You can't do anything more with PE as a preinstallation environment than with DOS (hum, well, I'm exagerating a bit )
  9. Hello, First, I'm not using VBS for web development....si I think it's the good forum I'm trying to use a software that gives the MAC adress in VBScript, and to write the result of this command in a file. Here is my line : set VLOB_WSHSH = WScript.CreateObject("WScript.shell") retour = VLOB_WSHSH.Run("d:\compname.exe /d ?m 1>>d:\adresse.txt 2>>d:\erreurs.log",1,True) But the file is never created...it's supposed to contain the MAC adress. I tried lots of things, from VLOB_WSHSH.Run("d:\compname.exe /d ?m >> d:\adresse.txt") to lines like the first I show...I can write/read on the drive, I tried to create the file before writing in it but it's useless. If someone can help me....thanks!
  10. Oh, I forgot something very useful : compname...it's a really great piece of software I discovered here and which I use every day now It can display alll what you want, such as IP or MAC adress, and lots of stuff like that....you can even change these informations. It's available on this page.
  11. You can't use WMI in windows PE : it's not implemented, as written in the doc describing the limitations. To get the IP, you can use the ipconfig command and then take what you want in what is given in the result.
  12. Normally you can just do what is described in the PE documentation : put the files in the right place...but it seems it doesn't work as expected, it's not the first time someone has this problem. I don't have the solution...but it's becoming a common issue :/
  13. Hello, I'm trying to do a VBS/WSH script which gives the amount of RAM that is installed on the computer... I boot from the network on win PE and I need this information just after installing WSH. I found lots of scripts doing that, but it always uses WMI that is not implemented in the official Win PE (I can only work with the official PE). Is there a solution to my problem? (even if it's not a script, just a program, or whatever...just something that gives this information ) Thanks!
  14. I think you'll have to write it....it's written in the documentation : windowsPE can't run 16 bits programs. I searched something to "bypass" this but I didn't find anything. The problem is that it's not a problem of plugin...there's simply no possibility to run 16 bits programs. WindowsPE doesn't have "WoW32" (windows on windows32), the software that allows this sort of thing. That's why I have a lot of problems migrating from DOS to Windows PE. Good luck :/
  15. If I remember well, it depends on the motherboard you use : you can do this only on recent hardware. Booting off (eh, I would have said "from", I'm improving my english skills ) a USB key isn't implemented on motherboards older than 18 months or something like that... Anyone to confirm?
  • Create New...