gadget

Wasn't fixed, have worked someting out though: On your freshly booted WinPE (I'm testing 3.1) do an ipconfig /all to check the lease obtained time then run time xx:xx where xx:xx hours and minutes is less than the lease obtained time... Do ipconfig /all and see the lease obtaied time..... ???????????????????? Tested on a win 7 box with an 8 hour lease and it done exactly the same thing....... Problem with this 1876 date is that the system cannot renew it's ip address when it expires.......

Fixed: Removed net time and no need for w32time, just called an api NetRemoteTOD and returns the time correctly for a remote server... Thanks to http://www.codeguru.com/vb/gen/vb_system/network/article.php/c1637/Get-Time-from-Remote-NT-Server.htm and thanks for all the suggestions here....

Thanks, secure standalone network - no internet might spoof an internal timeserver though... one of the things i am looking at..

There is a reason for this! Net /time is deprecated, which would explain why the old version still works. Looks like you need to the use Windows time service now. But that is a great error! It is a fab error, unfortunatly w32tm is not available (or am I missing something) in WinPE 2 and above..

Hi, Just noticed a problem here which possible has been happening since we first introduced WinPE 2.0. WinPE 1.6 and below does not have his error, I use WinPE all flavours here to deploy images onto systems. One task is to set the system clock using net time /domain:****** /set /yes but this corrupts the Lease Obtained time to a point in the past << see. Due to the qty of systems attaching, the lease time is eight hours. Under normal operation, the systems are complete and removed before the lease expires but some systems will remain connected and when the lease expires, it cannot obtain a new address and will drop off the network causing configuration issues. doing ipconfig /release and the /renew is hit and miss if it works. No errors on the dhcp server, and no requests sent from the client. w32tm is not supported in pe nor is _local_time part of its wmi subset,,, Anyone come across this at all... I use a windows 2003 wds with legacy. Tested: net time \\server_name /set / yes Windows 2000 domain Windows 2008 domain Logging on with domain credentials prior to running net time pausing script after network initialisation then running net time pausing all over the script after net time, including ip.../ /release /renew at varying pause times, sometimes the lease renews, most times it will not... and on and on and on

Either works but cmd is the preferred MS way of thinking.

Simplest form, in startnet.cmd CLS Echo "Select: ANd press [RETURN] echo "1. Run Ghost" echo "2. Flash Bios" then create two cmd files in system 32: 1.cmd [path]\ghost32.exe and 2.cmd Instert instructions to flash bios Messy but works... Good sample of an HTA menu is here: Could be easilyu adapted.

Thanks, I know, we have been running WDS in mixed mode since release. The thing I am attempting is to enter a eight digit code into the RIS OSchooser screens, this then loads a custom PE1.x image. With PE2 and above, you can only get a list menu so when updating a core PE2/3 image, I can only hope that the legacy computers still work, and in the most part they do. If I keep adding PE images to the WDS then the list gets stupidly long and the engineer can easily select the incorrect image. We have 600 systems a day connecting to WDS or RIS, different models and manufactures, so managing a PE2/3 image is a nightmare. The above restarts the WDS process from RIS but displays all the PE2/3 options. I have nearly got there, just need to isolate and load the required BCD file, just cannot get the bootloader to change location from \\reminst\boot........

I know i'm digging this one up from the grave but,,,,, What I am attempting is to get a winpe 2.0 or 3.0 to boot using RIS. I like the 'oschooser' menu system in RIS. Using the above actually loads the wds start screen again showing the options of wims available and the Remote Installation. I have tried using custom BCD's ect but keep getting back to the same wds screen. Has anyone acheived booting winpe 2/3 through RIS?

Hmm, I like Explorer. Seems a lot faster and I switch between several different networks al the time and it's much faster adapting to the new network. With Vista and below I was having to release/renew ip and flush/register dns every network switch. Once the indexing is complete, searches are super fast. Oh, I think I prefere it over Snow Leopard.....

Well, I really like the Win7 Start menu, the ability to lock programs to the Task Bar and hit Start and type nero sou to locate the program much easier and faster then running through a old menu system. I am a sys admin come developer and run/support all flavours of windows, mac os x, unix, and a lot of command line stuff... I have been using Win7 for months now and adore the interface. Its fast and easy.... Join the revolution..

I would rename diskpart.bat to .cmd and do not call the batch file the same as the executable.

Deleted. My post about PEShutdown is so dated, please ignore it.

Don't forget, the assigned drives are only for thw winpe session. They may appear different in your installed operating system.

Search for PESHUTDOWN.EXE on this forum

in startnet, use the full path for the diskpart.txt, do not use speech marks

Set sata to compatability or slipstream the drivers using something like nlite. But it definatly sounds like the bootsec problem as well.

We cant use bartpe here as evrything has to be a genuine MS solution. ramdrv.sys can be copied from any server 2003 sp1 installation or extracted from the install media. Else i cn 'post' it to you.

add ramdrv.sys to system32/drivers then add this to winpesys.inf just before the language specific section (Recompile with mkimg.cmd). This shuld give a ??mb ramdrive on z: ;###################################################################################### ;Ramdrive ;RAMDRV HKLM,"SYSTEM\ControlSet001\Control\Class\{78A1C341-4539-11D3-B88D-00C04FAD5171},"Class",0000000000,"Sample" HKLM,"SYSTEM\ControlSet001\Control\Class\{78A1C341-4539-11D3-B88D-00C04FAD5171},"Icon",0000000000,"-5" HKLM,"SYSTEM\ControlSet001\Control\Class\{78A1C341-4539-11D3-B88D-00C04FAD5171}\0000","DriverDate",0000000000,"11-14-1999" HKLM,"SYSTEM\ControlSet001\Control\Class\{78A1C341-4539-11D3-B88D-00C04FAD5171}\0000","DriverDesc",0000000000,"Ramdrv Driver" HKLM,"SYSTEM\ControlSet001\Control\Class\{78A1C341-4539-11D3-B88D-00C04FAD5171}\0000","DriverVersion",0000000000,"5.0.2183.1" HKLM,"SYSTEM\ControlSet001\Control\Class\{78A1C341-4539-11D3-B88D-00C04FAD5171}\0000","InfPath",0000000000,"ramdrv.inf" HKLM,"SYSTEM\ControlSet001\Control\Class\{78A1C341-4539-11D3-B88D-00C04FAD5171}\0000","InfSection",0000000000,"DiskInstall" HKLM,"SYSTEM\ControlSet001\Control\Class\{78A1C341-4539-11D3-B88D-00C04FAD5171}\0000","InfSectionExt",0000000000,".NT" HKLM,"SYSTEM\ControlSet001\Control\Class\{78A1C341-4539-11D3-B88D-00C04FAD5171}\0000","MatchingDeviceId",0000000000,"ramdrv" HKLM,"SYSTEM\ControlSet001\Control\Class\{78A1C341-4539-11D3-B88D-00C04FAD5171}\0000","ProviderName",0000000000,"Microsoft" HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE",,0x00000010 HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","Capabilities",0x00010001,0x0 HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","Class",0000000000,"Sample" HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","ClassGUID",0000000000,"{78A1C341-4539-11D3-B88D-00C04FAD5171}" HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","ConfigFlags",0x00010001,0x4 HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","DeviceDesc",0000000000,"Ramdrv Driver" HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","Driver",0000000000,"{78A1C341-4539-11D3-B88D-00C04FAD5171}\0000" HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","HardwareID",0x00010000,"ROOT\ramdrv" HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","Mfg",0000000000,"Microsoft" HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000","Service",0000000000,"Ramdrv" HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000\Control","ActiveService",0000000000,"Ramdrv" HKLM,"SYSTEM\ControlSet001\Enum\Root\SAMPLE\0000\LogConf",,0x00000010 HKLM,"SYSTEM\ControlSet001\Services\ramdrv","DisplayName",0000000000,"Ramdrv Driver" HKLM,"SYSTEM\ControlSet001\Services\ramdrv","ErrorControl",0x00010001,0x1 HKLM,"SYSTEM\ControlSet001\Services\ramdrv","ImagePath",0x00020000,"System32\DRIVERS\ramdrv.sys" HKLM,"SYSTEM\ControlSet001\Services\ramdrv","Start",0x00010001,0x0 HKLM,"SYSTEM\ControlSet001\Services\ramdrv","Type",0x00010001,0x1 HKLM,"SYSTEM\ControlSet001\Services\ramdrv\Enum","0",0000000000,"ROOT\SAMPLE\0000" HKLM,"SYSTEM\ControlSet001\Services\ramdrv\Enum","Count",0x00010001,0x1 HKLM,"SYSTEM\ControlSet001\Services\ramdrv\Enum","NextInstance",0x00010001,0x1 HKLM,"SYSTEM\ControlSet001\Services\ramdrv\Parameters","BreakOnEntry",0x00010001,0x0 HKLM,"SYSTEM\ControlSet001\Services\ramdrv\Parameters","DebugComp",0x00010001,0xffffffff HKLM,"SYSTEM\ControlSet001\Services\ramdrv\Parameters","DebugLevel",0x00010001,0x0 HKLM,"SYSTEM\ControlSet001\Services\ramdrv\Parameters","DiskSize",0x00010001,0x1000000 HKLM,"SYSTEM\ControlSet001\Services\ramdrv\Parameters","DriveLetter",0000000000,"Z:" HKLM,"SYSTEM\ControlSet001\Services\ramdrv\Parameters","RootDirEntries",0x00010001,0x200 HKLM,"SYSTEM\ControlSet001\Services\ramdrv\Parameters","SectorsPerCluster",0x00010001,0x2

I would download the win2k3 including sp1 to be honest. I don't think the correct files that identify the windows build version get updated correctly when slipstreamed. Sorry

As far as I am aware, it will not run on the microsoft's deployable xp winpe. I did mention bartpe. I did look into this a couple of years ago but just opted for win2003 winpe.

You need to use windows 2003 sp1 as the source. or BartPE (can't beleive i said that!) Why use such an old PE. USe WinPE2.1 or above, much easier...

Jazkal - The system works fine with PE2.x, The scrips fail. These are custom scripts from another department and I cannot modify them. They are currently working on the transition. Tripredacus - I have examined the inf, copied and registered all dlls, cats ect. VB and VBS run fine but stops any computer running and wmi calls. Been designing pxe and winpe systems for nine years now. This one has me stumped!

Anyone still using PE 1.6? Due to legacy scripting, we need 1.6 to deploy some images but the newe Lenovo T400 uses the latest Intel 82567LM. Adding these drivers completely destroys any WMI calls which stops the scripting. This affects our entire estate of computers. Any one seen this before or know a work around? Unfortunatly PE2.x is a long way off being developed for this deployment process.

You will find it is a harware issue. I see hundreds of new systems each day go through here each day and very occasionally, one system will not connect to the network correctly within winpe2 yet are fine in their own o/s or pe1.x. Most of these are IBM/Lenovo but we do get the occasional HP. I wasted so much time on getting this fixed, flashing this, that and the other that now I just fail them and they are earmarked for manual/dvd installations. Waiting for one to come through so I can seize it and test with pe2.1.