keul Posted August 31, 2004 Posted August 31, 2004 Oops, just a typo, it's really cmdlines.txt on my cd. Post edited.
Lucius Snow Posted August 31, 2004 Posted August 31, 2004 Same problem here. No driverz folder created.keul, can you attach these old files to try your hybrid method ? Thanks.
turbomcp Posted August 31, 2004 Posted August 31, 2004 wellafter giving up with the problematic methodi did the followings:on cd:on cdroot-cd.txt$oem$\DRIVERZ\devpath.exe,driverz.exe,presetup.cmdon winnt.sifDetachedProgram=".\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.sifnothingpresetup.cmd does this:rem find cdromIF 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.exeREM Scanning for driverdirectories%cdrom%\$oem$\DRIVERZ\DevPath.exe %systemdrive%\DRIVERZexitDRIVERZ.EXE =all drivers combined(vga,raid,net,vmware,sound) compresses as sfx using winrar with this comment:Path=%systemdrive%\DriverzSavePathSilent=1Overwrite=1works good,extracts everything to c:\DRIVERZ\.........adds the right registry entries to devicepathBUT vmware install wont install the vga and scsi drivers(basicly any drivers)dont know if its vmware or something is missing hereanyway when i used oempnppath=.... in winnt.sif the vmware vga driver installed fine.
Lucius Snow Posted August 31, 2004 Posted August 31, 2004 Hmm thank you very but i'm confused about the method described ..We have to create a file named cdroot-cd.txt at the root of the CD ? And its content must be :$oem$\DRIVERZ\devpath.exe,driverz.exe,presetup.cmdIs it correct ?Then having the following 3 files in Driverz folder ?- devpath.exe- driverz.exe- presetup.cmdFor the rest, i think i got it.One last question, my CD is multiboot so $OEM$ is in \Setup\XP\Professional\$OEM$ and not in the root. If it just change the path in all the command lines you posted above, it'll work ?Thanks.
keul Posted August 31, 2004 Posted August 31, 2004 @Lucius Snow : Here are the old files you asked for, let's hope you will find something interesting...@turbomcp : great work ! Basically, all you did is replace serialzs's drvz.exe with a batch file . But that was really usefull as we now know (as far as your method isn't working in real environment too) that the problem lies elsewhere than in drvz.exe.It means that either windows doesn't care about devicepath during install (which is hardly believable since big_gie's / pyron's methods are based on that) or that the registry write is done AFTER device detection...
turbomcp Posted August 31, 2004 Posted August 31, 2004 okfirst 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 isthe three files: devpath.exe- driverz.exe- presetup.cmd i put on the cd in $oem$\driverz and i execute it from thereif you want to put this folder somewhere else no problem just change the presetup.cmd accordinlyyou 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 thiswhen i used oempnppath=.....in the registry i see :%SystemDrive%\drivers\001\viasraid;%SystemDrive%\drivers\000\viaraid;%SystemDrive%\drivers\nvidia;%SystemDrive%\drivers and so onwhen i use the devpath.exe i seec:\driverz\a;c:\driverz\b and so oni know its the same thing but still maybe its making setup not look there maybe it needs variables and not real pathdont knowguess ill have to test it somewhere and see
arry Posted August 31, 2004 Posted August 31, 2004 (edited) I am ready to rip my hair out...I have made plenty of unattended dvd's in the past but I just cannot get this working.Am I doing this correct.OKI create the c:\XPCD\$OEM$\Driverz dir and place my .7z files in there including my storage files.I then put the 3 files into the i386 folderIn TXTSETUP.SIF I add the 3 lines7za.exe = 1,,,,,,,2,0,0Drvz.exe = 1,,,,,,,2,0,0DevPath.exe = 1,,,,,,,2,0,0by the way there are multiples instances of [sourceDisksFiles] so does it matter exactly under which one the 3 lines go?I then edit Winnt.SIFand put in the following:[unattended]DriverSigningPolicy=IgnoreNonDriverSigningPolicy=Ignore[GuiUnattended]DetachedProgram="%SystemRoot%\system32\DRVZ.EXE" I then add the appropriate sections to dosnetinf and then add the contents of Add_to_txtsetupsif to txtsetup.sif......Anyone any idea of what I am doing wrong.As the DVD boots the only error I am getting is aec6280.sys is not found????Please help... After thinking about it....I am using a SATA hardrive so how can it work with no OemPnPDriversPath as this is invoked before the GUI even begins.....I am correct in saying this? Edited August 31, 2004 by arry
turbomcp Posted August 31, 2004 Posted August 31, 2004 okif you get that error right after the boot from cdthis 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 driverif they all dont have entries or wrong entries youll get errorsand by the way i couldnt get this method to work right(devpath,7za,drvz)
arry Posted August 31, 2004 Posted August 31, 2004 hmmmm I just checked txtsetup.sif and I found entries for that driver ??
turbomcp Posted August 31, 2004 Posted August 31, 2004 if you see the driver in txtsetip.sif in all the right entrieslook 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 calledaec6280.sy_????????
arry Posted August 31, 2004 Posted August 31, 2004 I don't understand. The file definitley insn't in the i386 folder...Isn't it suppose to extract from the zip file...I can find the file when I manually extract the .7z file???
Bâshrat the Sneaky Posted August 31, 2004 Posted August 31, 2004 hmm, just a thought. wasn't pyron's method capable on placing most commands since the center of his project was with the presetup.cmd file?my presetup.cmd file contained this code:...With this method you have to enter manually the 7z files to extract...
Lucius Snow Posted August 31, 2004 Posted August 31, 2004 So who has managed to make serialzs's method work ? I've tried many times with no success.
Pyron Posted August 31, 2004 Posted August 31, 2004 Okay, so now it's my turn to present a possible solution...Let's go back to the roots:Create a directory with your drivers, put SetDevicePath.exe in it. Compress the contents of this directory with WinRAR, make it self-executable. Put the following in the comment:path=c:\driverssetup=SetDevicePath.exe c:\driverssilent=2overwrite=1Put the resulting sfx-archive on your CD and start it with DetachedProgram in winnt.sif as usual.Here is the catch: I did not test it, as I don't use winnt.sif. So it would be great if someone could test this method.(I would have used 7-zip if wasn't so restrictive about sfx-archives)-- Pyron
keul Posted August 31, 2004 Posted August 31, 2004 Here are the results of my last tests :As turbomcp said, I looked at DevicePath just before Device detection but it was ok. So I tested his hipothesis (setting %SystemDrive%\ instead of C:\ in devicepath).So here's what I did :1. Launched drvz.exe on my current system.2. exported Devicepath from registry (which gave me the exact same thing as in my previous vmware tests).3. replaced every C:\ with %SystemDrive%4. Saved this file in CDRoot\%oem%\%1\test.reg5. removed DevPath.exe from i386 so that it doesn't interfere with my tests6. After that I ran Unattend Cd in vmware7. As soon as Gui setup started, I ran a dos command line "start c:\test.reg" which asked me if I was ok to import value in registry (of course, I was )Then I verified in registry that reg file was imported (during this time, *.7z files were unpacking thanks to drvz.exe).But one more time, no driver was installed.* So this confirms that C:\ and %SystemDrive% have the same effect.* As I did this only a few seconds after Gui start, I assume that our problem is not related to the fact that devpath.exe is ran a few seconds too late.@pyron : After reading your method again (the one with presetup.cmd), I see a major difference with this one : you're importing registry settings BEFORE launching setup gui. So what I think is that when launching setup gui, windows loads registry (or at least devicepath value) in memory and then searches in memory for devicepath. So changing this value after setup gui is started may be too late. That's why oempnpdriverspath is working and not devpath (its value is imported before). However, I will test the solution you're giving us (who knows, I may be wrong), tomorrow (well, in 8 or 9 hours).
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