Jump to content

xavmdq

Member
  • Posts

    8
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Argentina

Everything posted by xavmdq

  1. Update: I take out all nvidia lines and now works. But I need nvidia driver!
  2. I followed 3 or 4 post relating to nVidia RAID/SATA driver in txtsetup but I get the following error (in spanish): La entrada "nvraid" en la sección SourceDisksFiles del archivo INF no existe o está dañado In english is something like this: "nvraid" in section SourceDisksFiles of INF file don't exist or corrupted (I don't know what says exactly in english version of Windows Xp) I made the following steps (I want integrate SiS, Via and nVidia drivers): Step 1 -------- TXTSETUP.SIF file: [sourceDisksFiles] ;Before was: 1,,,,,,3_,4,1, like says the "official" guide and don't work too nvraid.sys = 1,,,,,,4_,4,1,,,1,4 nvatabus.sys = 1,,,,,,4_,4,1,,,1,4 sisraid.sys = 1,,,,,,4_,4,1,,,1,4 sisraid1.sys = 1,,,,,,4_,4,1,,,1,4 sisraid2.sys = 1,,,,,,4_,4,1,,,1,4 viamraid.sys = 1,,,,,,4_,4,1,,,1,4 [HardwareIdsDatabase] GenNvRaidDisk = "nvraid" *_NVRAIDBUS = "nvraid" ;i'm tried *NVRAIDBUS also PCI\VEN_10DE&DEV_008E = "nvatabus" PCI\VEN_10DE&DEV_0085 = "nvatabus" PCI\VEN_10DE&DEV_00D5 = "nvatabus" PCI\VEN_10DE&DEV_00EE = "nvatabus" PCI\VEN_10DE&DEV_00E3 = "nvatabus" PCI\VEN_10DE&DEV_00E5 = "nvatabus" PCI\VEN_10DE&DEV_0035 = "nvatabus" PCI\VEN_10DE&DEV_0036 = "nvatabus" PCI\VEN_10DE&DEV_003E = "nvatabus" PCI\VEN_10DE&DEV_0053 = "nvatabus" PCI\VEN_10DE&DEV_0054 = "nvatabus" PCI\VEN_10DE&DEV_0055 = "nvatabus" PCI\VEN_1039&DEV_0180 = "SiSRaid" PCI\VEN_1039&DEV_0181 = "SiSRaid1" PCI\VEN_1039&DEV_0182 = "SiSRaid2" PCI\VEN_1106&DEV_3349 = "viamraid" PCI\VEN_1106&DEV_0591 = "viamraid" PCI\VEN_1106&DEV_3249 = "viamraid" PCI\VEN_1106&DEV_3149 = "viamraid" PCI\VEN_1106&DEV_3164 = "viamraid" [sCSI.load] nvraid = nvraid,4 nvatabus = nvatabus,4 viamraid = viamraid.sys,4 SiSRaid = SiSRaid.sys,4 SiSRaid1 = SiSRaid1.sys,4 SiSRaid2 = SiSRaid2.sys,4 [sCSI] nvraid = "NVIDIA RAID CLASS DRIVER" nvatabus = "NVIDIA NForce Storage Controller" SiSRaid = "Windows 32bit XP SiS Raid/IDE Controller" SiSRaid1 = "Windows 32bit XP SiS Raid/IDE Controller" SiSRaid2 = "Windows 32bit XP SiS Raid/IDE Controller" viamraid = "VIA VT8251/8237/8237A/6421/6410 SATA RAID Controller(Windows 2K/XP/SRV2003)" Step 2 ------- WINNT.SIF file, section [unattended]: OemPreinstall=Yes DriverSigningPolicy=Ignore OemPnPDriversPath="drivers\nVidia;drivers\SiS1;drivers\SiS2;drivers\SiS3;drivers\SiS4;drivers\Via" Step 3 ------- Copy driver to $OEM$\$1\drivers and have the following: D:\WXPVOL_SP\$OEM$\$1\drivers\nVidia\disk1 D:\WXPVOL_SP\$OEM$\$1\drivers\nVidia\idecoi.dll D:\WXPVOL_SP\$OEM$\$1\drivers\nVidia\nvata.cat D:\WXPVOL_SP\$OEM$\$1\drivers\nVidia\nvatabus.inf D:\WXPVOL_SP\$OEM$\$1\drivers\nVidia\NvAtaBus.sys D:\WXPVOL_SP\$OEM$\$1\drivers\nVidia\nvcoi.dll D:\WXPVOL_SP\$OEM$\$1\drivers\nVidia\nvide.nvu D:\WXPVOL_SP\$OEM$\$1\drivers\nVidia\nvraid.cat D:\WXPVOL_SP\$OEM$\$1\drivers\nVidia\nvraid.inf D:\WXPVOL_SP\$OEM$\$1\drivers\nVidia\nvraid.sys D:\WXPVOL_SP\$OEM$\$1\drivers\nVidia\nvraidco.dll D:\WXPVOL_SP\$OEM$\$1\drivers\nVidia\nvuide.exe D:\WXPVOL_SP\$OEM$\$1\drivers\nVidia\raidtool D:\WXPVOL_SP\$OEM$\$1\drivers\nVidia\txtsetup.oem D:\WXPVOL_SP\$OEM$\$1\drivers\nVidia\raidtool\NvRaidEnu.dll D:\WXPVOL_SP\$OEM$\$1\drivers\nVidia\raidtool\NvRaidMan.exe D:\WXPVOL_SP\$OEM$\$1\drivers\nVidia\raidtool\nvraidservice.exe D:\WXPVOL_SP\$OEM$\$1\drivers\nVidia\raidtool\NvRaidSvEnu.dll D:\WXPVOL_SP\$OEM$\$1\drivers\nVidia\raidtool\NvRaidWizard.dll D:\WXPVOL_SP\$OEM$\$1\drivers\nVidia\raidtool\NvRaidWizardEnu.dll D:\WXPVOL_SP\$OEM$\$1\drivers\nVidia\raidtool\RegRaid.bat (don't show other folders with SiS and Via drivers) Step 4 ------- MAKECAB NvAtaBus.sys MAKECAB nvraid.sys Move NvAtaBus.sy_ and nvraid.sy_ to I386 folder I'm missing something?
  3. Well, I started with 4 hotfixes and found this: KB873339 -------- Filename Lang Version Size Date MD5 SP1QFE: hypertrm.dll SP 5.1.2600.1609 499200 04/11/17 f11ed006b5c81acc0455169e35f5b3e4 SP2GDR: hypertrm.dll SP 5.1.2600.2563 353280 04/11/17 3b55813b4360468745a397062bcd1196 SP2QFE: hypertrm.dll SP 5.1.2600.2563 353280 04/11/17 ced377116935183acb40761ccc5c52c1 KB885250 -------- Filename Lang Version Size Date MD5 SP1QFE: cscdll.dll SP 5.1.2600.1599(xpsp2.040919-1003) 92672 04/10/27 408defdb591e11f7449667b18e82b848 mrxsmb.sys EN 5.1.2600.1620(xpsp2.041130-1838) 440064 05/01/19 7f09b37065b61ddbc6116f612e6183d1 rdbss.sys EN 5.1.2600.1599(xpsp2.040919-1003) 170112 04/10/12 1fd256b6025449dca3670574c0229d65 SP2QFE: mrxsmb.sys EN 5.1.2600.2598(xpsp.041130-1728) 451584 05/01/19 7b195060ff456fa65954c72c5c1640ff SP2GDR: mrxsmb.sys EN 5.1.2600.2598(xpsp_sp2_gdr.041130-1729) 451584 05/01/19 5ddc9a1b2eb5a4bf010ce8c019a18c1f KB885626 -------- Filename Lang Version Size Date MD5 SP2QFE: update.sys EN 5.1.2600.2508(xpsp.040806-1825) 209280 04/09/01 a4815a4884898f355a3513e60843a4fd KB885835 -------- Filename Lang Version Size Date MD5 SP1QFE: cscdll.dll SP 5.1.2600.1599(xpsp2.040919-1003) 92672 04/10/27 408defdb591e11f7449667b18e82b848 lsasrv.dll SP 5.1.2600.1597(xpsp2.040919-1003) 686592 04/10/27 8f2ca617f6d9be42bf53355caabd1f19 mrxsmb.sys EN 5.1.2600.1599(xpsp2.040919-1003) 436608 04/10/12 e5d956e9839c75ccabddedc07e17670c ntkrnlmp.exe SP 5.1.2600.1605(xpsp2.040919-1003) 1902080 04/10/27 8f3dcf62607cba0baefb4b09718de80a ntkrnlpa.exe SP 5.1.2600.1605(xpsp2.040919-1003) 1958144 04/10/27 0d5f94d92e04b710f5d7e3a3d800fb6d ntkrpamp.exe SP 5.1.2600.1605(xpsp2.040919-1003) 1930752 04/10/27 ca11ac3a78c30ead2876a48bb9c271a2 ntoskrnl.exe SP 5.1.2600.1605(xpsp2.040919-1003) 2090752 04/10/27 b0c550f6bc2ca49605914dd2d9ce40a0 rdbss.sys EN 5.1.2600.1599(xpsp2.040919-1003) 170112 04/10/12 1fd256b6025449dca3670574c0229d65 shsvcs.dll SP 6.00.2800.1605(xpsp2.040919-1003) 116736 04/10/27 4befc79a950da7c16c5f6fa2fc62be1f SP2QFE: lsasrv.dll SP 5.1.2600.2525(xpsp.040919-1030) 726528 04/10/27 b6945f51e551e9f3dd4c3c58aba9c42f mrxsmb.sys EN 5.1.2600.2541(xpsp.040919-1030) 448128 04/10/27 a1be3cb080dcc0a8270d21e3ca3b7005 rdbss.sys EN 5.1.2600.2541(xpsp.040919-1030) 174592 04/10/27 d0fef8156d2d2fec557c100956d76887 SP2GDR: lsasrv.dll SP 5.1.2600.2525(xpsp_sp2_gdr.040919-1056) 726528 04/10/27 249da8ca8ace8811b5de51d873f3610b mrxsmb.sys EN 5.1.2600.2541(xpsp_sp2_gdr.040919-1056) 448128 04/10/27 c9d17daa82b917cf2fd6e4f595974934 rdbss.sys EN 5.1.2600.2541(xpsp_sp2_gdr.040919-1056) 174592 04/10/27 809ca45caa9072b3176ad44579d7f688 (sorry, I can't find a way to reduce CODE font size below 1) I don't understand why we have to install MSN7 and WMP10 before this hotfixes if they don't have related files. The files of this hotfixes are system critical (except first hotfix).
  4. Thanks guys, but I made disk with SVCPACK method. I tried to view the contents of hotfixes but I can't read each file (encrypted?) and for that reason I can't make a table with dependencies and file versions. I think some (or all) hotfixes can be applied (sliptreamed with /INTEGRATE switch) without having to install MSN7 and WMP10. When I have time I'll apply each hotfix and view the modifications taken. Thanks again and sorry for my english.
  5. Thanks, but that method is for English only. I go to easy way. I have 66MB of critical updates+WMP10+MSN7. I'll delete Migration folders (always made clean installs). Now I'm downloading SATA+RAID drivers for Via, Sis and nVidia (the most common in my country). I added Total Commander (copied to $oem$), make a script (called from cmdlines.txt) to add registry setting of Total Commander (I didn't use REG file because of unit problem, for example if I install windows to D drive). In cleanup.cmd I have the deletion commands and move links commands (I organize Internet aplication below Internet in Start Menu, etc.). The only thing I can't found is how to make appear the repair option. I hope I can burn this CD today.
  6. Can you post winnt.sif file from that disk? I want also the repair option.
  7. Hi, I'm following de Unnatended guide and can place hotfixes in two ways: SVCPACK directory with SVCPACK.INF or using /INTEGRATE switch (to slipstream?). Is this correct? Looking the post "HOTFIXES: Win2000 SP4 – WinXP SP1 – WinXP SP2" says that hotfixes go AFTER installing MSN 7 and WMP10. Then I can't slipstream hotfixes. I know I can use SVCPACK method but the idea is to save space on disk and speed up installation. All these hotfixes requieres MSN7 and WMP10? Now I'll look each critical update and I'll try to separate hotfixes to slipstream and hotfixes to SVCPACK.
×
×
  • Create New...