Jenny Taylor

HA! Well I believe I have identified my problem. Bye the way thanks for that bit of info jbm it actually pointed me in the right direction to what my problem really is. I was blaming the RAID drivers when in fact its nvidia. Unsigned. I still cant get the darn thing to cooperate even when trying it out on XP. And nothing improves matters if drivers and inf files are itemized in winnt.sif. So using an $OEM$ directory on the CD is now mealy a wish. BUT I managed a hack. B) It's crude but effective. I wrap all my additional programs like winzip, nero, office etc into an exe file and these load up using a (somewhat unorthodox method to launch the runonceex.cmd). Best part about that is it works on any drive letter. Prior to that happening any updates and hotfixes install during GUI mode. I still have to use the old F6/floppy method for the text mode part but what the heck. I figured after spending days messing with the thing this is good enough. Least I don’t have to use those 4 stupid floppy boot discs anymore now its been boot imaged to CD. Lol I have so much stuff loaded on now I think a DVD version is just around the corner. But it is kinda cool watching TV knowing the PC is self installing.

Just tried a test burning 1 cd with the RAID drivers on it via the $OEM$ directory and 1 cd without RAID Both tests resulted in a stop error screen 0x0000007B at the stage were windows 2000 is about to install after reboot. None of the two tests made any difference because I have OEM set to yes in winnt.sif When I set it to NO everything runs ok (except I cant install drivers or software additions etc via the OEM route obviously) So my questions are: Why is the use of OEM causing this problem and is there a way around it? Without the OEM ability I cant use RunOnce.exe or anything. Attached is a sample of my winnt.sif and txtsetup.sif files in case anyone cares to have a look and point me in the right direction. But I dont think these files are the problem for some reason the very use of OEM seems to dissagree with my pc Sample.ZIP

I've struggled with this for days now. Can someone help me please? First I thought it was to do with RAID but I sorted out that problem. Whenever I try to install windows 2000 with the OemPreinstall set to Yes in the winnt.sif I get errors like no raid fastrak.sys found. I figured it was to do with me burning the fasttrak raid drivers onto cd instead of using the usual method of F6 then floppy. Now I find that ANYTHING related to OEM set to yes just gives me an error. If i set it to NO then windows installs no problem. Ok I can live without an unattended RAID install (dont really care about that) but why is it giving me an error for anything else related to $OEM$. All I can install are hotfixes using the svcpack.inf and folder. Since they dont use the OEM call. As soon as I start trying to load in some extra programs like winzip. BOOM! error time. Switch OEM off in the winnt.sif and it all runs like clockwork. Really need some help please.

Hi JBM <quote> Are you copying the files to the i386 dir on the cd? Here is precisely what i am doing : I made the directory $OEM$ which is next to i386 NOT inside it Inside the $OEM$ is.. \$1\Drivers\ataraid\ (Here I copy all the files off the RAID floppy disc) these are.. Fasttrak.sys Fasttrak.cat Txtsetup.oem Fasttrak.inf ReadMe.txt After this I insert the below in the winnt.sif file OemPreinstall=yes OemPnPDriversPath="Drivers\ataraid" Next I add to the TXTSETUP.sif [sourceDisksFiles] Fasttrak.sys = 1,,,,,,3_,4,1 [HardwareIdDatabase] PCI\VEN_105A&DEV_7275 = "Fasttrak133" PCI\VEN_105A&DEV_5275 = "Fasttrak133" [sCSI.load] Fasttrak133_nt52 = Fasttrak.sys, 4 ;Fasttrak133_nt5 = Fasttrak.sys, 4 [scsi] Fasttrak133_nt52 = "win2000 Promis MBFasttrak133 Lite Controller" ;Fasttrak133_nt5 = "win2000 Promis MBFasttrak133 Lite Controller" Then I RUN MAKECAB C:\XPCD\$OEM$\$1\DRIVERS\ATARAID\FASTTRAK.SYS C:\XPCD\i386\FASTTRAK.SY_ Which as you know creates a file inside i386 When I run the install on a formatted hard drive I get the messege Cannot find Fasttrak.sys This always happens at the stage where the Win2000 files are going to be copied to the installation folder (the loading bare stage) If what I say I have done looks ok then I will attach a copy of winnt.sif/txtsetup.sif and the textsetup.oem files Maybe someone will spot my mistake. I've been through it a hundred times and also tried the same RAID as the tutorial...nothing works.

Windows 2000 with SP4 integrated Fasttrak ATA133 drivers used Hi. I really could do with some help on this one. I've followed the intermediate guide re: installing RAID drivers onto an unattended CD instead of a floppy to the letter. All works well if I DONT use the $OEM$\$1\drivers\blah\Fasttrak.sys folders directory on a burnt CD..But obviously I have to use the floppy disc to start an install of the OS. When I 1) Add the required $OEM$ dir to a CD and copy the RAID drivers to the relevant driver folder within it. 2) Update the winnt.sif with oempreinstall=yes and oempnpdriverspath set to the right location 3) Add whats needed to the txtsetup.sif file as per the tutorial 4) makecab Fasttrak.sys_ file etc etc and give the whole thing a go...I keep getting the same message Cannot find Fasttrak.sys file when i start to install. I've even tried using the same RAID version files in the exact same way as shown in the tutorial and made the necessary adjustments to sif files/makecab etc etc but I get the message cannot find si3112.sys. Is there something else I should have done? Some BIOS settings perhaps? Like I said it works fine running off a floppy. I've even tried installing the OS by using the same winnt.sif file in both the i386 folder and on a floppy disc in case it wasnt seeing the file but that didnt make a difference. I've run through the tutorials over and over checking and re checking my work but nothing seems to work. Can anyone help me here please. thanks