Comment 1 for bug 237867

I have the same issue.

To start it failed due to not mounting the files ( no cdrom ), and I fixed the same way, manually mounted the files.

Then I ran across this issue, I would assume either the ISO or the interpretation of the iso is breaking a symbolic link.

I ended up copying hardy over to get past that. ( rm stable; cp -r hardy stable ).

Then I had yet another issue, file names were truncated at 64 characters.

For example:
./pool/main/l/linux/fs-secondary-modules-2.6.24-19-generic-di_2.6.24-19.34_amd64.udeb

Ends up as
./pool/main/l/linux/fs-secondary-modules-2.6.24-19-generic-di_2.6.24-19.34_amd64.ude

And is thus not found.

 If I daemontools mount the ISO, it also shows the file names as truncated, and the stable as an empty file instead of a link.

But if I burn the same image, and put the disk in a freeBsd machine I have handy, mount it; its links and un-truncated file names.

So maybe something in the Windows ( Vista 64-bit for me ) side of things it making unetbootin read the files incorrect, and place them that way?