gadget

I've been playing this game for nearly 3 years now - must get some sleep soon. If you jump in give me a shout ingame or leave an eve mail- Lyle Waters -

It looks as though the drivers and inf file in the $oem$ directory do not match the flies under i386 etc. I had the same sort of thing with the intel pro 1000 nic and found an older version of a sys or inf (can't remember which) file laying in x:\i386 which was screwing it up. From cd the $oem$ drivers are not read so it uses the drivers from i386. As the system is booting from pxe I would delete all sys, inf etc files under i386 and copy the files from the $oem$.

see http://www.msfn.org/board/index.php?showtopic=48392&hl=yukon search here or microsoft to add nic drivers to the oem$ directories as well. Been covered many times here before. edoit: or http://www.msfn.org/board/index.php?showto...$oem$

Booting from pxe is kinda different. Do you get the pe environment or does it halt with error message during startup. If its the latter then the text mode setup drivers and modified .inf file need putting into an $oem$ directory on your image. Plenty of 'Network Driver' issues on the forum, just do qa quick search and all will be revealed.

Difficult to know where to start. What do you want to do - CD boot or use ris.... There are plenty of walkthroughs on this site for added network cards if required. CD's are dead easy, network boot via ris is a bit more involved. Treat PE as a rather large boot disk and the startnet.cmd is the autoexec.bat. Jou will need to copy across the ghost files prior to making the cd, this is described in the tutorials well. To run ghost just add ghost32 to the end of startnet.cmd. Using a more complex batch file, visual basic n stuff like that, you can write whole applications to do a whole range of wierd n wonderful things. What I would suggest 1st though is to complie (makeimg.bat) to an ISO then run vmware, mounting the cd as the iso image. Much faster and easier to debug. Best thing is to play with it and post more specific answers. PE is a great way to pretend to develop stuff for 6 -12 months at work as nobody else understands it..

Anyone know the correct procedures for getting the net logon service running in PE2005. Makes life easier to logon to a netware NDS tree? TIA

WMI support is cak in PE. Outside basic system informtion: memory, NIC, processor, hdd details: you will not get a lot of details. WMI will not report anything on floppy, cd rom, sound, video, ect... It is on my list of things to do to try and increase the repository but in the great circle of life, it's pretty far down on mt to do list. Do an example script to just pull the mac address or summing like that to test that wmi is working. Also, take of the crappy firewall as that seems to fig a lot of things up...b

Can't beleive I am such an oldtiming noob. A command I used years ago fulfils this problem: net time \\server /set I really need to start thinking at the most obvious levels before wasting a post.

Looking for ways to sync the client winpe system with the domain or standalone server. w32tm service is not available in pe, if I could add this service it would be best. Any help would be appreciated.

I am using loginw32.exe to login to and map network drives to my netware 5.1 servers. All works fine but I would really like to login from the command line as there are so many servers and combinations of network resources I need Pe to map drives to. The login scripts are a pain in the neck (toooo many). Anyone acheived this yet in a pure 32bit WinPE environment?

Did you download the trial? Been playing for over two years now. Definatly not a game you just turn on and play for 5 minutes and there is no game over button either. If you are not careful, it can eat away all of your time....

No Eve-Online players. What a shame......

i know the /min switch but what it's the original cmd window, the 1st one that shows, the one where you type exit and it restarts pe. Gonna play with some vb6 me thinks. Found a program consolesize works great.

my problem is not wsh. I have a program (not by me) that requires these to run. PS. How do you minimise that original command window that opens up?

Let me guess, you are now a retired stripper... I still have problems running some vb scripts cos I havent msvbvm50/60.dll registered. Might get round to changing that soon.

Download the latest win2k drivers from http://downloadfinder.intel.com/scripts-df...llName=Windows* 2000 Server〈=eng created a new folder fot the RIS section %PERoot%\$oem$\1\e1000 added the oem path OemPnpDriversPath = \e1000 (under unattended) in the \i386\template\ristndrd.sif file. copied the drivers into this, replaced the inf file with the attatched inf file ( http://downloadfinder.intel.com/scripts-df...ystems〈=eng ) deleted any oem*.inf file from the i386 tree deleted any entries for e1000*.* anywhere on my image copied all the driver files to i386\system32 inf file into \inf folder sys files into system32\drivers deleted all *.pnf files in i386 restarted the binlsvc (net stop/Net start) The problem that I had was in the oem driver section for the e100 card, somehow an old set of e1000 drivers was in there as well. e1000nt5.inf

I think you may need the msvbvm50 and 60 dll in i386 and registered in winpesys.inf when you compile PE. Same as what is here: http://www.msfn.org/board/index.php?showtopic=33396 If i find the correct stuff i'll let you know, just cant get my hands on my own documentation.

Trying to acheive the same thing here. I had it with just the: msvbvm50.dll msvbvm60.dll files but I have lost the winpesys.inf entries required to register the dll's

I dont personally use explorer to view the network. I'd know the resource and map from command line: net use [drive]: \\netorkPC\Share then type in the requested user name. If that fails, I'd contact Winternals support I thinks. Umm, that copy of erd looks pirated?

No wonder I was getting stuck. Found a rouge file in the e100b that belongs to the e1000 driver. Found it by accident as well. All is fine now... Used the latest drivers and inf file as per intels website.

No wonder I was getting stuck. Found a rouge file in the e100b that belongs to the e1000 driver. Found it by accident as well. All is fine now... Used the latest drivers and inf file as per intels website.

Does the Wbemoc.inf file represent what wmi classes are in pe as wmi in pe is rather basic. If I can increase wmi funtionality it would make my life much easier...

-If you build a new WinPE using Windows 2003 Server with SP1 as source, you will be able to integrate newer Intel® PRO Network Connections Drivers e1000325.inf without any problems.- Hmm, didnt work for me

I cant get round this pro 1000 problem. I have spk1 which cannot be uninstalled and the servers are now imbedded into our environment, rebuilding is not really an option. Pro 1000 boots into PE but dont work correctly in PE - wont resolve names or connect to Netware boxes. Have tried the above but could really do with some help. Can you supply the driver versions you used Br4tt3 and a copy of the inf file. Thanks

Just putting winbomi in the root of the cd/image solves this