Codesmith Posted November 11, 2004 Share Posted November 11, 2004 Hi all;I've been playing around with XPCreate for about 6 months now, and while I love it for my older (read: simpler) boxen, I've encountered some difficulties with new boards and SATA. I've tried to read as many of the forum posts I can, but I didn't find this particular problem.I've built a XPCreate Home CD with slipstreamed drivers for a SI3112R and VIA 6420 series SATA controllers. I modded my winnt.sif as appropriate, and placed the drivers in the $OEM$\$1\DRIVERS subfolders. I checked the txtsetup.oem files to ensure that they refer to the proper file locations. The creation of the ISO went flawlessly, I tested the ISO in VMWare with good results and then burned a CD and went to the new box.I'm working on Athlon64 3400+, Asus K8V SE Deluxe - UAYZ, 512MB DDR400, WD2000 Caviar 200GB SATA, MSI 5900XT AGP, LG SuperMulti 16x DVDRW and a Panasonic 1.44Mb 3.5" floppy. And when I try to install, "No hard drive found". If I try to use a floppy and the F6 method, I get a message stating that the file viaraid.sys cannot be copied.This is not the first time I've run into a conflict with XPCreate and floppy based drivers. Mind you, I've heard that you cannot use an unattended install with floppy driver installs. At all.... I'm at a bit of a loss here. I'm hoping that it's not something really simple... Thanx.. CodesmithPS - Oh yeah... If I replace the drive with a normal IDE drive, the install goes in flawlessly...Here's my ini and sif files... and a directory listing...xpcreate.ini[XPCREATE]BOOTIMGFILE=CDBURNER=CDERASE=NOCDLABEL=XP2HOMECDSPEED=24COPYSOURCE=NODELISOS=NODELROOT=NODELTEMP=NODLAUTO=NODLURL=http://xpcreate.wiretapped.us/HFLISTSDOCABS=YESDOCD=NODOISO=YESDOPATH=NODOSATA=YESDOSVCPACK=NODRIVERDIR=$OEM$\$1\DRIVERSEXITQUIET=NOOVERWRITEOEM=YESQLOG=SILENTINSTALL=YESSLIPHF1=YESSLIPHF2=YESSLIPMDC=YESSLIPSPK=YESXPISO=XP2HOME_AUTOwSATA.ISOXPSOURCE=G:and winnt.sif;SetupMgrTag[Data] AutoPartition=0 MsDosInitiated="0" UnattendedInstall="Yes" AutomaticUpdates=Yes [unattended] UnattendMode=FullUnattended OemSkipEula=Yes OemPreinstall=Yes UnattendSwitch="yes" TargetPath=\WINDOWS Repartition=no FileSystem=* WaitRorReboot="No" DriverSigningPolicy=Ignore OemPnPDriversPath="\DRIVERS\SI3112R;\DRIVERS\VT6420"[GuiUnattended] AdminPassword="********" EncryptedAdminPassword=NO OEMSkipRegional=1 TimeZone=35 OemSkipWelcome=1[Display] Xresolution=800 Yresolution=600[userData] ProductKey="*****-*****-*****-*****-*****" FullName="User Name" OrgName="System" ComputerName=*[TapiLocation] CountryCode=107 Dialing=Tone AreaCode=519[RegionalSettings] LanguageGroup=1 Language=00000409[branding] BrandIEUsingUnattended=No IEBrandingFile=customie6.ins[Proxy] Proxy_Enable=0 Use_Same_Proxy=1[identification] JoinWorkgroup=WORKGROUP[Networking] InstallDefaultComponents=Yes[WindowsFirewall] Profiles=WindowsFirewall.TurnOffFirewall[WindowsFirewall.TurnOffFirewall] Mode=0and a directory listing of my FILESCD directoryD:\xpcreate\FILESCD\$OEM$\customie6.insD:\xpcreate\FILESCD\$OEM$\customie6_config.cabD:\xpcreate\FILESCD\$OEM$\$1\DRIVERS\SI3112R\si3112r.catD:\xpcreate\FILESCD\$OEM$\$1\DRIVERS\SI3112R\Si3112r.infD:\xpcreate\FILESCD\$OEM$\$1\DRIVERS\SI3112R\Si3112r.sysD:\xpcreate\FILESCD\$OEM$\$1\DRIVERS\SI3112R\SiiSupp.vxdD:\xpcreate\FILESCD\$OEM$\$1\DRIVERS\SI3112R\SilSupp.cplD:\xpcreate\FILESCD\$OEM$\$1\DRIVERS\SI3112R\SIWinAcc.sysD:\xpcreate\FILESCD\$OEM$\$1\DRIVERS\SI3112R\TxtSetup.oemD:\xpcreate\FILESCD\$OEM$\$1\DRIVERS\VT6420\TXTSETUP.OEMD:\xpcreate\FILESCD\$OEM$\$1\DRIVERS\VT6420\viamraid.catD:\xpcreate\FILESCD\$OEM$\$1\DRIVERS\VT6420\VIAMRAID.INFD:\xpcreate\FILESCD\$OEM$\$1\DRIVERS\VT6420\viamraid.sysD:\xpcreate\FILESCD\$OEM$\$1\DRIVERS\VT6420\viapdsk.catD:\xpcreate\FILESCD\$OEM$\$1\DRIVERS\VT6420\viapdsk.sysD:\xpcreate\FILESCD\$OEM$\$1\DRIVERS\VT6420\viapide.infD:\xpcreate\FILESCD\I386\winnt.sifDon't worry about the customie6 stuff.. It has to do with the IE6 Administrators Kit for setting up some custom IE6 stuff... B) It work's just fine... Link to comment Share on other sites More sharing options...
Bilou_Gateux Posted November 12, 2004 Share Posted November 12, 2004 See here.try to add reference to your sys driver in dosnet.inf under section [FloppyFiles.2]and better follow instructions by TBone2 Link to comment Share on other sites More sharing options...
GreenMachine Posted November 22, 2004 Share Posted November 22, 2004 Welcome to MSFN, Codesmith!Did Bilou's suggestion solve this problem, or are you still in Limbo? 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