Jump to content

toml

Member
  • Posts

    3
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by toml

  1. Thank you very much for the information. I've been "way laid" a day or two on something else, but I'm going to go check out what you've suggested. Hopefully, it'll cut through some of the thick air here! Tom
  2. 2nd Iteration: After much more checking, I've discovered a couple of things that have helped but not solved my problem. For one, I had deleted a couple of files from the diskette a x.mpd and x.vxd that are referenced in the associated .ini file. Putting these back, though, didn't make any difference. I then added back in the [defaults] section and now, I do get a message indicating what driver to install, then followed by the error. However, if I say "continue" after I get the error and then come back and try it two or three times again, it will load and work OK!! I have no idea why, but it appears that there's a lot more interaction between the .oem file and the .inf file than I ever imagined. Why brings me to the next question: I now suspect that things I have changed in the txtsetup.oem file are not in "sync" with what's in the associated .inf files. I understand there is a facility available in Microsoft's DDK called "chkinf" but I can't locate a downloadable version of it anywhere. So ... does any have a copy of "chkinf" that I could obtain? I think this may be the next step in resolving the problem. Thanks, Tom
  3. Hi, In preparation for even bigger and greater things, I'm taking on the first item in working towards a clean XP install disk with all the latest fixes, including SP2, and all my device drivers. I'm a novice at this and have spent the last 24 hours going through Microsoft website, a couple of other sites, and luckily, I found MSFN. Anyway, the very first step is to combine two driver diskettes into one. One river diskette is for my IOinit SCSI controller and the second is for my Si 3114 SATA Raid controller on my DFI M/B. Both driver installation disks are very simple, as far as the txtsetup.oem files go, yet I haven't managed even this simple task of successfully combining the two. The initIO SCSI controller txtsetup.oem looks like (I deleted all the comments and blank lines): [Disks] d0 = "INITIO INI-A100U2W Driver Disk", \disk1, \ d1 = "INITIO INI-A100U2W Driver Disk", \disk1, \win2k [Defaults] scsi = INIA100 [scsi] INIA100 = "INITIO INI-A100U2W SCSI Host Adapter 10-8-2002" [Files.scsi.INIA100] inf = d0, INIA100.INF driver = d1, INIA100.SYS, INIA100 The Si3114 SATARAID controller txtsetup.oem looks like: [Disks] disk1 = "Silicon Image SiI 3114 SATARaid Driver Installation Disk",\Si3114r.sys,\ [Defaults] SCSI = Si3114r_XP [sCSI] ; HwComponent section Si3114r_XP = "Silicon Image SiI 3114 SATARaid Controller for Windows XP" Si3114r_NT = "Silicon Image SiI 3114 SATARaid Controller for Windows NT 4.0 and 2000" [Files.SCSI.Si3114r_XP] driver = disk1,si3114r.sys, Si3114r driver = disk1,SiWinAcc.sys, SiFilter inf = disk1,SI3114r.inf ;;catalog = disk1, Si3114r.cat [Files.SCSI.Si3114r_NT] driver = disk1,si3114r.sys, Si3114r inf = disk1,SI3114r.inf ;;catalog = disk1, Si3114r.cat [HardwareIds.SCSI.Si3114r] id = "PCI\VEN_1095&DEV_3114&SUBSYS_61141095", "Si3114r" [Config.Si3114r] value = ProblemDevices, "", REG_SZ, "" value = ProblemDevices, "Maxtor 4D060H3 DAK05GK0", REG_SZ, "MaxMode = UDMA-5" I've combined this onto one diskette with the following files (I deleted readme.txt's): txtsetup.oem (my new "combined" version) Win2k\ directory with initio files in it disk1 (placeholder with some text in it) Inia100.inf SI3114r.inf Si3114r.mpd Si3114r.sys SIISUPP.VXD SIWinAcc.sys tcl.dat (placeholder with some text in it) The Win2k\ directory has the following in it: inia100.sys And my combined txtsetup.oem looks like: [Disks] inid0 = "TOML COMBINED DRIVER DISKETTE", \tcl.dat, \ inid1 = "TOML COMBINED DRIVER DISKETTE", \tcl.dat, \win2k sraiddisk = "TOML COMBINED DRIVER DISKETTE",\tcl.dat,\ [sCSI] ; HwComponent section INIA100 = "INITIO INI-A100U2W SCSI Host Adapter 10-8-2002" Si3114r_XP = "TomL SiI 3114 SATARaid Controller for Windows XP" [Files.scsi.INIA100] inf = inid0, INIA100.INF driver = inid1, INIA100.SYS, INIA100 [Files.SCSI.Si3114r_XP] driver = sraiddisk,si3114r.sys, Si3114r driver = sraiddisk,SiWinAcc.sys, SiFilter inf = sraiddisk,SI3114r.inf ;;catalog = disk1, Si3114r.cat [HardwareIds.SCSI.Si3114r] id = "PCI\VEN_1095&DEV_3114&SUBSYS_61141095", "Si3114r" [Config.Si3114r] value = ProblemDevices, "", REG_SZ, "" value = ProblemDevices, "Maxtor 4D060H3 DAK05GK0", REG_SZ, "MaxMode = UDMA-5" I'm using the recovery console as a quick way to verify that the new combined diskette driver works, e.g., F6 during startup and then pointing it to the A: diskette. I can use the two original diskettes, initio first, then the 3114 SATARAID driver diskette, and the recovery console loads and runs OK. My attempt to load the "combined" drivers, using the F6 mechanism, results in txtsetup.oem error (1024) @ line 1742 in d:\xpclist\base\boot\setup\oemdisk.c (This may not be quite the exact error message, as sometimes I can't read my own writing). I never received the message asking what drivers I would like to install. I'm assuming the "d:\xpclist\b .... \oemdisk.c " refers to the location of the source file when the "assertion" statement was issued in the source code, as it doesn't relate at all to anything I'm doing or that I have on my system. I haven't modified the .inf files at all; I didn't think I would have to. Also, I haven't paid particular attention to lowercase-uppercase, as I've found nothing that indicates that I need to. Also, since I'm doing this for XP, I eliminated the NT portion of the 3114 SATA RAID txtsetup.oem. I can easily provide more information, but I didn't want to occupy more space on this wonderful website than what I thought was necessary for someone to see what is probably my "dumb" error. I've searched in vain for any description of the txtsetup error Any help will be sincerely appreciated. Tom toml@direcway.com
×
×
  • Create New...