Antonio Aacini
December 11th 03, 09:56 PM
I am using Hardlink precisely to separate some certain
files and put them in a directory so I avoid to process
all the original files. Of course, I can do this by
simply copying the selected files to another directory,
but this implies duplicate the disk space used by the
files and takes more time also because the files are .MP3
large files and there are a lot of them.
If I modify my DOS program so it uses LONGNAME functions,
do you think that the Hardlink names will be find?
I wonder about this matter: In a NTFS disk when a DOS
program uses the old-style functions to manage files the
Windows emulator of DOS must translate the real NTFS
structures to the old directory entry used by MS-DOS, so
the NTFS names MUST have the equivalent DOS 8.3 names.
Why this don't happens in a Hardlink name? I don't think
that this is because the NTFS structure per se, I think
that may be a design error of the FSUTIL command, the
program that creates the Hardlink names.
>-----Original Message-----
>I don't think this is even possible.
>NTFS Hard links are not able to be represented in a 8.3
>style format, because they aren't files nor directories,
>nor anything else that a FAT file system would
>understand.
>
>This is one of those instances where the file system
does
>matter to DOS programs.
>
>Since the files are still there under their original
>paths/filenames, is there a reason you can't process
them
>with your DOS program with their "true" paths and
>filenames?
>
>
>>-----Original Message-----
>>I created a Hardlink name for several files with the
>>command FSUTIL HARDLINK CREATE of Windows XP. Then I
>want
>>to process these new names with a MS-DOS type program,
>>but surprise! The Hardlink names don't have an
>equivalent
>>DOS 8.3 type name as any other file created in Windows
>>XP! So the DOS program don't found anyone of them.
>>
>>So I tried to create a DOS 8.3 name to these Hardlink
>>names with the command FSUTIL FILE SETSHORTNAME but,
>>surprise again! The SETSHORTNAME command works with all
>>Windows XP files EXCEPT those created with HARDLINK!
>>
>>I really need to process these files with a DOS type
>>program. What I can do?
>>
>>Thanks a lot
>>Antonio
>>.
>>
>.
>
files and put them in a directory so I avoid to process
all the original files. Of course, I can do this by
simply copying the selected files to another directory,
but this implies duplicate the disk space used by the
files and takes more time also because the files are .MP3
large files and there are a lot of them.
If I modify my DOS program so it uses LONGNAME functions,
do you think that the Hardlink names will be find?
I wonder about this matter: In a NTFS disk when a DOS
program uses the old-style functions to manage files the
Windows emulator of DOS must translate the real NTFS
structures to the old directory entry used by MS-DOS, so
the NTFS names MUST have the equivalent DOS 8.3 names.
Why this don't happens in a Hardlink name? I don't think
that this is because the NTFS structure per se, I think
that may be a design error of the FSUTIL command, the
program that creates the Hardlink names.
>-----Original Message-----
>I don't think this is even possible.
>NTFS Hard links are not able to be represented in a 8.3
>style format, because they aren't files nor directories,
>nor anything else that a FAT file system would
>understand.
>
>This is one of those instances where the file system
does
>matter to DOS programs.
>
>Since the files are still there under their original
>paths/filenames, is there a reason you can't process
them
>with your DOS program with their "true" paths and
>filenames?
>
>
>>-----Original Message-----
>>I created a Hardlink name for several files with the
>>command FSUTIL HARDLINK CREATE of Windows XP. Then I
>want
>>to process these new names with a MS-DOS type program,
>>but surprise! The Hardlink names don't have an
>equivalent
>>DOS 8.3 type name as any other file created in Windows
>>XP! So the DOS program don't found anyone of them.
>>
>>So I tried to create a DOS 8.3 name to these Hardlink
>>names with the command FSUTIL FILE SETSHORTNAME but,
>>surprise again! The SETSHORTNAME command works with all
>>Windows XP files EXCEPT those created with HARDLINK!
>>
>>I really need to process these files with a DOS type
>>program. What I can do?
>>
>>Thanks a lot
>>Antonio
>>.
>>
>.
>