Blade]ZFA[

I'm not sure what version of Ghost you're using, but for mass rollouts, you should be using the Enterprise console. Basically what that allows you to do is install a boot partion (Basically putting the contents of the floppy disk on to the HD). Ghost creates this partition for you and you multicast it on to the HD. Once this is done, the nic of the machine will show up in the console and you can more easily perform cloning operations. We currently have any clients simply pull an ip from the dhcp server. You can rename computers based on whatever scheme you choose, and if you're running NT you can have it automatically add to a domain and change the sid. There are also more advanced features that allow you to create autoinstall packages among other things. There's more, but I think you'll find that the Enterprise version if you're not already using it is more suited to large rollouts. PS Convince Management to go NTFS! I personally don't find many users have the need to reghost themselves, or if they do I send them the CD's (You can clone an image to multiple cd's). So you may be able to not have the ghost image on the E drive...)

I had a user who had that problem, and it definitely was a stumper. In his case, the problem was that the nic's were either not properly getting an interrupt or memory resources. The solution was to upgrade his vid driver to the nvidia reference drivers. We narrowed it down to a resource problem, since he was able to take out that nic and install it fine in another XP box. As well, he took the working nic out of the duplicate XP box and when he went to install on the original, received the same data error message. It might help to troubleshoot by finding what interrupt, memory resources are being allocated, and if it's sharing with something else. Hope this helps.