turbomcp

ok my friend this is how it works peiod: when WindowsXP setup has starts, any additional detected hard drives that have existing partitions will be assigned drive letters first if the drive doesnt have a partition it is "ignored" and the next volume gets drive letter.(lets say the cd-rom) i think what you should do is this: leave the unattended "open" to select the drives then format them as whatever you want(c:,d:\) then everything else with be unattaneded and everything should work

hi something i thought of how are the disks(channels configured) are those 2 sata disks and then cdrom on ide? maybe windows configures the letters based on channels like this: 1.sata 1 2.sata 2 3.ide primary 4.ide slave

dont forget to record the iss file using -r -a not just -R cause it doesnt work in the latest version it creates the wrong iss file(incomplete) and then setup doesnt run

getting error when windows loads(text mode even before partition or welcome) "the file s150sx8.sys is corrupted" sorry:( forget my post was just too excited about this new pak:) what i did was compress the driver(intel one) again and replace it and it works fine(i mean in vmware) will try real machines tomorow or today if i find one:) great work

ok heres a newsflash you should use wsftp90ec.exe -a -r when recording the iss file not -R this is how it works in the new version when using those commands it will record the right iss file format and everything works:)

anybody tried to make this thing work silently i used version 9.0 with -R and iss file and it worked fine now in version 9.01 it doesnt install heres what i did install it with -R take the iss file install using this: REG ADD %KEY%\012 /VE /D "Ipswitch WS FTP Professional v9.0" /f REG ADD %KEY%\012 /V 1 /D "%cdrom%\install\Applications\Ipswitch\fo-wsf9.exe -s -f1\"%cdrom%\install\Applications\Ipswitch\setup.iss\" -f2\"%systemdrive%\ftp.log\"" /f it doesnt work:( dont know maybe im forgeting something here

hi i used the guide for erd and in general it works except for two errors i get winbom error for network adapter(i beleieve this is vmware fault because of the driver) and i get annot read registry files from current installation,system,software...) if i logoff and login it recognizes the right c:\windows directory and works ok i just wanna get rid of this error it must be specificied somewhere any ideas??

winternals enterprise defrag is no.1 tool just check the benchmarks ,it kills every other defrager out there you can rip the dos files and run it from command line its the fastest there is and the overall best for professionals if you want gui go with diskeeper

i dont get it didnt we conclude this issue by saying windows doent look in the registry(atleast not in that location) after gui starts only before that? we tried entering the same info before gui starts and everything works so how can this thing work?(i wish it would but how)

100% sure my drivers are there(in the 7z files) i checked and i extracted them the only thing i did to make the 7z archieves is right click the root folder ADD TO ARCHIEVE and specified the options from the guide i have no idea why it doesnt extract the subfolders only the root folder

maybe microsoft tweaked the french version to work right:) im moving to xp frech edition:) everything works there:)

same here i got the new file replaced it and run test again i only have the root folder in driverz like this: c:\driverz\vmware(empty) c:\driverz\vga(empty and so on and on the registry i got those directoies only i used 7zip to make a 7z of the folders i want with the drivers once again has anybody made this thing work right and how please post all 3 relevant files here so we all know we are testing the right versions of everything and that it works right thanks

i hate to be a party ruiner:( but like other people said i got to a conclusion that this cannot be done after gui starts ,so the only advance i did right now is just to compress and decompress drivers and this little util from serials that scans the directory for me:) instead of me typing it all and making mistakes so i dont see anyway this will work even with new version windows just doesnt look in that value after gui setup starts:(

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 burn not perfect but it will do for now

one more update from what i saw HIVESFT.INF is being called from txtsetup.sif on fresh or upgrade installs so 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 too and then we will be set to go:) i will try it and let you know if thats possible

ok guys breaking news i read the theory of devicepath read into memory even before t39 so i decided to try alittle trick myself i run devpath.exe on my c:\driverz got the registry entries and added them to HIVESFT.INF in i386 which is basicly the first registry enteries there are before the setup starts the default entry there for devicepath is %systemroot%\inf i added mine after that and made sure they are there before my other script runs at t39. my HIVESFT.INF looks like this now HKLM,"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 RIGHT all 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:)

if you see the driver in txtsetip.sif in all the right entries look somewhere else>> dosnet.inf [FloppyFiles.2] and [Files] (even though i added my own drivers without dosnet.inf and it worked fine) are you sure that in i386 folder you have your driver? that is a driver called aec6280.sy_ ????????

ok if you get that error right after the boot from cd this means either it cant find the file in i386(compressed version) or your txtsetup.sif is missing one of the following somehwhere(doesnt matter where you entered it it scans the whole file) [sourceDisksFiles] look for aec6280 [HardwareIdsDatabase] [sCSI.load] [sCSI] these should have entries for that driver if they all dont have entries or wrong entries youll get errors and by the way i couldnt get this method to work right (devpath,7za,drvz)

if you cut/move the file to a ntfs folder on same volume it will retain his permissions if you copy the file the user will looose permissions he had

ok first my "method" is not new:) i was just tired of it not working and decided to do something about it:) you dont have to have the cd.txt in the root of cd you can use another file for checking where the cd is the three files: devpath.exe - driverz.exe - presetup.cmd i put on the cd in $oem$\driverz and i execute it from there if you want to put this folder somewhere else no problem just change the presetup.cmd accordinly you know i checked the registry before hardware detection starts it seems ok (shift+f10 and then regedit) so i dont quite get why its not installing it right. anyway one thing i saw was this when i used oempnppath=..... in the registry i see : %SystemDrive%\drivers\001\viasraid;%SystemDrive%\drivers\000\viaraid;%SystemDrive%\drivers\nvidia;%SystemDrive%\drivers and so on when i use the devpath.exe i see c:\driverz\a;c:\driverz\b and so on i know its the same thing but still maybe its making setup not look there maybe it needs variables and not real path dont know guess ill have to test it somewhere and see

well after giving up with the problematic method i did the followings: on cd: on cdroot-cd.txt $oem$\DRIVERZ\devpath.exe,driverz.exe,presetup.cmd on winnt.sif DetachedProgram=".\system32\cmd.exe" Arguments="/C START /MIN FOR %I IN (D: E: F: G: H:) DO (IF EXIST %I\$OEM$\DRIVERZ\PRESETUP.CMD (%I\$OEM$\DRIVERZ\presetup.CMD) ELSE (FOR /D %J IN (%I\*) DO (IF EXIST %J\$OEM$\DRIVERZ\presetup.CMD (%J\$OEM$\DRIVERZ\presetup.CMD))))" on txtsetup.sif nothing presetup.cmd does this: rem find cdrom IF EXIST D:\CD.txt set CDROM=D: IF EXIST E:\CD.txt set CDROM=E: IF EXIST F:\CD.txt set CDROM=F: IF EXIST G:\CD.txt set CDROM=G: IF EXIST H:\CD.txt set CDROM=H: IF EXIST I:\CD.txt set CDROM=I: IF EXIST J:\CD.txt set CDROM=J: start /wait %cdrom%\$oem$\Driverz\driverz.exe REM Scanning for driverdirectories %cdrom%\$oem$\DRIVERZ\DevPath.exe %systemdrive%\DRIVERZ exit DRIVERZ.EXE =all drivers combined(vga,raid,net,vmware,sound) compresses as sfx using winrar with this comment: Path=%systemdrive%\Driverz SavePath Silent=1 Overwrite=1 works good,extracts everything to c:\DRIVERZ\......... adds the right registry entries to devicepath BUT vmware install wont install the vga and scsi drivers(basicly any drivers) dont know if its vmware or something is missing here anyway when i used oempnppath=.... in winnt.sif the vmware vga driver installed fine.

hi i am making afew checks to the compressed drivers method and i dont see why this is needed before i used vmware drivers for testing and everything installed fine(vga) now ever since i added this entry it doesnt get installed at the end of install it is marked with yellow mark any idea what exactly does this do????????? cause to me it seems it conflicts with: DriverSigningPolicy=Ignore

i have a stupid question(guess thats why i am here for sometimes:)) i have an asus p4p800 delux with via raid and also have another board which i cant remeber with viasraid before i used the txtsetup.sif mehtod(added the right entries in txtsetup.sif and compressed drivers to i386,added the winnt.sif entries) and that was it it worked so my question is why do i need to patch the dosnet.inf too?? and while we are at it will the mraid work on the sraid from via? is that some updated version or complete diffrent driver?(in that case i will need to add the viasraid also will appreciate any replies thanks

i was begining to think im nuts or something since this thing doesnt work did about 10 installs on vmware or physical pc same thing anyway i think vmware doesnt have any "bugs" this is regular extraction and search for drivers during install,nothing more if it will work in vmware it will work on regular pc also i mean when i use oempnppath= for vmware drivers they all work great so vmware can do it its something to do with the filesa themself and what they do anyway waiting for serials to see whats happening

you can also just loggof and login it will process the runonce also