first off, thanks for creating this project! A few things I've noticed while trying to work with it:
- as others in the mailing list have mentioned, there is no RTL8139 driver included yet. It would be nice if the next upgrade could include it as an option. Also, I've heard there is a different project that created a boot disk with tons of different drivers at once, using PCI auto-detection. Now that would be nice to have.
Anyway, I've customly hacked together a RTL8139 boot disk that works fine now. Most - but not all - of my client computers use RTL8139-based NICs.
- both when first booting and when rebooting after the partitioning, the disk asks whether the SMB login data (per default "GUEST", no password, don't save password list) is correct. I've edited this data to use a special account called "UNATTENDED" per default, somewhere in the system.ini (or protocol.ini?). The batch file is still asking though. Is there a way to set the ini files so that it won't ask and just go ahead and try connecting?
- After the partitioning, I've found it asks whether it should really format the disk. I always thought format.exe had a /y option for no longer asking, but I guess I was wrong (I tried with the format.exe supplied with unattended as well as with Windows 2000's version; neither had that option). Is there another way, using the Perl script, to tell it to go ahead?
- The third step, as I recall, where it stops is with the serial number. Even though I have provided a valid serial number in my ./site/unattended.txt file, it asks both during the perl script execution and during Windows 2000 Setup. I've used the format as it is printed; maybe I must leave out the dashes? Or maybe, as seen in your example
ProductKey=XXXXX-YYYYY-ZZZZZ-00000-11111
, I *must not* put quotation marks in that case? I should probably read Microsoft's full documentation on that sooner or later.
- Next up is a problem most likely difficult to solve (if possible at all): with the next reboot, the BIOS will recognize the disk again, and the disk will start its batch script again, even thought Windows 2000 Setup should continue. As far as I know, it is not possible in MS-DOS to continue booting from another partition (as it is possible in various other OS's, as the Windows 2000 Setup CD and your Boot CD prove). But maybe it *is* in FreeDOS? Maybe your batch script could recognize that the boot.ini contains an entry for the new already begun Setup and then stop continuing with mounting the share? (This one isn't really important, though it would be interesting.)
- Oh, and while we're at boot.ini, I've noticed with this kind of running Windows 2000 Setup, there is a "Previous Windows installation" item in the boot menu. Shouldn't the script take care of that?
Once again, thanks for your efforts, and thanks in advance for a reply!
Regards,
-- S�ren 'Chucker' Kuklau
------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com _______________________________________________ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info
