Bombada Posted September 1, 2004 Share Posted September 1, 2004 Hehe very nice ,OemPnPDriversPath was already @ the limit with 3900 characters.Your methode is very nice, but I canot download the file ;(.Guide4Driver.cab the LINK is also @ the Limit (-LOL-)If some one can send me the file, ore attach it in his post, i will be very happy. Link to comment Share on other sites More sharing options...
Thauzar Posted September 1, 2004 Share Posted September 1, 2004 yeah, I retried with the renamed new files, and the older 7z files but someone should really post link for the elder 7za files so we could rename it and make this thing work Link to comment Share on other sites More sharing options...
arry Posted September 1, 2004 Share Posted September 1, 2004 Can someone please tell me....who if anyone has actually got this to work....I mean in theory its fantastic .......but are we wasting our time... Link to comment Share on other sites More sharing options...
serialzs Posted September 1, 2004 Author Share Posted September 1, 2004 @alldid all of using this having trouble??? anyone having trouble in my PROG. have you followed the instruction of Silent Installation of Windows Device Drivers in http://unattended.msfn.org/xp/drivers.htm and installed your DRIVERS right???if it work in your OS installer my Prog will install it right and runs good...i just make it a compressed DRIVERS instead of a BIG EXTRACTED FILES...i see in TXTSETUP.SIF there are so many [sourceDisksFiles]7za.exe = 1,,,,,,,2,0,0Drvz.exe = 1,,,,,,,2,0,0DevPath.exe = 1,,,,,,,2,0,0 you will only put this lines in the 1st [sourceDisksFiles] that you will FOUND, NOT in all of it...to be sure! put it like this at the 1st found [sourceDisksFiles][sourceDisksFiles]7za.exe = 1,,,,,,,2,0,0Drvz.exe = 1,,,,,,,2,0,0DevPath.exe = 1,,,,,,,2,0,0put it that way... under of DevPath.exe = 1,,,,,,,2,0,0 will be the line that already exist...[WinntDirectories]2 = system32and make sure that the above line exist in txtsetup.sifi USE it in my WINDOWS XP PRO SP2 v2096 for those having trouble what version did you USED??? -=[serialzs]=- Link to comment Share on other sites More sharing options...
turbomcp Posted September 1, 2004 Share Posted September 1, 2004 ok guysbreaking newsi read the theory of devicepath read into memory even before t39so i decided to try alittle trick myselfi run devpath.exe on my c:\driverzgot the registry entries and added them to HIVESFT.INF in i386which is basicly the first registry enteries there are before the setup startsthe default entry there for devicepath is %systemroot%\infi added mine after that and made sure they are there before my other script runs at t39.my HIVESFT.INF looks like this nowHKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion","DevicePath",0x00020002,"%SystemRoot%\Inf;c:\driverz\L\L\3C\1;c:\driverz\L\L\3C\2;c:\driverz\L\L\3C;c:\driverz\L\L\BR\1;c:\driverz\L\L\BR\2;c:\driverz\L\L\BR;c:\driverz\L\L\BU\1;c:\driverz\L\L\BU\2;c:\driverz\L\L\BU\3;c:\driverz\L\L\BU;c:\driverz\L\L\D\1;c:\driverz\L\L\D\500sx;c:\driverz\L\L\D\500T;c:\driverz\L\L\D\530TX+;c:\driverz\L\L\D\550T;c:\driverz\L\L\D\550TX;c:\driverz\L\L\D;c:\driverz\L\L\I;c:\driverz\L\L\L\0;c:\driverz\L\L\L\1;c:\driverz\L\L\L\2;c:\driverz\L\L\L\3;c:\driverz\L\L\L\4;c:\driverz\L\L\L\5;c:\driverz\L\L\L\6;c:\driverz\L\L\L\7;c:\driverz\L\L\L\8;c:\driverz\L\L\L\9;c:\driverz\L\L\L;c:\driverz\L\L\LI\1;c:\driverz\L\L\LI\2;c:\driverz\L\L\LI\3;c:\driverz\L\L\LI\4;c:\driverz\L\L\LI\5;c:\driverz\L\L\LI\6;c:\driverz\L\L\LI\7;c:\driverz\L\L\LI;c:\driverz\L\L\M;c:\driverz\L\L\N\1;c:\driverz\L\L\N\2;c:\driverz\L\L\N\3;c:\driverz\L\L\N\4\WIN2K;c:\driverz\L\L\N\4;c:\driverz\L\L\N\5;c:\driverz\L\L\N\6;c:\driverz\L\L\N\7;c:\driverz\L\L\N;c:\driverz\L\L\NV;c:\driverz\L\L\O\1;c:\driverz\L\L\O\10;c:\driverz\L\L\O\11;c:\driverz\L\L\O\2;c:\driverz\L\L\O\3;c:\driverz\L\L\O\4;c:\driverz\L\L\O\5;c:\driverz\L\L\O\6;c:\driverz\L\L\O\7;c:\driverz\L\L\O\8;c:\driverz\L\L\O\9;c:\driverz\L\L\O;c:\driverz\L\L\R\1;c:\driverz\L\L\R\2;c:\driverz\L\L\R\3;c:\driverz\L\L\R;c:\driverz\L\L\S;c:\driverz\L\L\V\1;c:\driverz\L\L\V\2;c:\driverz\L\L\V\3;c:\driverz\L\L\V\4;c:\driverz\L\L\V\5;c:\driverz\L\L\V\6;c:\driverz\L\L\V;c:\driverz\L\L;c:\driverz\L;c:\driverz\R\acard\6280;c:\driverz\R\acard\6290;c:\driverz\R\acard\67160;c:\driverz\R\acard\671x;c:\driverz\R\acard\6880;c:\driverz\R\acard\6890;c:\driverz\R\acard\68x5;c:\driverz\R\acard;c:\driverz\R\adaptec\aac;c:\driverz\R\adaptec\aar1210;c:\driverz\R\adaptec\i2o;c:\driverz\R\adaptec\u160;c:\driverz\R\adaptec\u320;c:\driverz\R\adaptec\u320r;c:\driverz\R\adaptec;c:\driverz\R\ali;c:\driverz\R\amd;c:\driverz\R\highpoint\hpt366;c:\driverz\R\highpoint\hpt371;c:\driverz\R\highpoint\hpt374;c:\driverz\R\highpoint\hpt3xx;c:\driverz\R\highpoint\rr182x;c:\driverz\R\highpoint;c:\driverz\R\intel\eide;c:\driverz\R\intel\sataraid;c:\driverz\R\intel\u320r\winnt\x86;c:\driverz\R\intel\u320r\winnt;c:\driverz\R\intel\u320r;c:\driverz\R\intel;c:\driverz\R\ite;c:\driverz\R\lsilogic\megaide;c:\driverz\R\lsilogic\mraid35x;c:\driverz\R\lsilogic\mylex;c:\driverz\R\lsilogic\symmpi;c:\driverz\R\lsilogic;c:\driverz\R\nvidia\eide;c:\driverz\R\nvidia\raid;c:\driverz\R\nvidia;c:\driverz\R\promise\fasttrak;c:\driverz\R\promise\fasttx2k;c:\driverz\R\promise\sx4000;c:\driverz\R\promise\sx6000;c:\driverz\R\promise\ulsata;c:\driverz\R\promise\ultra;c:\driverz\R\promise;c:\driverz\R\qlogic\12160;c:\driverz\R\qlogic;c:\driverz\R\siimage\3112;c:\driverz\R\siimage\3112r;c:\driverz\R\siimage\3114;c:\driverz\R\siimage\3114r;c:\driverz\R\siimage\3124;c:\driverz\R\siimage\3124r;c:\driverz\R\siimage\649r;c:\driverz\R\siimage\680;c:\driverz\R\siimage\680r;c:\driverz\R\siimage;c:\driverz\R\sis\eide;c:\driverz\R\sis\raid;c:\driverz\R\sis;c:\driverz\R\via\eide;c:\driverz\R\via\ideraid;c:\driverz\R\via\miniport;c:\driverz\R\via\sataraid;c:\driverz\R\via\Viasraid;c:\driverz\R\via;c:\driverz\R;c:\driverz\SND\A;c:\driverz\SND\C;c:\driverz\SND\CR\COMMON;c:\driverz\SND\CR\Extra;c:\driverz\SND\CR\LANG;c:\driverz\SND\CR\LS;c:\driverz\SND\CR\WIN2K_XP\Data;c:\driverz\SND\CR\WIN2K_XP;c:\driverz\SND\CR;c:\driverz\SND\N;c:\driverz\SND\R;c:\driverz\SND\S;c:\driverz\SND\T\A;c:\driverz\SND\T\D;c:\driverz\SND\T;c:\driverz\SND\V\E;c:\driverz\SND\V\V;c:\driverz\SND\V;c:\driverz\SND;c:\driverz\V\ATI\B_17154;c:\driverz\V\ATI;c:\driverz\V\NVIDIA;c:\driverz\V;c:\driverz\Vmware\hgfs\win2k;c:\driverz\Vmware\hgfs;c:\driverz\Vmware\memctl\win2k;c:\driverz\Vmware\memctl;c:\driverz\Vmware\mouse\win2k;c:\driverz\Vmware\mouse;c:\driverz\Vmware\scsi\win2k;c:\driverz\Vmware\scsi;c:\driverz\Vmware\video\winnt2k;c:\driverz\Vmware\video;c:\driverz\Vmware\vmxnet\win2k;c:\driverz\Vmware\vmxnet;c:\driverz\Vmware"run setup and guess what?ALL DRIVERS WERE INSTALLED RIGHTall of them(in vmware but it will work now for sure)(H)so now my friends we have to find away to extract it before gui starts,scan it and add entries to HIVESFT.INF atleast it works this s***ty thing:)and theres no need for oempnppath:) Link to comment Share on other sites More sharing options...
turbomcp Posted September 1, 2004 Share Posted September 1, 2004 one more updatefrom what i saw HIVESFT.INF is being called from txtsetup.sifon fresh or upgrade installsso maybe we can make our own program that will scan c:\driverz(offline)collect data into another inf file(new one)and just "tell" txtsetup.sif to load that one tooand then we will be set to go:)i will try it and let you know if thats possible Link to comment Share on other sites More sharing options...
keul Posted September 1, 2004 Share Posted September 1, 2004 @serialzs : I don't want to bother anyone with repeating myself but here are the facts (short version this time )I insist on the fact that the details below are the results of tests done on my computer only (on my current windows / in real enviromnent unattend bootcd / vmware bootcd) (tests done on winxppro french sp1 final and sp2 final) and I don't want to talk for anybody else, maybe it's just me...- Your new files don't work at all (no driverz folder created, no files copied or even unpacked). I think there is definetly a difference between the autoit script of both drvz.exe version (apart from the call to 7z.exe changed to 7za.exe)- Your old drvz.exe with 7za.exe renamed to 7z.exe WORKS (I mean, files are copied, unpacked and any directory under c:\driverz is added in devicepath when gui setup is started). BUT the drivers don't get installed (in both enviromnents-real/vmware).- Yes, the same drivers, unpacked the same way in the same folder but with oempnpdriverpath work.- as turbomcp just wrote it, it seems that my theory is confirmed and that devicepath is read before t-39@turbomcp: great news! This is not what we were hoping for, but now we do know why it's not working as expected...@all:So what we have to do now, as turbomcp said is adding entries before the gui starts...Unfortunately, I don't know any way (value in winnt.sif...) to run files before Gui starts. So I see only 3 solutions :1- use no-dynamic devicepath (oemphpdriverpath or HIVESFT.INF), and that is NOT what we want (in that case, we won't be here)2- use pyron's method which involves using a false setup.exe doing our stuff (unpack, devpath...) and then launching real setup3- use the method described in this post (with serialzs's drvz.exe or turbomcp's cmd file) and after the call to DevPath.exe make windows gui setup RELOAD information about devicepath from registry. I am not an expert in registry but I think that there might be a way to make windows refresh values that get written...Well I'm gonna do some research on thrid point and keep you informed. Link to comment Share on other sites More sharing options...
zorro1 Posted September 1, 2004 Share Posted September 1, 2004 - Your new files don't work at all (no driverz folder created, no files copied or even unpacked).for me too with french SP2 Link to comment Share on other sites More sharing options...
turbomcp Posted September 1, 2004 Share Posted September 1, 2004 (edited) Usually killing explorer.exe will refresh the registry. But since there is no explorer.exe and no taskman.exe during setup this can't be done.So for now we got rid of the OEMPnPDriversPath in winnt.sif, which is also a good thing. The manual things we have to do when adding drivers (nor serial ata) are these:-make a new archieve called driverz.exe(containing all drivers needed)-extract it(on local computer)-run devicepath.exe on c:\driverz-copy registry devicepath and paste it to HIVESFT.INF-replace this file in iso and burnnot perfect but it will do for now Edited September 1, 2004 by Bâshrat the Sneaky Link to comment Share on other sites More sharing options...
Thauzar Posted September 1, 2004 Share Posted September 1, 2004 @serialI am under Windows XP SP2 final release, french version. I will retry with the 3 lines in [sourceblablabla] at the beginning and not and the end of the list. Else, i am experiencing the same problem as Keul and the others @allIs everyone having trouble on a french system??? Anyway, I don't want to play in my hive files so I really hope new files get posted soon Keep on I think you are moving closer to solving this. Link to comment Share on other sites More sharing options...
zorro1 Posted September 1, 2004 Share Posted September 1, 2004 test Methode 1 with motherboard ASUS A7N8X-E deluxe Raid driver SI3112r -> OKLan Marvell Yukon -> OKnVidia force ethernet -> OKMethode 2 -> KO Link to comment Share on other sites More sharing options...
Bâshrat the Sneaky Posted September 1, 2004 Share Posted September 1, 2004 test Methode 1 with motherboard ASUS A7N8X-E deluxe Raid driver SI3112r -> OKLan Marvell Yukon -> OKnVidia force ethernet -> OKMethode 2 -> KOKO????Good news! But did you use the entire pack? Are you using the 3112 controller in RAID? Link to comment Share on other sites More sharing options...
serialzs Posted September 1, 2004 Author Share Posted September 1, 2004 @allim sorrie for the NEW UPDATE drvz.exe, I see the PROBLEM now... I modify it again and test it...JUST CHANGE the DRVZ.EXE...the others will stay the same...TRY THIS NEW ONE... -=[serialzs]=-Drvz.zip Link to comment Share on other sites More sharing options...
Bâshrat the Sneaky Posted September 1, 2004 Share Posted September 1, 2004 @allim sorrie for the NEW UPDATE drvz.exe, I see the PROBLEM now... I modify it again and test it...JUST CHANGE the DRVZ.EXE...the others will stay the same...TRY THIS NEW ONE... -=[serialzs]=-THANK YOU!!! We're hoping for the best.... (at least I am )Could you also edit your first post please? Link to comment Share on other sites More sharing options...
Lucius Snow Posted September 1, 2004 Share Posted September 1, 2004 Cheers serialzs. I'll try that now and let you know. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now