ISO image creation makes files name truncated.

it may be realated to:
FreeDOS itself supports no long file names
http://fd-doc.sourceforge.net/faq/cgi-bin/viewfaq.cgi?faq=General_Information/164

FreeDOS does not support LFN, but you can
get free "DOSLFN" and "LFNDOS" drivers for all DOS
Versions.

I can't use DOS into my project because it is copyrighted by Microsoft,it against the rules. Isn't this problem related to the mkisofs cd/rom parameters ?

I didnt say to use DOS, what I said is since you are using a FreeDOS image to boot from CD any file name longer than 8 characters is truncated like you describe, because Freedos and most DOS's for that matter do not support long file names out of the box (in dos 8 characters + 3 extention was the rule for file names)

But by using DOSLFN you may be able to.
http://www.freedos.org/software/?prog=doslfn
DOSLFN is a program to provide the long filename (LFN) Win9x API in plain DOS
I do not believe this would brake any copyright rules.

You could also make sure the initial files required to start win7 installation are 8 char or less.
Like  autounatted.xml to AutoU.xml

Wouldnt this cover your needs?
How To Create Unattended Windows 7 Installation Setup
http://www.intowindows.com/how-to-create-unattended-windows-7-installation-setup/

I've already fixed the Windows 7 Unattended installation part,now I have to fix the LFN part. I ran doslfn as soon as FREEDOS has been loaded into the RAM memory,but it didn't work. Autounat.xml is not became autounattend.xml.

didn't work. Anyway this is my new makeiso.bat file,maybe you found some error :

@echo off
set isofile=fdoem.iso
set basedir=CDROOT
REM boot isolinux
set params=-b isolinux/isolinux.bin -no-emul-boot -boot-load-size 4 -boot-info-table -N
REM support Joliet (MS Windows (R) long filename support) filesystem
set params=%params% -iso-level 2
set params=%params% -J
set params=%params% -l
set params=%params% -D
set params=%params% -joliet-long
set params=%params% -relaxed-filenames
REM rename boot.catalog to _$ and hide it.
REM set params=%params% -c boot.catalog -hide boot.catalog -hide-joliet boot.catalog
rem set params=%params% -c _$ -hide-joliet _$ -hide _$
if exist %isofile% del %isofile%
if exist %isofile% GOTO errRO
if NOT "%MKISOFSRC%"=="" set MKISOFSRC.$$$=%MKISOFSRC%
set MKISOFSRC=mkisofs.rc
set msg=Creating cdrom imagefile %isofile% out of directory %basedir%
echo %msg%
if "%OS%"=="Windows_NT" title %msg%
echo -o %isofile% %params% %basedir% > makeiso_.$$$
type makeiso_.$$$
MKISOFS.EXE @makeiso_.$$$
if "%errorlevel%"=="0" set msg=Created cdrom imagefile %isofile% out of directory %basedir%
if "%errorlevel%"=="0" goto end
set msg=Error %errorlevel% :
if "%errorlevel%"=="65535" set msg=%msg% Rename isolinux directory and isolinux.bin all lowercase!
if "%errorlevel%"=="9020" set msg=%msg% Please shorten command line, command line too long.
if "%errorlevel%"=="255" set msg=%msg% Please do not rename or remove isolinux\isolinux.bin
if "%errorlevel%"=="13" set msg=%msg% Please remove read-only attribute from file isolinux.bin
del %isofile%
goto end

:errRO
set msg=Error: Unable to remove existing ISO file: %isofile%
goto end

:end
if exist makeiso_.$$$ del makeiso_.$$$
if NOT "%MKISOFSRC.$$$%"=="" set MKISOFSRC=%MKISOFSRC.$$$%
set MKISOFSRC.$$$=
echo.
echo %msg%
REM when ran on NT, e.g. via explorer instead of from cmd shell
if "%OS%"=="Windows_NT" title %msg%  
if "%OS%"=="Windows_NT" pause
if "%OS%"=="Windows_NT" title ""

I read the doslfn.txt file and it says :

c (CDROM support): Enables CDROM support, i.e. DOSLFN uses much more memory
  to keep code for CDROM initialization and CDROM access. This switch defaults
  to the state whether SHSUCDX v3.01 is loaded or not (this version of DOSLFN
  does not work with MSCDEX or earlier versions of SHSUCDX). You must include
  a c+ switch if you load DOSLFN before SHSUCDX, and you want long file names
  on CDROM!
 
I have changed the old version of SHSUCDX with this new one and I started doslfn with the -c+ switch,something like this : doslfn - c+,but nothing helped.

I've added the Rock Ridge extensions,this is the output of the image creation. As you can see,long file names are again truncated even using your parameters :

Creating cdrom imagefile fdoem.iso out of directory CDROOT
-o fdoem.iso -b isolinux/isolinux.bin -no-emul-boot -boot-load-size 4 -boot-info
-table -N -r -iso-level 2 -J -l -D -joliet-long -relaxed-filenames CDROOT

Using "mkisofs.rc"

Warning: creating filesystem that does not conform to ISO-9660.
Using TERMINALSERVICES-SESSION000.MAN for  CDROOT/Reinst/usmt/amd64/DlManifests/
terminalservices-sessiondirectory-server-dl.man (terminalservices-sessiondirecto
ry-client-dl.man)
Using TERMINALSERVICES-APPSERV000.MAN for  CDROOT/Reinst/usmt/amd64/DlManifests/
terminalservices-appserver-licensing-dl.man (terminalservices-appserver-dl.man)
Using MICROSOFT-WINDOWS-IIS-RE000.MAN for  CDROOT/Reinst/usmt/amd64/DlManifests/
microsoft-windows-iis-requestmonitor-deployment-dl.man (microsoft-windows-iis-re
questfiltering-deployment-dl.man)
Using MICROSOFT-WINDOWS-IIS-MA000.MAN for  CDROOT/Reinst/usmt/amd64/DlManifests/
microsoft-windows-iis-managementservice-deployment-dl.man (microsoft-windows-iis
-managementscriptingtools-deployment-dl.man)
Using MICROSOFT-WINDOWS-IIS-MA001.MAN for  CDROOT/Reinst/usmt/amd64/DlManifests/
microsoft-windows-iis-managementscriptingtools-deployment-dl.man (microsoft-wind
ows-iis-managementconsole-deployment-dl.man)
Using MICROSOFT-WINDOWS-IIS-LE000.MAN for  CDROOT/Reinst/usmt/amd64/DlManifests/
microsoft-windows-iis-legacysnapin-deployment-dl.man (microsoft-windows-iis-lega
cyscripts-deployment-dl.man)
Using MICROSOFT-WINDOWS-IIS-IS000.MAN for  CDROOT/Reinst/usmt/amd64/DlManifests/
microsoft-windows-iis-isapifilter-deployment-dl.man (microsoft-windows-iis-isapi
extensions-deployment-dl.man)
Using MICROSOFT-WINDOWS-IIS-HT000.MAN for  CDROOT/Reinst/usmt/amd64/DlManifests/
microsoft-windows-iis-httpcompressionstatic-deployment-dl.man (microsoft-windows
-iis-httpcompressiondynamic-deployment-dl.man)
Using MICROSOFT-WINDOWS-FAX-CL000.MAN for  CDROOT/Reinst/usmt/amd64/DlManifests/
microsoft-windows-fax-client-proenterprise-dl.man (microsoft-windows-fax-client-
applications-dl.man)
Using MICROSOFT-WINDOWS-CERTIF000.MAN for  CDROOT/Reinst/usmt/amd64/DlManifests/
microsoft-windows-certificateservices-mscep-dl.man (microsoft-windows-certificat
eservices-camanagement-dl.man)
Using MICROSOFT-WINDOWS-CERTIF001.MAN for  CDROOT/Reinst/usmt/amd64/DlManifests/
microsoft-windows-certificateservices-camanagement-dl.man (microsoft-windows-cer
tificateservices-ca-dl.man)
Using POWERMANAGEMENT-POWERPOL000.MAN for  CDROOT/Reinst/usmt/amd64/ReplacementM
anifests/powermanagement-powerpolicy-migration-replacement.man (powermanagement-
powerpolicy-definitions-replacement.man)
Using MICROSOFT-WINDOWS-TERMINALSE000 for  CDROOT/Reinst/usmt/amd64/ReplacementM
anifests/microsoft-windows-terminalservices-licenseserver (microsoft-windows-ter
minalservices-appserver-licensing)
Using TERMINALSERVICES-SESSION000.MAN for  CDROOT/Reinst/usmt/x86/DlManifests/te
rminalservices-sessiondirectory-server-dl.man (terminalservices-sessiondirectory
-client-dl.man)
Using TERMINALSERVICES-APPSERV000.MAN for  CDROOT/Reinst/usmt/x86/DlManifests/te
rminalservices-appserver-licensing-dl.man (terminalservices-appserver-dl.man)
Using MICROSOFT-WINDOWS-IIS-RE000.MAN for  CDROOT/Reinst/usmt/x86/DlManifests/mi
crosoft-windows-iis-requestmonitor-deployment-dl.man (microsoft-windows-iis-requ
estfiltering-deployment-dl.man)
Using MICROSOFT-WINDOWS-IIS-MA000.MAN for  CDROOT/Reinst/usmt/x86/DlManifests/mi
crosoft-windows-iis-managementservice-deployment-dl.man (microsoft-windows-iis-m
anagementscriptingtools-deployment-dl.man)
Using MICROSOFT-WINDOWS-IIS-MA001.MAN for  CDROOT/Reinst/usmt/x86/DlManifests/mi
crosoft-windows-iis-managementscriptingtools-deployment-dl.man (microsoft-window
s-iis-managementconsole-deployment-dl.man)
Using MICROSOFT-WINDOWS-IIS-LE000.MAN for  CDROOT/Reinst/usmt/x86/DlManifests/mi
crosoft-windows-iis-legacysnapin-deployment-dl.man (microsoft-windows-iis-legacy
scripts-deployment-dl.man)
Using MICROSOFT-WINDOWS-IIS-IS000.MAN for  CDROOT/Reinst/usmt/x86/DlManifests/mi
crosoft-windows-iis-isapifilter-deployment-dl.man (microsoft-windows-iis-isapiex
tensions-deployment-dl.man)
Using MICROSOFT-WINDOWS-IIS-HT000.MAN for  CDROOT/Reinst/usmt/x86/DlManifests/mi
crosoft-windows-iis-httpcompressionstatic-deployment-dl.man (microsoft-windows-i
is-httpcompressiondynamic-deployment-dl.man)
Using MICROSOFT-WINDOWS-FAX-CL000.MAN for  CDROOT/Reinst/usmt/x86/DlManifests/mi
crosoft-windows-fax-client-proenterprise-dl.man (microsoft-windows-fax-client-ap
plications-dl.man)
Using MICROSOFT-WINDOWS-CERTIF000.MAN for  CDROOT/Reinst/usmt/x86/DlManifests/mi
crosoft-windows-certificateservices-mscep-dl.man (microsoft-windows-certificates
ervices-camanagement-dl.man)
Using MICROSOFT-WINDOWS-CERTIF001.MAN for  CDROOT/Reinst/usmt/x86/DlManifests/mi
crosoft-windows-certificateservices-camanagement-dl.man (microsoft-windows-certi
ficateservices-ca-dl.man)
Using POWERMANAGEMENT-POWERPOL000.MAN for  CDROOT/Reinst/usmt/x86/ReplacementMan
ifests/powermanagement-powerpolicy-migration-replacement.man (powermanagement-po
werpolicy-definitions-replacement.man)
Using MICROSOFT-WINDOWS-TERMINALSE000 for  CDROOT/Reinst/usmt/x86/ReplacementMan
ifests/microsoft-windows-terminalservices-licenseserver (microsoft-windows-termi
nalservices-appserver-licensing)
Size of boot image is 4 sectors -> No emulation
  2.84% done, estimate finish Mon Sep 27 09:07:08 2010
  5.66% done, estimate finish Mon Sep 27 09:07:08 2010
  8.49% done, estimate finish Mon Sep 27 09:07:08 2010
 11.32% done, estimate finish Mon Sep 27 09:07:08 2010
 14.15% done, estimate finish Mon Sep 27 09:07:08 2010
 16.97% done, estimate finish Mon Sep 27 09:07:08 2010
 19.81% done, estimate finish Mon Sep 27 09:07:08 2010
 22.63% done, estimate finish Mon Sep 27 09:07:08 2010
 25.46% done, estimate finish Mon Sep 27 09:07:08 2010
 28.29% done, estimate finish Mon Sep 27 09:07:08 2010
 31.12% done, estimate finish Mon Sep 27 09:07:08 2010
 33.95% done, estimate finish Mon Sep 27 09:07:08 2010
 36.78% done, estimate finish Mon Sep 27 09:07:08 2010
 39.60% done, estimate finish Mon Sep 27 09:07:08 2010
 42.44% done, estimate finish Mon Sep 27 09:07:08 2010
 45.26% done, estimate finish Mon Sep 27 09:07:08 2010
 48.09% done, estimate finish Mon Sep 27 09:07:08 2010
 50.92% done, estimate finish Mon Sep 27 09:07:08 2010
 53.75% done, estimate finish Mon Sep 27 09:07:08 2010
 56.57% done, estimate finish Mon Sep 27 09:07:08 2010
 59.41% done, estimate finish Mon Sep 27 09:07:08 2010
 62.23% done, estimate finish Mon Sep 27 09:07:08 2010
 65.07% done, estimate finish Mon Sep 27 09:07:08 2010
 67.89% done, estimate finish Mon Sep 27 09:07:08 2010
 70.72% done, estimate finish Mon Sep 27 09:07:08 2010
 73.55% done, estimate finish Mon Sep 27 09:07:08 2010
 76.38% done, estimate finish Mon Sep 27 09:07:09 2010
 79.20% done, estimate finish Mon Sep 27 09:07:09 2010
 82.04% done, estimate finish Mon Sep 27 09:07:09 2010
 84.86% done, estimate finish Mon Sep 27 09:07:09 2010
 87.69% done, estimate finish Mon Sep 27 09:07:09 2010
 90.52% done, estimate finish Mon Sep 27 09:07:09 2010
 93.35% done, estimate finish Mon Sep 27 09:07:09 2010
 96.18% done, estimate finish Mon Sep 27 09:07:09 2010
 99.01% done, estimate finish Mon Sep 27 09:07:10 2010
Total translation table size: 2048
Total rockridge attributes bytes: 113074
Total directory bytes: 315392
Path table size(bytes): 2732
Max brk space used 1615f58
176766 extents written (345 MB)

Created cdrom imagefile fdoem.iso out of directory CDROOT
Premere un tasto per continuare . . .

its obviously truncating at 31 characters now

Try   -iso-level 4

ok. this problem is fixed :

Creating cdrom imagefile fdoem.iso out of directory CDROOT
-o fdoem.iso -b isolinux/isolinux.bin -no-emul-boot -boot-load-size 4 -boot-info
-table -N -r -iso-level 4 -J -l -D -joliet-long -relaxed-filenames CDROOT
Using "mkisofs.rc"
Warning: creating filesystem that does not conform to ISO-9660.
Warning: Creating ISO-9660:1999 (version 2) filesystem.
Warning: ISO-9660 filenames longer than 31 may cause buffer overflows in the OS.

Size of boot image is 4 sectors -> No emulation
  2.83% done, estimate finish Mon Sep 27 09:57:22 2010
  5.66% done, estimate finish Mon Sep 27 09:57:22 2010
  8.49% done, estimate finish Mon Sep 27 09:57:22 2010
 11.32% done, estimate finish Mon Sep 27 09:57:22 2010
 14.14% done, estimate finish Mon Sep 27 09:57:22 2010
 16.98% done, estimate finish Mon Sep 27 09:57:22 2010
 19.80% done, estimate finish Mon Sep 27 09:57:22 2010
 22.63% done, estimate finish Mon Sep 27 09:57:22 2010
 25.46% done, estimate finish Mon Sep 27 09:57:22 2010
 28.29% done, estimate finish Mon Sep 27 09:57:22 2010
 31.11% done, estimate finish Mon Sep 27 09:57:22 2010
 33.95% done, estimate finish Mon Sep 27 09:57:22 2010
 36.77% done, estimate finish Mon Sep 27 09:57:22 2010
 39.60% done, estimate finish Mon Sep 27 09:57:22 2010
 42.43% done, estimate finish Mon Sep 27 09:57:22 2010
 45.26% done, estimate finish Mon Sep 27 09:57:24 2010
 48.09% done, estimate finish Mon Sep 27 09:57:24 2010
 50.92% done, estimate finish Mon Sep 27 09:57:23 2010
 53.74% done, estimate finish Mon Sep 27 09:57:23 2010
 56.58% done, estimate finish Mon Sep 27 09:57:23 2010
 59.40% done, estimate finish Mon Sep 27 09:57:23 2010
 62.23% done, estimate finish Mon Sep 27 09:57:23 2010
 65.06% done, estimate finish Mon Sep 27 09:57:23 2010
 67.89% done, estimate finish Mon Sep 27 09:57:23 2010
 70.71% done, estimate finish Mon Sep 27 09:57:23 2010
 73.55% done, estimate finish Mon Sep 27 09:57:23 2010
 76.37% done, estimate finish Mon Sep 27 09:57:23 2010
 79.20% done, estimate finish Mon Sep 27 09:57:23 2010
 82.03% done, estimate finish Mon Sep 27 09:57:23 2010
 84.86% done, estimate finish Mon Sep 27 09:57:23 2010
 87.68% done, estimate finish Mon Sep 27 09:57:23 2010
 90.51% done, estimate finish Mon Sep 27 09:57:23 2010
 93.35% done, estimate finish Mon Sep 27 09:57:23 2010
 96.18% done, estimate finish Mon Sep 27 09:57:23 2010
 99.00% done, estimate finish Mon Sep 27 09:57:24 2010
Total translation table size: 2048
Total rockridge attributes bytes: 113522
Total directory bytes: 319488
Path table size(bytes): 3142
Max brk space used 367e0
176773 extents written (345 MB)

Created cdrom imagefile fdoem.iso out of directory CDROOT

still remain the autounattend.xml file problem,because it is again truncated to 8+3 chars,even if when I make the iso image it is autounattend.xml (12+3) chars long,much less than 31 chars. I don't understand.

oh no,not only the autounattend.xml file is truncated,but every file it is.

Maybe I found where could be the problem : Since I'm using Nero to burn the CD,maybe it is not configured well to support long file names. Can you suggest to me what could be the best configuration should I make between these ?

Mod Data : Mode 1 or Mode 2 / XA

File System : Only ISO 9660 or ISO 9660 + Joliet or ISO 9660:1999

Name File Lenght (ISO) : Max 11 (8+3 ; level 1) or Max 31 chars (lev.2 )

Charset : ISO 9660 (standard CD/ROM ISO) or DOS or ASCII

Im confused??

aren't you using MKISOFS to make the ISO File?
in nero you should be burning Image!! you used MKISOFS to take care or;

 Mod Data : Mode 1 or Mode 2 / XAFile System : Only ISO 9660 or ISO 9660 + Joliet or ISO 9660:1999Name File Lenght (ISO) : Max 11 (8+3 ; level 1) or Max 31 chars (lev.2 )Charset : ISO 9660 (standard CD/ROM ISO) or DOS or ASCII

and if you have Nero why not us it to make the Bootable CD you don't need MKISOFS?

If your Goal is to have an Unattended win7 installation you should really look at
How To Create Unattended Windows 7 Installation Setuphttp://www.intowindows.com/how-to-create-unattended-windows-7-installation-setup/

If I use Nero,I can't choose the boot image file,but with mkisofs I can do it,passing this parameter : -b isolinux/isolinux.bin. Do you need another way to start the unattended installation of Windows 7 ? I know that the only way is to put the file autounattend.xml on the root of the drive where are located the other installation files. The only thing I need is to understand how can I make this file readable by FreeDOS.

Yes you can Include boot image in Nero  (Which version are you using?)
create a - CD-Rom (Boot)  and you can specify the boot image file.

The way I do Unattended is by using VLite It takes care of everything and it free.
http://www.vlite.net/download.html

this is the tutorial on how
How To Create Unattended Windows 7 Installation Setup
http://www.intowindows.com/how-to-create-unattended-windows-7-installation-setup/

I'm assuming your using a computer with Windows OS, are you?

I'm using NERO 2010. My boot file is isolinux.bin. How can I specify the boot image file ? I'm using Windows OS and Linux OS.

Nero 2010 doesn't tell me which (Free edition, Nero Burning Rom, Nero  Multimedia Suite 10 etc)

Ill Assume the Nero Burning Rom 10
Download Manual PDF from Nero
http://ftp6.nero.com/user_guides/nero10/burningrom/NeroBurningRom_en-US.pdf
and look at page 70 to 73

(page 71 mentions ISOLINUX)

ok. I've followed carefully the Manual from Nero. I burnt a boot DVD-ROM using isolinux.bin and the default options but the problem is still there and I've used the dr-dos boot image of Nero. In this case long file names are disappeared from the DVD after the burning.

Since it seems hard to make the long file names recognized by FreeDOS,even wiith DOSLFN,I thought to change the place where this file should be. I copied it from the root of the cd/rom into the root of the second partition of my first hard disk. And then
from Linux I've compiled grubinst and I did :

./grubinst --install-partition=0 /dev/sda

and I copied the file grldr to (hd0,0) with this menu.lst conf file :

title Start the installation of Windows Vista / Seven
root (hd0,1)
chainloader /bootmgr

Anyway I give you the points for your help.

Happy to hear you found a solution that suites your needs.

RXDOS claims to to be able to use Long file names!!
http://rxdos.sourceforge.net/

Anyway,I'm thinking...I found an alternative solution,ok,but the main question remains unresolved. In the future someone could comes here without to find a valid solution. This is not right,isn't it ?

I guess it depends on what brings them to the question.
Considering they use search engines on key words

We covered many approaches.
So if they are just looking for how to make boot CD with Nero
or just Unamended win7 (using VLITE)

It may not answer your question but might point them in a new direction.

But your right the actual question was not solved.

It didn't work,but this could be part of the solution. The question still remains unresolved.