MSFN Forum: Issues with TXTSETUP.oem - MSFN Forum

Jump to content



If you are having issues with Windows after removing components and have come to ask for help, please attach (not paste) your Last Session.ini file to your post to facilitate quicker assistance.
Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

Issues with TXTSETUP.oem Workaround for PERC5 and PERC6 x64 Rate Topic: -----

#1 User is offline   BikinDutchman 

  • Member
  • PipPip
  • Group: Members
  • Posts: 231
  • Joined: 11-January 07

  Posted 11 July 2008 - 10:35 PM

Hi all,

In the past week I found a special problem with nLite integration of Dell PERC5 and 6 RAID 64 bit drivers. I reported this to Nuhi but I think it is also interesting for those who are struggling with this integration.

Below is the TXTSETUP.oem with comments removed and my edits:

Quote

[Disks]
PERC_64 = "DELL PERC5 and PERC6/CERC6 RAID Controller Driver (Server 2003 for x64)", \percsas.sys, \
[Defaults]
scsi = PERC_64
[scsi]
PERC_64d1 = "DELL PERC5 and PERC6/CERC6 RAID Controller Driver (Server 2003 for x64)",percsas
[HardwareIds.scsi.PERC_64]
PERC_64id = "PCI\VEN_1028&DEV_0015&SUBSYS_1F011028", "percsas"
PERC_64id = "PCI\VEN_1028&DEV_0015&SUBSYS_1F021028", "percsas"
PERC_64id = "PCI\VEN_1028&DEV_0015&SUBSYS_1F031028", "percsas"
PERC_64id = "PCI\VEN_1000&DEV_0060&SUBSYS_1F0A1028", "percsas"
PERC_64id = "PCI\VEN_1000&DEV_0060&SUBSYS_1F0B1028", "percsas"
PERC_64id = "PCI\VEN_1000&DEV_0060&SUBSYS_1F0C1028", "percsas"
PERC_64id = "PCI\VEN_1000&DEV_0060&SUBSYS_1F0D1028", "percsas"
PERC_64id = "PCI\VEN_1000&DEV_0060&SUBSYS_1F111028", "percsas"
[Files.scsi.PERC_64]
driver = PERC_64d1, percsas.sys, percsas
inf = PERC_64d1, oemsetup.inf, percsas
inf = PERC_64d1, nodev.inf
catalog = PERC_64d1, percsas.cat
[Config.percsas]
value=parameters\PnpInterface,5, REG_DWORD,1
value = "", Tag, REG_DWORD, 20


The edits for the [Disks], [scsi] and [Files.scsi.PERC_64] sections are cosmetic. The percsas is for something that, according to INF file scripture does not make sense, but I see it a lot in Dell TXTSETUP.oem files.
The edits for the [HardwareIds.scsi.PERC_64] section are mandatory for the integration to work with nLite 1.4.7.

Warning: it gets a little technical from here :boring: and I continue in geek speek:

Problem is that someone (at Dell?) was so fond of the PERC_64 key that (s)he used it for almost every entry.
-Well that looks just strange for the [Disks], [scsi] and [Files.scsi.PERC_64] sections but it is dead wrong for the [HardwareIds.scsi.PERC_64] section.
-It might be that the latter is no problem with an official F6 install, but nLite 1.4.7 does not take this so lite, and does not include the entries under the HardwareIdDatabase of TXTSETUP.sif.
-That, in turn, causes the PERC 5 or 6 array to be not detected during textmode install :realmad: .

I hope this was the only one TXTSETUP.oem that has this problem but I am not optimistic so we can probably add this one concern to the many that we already have. OK it keeps us from the street :hello: .


#2 User is offline   joesuffceren 

  • Group: Members
  • Posts: 1
  • Joined: 13-December 08

Posted 13 December 2008 - 09:23 PM

This definitely helped me with my Dell Poweredge 2900. Thanks! One thing to note, though, is that I had to add the following three lines to the txtsetup.sif file as well (as noted in post http://www.msfn.org/board/lofiversion/inde...p/t94068.html):

PCI\VEN_1028&DEV_0015&SUBSYS_1F011028="percsas"
PCI\VEN_1028&DEV_0015&SUBSYS_1F021028="percsas"
PCI\VEN_1028&DEV_0015&SUBSYS_1F031028="percsas"


I added these lines directly below the [HardwareIdsDatabase] tag, so:
[HardwareIdsDatabase]
PCI\VEN_1028&DEV_0015&SUBSYS_1F011028="percsas"
PCI\VEN_1028&DEV_0015&SUBSYS_1F021028="percsas"
PCI\VEN_1028&DEV_0015&SUBSYS_1F031028="percsas"
[i]old first line that was originally directly beneath tag goes here[/i]


I have no clue why or how any of this works, but I know that combining these two fixes made my install work, so I'm happy. Thanks, all, for sharing.

#3 User is offline   thtanner 

  • Group: Members
  • Posts: 1
  • Joined: 14-January 11
  • OS:Windows 7 x64
  • Country: Country Flag

Posted 14 January 2011 - 01:47 PM

This topic has been of great assistance recently when attempting to integrate the PERC 6/i drivers for 2003 x64 for my Dell PowerEdge 2950.

I was able to take the information from both replies to come up with a solid solution that works with nLite on the first try.

Download the latest x64 PERC5/6 drivers from Dell (which are DELL_MULTI-DEVICE_A07_R211422.exe as of writing).

Replace the text in txtsetup.oem with the following...

[Disks]
PERC_64 = "DELL PERC5 and PERC6/CERC6 RAID Controller Driver (Server 2003 for x64)", \percsas.sys, \
[Defaults]
scsi = PERC_64
[scsi]
PERC_64 = "DELL PERC5 and PERC6/CERC6 RAID Controller Driver (Server 2003 for x64)",percsas
[HardwareIds.scsi.PERC_64]
id = "PCI\VEN_1028&DEV_0015&SUBSYS_1F011028", "percsas"
id = "PCI\VEN_1028&DEV_0015&SUBSYS_1F021028", "percsas"
id = "PCI\VEN_1028&DEV_0015&SUBSYS_1F031028", "percsas"
id = "PCI\VEN_1000&DEV_0060&SUBSYS_1F0A1028", "percsas"
id = "PCI\VEN_1000&DEV_0060&SUBSYS_1F0B1028", "percsas"
id = "PCI\VEN_1000&DEV_0060&SUBSYS_1F0C1028", "percsas"
id = "PCI\VEN_1000&DEV_0060&SUBSYS_1F0D1028", "percsas"
id = "PCI\VEN_1000&DEV_0060&SUBSYS_1F111028", "percsas"
[Files.scsi.PERC_64]
driver = PERC_64, percsas.sys, percsas
inf = PERC_64, oemsetup.inf
inf = PERC_64, nodev.inf
catalog = PERC_64, percsas.cat
[Config.percsas]
value=parameters\PnpInterface,5, REG_DWORD,1
value = "", Tag, REG_DWORD, 20



With the following edit, the drivers will properly integrate into a XP x64/Server 2003 x64 installation with nLite. No changes to the txtsetup.sif is necessary, as my edits above allow nLite to properly amend the file.

Keywords for Googlers such as myself: nLite, PERC 5, PERC 6, Dell, PowerEdge 2950, 2003, x64

This post has been edited by thtanner: 14 January 2011 - 01:51 PM


Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users



All trademarks mentioned on this page are the property of their respective owners
Copyright © 2001 - 2011 msfn.org
Privacy Policy