Jordan Share <[EMAIL PROTECTED]> writes: > >>I am getting the error: > >> > >>Setup was unable to copy the following file: > >> > >>IA32 > >> > >>o press ENTER to retry the copy operation > >>[ etc. ] > >> > >>I did a find in the os directory and this is the only hit: > >>./win2ksp4/I386/$oem$/$1/drivers/shuttle/LAN/Windows/Drivers/IA32
Aha. This path: /os/win2ksp4/I386/$oem$/$1/drivers/shuttle/LAN/Windows/Drivers ...is 62 characters long. Append "IA32" and it exceeds 64 characters, which is the maximum path length for FreeDOS. I started to understand what was happening when I booted to FreeDOS and created this directory chain: \foo1\foo2\foo3\foo4\foo5\foo6\foo7\foo8\foo9\foo10\foo11\foo12 When I tried "mkdir foo13", it failed. The only thing I do not understand is why your $oem$ structure works when using the FreeDOS-based boot disk. I confirmed this theory by reading the FreeDOS kernel source code. The PARSE_MAX constant creates the limitation. I suppose we could build our own copy of FreeDOS. And maybe I will do that eventually... Meanwhile, I think we should just document this and move on. Even just testing for it in install.pl would be expensive, since it requires recursing through the entire $oem$ structure looking for the longest total path. I am not sure it is worth it. - Pat ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ unattended-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-devel
