ChrisBaksa

Actually... It's called GHOST32.EXE Chris

Use nLite. Easy as Pie. Makes the ISO file and all. I created a bootable SP2 cd last week with nLite. Chris

The INF file goes in the I386\INF directory and the SYS file goes in the \I386\System32\Drivers Directory. Depending on the driver... you may need additional files which would go in \I386\System32. Chris

Hotfixes in PE are simple. One for one Replacement of the file. Chris

Just got my hands on 1.5. Funny... The help file is listing it as PE 2004! Chris

I have my TAM on this now.. I should have it by next week. I have a beta copy of 1.5 but I don't like wasting time with betas. Chris

I had a feeling it was directory related. Based on the C:\\ that the error was showing. Lets chalk that one up to a .... DOH! We've all been there once or twice! If you script your build process.. toss a line in that will change dir to that location first. Chris

Your best bet is to bite the bullet and get on the network. Use the Netconfig tool (it's on this forum somewhere). It will let you config a static ip. Or Put up a dhcp server when you build a new system. It's a whole new world with network connectivity. Can you use DVD? Thats an option as well. Chris

What you can remove depends on what you need to begin with., Microsoft is supplying a list of files that can be safely removed in the next release of PE. Here is the list and the accompanying text explaines it. Reducing the Size of Windows PE The non-customized size of Windows PE is about 160 megabytes (MB). By removing non-essential files, you can reduce the 32-bit version of Windows PE to an on-disk image size of 86 MB. Important Removing files from Windows PE may cause your custom applications to fail. List of files: fonts\8514fix.fon fonts\8514oem.fon fonts\8514sys.fon fonts\ahronbd.ttf fonts\andlso.ttf fonts\angsa.ttf fonts\angsab.ttf fonts\angsai.ttf fonts\angsau.ttf fonts\angsaub.ttf fonts\angsaui.ttf fonts\angsauz.ttf fonts\angsaz.ttf fonts\app850.fon fonts\arialbd.ttf fonts\arialbi.ttf fonts\ariali.ttf fonts\ariblk.ttf fonts\artrbdo.ttf fonts\artro.ttf fonts\browa.ttf fonts\browab.ttf fonts\browai.ttf fonts\browau.ttf fonts\browaub.ttf fonts\browaui.ttf fonts\browauz.ttf fonts\browaz.ttf fonts\cga40850.fon fonts\cga40woa.fon fonts\cga80850.fon fonts\cga80woa.fon fonts\comic.ttf fonts\comicbd.ttf fonts\cordia.ttf fonts\cordiab.ttf fonts\cordiai.ttf fonts\cordiau.ttf fonts\cordiaub.ttf fonts\cordiaui.ttf fonts\cordiauz.ttf fonts\cordiaz.ttf fonts\cour.ttf fonts\courbd.ttf fonts\courbi.ttf fonts\coure.fon fonts\courf.fon fonts\couri.ttf fonts\david.ttf fonts\davidbd.ttf fonts\davidtr.ttf fonts\dosapp.fon fonts\ega40850.fon fonts\ega40woa.fon fonts\ega80850.fon fonts\ega80woa.fon fonts\estre.ttf fonts\framd.ttf fonts\framdit.ttf fonts\frank.ttf fonts\gautami.ttf fonts\georgia.ttf fonts\georgiab.ttf fonts\georgiai.ttf fonts\georgiaz.ttf fonts\impact.ttf fonts\kartika.ttf fonts\latha.ttf fonts\lsans.ttf fonts\lsansd.ttf fonts\lsansdi.ttf fonts\lsansi.ttf fonts\lucon.ttf fonts\lvnm.ttf fonts\lvnmbd.ttf fonts\l_10646.ttf fonts\mangal.ttf fonts\micross.ttf fonts\modern.fon fonts\mriam.ttf fonts\mriamc.ttf fonts\mriamfx.ttf fonts\mriamtr.ttf fonts\mvboli.ttf fonts\nrkis.ttf fonts\pala.ttf fonts\palab.ttf fonts\palabi.ttf fonts\palai.ttf fonts\raavi.ttf fonts\rod.ttf fonts\rodtr.ttf fonts\roman.fon fonts\script.fon fonts\serife.fon fonts\seriff.fon fonts\shruti.ttf fonts\simpbdo.ttf fonts\simpfxo.ttf fonts\simpo.ttf fonts\smalle.fon fonts\smallf.fon fonts\sserife.fon fonts\sseriff.fon fonts\sylfaen.ttf fonts\symbol.ttf fonts\tahoma.ttf fonts\tahomabd.ttf fonts\times.ttf fonts\timesbd.ttf fonts\timesbi.ttf fonts\timesi.ttf fonts\tradbdo.ttf fonts\trado.ttf fonts\trebuc.ttf fonts\trebucbd.ttf fonts\trebucbi.ttf fonts\trebucit.ttf fonts\tunga.ttf fonts\upcdb.ttf fonts\upcdbi.ttf fonts\upcdi.ttf fonts\upcdl.ttf fonts\upceb.ttf fonts\upcebi.ttf fonts\upcei.ttf fonts\upcel.ttf fonts\upcfb.ttf fonts\upcfbi.ttf fonts\upcfi.ttf fonts\upcfl.ttf fonts\upcib.ttf fonts\upcibi.ttf fonts\upcii.ttf fonts\upcil.ttf fonts\upcjb.ttf fonts\upcjbi.ttf fonts\upcji.ttf fonts\upcjl.ttf fonts\upckb.ttf fonts\upckbi.ttf fonts\upcki.ttf fonts\upckl.ttf fonts\upclb.ttf fonts\upclbi.ttf fonts\upcli.ttf fonts\upcll.ttf fonts\verdana.ttf fonts\verdanab.ttf fonts\verdanai.ttf fonts\verdanaz.ttf fonts\vga850.fon fonts\vga860.fon fonts\vga863.fon fonts\vga865.fon fonts\vgafix.fon fonts\vgaoem.fon fonts\vgasys.fon fonts\vrinda.ttf fonts\webdings.ttf fonts\wingding.ttf msagent help spcmdcon.sys bootfix.bin winbom.ini System32\winpe.bmp System32\fus2base.sys System32\fpnpbase.sys System32\fpnpbase.usa System32\ditrace.exe System32\portmon.exe System32\rsvp.exe System32\peer.exe System32\net.hlp System32\xlog.exe System32\eqnloop.exe System32\eqndiag.exe System32\eqnlogr.exe System32\odbccp32.cpl System32\c320tnt.cod System32\c218tnt.cod System32\Drivers\te_protu.qm System32\Drivers\gm.dls System32\Drivers\te_protu.sm System32\Drivers\*.bin System32\Drivers\*.usa System32\Drivers\*.t4 System32\Drivers\te_protm.pm2 System32\Drivers\el656ct5.sys System32\Drivers\fusbbase.sys System32\Drivers\fxusbase.sys System32\Drivers\fpcibase.sys System32\Drivers\fpcmbase.sys System32\Drivers\atmuni.sys System32\Drivers\stlnata.sys System32\Drivers\emu10klm.sys System32\Drivers\cinemst2.sys System32\Drivers\el656se5.sys System32\Drivers\digirlpt.sys inf\net10.inf System32\DRIVERS\tdkcd31.sys inf\net1394.inf inf\net21x4.inf System32\DRIVERS\dc21x4.sys inf\net3c556.inf System32\DRIVERS\EL556ND5.sys inf\net3c589.inf System32\DRIVERS\el589nd5.sys inf\net3c985.inf System32\DRIVERS\el985n51.sys inf\net3sr.inf System32\DRIVERS\srwlnd5.sys inf\net5515n.inf System32\DRIVERS\ip5515.sys inf\net557.inf System32\DRIVERS\e100b325.sys inf\net559ib.inf System32\DRIVERS\D100IB5.SYS inf\net575nt.inf System32\DRIVERS\el575ND5.sys inf\net650d.inf System32\DRIVERS\dfe650d.sys inf\net656c5.inf System32\DRIVERS\el656CD5.sys inf\net656n5.inf System32\DRIVERS\el656ND5.sys inf\net713.inf System32\DRIVERS\mxnic.sys inf\net83820.inf System32\DRIVERS\DP83820.sys inf\net8511.inf System32\DRIVERS\ADM8511.SYS inf\netac300.inf System32\DRIVERS\ac300nd5.sys inf\netali.inf System32\DRIVERS\ALI5261.SYS inf\netambi.inf System32\DRIVERS\AMB8002.SYS inf\netamd.inf System32\DRIVERS\pcntn5m.sys inf\netamd2.inf System32\DRIVERS\pcntpci5.sys inf\netamdhl.inf System32\DRIVERS\pcntn5hl.sys inf\netan983.inf System32\DRIVERS\an983.sys inf\netana.inf System32\DRIVERS\adptsf50.sys inf\netasp2k.inf System32\DRIVERS\aspndis3.sys inf\netb57xp.inf System32\DRIVERS\b57xp32.sys inf\netbcm4e.inf System32\DRIVERS\BCM4E5.SYS inf\netbcm4p.inf System32\DRIVERS\bcm42xx5.sys inf\netbcm4u.inf System32\DRIVERS\bcm42u.sys inf\netbrzw.inf System32\DRIVERS\BRZWLAN.sys inf\netcb102.inf System32\DRIVERS\cb102.sys inf\netcb325.inf System32\DRIVERS\CB325.SYS inf\netcbe.inf System32\DRIVERS\cben5.sys inf\netce2.inf System32\DRIVERS\ce2n5.sys inf\netce3.inf System32\DRIVERS\CE3N5.SYS inf\netcem28.inf System32\DRIVERS\cem28n5.sys inf\netcem33.inf System32\DRIVERS\cem33n5.sys inf\netcem56.inf System32\DRIVERS\cem56n5.sys inf\netcicap.inf inf\netclass.inf inf\netcpqc.inf System32\DRIVERS\cnxt1803.sys inf\netcpqg.inf System32\DRIVERS\n1000nt5.sys inf\netcpqi.inf System32\DRIVERS\n100325.sys inf\netcpqmt.inf System32\DRIVERS\cpqtrnd5.sys System32\ctmasetp.dll System32\DRIVERS\rocket.sys inf\netdefxa.inf System32\DRIVERS\DEFPA.sys inf\netdf650.inf System32\DRIVERS\dfe650.sys inf\netdgdxb.inf System32\DRIVERS\bioprime.bin inf\netdlh5x.inf System32\DRIVERS\DLH5XND5.sys inf\netdm.inf System32\DRIVERS\DM9PCI5.SYS inf\nete1000.inf System32\DRIVERS\e1000nt5.sys inf\nete100i.inf System32\DRIVERS\E100ISA4.sys inf\netejxmp.inf System32\DRIVERS\IBMEXMP.sys inf\netel515.inf System32\DRIVERS\EL515.sys inf\netel574.inf System32\DRIVERS\el574nd4.sys inf\netel5x9.inf inf\netel90a.inf System32\DRIVERS\el90xnd5.sys inf\netel90b.inf System32\DRIVERS\el90xbc5.sys inf\netel980.inf System32\DRIVERS\el98xn5.sys inf\netel99x.inf System32\DRIVERS\EL99XN51.SYS System32\DRIVERS\EL99XRUN.OUT inf\netepicn.inf System32\DRIVERS\lanepic5.sys inf\netepro.inf System32\DRIVERS\epro4.sys inf\netex10.inf System32\DRIVERS\ex10.sys inf\netf56n5.inf inf\netfa312.inf System32\DRIVERS\FA312nd5.sys inf\netfa410.inf System32\DRIVERS\fa410nd5.sys inf\netfjvi.inf System32\DRIVERS\f3ab18xi.sys inf\netfjvj.inf System32\DRIVERS\f3ab18xj.sys inf\netfore.inf System32\DRIVERS\PCA200E.BIN System32\DRIVERS\PCA200E.SYS inf\netforeh.inf System32\DRIVERS\FOREHE.SYS inf\netibm.inf System32\DRIVERS\IBMTOK.sys inf\netibm2.inf System32\DRIVERS\IBMTRP.SYS inf\netklsi.inf System32\DRIVERS\usb101et.sys inf\netktc.inf System32\DRIVERS\KTC111.SYS inf\netlm.inf System32\DRIVERS\lmndis3.sys inf\netlm56.inf inf\netlnev2.inf System32\DRIVERS\LNE100.SYS inf\netmadge.inf System32\DRIVERS\mdgndis5.sys inf\netmhzn5.inf System32\DRIVERS\xem336n5.sys inf\netnf3.inf System32\DRIVERS\NetFlx3.sys inf\netngr.inf System32\DRIVERS\Ngrpci.sys inf\netnovel.inf System32\DRIVERS\ne2000.sys inf\netosi2c.inf System32\DRIVERS\otc06x5.sys inf\netosi5.inf System32\DRIVERS\otceth5.SYS inf\netpc100.inf System32\DRIVERS\pc100nds.sys inf\netpnic.inf System32\DRIVERS\lne100tx.sys inf\netpwr2.inf System32\DRIVERS\smcpwr2n.sys inf\netrlw2k.inf System32\DRIVERS\rlnet5.sys inf\netrtpnt.inf System32\DRIVERS\RTL8029.sys inf\netrtsnt.inf System32\DRIVERS\RTL8139.sys inf\netsis.inf System32\DRIVERS\sisnic.sys inf\netsk98.inf System32\DRIVERS\sk98xwin.SYS inf\netsk_fp.inf System32\DRIVERS\SkFpWin.SYS inf\netsla30.inf System32\DRIVERS\Sla30nd5.sys inf\netsmc.inf System32\DRIVERS\smc8000n.sys inf\netsnip.inf inf\nettb155.inf System32\DRIVERS\tbatm155.sys inf\nettdkb.inf System32\DRIVERS\tdk100b.sys inf\nettiger.inf System32\DRIVERS\tjisdn.sys inf\nettpro.inf System32\DRIVERS\tpro4.sys inf\netvt86.inf System32\DRIVERS\fetnd5.sys inf\netw840.inf System32\DRIVERS\W840ND.sys inf\netw926.inf System32\DRIVERS\w926nd.sys inf\netw940.inf System32\DRIVERS\w940nd.sys inf\netwlan.inf System32\DRIVERS\NetWlan5.img System32\DRIVERS\NetWlan5.sys inf\netwlan2.inf System32\DRIVERS\wlandrv2.sys inf\netwv48.inf System32\DRIVERS\wlluc48.sys inf\netx500.inf System32\DRIVERS\pcx500.sys inf\netx56n5.inf inf\netxcpq.inf System32\DRIVERS\cpqndis5.sys WinSxS\x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.0.0_x-ww_8d353f13\gdiplus.dll system32\alrsvc.dll system32\avmc20.dll system32\avmcapi.dll system32\avmenum.dll system32\browser.dll system32\browseui.dll system32\certcli.dll system32\cmprops.dll system32\cnbjmon.dll system32\console.dll system32\cryptnet.dll system32\cscdll.dll system32\ctmasetp.dll system32\ctmrclas.dll system32\dbgeng.dll system32\dbghelp.dll system32\dciman32.dll system32\ddraw.dll system32\devmgr.dll system32\dgclass.dll system32\dgnet.dll system32\dgrpsetu.dll system32\diapi2.dll system32\diapi232.dll system32\diapi2nt.dll system32\disrvpp.dll system32\disrvsu.dll system32\divaprop.dll system32\divasu.dll system32\dmconfig.dll system32\dnsrslvr.dll system32\duser.dll system32\eqnclass.dll system32\extmgr.dll system32\gptext.dll system32\halsp.dll system32\hccoin.dll system32\icmp.dll system32\imgutil.dll system32\initpki.dll system32\io8ports.dll system32\iologmsg.dll system32\kbdbe.dll system32\kbdbr.dll system32\kbdca.dll system32\kbdda.dll system32\kbddv.dll system32\kbdes.dll system32\kbdfc.dll system32\kbdfi.dll system32\kbdfr.dll system32\kbdgae.dll system32\kbdgr.dll system32\kbdgr1.dll system32\kbdic.dll system32\kbdir.dll system32\kbdit.dll system32\kbdit142.dll system32\kbdla.dll system32\kbdmac.dll system32\kbdne.dll system32\kbdnec.dll system32\kbdno.dll system32\kbdpo.dll system32\kbdsf.dll system32\kbdsg.dll system32\kbdsp.dll system32\kbdsw.dll system32\kbduk.dll system32\kbdusl.dll system32\kbdusr.dll system32\kbdusx.dll system32\ksuser.dll system32\licwmi.dll system32\linkinfo.dll system32\loadperf.dll system32\localspl.dll system32\lz32.dll system32\mfc42.dll system32\mmfutil.dll system32\mobsync.dll system32\mprui.dll system32\msafd.dll system32\mscat32.dll system32\mscms.dll system32\msftedit.dll system32\msgsvc.dll system32\msimg32.dll system32\msjet40.dll system32\msls31.dll system32\mssign32.dll system32\mssip32.dll system32\msvcirt.dll system32\mswstr10.dll system32\netevent.dll system32\netui2.dll system32\nwapi32.dll system32\nwcfg.dll system32\nwevent.dll system32\nwprovau.dll system32\nwwks.dll system32\oakley.dll system32\odbc16gt.dll system32\odbc32gt.dll system32\odbcbcp.dll system32\odbcconf.dll system32\odbccp32.dll system32\odbccr32.dll system32\odbccu32.dll system32\odbcji32.dll system32\odbcjt32.dll system32\odbcp32r.dll system32\odbctrac.dll system32\oleacc.dll system32\oleaccrc.dll system32\olecli32.dll system32\olecnv32.dll system32\oledlg.dll system32\olepro32.dll system32\olesvr.dll system32\olesvr32.dll system32\olethk32.dll system32\perfctrs.dll system32\perfnw.dll system32\pstorec.dll system32\query.dll system32\rasdlg.dll system32\rnr20.dll system32\rsvpmsg.dll system32\rsvpperf.dll system32\rtipxmib.dll system32\scecli.dll system32\security.dll system32\servdeps.dll system32\shdocvw.dll system32\snmpapi.dll system32\softpub.dll system32\spdports.dll system32\spoolss.dll system32\spxcoins.dll system32\spxports.dll system32\stlnprop.dll system32\sxports.dll system32\ufat.dll system32\ureg.dll system32\url.dll system32\urlmon.dll system32\utildll.dll system32\vdmdbg.dll system32\w32topl.dll system32\wdigest.dll system32\win32spl.dll system32\winhttp.dll system32\winipsec.dll system32\winscard.dll system32\wshisn.dll system32\wzcsapi.dll system32\xmlprov.dll system32\xmlprovi.dll

I do the same for version control. I keep a file called VERSION.TXT. At the top is my version control data. See below. [Version] WINPE=1.2 Compiled OS Binaries=WIN2K3 STD Build Version=3.9 After that is my change control data. [Version History] ----------------------- 30-06-04 - Version 3.9 ----------------------- Chris Baksa - Updated Compaq/HP Raid Controller Driver (CpqCissm.sys). Adds support for the new 6i controller. Chris Baksa - Updated the IBM ServeRaid Software to Version 7.0 Chris Baksa - Incremented the PE build Verison to 3.9. ect... ect...ect... My VB scripting that is on the CD when I compile retrevies the Version info from this file (in this case 3.9) and then checks the PE_VERSION.INI on the network which look like this... [PECD_valid] 1.5=no 1.6=no 1.7=no 1.8=no 1.9=no 2.0=no 2.1=no 2.5=no 3.0=no 3.1=no 3.2=yes 3.5=no 3.6=yes 3.8=yes 3.9=yes This way I have full contol over what version can and can't be used. Once connected... all menus and software run from the server. Chris

superbikkel, In a corporate environment where every thing you do has to go through a Change Mannagement process and be signed off by counless people... It does not pay to keep modifying the CD. It's simply easier to make changes on a network rather than have 50+ SA's yell at you because you have a new CD that they have to burn. Granted... those tools are nice and usefull, but I'm not an SA... I am an Engineer. (No disrespect to those SA's out there. I started there too) Chris

If I recall... Sysprep can ONLY reside in the c:\sysprep folder. It is hard coded to look there. Here is a cut and past from teh Sysprep help file about how to set it up... Click Start, click Run, and then type: cmd At the command prompt, change to the root of the system drive (%SYSTEMDRIVE%), and then type: md sysprep From the \Support\Tools\Deploy.cab file of the Windows XP product CD, copy Sysprep.exe and Setupcl.exe to the Sysprep folder that you created. Chris

I build all flavors of vmware... Workstation, ESX, GSX... It works well. You will need a mass controller driver for a few of them which is avaliable on VMWares site. Correct... The default boot order for a new session needs to be changed so the CD Rom drive is 1st. Ran into that last year. I've done extensive work with VMware and would be happy to assist anyone who is having issues. Chris

FYI... PE 1.5 (not officially out yet) has full support for Xp SP2. PE 1.2 was not designed to be able to build a XP SP2 cd. I don't think submitting a bug to MS will get very far because of the physical support for the versions as I described above. PE 1.6 is the version that you will need for Win2k3 Server SP1. That version has been delayed. Chris

Most of us Corporate folks don't have much on our PE Disks. There is no need when you have a large network and the ability to access it from just about anywhere. Quick booting and a streamlined PE disk is much more important than what is on it Chris

The i386 folder does not really need to be in the same EXACT folder. Make Dir called DISTRIBUTION or some thig like that and then copy your i386 files into it. You unattended install will call teh files from any location or dir as long as you specify it on the install line. The problem you are going to run into is space on the CD. Chris

You can install windows into any directory you want. The process is the same. [unattended] UnattendMode=FullUnattended OemSkipEula=Yes OemPreinstall=YES DriverSigningPolicy=Ignore OemPnPDriversPath= TargetPath=\WINDOWS FileSystem=ConvertNTFS Just change teh TARGETPATH line in teh UNattend.txt Chris

PXE booting will be possible with Version 1.6 which is not yet avaliable. I have all my code in place for my PXE build... And I'm stopped at haveing an ISO that will PXE boot. RIS is not an option for me in our environment. Microsoft says it will be at least 4 - 6 weeks before thay will even have a beta of 1.6. Chris

Sorry ... I don't know what is happening to your PE. Are you compiling manually or are you using Barts? Make sure you didn't copy any file into the system32 dir. If you give me an E-mail address I'll zip up my dir and mail it to you. Chris

Image the partition. The last version of Smart Start with the System Partiton option was version 5.5. If you make one image ( which is just over 3 megs in size using powerquest tools) you will not need to to do anything else. It can be used with any Legacy Server that needs the system partiton. Create a look up table (ini file) so your build script can reference it to see if it needs the partition or not. Like this... [Partition] DL360=Y DL380=Y DL380G3=N DL580=Y DL580G2=N The imaged partition is deployed in seconds. Chris

Just finished and tested. Here is what I did. Keep in mind that MY PE is comliled with 2003 Server Binaries. If you Use XP, then use the same process but take keep the XP drivers. (altho the 2003 drivers should work too) Delete everything you currently have under the IBM_SERVERAID directory (leave the folder). Copy the entire folder (and sub directories) "WINDOWS" from the root of the ServRaid 7 CD into the IBM_SERVERAID directory. Delete the following Directories (not required and will keep size down) IBM_SERVERAID\windows\manager IBM_SERVERAID\windows\win2k_xp IBM_SERVERAID\windows\winnt IBM_SERVERAID\windows\win2003\sata\cmdline IBM_SERVERAID\windows\win2003\scsi\cmdline On the ServeRaid 7 CD... Open up the \diskette\scsi\win2003.img with Winimage or some other imaging software. Extract the txtsetup.oem file and place it in the root of the IBM_SERVERAID folder. Your SIF file should look like this.... [OemDriverParams] OemDriverRoot="drivers\additional_oem" OemDriverDirs=IBM_SERVERAID If you added additional Drivers... Add them to the end like so... OemDriverDirs=IBM_SERVERAID, MORE_DRIVERS Compile your new PE CD. Chris

I'm going to Update my PE disk with the SereRaid 7 drivers today. I'll get back to you when I've completed and tested this. Based on your post I think it's just a path issue. In theory... All you need to do is copy the directory structure off the Drivers cd and add the path to it to the SIF file. No modification of the files in the directory are required. If you are updating a current driver... Then it gets tricky. I had to update the existing Smart Array 5xxxx driver to the new 5xxx/6xxx driver. That was a pain in the Backside. Chris

No. I have modified the TXTSETUP.OEM. If you keep the same driver dir structure as it came on the Cd, you will not need to modify the file. You issue might be the winpeoem.sif You are missing the entry for OemDriverRoot Yours.... [OemDriverParams] OemDriverRoot="" OemDriverDirs=\system32\Drivers\IBMRAID Mine... [OemDriverParams] OemDriverRoot="drivers\additional_oem" OemDriverDirs=IBM_SERVERAID, VMWARE_SCSI, IBM_MEGARAID Chris

Here is what works for me... The ServeRaid Driver is NOT included in Win2k3 or XP. It is 100% a new addition. The Destination directory for my driver is ... I386\System32\Drivers\ADDITIONAL_OEM\IBM_SERVERAID My winpeoem.sif file looks like this... [Version] signature="$Windows NT$" [OemDriverParams] OemDriverRoot="drivers\additional_oem" OemDriverDirs=IBM_SERVERAID, VMWARE_SCSI, IBM_MEGARAID I have not integrated the Latest Servraid 7 drivers yet But they should be a direct replacement of what I have in my IBM_SERVERAID Directory which looks like this... Directory of I386\System32\Drivers\ADDITIONAL_OEM\IBM_SERVERAID 05/04/2004 01:50 PM <DIR> . 05/04/2004 01:50 PM <DIR> .. 06/17/2003 07:45 AM 30,509 readme.txt 06/17/2003 07:45 AM 1,202 txtsetup.oem 05/04/2004 01:50 PM <DIR> win2003 2 File(s) 31,711 bytes Directory of I386\System32\Drivers\ADDITIONAL_OEM\IBM_SERVERAID\win2003 05/04/2004 01:50 PM <DIR> . 05/04/2004 01:50 PM <DIR> .. 05/04/2004 01:50 PM <DIR> driver 0 File(s) 0 bytes Directory of I386\System32\Drivers\ADDITIONAL_OEM\IBM_SERVERAID\win2003\driver 05/04/2004 01:50 PM <DIR> . 05/04/2004 01:50 PM <DIR> .. 05/04/2004 01:50 PM <DIR> server 0 File(s) 0 bytes Directory of I386\System32\Drivers\ADDITIONAL_OEM\IBM_SERVERAID\win2003\driver\server 05/04/2004 01:50 PM <DIR> . 05/04/2004 01:50 PM <DIR> .. 05/04/2004 01:50 PM <DIR> i_v 05/04/2004 01:50 PM <DIR> powerpc 0 File(s) 0 bytes Directory of I386\System32\Drivers\ADDITIONAL_OEM\IBM_SERVERAID\win2003\driver\server\i_v 05/04/2004 01:50 PM <DIR> . 05/04/2004 01:50 PM <DIR> .. 07/15/2003 08:27 AM 8,779 ibmnfrd3.cat 06/17/2003 07:45 AM 35,328 nfrd960.sys 06/17/2003 07:45 AM 32,009 nfrdci03.dll 06/17/2003 07:45 AM 5,450 oemsetup.inf 4 File(s) 81,566 bytes Directory of I386\System32\Drivers\ADDITIONAL_OEM\IBM_SERVERAID\win2003\driver\server\powerpc 05/04/2004 01:50 PM <DIR> . 05/04/2004 01:50 PM <DIR> .. 07/15/2003 08:27 AM 8,623 ipsraid3.cat 06/17/2003 07:45 AM 85,504 ipsraidn.sys 06/17/2003 07:45 AM 32,009 nfrdci03.dll 06/17/2003 07:45 AM 5,215 oemsetup.inf 4 File(s) 131,351 bytes Hope This helped... Chris

If you have more than one adapter in this machine you need to specify the Adapter the IP gets assigned to. [params.Adapter1] PCIBusNumber=10 PCIDeviceNumber=2 PCIFunctionNumber=0 INFID=PCI\VEN_14E4&DEV_1645&SUBSYS_007C0E11&REV_15\3&172E68DD&0&10 Chris