KinetiK Posted July 31, 2006 Posted July 31, 2006 Hi, latly the Company i work for, got this new XP from Microsoft Partner program called Windows XP Fundamentals for Legacy PC's, looks like they were really inspired by nLite, this XP allows you to choose wich components you want to install, and thats the perfect thing for me, i work as an IT and i could never use XP, i always used Windows 2000 and i totaly removed IE with nLite and i dont even have problems with it...im askinh Nicely, and im doubting that i will get a positive answer, cause this XP is not a PUBLIC release, its just for Microsoft Partners...the question...Will you guys ever Support Windows XP FLP on nLite?, the only thing that i need it for is SATA/RAID driver intergration, i am a fan of Reliability and Stability, thats why i Always used Win2k, now i have the chance to use alot of software that didnt work in Win2k, in a Stable XP...Thnx alot, KinetiK.
Alanoll Posted July 31, 2006 Posted July 31, 2006 http://unattended.msfn.org/unattended.xp/view/web/36/That's basically all that nLite does when adding the drivers itself for Mass Storage.
KinetiK Posted July 31, 2006 Author Posted July 31, 2006 yea i checked the link before, but i have to say the TXTSETUP.SIF is a bit different, i found 5 same sentences that the tutorial explains, i was kinda confused there...btw, thnx alot for replying
Alanoll Posted July 31, 2006 Posted July 31, 2006 yea i checked the link before, but i have to say the TXTSETUP.SIF is a bit different, i found 5 same sentences that the tutorial explains, i was kinda confused there...btw, thnx alot for replyingexplain
KinetiK Posted August 1, 2006 Author Posted August 1, 2006 If you prefer however to NOT risk erasing the "invisible" EOF marker, then just search for the sections above, and add the entries to each one, i.e. SourceDisksFiles goes in SourceDisksFiles; SCSI.load goes in SCSI.loadi found 8 [sourceDisksFiles] sentences...that confused mebtw, those codes (i bolded them), can you explain them abit to me, i never slipstreamed manualy before[sourceDisksFiles]si3112.sys = 1,,,,,,3_,4,1 [HardwareIdsDatabase] PCI\VEN_1095&DEV_3112&SUBSYS_31121095 = "Si3112" PCI\VEN_1095&DEV_3112&SUBSYS_34238086 = "Si3112" PCI\VEN_1095&DEV_3112&SUBSYS_311215D9 = "Si3112" PCI\VEN_1095&DEV_3112&SUBSYS_B0021458 = "Si3112" PCI\VEN_1095&DEV_3112&SUBSYS_01661028 = "Si3112" PCI\VEN_1095&DEV_3112&SUBSYS_82141033 = "Si3112" PCI\VEN_1095&DEV_3512&SUBSYS_35121095 = "Si3112" PCI\VEN_1095&DEV_3512&SUBSYS_01661028 = "Si3112" [sCSI.load] si3112 = si3112.sys,4 [sCSI] si3112 = "Silicon Image SiI 3112 SATALink Controller"
Keeperos Posted August 1, 2006 Posted August 1, 2006 (edited) Ahh, yeah, I got that too following a different guide minutes before I found out about nLite!!!Basically you need to add the lines for each ID the device (controller) might have (or sth).That's why there's more than one.What applied to one of them applies to all.Luckily I also have the same controller so I can even supply you with the code I used and successfully tested![SourceDisksFiles]Si3112r.sys = 1,,,,,,3_,4,1[HardwareIdsDatabase]PCI\VEN_1095&DEV_3112&SUBSYS_61121095 = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_611215D9 = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_34228086 = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_B0031458 = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_A0111019 = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_A0121019 = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_A0131019 = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_A0141019 = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_A0151019 = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_1014147B = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_100B147B = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_1402147B = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_1404147B = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_1802147B = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_1804147B = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_1C00147B = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_5930107D = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_249510F1 = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_809D1043 = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_0270A0A0 = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_044DA0A0 = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_044CA0A0 = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_92011905 = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_92151905 = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_904C1905 = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_904B1905 = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_A41810FD = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_A41910FD = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_A71910FD = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_90171695 = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_C2001297 = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_C2011297 = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_15D40035 = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_340217F2 = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_100415BD = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_F641270F = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_0C0F105B = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_0C13105B = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_0C58105B = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_0C40105B = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_0C41105B = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_0C42105B = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_0C43105B = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_0C44105B = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_0C22105B = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_0C2A105B = "Si3112r_XP"PCI\VEN_1095&DEV_3112&SUBSYS_2A1E103C = "Si3112r_XP"PCI\VEN_1095&DEV_3512&SUBSYS_65121095 = "Si3112r_XP"PCI\VEN_1095&DEV_3512&SUBSYS_B0031458 = "Si3112r_XP"PCI\VEN_1095&DEV_3512&SUBSYS_1014147B = "Si3112r_XP"PCI\VEN_1095&DEV_3512&SUBSYS_1021147B = "Si3112r_XP"PCI\VEN_1095&DEV_3512&SUBSYS_100B147B = "Si3112r_XP"PCI\VEN_1095&DEV_3512&SUBSYS_1C06147B = "Si3112r_XP"PCI\VEN_1095&DEV_3512&SUBSYS_1C00147B = "Si3112r_XP"PCI\VEN_1095&DEV_3512&SUBSYS_1C03147B = "Si3112r_XP"PCI\VEN_1095&DEV_3512&SUBSYS_1C04147B = "Si3112r_XP"PCI\VEN_1095&DEV_3512&SUBSYS_1406147B = "Si3112r_XP"PCI\VEN_1095&DEV_3512&SUBSYS_1407147B = "Si3112r_XP"PCI\VEN_1095&DEV_3512&SUBSYS_90191695 = "Si3112r_XP"PCI\VEN_1095&DEV_3512&SUBSYS_C2021297 = "Si3112r_XP"PCI\VEN_1095&DEV_3512&SUBSYS_C2031297 = "Si3112r_XP"PCI\VEN_1095&DEV_3512&SUBSYS_C2041297 = "Si3112r_XP"PCI\VEN_1095&DEV_3512&SUBSYS_534D108E = "Si3112r_XP"PCI\VEN_1095&DEV_3512&SUBSYS_02B71014 = "Si3112r_XP"PCI\VEN_1095&DEV_3512&SUBSYS_02C51095 = "Si3112r_XP"PCI\VEN_1095&DEV_3512&SUBSYS_2A1E103C = "Si3112r_XP"PCI\VEN_1095&DEV_3512&SUBSYS_91451462 = "Si3112r_XP"PCI\VEN_1095&DEV_3512&SUBSYS_006C1025 = "Si3112r_XP"PCI\VEN_1095&DEV_3512&SUBSYS_010D1025 = "Si3112r_XP"PCI\VEN_1002&DEV_436E&SUBSYS_436E1002 = "Si3112r_XP"PCI\VEN_1002&DEV_436E&SUBSYS_0A44174B = "Si3112r_XP"PCI\VEN_1002&DEV_436E&SUBSYS_0A45174B = "Si3112r_XP"PCI\VEN_1002&DEV_436E&SUBSYS_00301462 = "Si3112r_XP"PCI\VEN_1002&DEV_436E&SUBSYS_A43110FD = "Si3112r_XP"PCI\VEN_1002&DEV_436E&SUBSYS_F3631297 = "Si3112r_XP"PCI\VEN_1002&DEV_436E&SUBSYS_07201462 = "Si3112r_XP"PCI\VEN_1002&DEV_436E&SUBSYS_B0031458 = "Si3112r_XP"PCI\VEN_1002&DEV_436E&SUBSYS_92691509 = "Si3112r_XP"PCI\VEN_1002&DEV_436E&SUBSYS_5005148C = "Si3112r_XP"PCI\VEN_1002&DEV_4379&SUBSYS_43791002 = "Si3112r_XP"PCI\VEN_1002&DEV_437A&SUBSYS_437A1002 = "Si3112r_XP"PCI\VEN_1002&DEV_4379&SUBSYS_3009103C = "Si3112r_XP"PCI\VEN_1002&DEV_437A&SUBSYS_3009103C = "Si3112r_XP"[SCSI.load]Si3112r_XP = Si3112r.sys, 4[scsi]Si3112r_XP = "Silicon Image SiI 3x12 SATARaid Controller for Windows XP/Server 2003"The drivers I used were in the "3112r_x86_10561_logo.zip" that I found in the SiI site.Feel free to test my code and see if it'll work for you!Good Luck! Edited August 1, 2006 by Keeperos
KinetiK Posted August 1, 2006 Author Posted August 1, 2006 (edited) the guide was very similiarnow mate, my RAID chip is from VIA its the 1st link, should i try to add my VIA driver with your codes or wat? Edited August 1, 2006 by KinetiK
Alanoll Posted August 1, 2006 Posted August 1, 2006 the guide was very similiarnow mate, my RAID chip is from VIA its the 1st link, should i try to add my VIA driver with your codes or wat?Find the codes yourself. The TXTSETUP.OEM file included with the drivers is where all those Device IDs come from. Just find each unique one that's for your driver (they're usually split amongst OS [2000,XP,2003]) and add a line to TXTSETUP.SIF for each.Think of the process as more of a pattern.[SourceDisksFiles]Si3112r.sys = 1,,,,,,3_,4,1Replace Si3112r.sys with the filename of your driver.[SCSI.load]Si3112r_XP = Si3112r.sys, 4[scsi]Si3112r_XP = "Silicon Image SiI 3x12 SATARaid Controller for Windows XP/Server 2003"Defines a name for the drive and description, as well as tell SETUP to load the driver file. The name can be anything, but needs to be unique from any others. Usually they are because they're based off model numbers and if setup doesn't support your card, then the model isn't there.The Si3112r_XP is where the right side of the equal sign comes from to tell SETUP which driver to use for those device IDs.
KinetiK Posted August 1, 2006 Author Posted August 1, 2006 (edited) so the codes dont play a big role, they just need to be UNIQUE?EDIT: damnit, i need to work on my english sorry guys i just UNDERSTOOD it but still not gettin itthis is the txtsetup.oem of my driver[Disks]D-I386-NT5-RAID="VIA RAID Combo Driver Diskette",\I386\VIAMRAID, \NT5D-I386-NT4-RAID="VIA RAID Combo Driver Diskette",\I386\VIAMRAID, \NT4[Defaults]scsi = VCOMBORAID_I386_NT5[sCSI]VCOMBORAID_I386_NT5="VIA VT8251/8237/8237A/6421/6410 SATA RAID Controller(Windows 2K/XP/SRV2003)"VCOMBORAID_I386_NT4="VIA VT8251/8237/8237A/6421/6410 SATA RAID Controller(Windows NT4)"[Files.SCSI.VCOMBORAID_I386_NT5]driver = D-I386-NT5-RAID, viamraid.sys, CFG_NT5inf = D-I386-NT5-RAID, viamraid.infcatalog = D-I386-NT5-RAID, viamraid.cat[Files.SCSI.VCOMBORAID_I386_NT4]driver = D-I386-NT4-RAID, viamraid.sys, CFG_NT4inf = D-I386-NT4-RAID, viamraid.inf[config.CFG_NT5]value = parameters\PnpInterface,5,REG_DWORD,1[config.CFG_NT4]value = "", Tag, REG_DWORD, 1[HardwareIds.scsi.VCOMBORAID_I386_NT5]id = "PCI\VEN_1106&DEV_3349","viamraid"id = "PCI\VEN_1106&DEV_0591","viamraid"id = "PCI\VEN_1106&DEV_3249","viamraid"id = "PCI\VEN_1106&DEV_3149","viamraid"id = "PCI\VEN_1106&DEV_3164","viamraid"now im asking officialy for help Edited August 1, 2006 by KinetiK
Alanoll Posted August 1, 2006 Posted August 1, 2006 [SourceDisksFiles]viamraid.sys = 1,,,,,,3_,4,1[HardwareIdsDatabase]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]viamraid = viamraid.sys,4[SCSI]viamraid = "VIA RAID Combo Driver Diskette"Would be the appropriately lines. Then you MAKECAB the viamraid.sys file to compress it to a .sy_ file and copy it to I386. Edit TXTSETUP.SIF in the I386 folder with the above lines and you should be good
KinetiK Posted August 2, 2006 Author Posted August 2, 2006 thnx mate, i did all the stuff what you explain therenow just one thing, is there any need for WINNT.SIF, if yes then...do i need to create on cause i cant find it anywhere on the XPCD?
Keeperos Posted August 2, 2006 Posted August 2, 2006 I'm not entirely sure on that part...With nLite you don't need to use the WINNT.SIF.Furthermore for the TXT version you certainly won't need it since it is directly loaded at setup.However I am not sure if you need it for the PnP part of windows.If I had to guess I'd say that you don't, but I am not entirely sure.WINNT.SIF is only there when and if you need it. normally it should be in the I386 folder, if it isn't then you can create it with either of two ways (that is besides using notepad):even if you can't use nLite in general I don't think you'd have a problem just using the unattended setup part (that's where the WINNT.SIF is created.)The oher way is to use Microsoft's setupmgr.exe.You can find it in your windows CD, under SUPPORT\TOOLS\DEPLOY.CAB.Best of luck
KinetiK Posted August 2, 2006 Author Posted August 2, 2006 1st of all, thnx to all of you guys,you really helped me out, all the steps worked but it looks like that this OS doesn't SUPPORT RAID from the core (typical M$, they do what they want) i burned more then 10 cd-s just to TRY it, the last one was perfect but when it started to install it just restarted my computer...so 1st i thought maybe the driver isnt compatible with this XP, but a BSOD would answer me that and i didnt have one...all i can do is stick to W2k and wait for nLite support or any CODEHACK on the internetagain, thnx alot guys .
nuhi Posted August 6, 2006 Posted August 6, 2006 Well since I don't have it and it's limited in many ways (parallel processes limit?) I don't see it supported that soon or ever.It uses some Vista deployment routines so I'll check that later on when Vista is final.
KinetiK Posted August 7, 2006 Author Posted August 7, 2006 I tested it on a Laptop, aslong as i used it 3-4 full hours, i didnt see any limitation, it just worked perfect .
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now