Br4tt3

I started out with a custom WinXP SP2 slipstreamed CD with an updated TXTSETUP.SIF file. In my case the custom TXTSETUP.SIF file was intact when it had been transfered to the WinPE build. Didnt run into to any troubble as to this specific problem yet.. I had edited the file for supporting RAID controllers. So far so good...

Well... u have to get a hold off WinPE 1.5 if I am not misstaken.. that is the one based on WinXP SP2. WinPE 1.2 is the one based on WinXP SP1. Obtain it from Microsoft. Call tha redmond guys..

What are the appz and check the application dev section (MSI / InstallShield) of www.msfn.org... but a good start would be the name of the appz u r trying to install:

Check to see wheather the machines affected by the odd behaviour has newest BIOS etc etc. Also make sure they meet the crtirieas for PC98 compatability (PXE) and so on.... then again there might be a common thing amongst the not working comps (as a bios version in common and so on) ? I u can attach a CD like u said and install XP onto that machine but it crashes with RIS my guess it has to do with NIC or firmware ( read the spec for RIS / PXE ) think it is called PC98 compatability or something. if they meet all the criterias (all new pc's does) then it is just a matter of adding drivers and stuff..

Yup, if i hit F6 at boot I can load 3 of 6 drivers (for diffrent devices) while the 3 remaining drivers doesnt work with WinPE 1.2. Also, HDD access is acchieved with the 3 mentioned above, 3 remaining doesnt list any when running: list volume (diskpart) Thats about it, now I have moved onto WinPE 1.5 ( where the same driver seems to work for all devices as long as I change the TXTSETUP.OEM file for each chipset I want to support. Any1 know why MS changed this behaviour in WinPE 1.5 vs WinPE 1.2? The one that states, only chipsets listed in the [Defaults] section is used when doing PnP? Take care.

not for sure but i guess it would be a reg entry or a binary file that contains the settings... check out MS BDD 2.0, it contains scripts for manipulating those kinds of things. It prolly is in the user hive somewhere. BDD 2.0 is still beta though... go to beta.microsoft.com

Yes... I am running a similar configuration. Sure thing. However, cannot provide u with documentation as it is corporate documentation. Here is what to think of: 1. Get ur Win2k3 server with RIS up and running 2. Get a WinXP i386 folder, slipstream SP2 into it... that is A. sp2.exe -x (extract) to temp B. temp\i386\update\update.exe -s:c: (indicates that the WinXP gold i386 folder is placed in the root of c:) C. run the risetup.exe (from script if u wanna do unattended, then append a .inf file, or manually) pointing to the slipstreamed WinXP SP2 folder D. edit any stuff u want to be fixed in ur .sif on the RIS as drivers and stuff $OEM$ What to think of: default, sp2 firewall is enabled... only TCP/IP ports needed for installation is allowed. Any other / system ports must be manually opended from the .sif file. Default ports are stuff like getting DNS / DHCP / GPO... Keep truckin

That or run a startupscript with the same entries (/renew) that will excute as soon as they start the comps up again...

As always... .vbs is alot nicer!

Thx dude.. I will sketch some on it and try it out, get back to u.

Dunno but a good way of starting the troubbleshooting is to get a MS "gold" WinXP (with slipstreamed SP) and perform the RIS installation from that CD instead of using Dell's provided CD.

got it... enable support or delegation with ACL on NetServices Object in Site & services. 1. Open ADSIEdit 2. Change ACL to Write + Create All Child object on NetServices 3. Rock n Roll Hint = Use netsh.exe for the tasks so they can be produced via .vbs scripting or a service account for installations ( RIS for example )

net use X: \\server\shared folder /user:domain\username

makecab.exe...

Mine was the perc 4 driver for Windows 2003 avail from Dell webby...

Hmm... and another question then when it comes to adding masstorage drivers to a WinPE (1.5) build this time. In the winpe.chm file it states: Customizing WinPE, Adding masstorage drivers: ( txtsetup.oem file) "Many driver packages today support a variety of mass-storage devices, and only those listed in the [Defaults] section will be loaded...." Oki, I have confirmed that the first listed entry in the [Defaults] section in the txtsetup.oem file gets loaded correctly and works when I am accessing the disk from within WinPE, lets call it RAID1A. [Defaults] scsi = RAID1A Since I want to support multiple chipsets of the same software driver as in RAID1B and RAIDC from within the same driver package I want to add multiple entries to the[Defaults] section as in: [Defaults] scsi = RAID1A scsi = RAID1B scsi = RAID1C This part doesnt work for me as I have tried it a coupple of times. Alternative 2. Have multiple driver folders in WinPE ( with the same software driver in each driver folder, just diffrent entries to the [Defaults] section specifying a new chipset for every new driver folder to the TXTSETUP.OEM file ) This alternative seems foolish to me as I would quickly run out of space avail on the CD as I would increase the overhead for adding a driver for each chipset I want to support. Any suggestions to solve the issue? Or is it by design ( I guess )? Sorry for boring u with these booring driver questions....

Thx man.. didnt get it working with the manual adding mass storage way. Tried the utility u mentioned and voila! Also tried to add the same driver using txtsetup.sif file in WinPE and that turned out to do the trick as well.. which leads me to wonder if there is any diffrence between adding a masstorage driver through winpeoem.sif or by using txtsetup.sif... well.. thx anyway, saved my day!

Sure thing... Background scenario: We are using WinPE (1.2) based on WinXP for kicking off installations of Win2003 Server. We are using Dell as hardware vendor for the servers. Until recently we have been able to find Windows 2003 drivers for masstorage devices that would plug in just fine into WinPE (1.2). Since we need to write to disk to acchieve installation features we need to prep the WinPE image with those specific drivers. A coupple weeks ago Dell released a new RAID driver for newly supported RAID devices. I download the driver for Win2003 and plug into WinPE, I can support 2 out of a total 7 RAID devices all supported by the same family driver included from Dell. This way I know the driver added to WinPE works, however, the same driver for Win2003 cannot support all the diffrent flavours of chipsets included in the family driver and the installation crasches... Dell of course wont support XP drivers for their server hardware so I am bound to use Windows 2003 that just work on some chipsets... As a consequence, if I cant provide native driver support for the distribution mechanism (WinPE) for an installation I cant guarentee that it will work. To verify that the drivers provided by Dell works for all the chipsets of the RAID devices, I plugged them into RIS and ran the installation from there... everything worked as a charm tried to make WinPE based on Win2003 source but it turned out to be the same (n00bish me) and tried WinPe (1.5) which also is based on WinXP which gave me the same result.... So when will MS release WinPE based on Win2003 ?

My bad when it comes to the error... forgot to remove a string in my old WinPE folder.. However, the main question still remains open.. what is the main idea about building WinPE of an Win2003 vs WinXP source if one can not get around the problem of adding native drivers to WinPE ? Most Win2003 / Win2000 drivers can be plugged into WinPE(1.2) but not all.. I guess WinPE then mostly is suited for client distribution (rather then server) as one cannot guarantee native driver support to the distribution mechanism.. Any1 wanna take me up on that? Thx...

Hi Question: Can I use a Windows 2003 Server CD to build the WinPE folder structure? And would this generate a Win2003 "based" WinPE as when building WinPE from a WinXP CD? I am using WinPE 1.2 and was reading the winpe.chm document that states under mkimg.cmd: "This command builds the file set for the Windows Preinstallation Environment (Windows PE, also known as WinPE) from any Windows XP or Windows .NET Server 2003, Standard Edition product CD.." I have tried to build an .iso file which works but when I use it, it just fails with: "File txtsetup.oem caused an unexpected error (18) at line 1814 in d:\srv03rtm\base\boot\setup\oemdisk.c." Since I have not added any drivers to the image.. just taken it from scratch I dont know why it fails? Regards Sausage Eater From .SE

Hi folks... I am using WinPE 1.2 ( the one based on WinXP ) and I am trying to add masstorage device drivers to the CD. I know how to add drivers of this kind, done a coupple of times, however, this time it will not work. I am trying to boot a server with a RAID controller and when running diskpart it crasches. My question is: If I insert a ordinary XP CD and hit F6 to specify additional drivers and the OS swallows the drivers, would this be a GO sign for WinPE 1.2 ? and if the OS BSOD's cuz of the drivers, will this be a adequeate test to say that the drivers are not applicable on WinPE (1.2) since the drivers a ordinary meant for Windows 2003 server? Hope u get the issue... Thanks and keep truckin

I have been searchin for the same kind of tool / procedure.... only thing every1 is talking about is killing explorer for some entries in the reg, however that usualy doesnt solve issues that require reboots... Dunno if it is by design it wont work as i can guess every1 in here has had the same question.

Hi I am trying to delegate dHCPClasses creation by means of vbscript and an service account created for that purpose. I am going to use this for distrubtion of installation of RIS installations (which require authorization in dhcp). When authorizing a server in dhcp, one need to modify the attribute "dhcpservers". My question: which specific permission do I need to delegate to the account for it to be able to create specific dhcpserver entries?????

Whoooppps... slipped.. that would be TXTSETUP.SIF file...

I used the second supported way of adding raid / scsi support to your image, TXTSETUP.INF. This way turned out to be much easier and flexible than the answer.sif file & txtsetup.oem way. The main pro was that u didnt lack the support of natively Win supported boot devices.... even though it is a mess dealing with driver files. And by the way... MSFN had the answer again! Keep truckin...