Jump to content

Zaker

Member
  • Posts

    77
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Canada

Everything posted by Zaker

  1. I am replicating your exact dir structure, hopefully it works... Did you not modify the TXTSETUP.OEM file at all? Thanks.
  2. Greetings. We have read lots about this topic, but still cannot make this work. We use WinPE to boot our IBM x225 servers, attach to the network, and run a batch file that runs diskpart and formats the drives, then finally launches an unattend.txt to build a Win2k3 Standard Server. The new RAID controller for the x225s, the IBMServerRAID 6i has newer drivers than what comes with PE or 2k3. Without them, PE does not recognize the drives. We are trying to incorporate them into the PE boot CD, and have had no luck. Here's what we've done. - copy the entire PE 1.2 CD to a machine, say C:\PECD - modify the i386\system32\startnet.cmd to include the NET USE stuff that will map the drive to the network and run our .bat file. - create a dir called i386\system32\Drivers\IBMRAID - copy all files from the IBM ServerRAID v7 diskette that we created that contains all the files it needs, including TXTSETUP.OEM - modify i386\system32\WINPEOEM.SIF and remove the comment from; [massstoragedrivers.append] mydriver = nfrd960.sys - remove the comment from; [OemDriverParams] OemDriverRoot="" OemDriverDirs=\system32\Drivers\IBMRAID - create an ISO via the OSCDIMG command, and burn the ISO - boot the server to the CD, and that works fine - PE starts loading and not long after, we get the infamous error; File TXTSETUP.OEM caused and unexpected error (18) at line 1742 in d:\xpsp1\base\boot\setup\oemdisk.c I have read all the posts that I can about editing TXTSETUP.OEM, but nothing changes. PLEASE OFFER ANY SUGGESTIONS THAT YOU MAY HAVE. If I ommited important info, please advise. Thanks in advance to anyone who responds.
×
×
  • Create New...