Urs Rau wrote:
Thanks Jordan,
On Mon, 18 Oct 2004 08:35:48 -0700, Jordan Share <[EMAIL PROTECTED]> wrote:
It didn't happen with Unattended 3.5 because they were using MSDOS, and
this is a Freedos problem.
But this tells me about loads of files that are over the 64 absolute
filename + path limit, but all of these appear to make it to the HD
intact.
Perhaps it is just a limit on the path, and not the filename&path together?
But the files I do get error messages about are the ones that are 4
levels of directories down relative to $OEM". Maybe the problem is not
the 64 character filename limit at all or maybe there are two
problems?
Problem 1 being the 64 characters filename length issue.
And problem2 being the case of subdirs more than 4 levels down from
$OEM$ (meaning more than 8 levels down in total).
I ran into the same problem when I converted to the latest version.
Except I forgot what it was. So I googled for it. Surprisingly, I
found someone with the exact same problem that I had. Oh. It was *me*,
in a thread that started from when I tested 4.0, months ago. Heh. :)
FMI what was the subject of the thread?
Here is the link to the archive:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg00090.html
Jordan
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
unattended-info mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/unattended-info
