Hi, On Fri, Feb 06, 2009 at 07:46:36PM +0100, Pierre Bourgin wrote:
> Aha, a search-windrivers.pl fan ! > > Unfortunately, I'm not shure search-windrivers.pl will work: > TXTSETUP.OEM is a specific stuff for mass storage driver, drivers that > Windows kernel need to load on startup if it want to access storage > devices. > > search-windrivers.pl provides drivers for plug-and-play system, ie once > the kernel has booted and is able to read files from hard-drive. Exacly. > With SATA controllers, it works most of time, since windows is able to > use generic/legacy access to controllers, so it can later install > drivers. > But for specific mass storage systems (SCSI, RAID, etc.) or recent ICH > intel stuff, It can be a real pain. Trouble seriously starts when you got serveral diffrent mass storage systems you need to support, so you need to combine the TXTSETUP.OEM files. > Back to [OEMBootFiles] trouble: nt5x-install mimics the Windows > installer comportment in DOS mode in order to avoid its boring copy > files mechanism; but this step also prepare stuff for real windows > kernel boot. > A short read of this script does not seem to take care about mass > storage specific hack,related to files copy or file content updates. > > Peharps the guy who wrote wonderful nt5x-install (project > http://unatteneded-gui.sf.net) have some interresting comments ? > Cc: him. > > But I don't know why this section is empty ... are you shure it's empty > because of nt5x-install ? What do you mean by DOS reboot ? You let > Windows starts ? In such as case, avoid it: reboot directly with > unattended and check the file content (Ctl-C to stop the installation). Directly after nt5x-install restarted the box, I had it boot form a dos boot disk, so I could see the content of the harddisk. Since my 2nd post on this, I have analysed the problem at bit more and figured out that it is the write_ini_entry that empty out the [OEMBootFiles] section. So I tired to be smart, commented out the write_ini_entry, modified the unattend.txt "masterfile" so it had entries those lines makes. However it dont work, so I guess the old installation method makes changes to a file, posible the winnt.sif file. Anyone knows more about this? If so please try to explain it abit, so I can either 1) write a script that makes the right changes to the installation files or 2) manually fix winnt.sif so my trouble is solved for now. Nils -- Nils Østbjerg SAMF-IT, Faculty of Social Sciences, Aalborg University, Denmark ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ unattended-devel mailing list unattended-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-devel
