I seem to remember seeing this when I was first tinkering with the included OS install. It had been cause by a corupt copy of the WINNT32.hlp file copied from an appently bad disk. You may want to try a different disk.
The included OS install is a great tool, but for our enviroment, it ran just a bit too slow and did not allow for hardware independence. I created a document, located at
https://www-secure.symantec.com/connect/articles/quicker-scripted-os-install, that explains the procedure we went through here to speed up the process and allow for hardware independence. You might want to check it out if you would like a faster install.