James MacLean <[EMAIL PROTECTED]> writes: > Just got the nerve to start silent XP installs :). Find that I am > getting a bunch of "Copy Error" "Setup cannot copy the file > <Something>.dll.
Does it provide an error code? As M. Bottura suggests, this could be a hardware problem. It could also be a permissions problem. > Not knowing the logic of how Windows decides what to copy from the > copy medium to the local drive, I am wondering if there is an INF > file or some area that I should be updating to include these files > so that they will be copied properly? It should "just work". > Also, tried setting up a DELL cd distribution point, but it doesn't > seem to work like a normal XP install CD... Any pointers on how to > get it to actually be useable? It has the $OEM$ at the root of the > CD. When you install from CD, setup looks for $OEM$ at the root of the CD instead of inside the i386 directory (nobody knows why). So when you copy the CD to the network, that $OEM$ folder will be ignored. You could move it to live under i386, but there is no guarantee that the contents will actually do what you want. What I have been doing for Dells is just copy the i386 folder and populate $OEM$ myself with the current drivers from Dell's site. I lose the Dell custom background and cutesy support tool and so on, but that does not bother me too much... - Pat ------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 _______________________________________________ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info
