Using the Linux boot disk, it quickly copies the first "group" of files (ending with os/WinXPsp2/I386/NTLDR) and then hangs. The screen says "Please wait while Setup copies files to your hard disk." After a while, there is occasional progress but smb messages appear and eventually Setup times out.
smb_add_request: request [c54de0e0, mid=6092] timed out!
First, it seems that the first delay happens even with the DOS boot. I guess Setup is doing some internal preparation (maybe checking hardware).
This happened to me several times, too. It was always caused by either:
1) server side
- server too old/slow to handle the requests (I suspect other hardware problems)
- network card in the server broken / bad driver (what card do you have and what module does it use)?
It's an Athalon 1800 with a "3Com Corporation 3c905 100BaseTX [Boomerang]" (according to "lspci") using the "3c59x" module. There is nothing else using this server -- it's totally unloaded.
2) client side
- on some older hardware I occassionally saw it when I was installing more than 5 clients in the same time; it was not "critical" and it recovered though.
Since it's a P3-600MHz, also with a 3c905 card, I figured it would make a good test machine.
I ran a tcpdump with the DOS boot, and noticed that it's using a different interface to Samba. It uses the older NetBios stuff rather than the new CIFS.
Thinking perhaps the problem was with Samba, I upgraded the server from version 3.0.7 to 3.0.10.
That did it! It continued copying files to the end and rebooted.
I guess for now I just let it run. Thanks!
Other observations:
(1) One of the "./prepare" files does not seem to exist:
just correct it in the script (or remove it). links in the internet tend to change...
Yup. Figured you might want to change it in your code. I haven't worked out what the new URL is, yet.
(2) Linux Boot does not default the Guest password to "Guest" when manually changing the defaults. There's nothing wrong with this; it's just different than the DOS boot disk.
you can prepare your own CD with your own server, path, username and password.
I tried that, but "make" started looking for kernel source and I didn't want to spend the time working it out just yet.
Another observation:
The Linux console blanker kicked in during the install. Could this be disabled. It caused me a moment of panic before I realized what it was.
Brian
( [EMAIL PROTECTED] )-------------------------------------------------------------------------------
Sticks and stones may break bones, but words will shatter the soul.
th.
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
