I'm working on a number of custom installation scripts for my environment, and am having trouble testing them. I find that testing doesn't work very well when doing it outside the context of actually installing via Unattended, and doing a full install takes forever, compared to the problems with my scripts. That is, an hour of turnaround time to fix a path problem or syntax error really delays my development.
Does anyone have any tips on doing testing more quickly? -Bitt Faulk ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ unattended-info mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/unattended-info
