Hello all, and Tommyp! I'm very glad to have found your script, I've been trying to find a solution for this for a few months off and on. The whole process has taken me on a wild adventure, which I am glad to have the experience for. I'll go into details after a question, so those of you who do not wish to read so much may be spared its' length I set up the folders and inserted files (ie6) and such per the instructions of all the text files, ran the CMD and everything seemed to execute properly. But on install from this CD my Internet Explorer folder is almost empty. No IE or Outlook icons are present. My fdvfiles dir is empty, that was the first thing I checked I've examined the cabs processed by the script and it seems to be okay, so I'm thinking the problems lies somewhere in the install or copy of ie6 files during win2000 installation. I saw one other mention on the forum of this happening, and a suggestion to reread instructions and try again. I tried 3 times double checking myself and it seems to be right. Any suggestions on what to look for, or where I can check if the files are being copied or installed during win2k installation? Also I had some unattended setup options and other tweaks in my source before I ran the script, could there be a conflict there? Thanks in advance for any help or suggestions you may offer! Read the bold in the story below for some useful programs that may also help you in your trails of the Unattended Boot cd. ~~~ The story commences: In my happiness and excitement of finding this script, I quickly set up the files as instructed, drop in my ie6 files and download all the hotfixes I need. I edit the TXTSETUP.SIF to remove the box at the end of the file, but remove the line breaks at the end of the previous entry. So when I run the CMD file, the append command creates a conflict in the file. After the script finishes, I happily burn a cd and pop it into my laptop, expecting all to go well as it has with my other unattended bootable cds. The installer pauses at it's blue screen and mocks me with the quite vague "Line 11933 of the inf file is invalid." THE inf file? WHAT INF FILE? oi. So, trying to figure out what inf file I burn a cd-rw with the two largest infs renamed to try and eliminate the problem file. No go. Frustrated with recompling an iso and burning 3 cd-rws to match to try and detect the problem file, I turn to Virtual PC from Microsoft. Another unattended install site suggested to use that to test Unattended Installs of Programs, but I didn't think it was going to be as easy or useful as it turned out to be! I keep describing to friends as a PC Emulator for the PC, which works out great for testing this kind of thing. I was getting a little sick of killing my laptop installation just to try an auto-install disc, now all I do is load the .ISO in the Virtual CD drive and boot! Next, I take the long route of process of elimination to figure out the problem file in my disc setup. To remove the long process of rebuilding a bootable .ISO of the win2k setup files to determine the problem, I download MagicISO, an ISO-Image editor to ease my pain. Granted, I should have followed my initial instincts of seeing what problems may lay in the main files the CMD script and unattended installs work with and I probably would have saved myself an hours worth of grunt work, but I got two very useful programs out of the deal so I don't feel so bad about it. So! Go try Virtual PC from Microsoft, VMWare is the competitor, for those trying to get away from Microsoft at least a little. And also try MagicISO which can edit and create bootable CDs also. Thanks for reading! P.S. I have torrents if you need them!
