Anyway, a winnt.sif file for all intents and purposes is the same as a unattend.txt file. In fact, I renamed my unattend.txt to winnt.sif included the GuiRunOnce section to trigger the post-installation tasks and I was good to go.
One thing I would recommend is that you limit the number of directory nesting (subdirectories) as much as possible. For instance, there is not reason why you can't combined all your nic drivers in the same folder - $oem$\$1\drivers\nic instead of $oem$\$1\drivers\intel\eepro100\Winxp. Also, try to limit the name of subdirectories to 8 characters or less.
Good Luck!
On 3/3/06, Chris Bradshaw <[EMAIL PROTECTED]> wrote:
Hi....
Somewhat newbit question....
I was just wondering if unattended can be made to work (without undue
effort) if I use nLite to slipstream MS hotfixes (eg: RyanVM's Update
Pack) or integrate drivers into the WinXP/2k3 OS file tree?
I have tried to use nLite to integrate drivers with XP, but during the
install it complained about missing files....
I then tried to use nLite to slipstream hotfixes with XP, but again
during the install it complained about missing files....(things like
.fon and .dll files)....
I am guessing that the problem is that nLite and slipstreaming was
intended for the WINNT.SIF method of unattended installations, but the
unattended.sourceforge.net way uses an unattended.txt file + DOS mode
for initial install......am I near the mark?
Thanx in advance
Chris Bradshaw.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmdlnk&kid0944&bid$1720&dat1642
_______________________________________________
unattended-info mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/unattended-info
--
Regards,
Conrad Lawes
PXE Guru
