> You're doing it wrong. Use ISO9660 (e.g. Linux mkisofs) tools > to modify this.
Yes, I know I'm "doing it wrong"; my point is that "doing it right" requires picking apart the source code and reverse-engineering the build process for the sake of adding a few dozen characters to a single file, all so I can override defaults that make no sense for any real Windows production environment. (If you're going to enable Guest, you may as well dispense with the login entirely and just set the share/fs perms on \\ntinstall\install to Everyone:Read) > > Jumping back and forth between the boot medium, c:\netinst, > z:\dosbin, > > and z:\scripts without any indication of how and when > script execution > > is handed off (or why) makes the system nigh-unmodifiable. > > You have the source code, go modify it if you don't like the > coding style. Which part of "nigh-unmodifiable" are you having trouble understanding? I'd gladly go and modify the source code, if the source were at all comprehensible. As it is it's hundreds of lines of undocumented spaghetti logic. I haven't the time to rewrite the entire scripting system into something that's actually maintainable. It's easier for me to just start ex nihilo with a DOS bootdisk, the Server 2003 SP1 deployment tools, and VBScript for the postinstall (which is what I'm doing). Chris Doherty Helpdesk Analyst Crompton Co./Cie a Chemtura Company Elmira: (519) 669-1671 x319 ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ unattended-info mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/unattended-info
