By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,573 Members | 1,777 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,573 IT Pros & Developers. It's quick & easy.

FAT16 vs. FAT32 OR NTFS

P: n/a
I am wondering would this work on FAT16 and FAT32?

if File.Exists("filePath\TestingTester.exe")

I know that FAT16 uses 8 char file names and that a file longer then this
would be automatically renamed to let's say:

file name TestingTester.exe would be called Testin~1.exe

Thank you,

--
Dino Buljubasic
Software Developer
http://rivusglobal.com
Nov 20 '05 #1
Share this Question
Share on Google+
7 Replies


P: n/a
Hi Dino,

Long file name (LFN) support is the job of the OS - using whatever file
system it has. Try it on a floppy - <that> certainly won't be NTFS!! ;-)

On FAT, long file names work by using additional directory entries for the
long name and having a reference from that to the file's <actual> directory
entry which will be in the ancient 8.3 format. This allows non-LFN supporting
OS's to play with files without regard to the long filename.

Regards,
Fergus
Nov 20 '05 #2

P: n/a
Thanks Fergus,

I thought the same. However, I am having a problem when trying to update my
applicaton on Win98 (not 2nd edition, or Me).

When I install my application, it will be installed as TestTe~1.exe (and
original name is TestTesting.exe). Now when I do auto update, I do date
comparison to find out which one is newer version, so thet is the place
where my autoupdate does not find the file TestTesting.exe because it is
written as TestTe~1.exe.

I thought it can only be the file name length. What else could it be? It
works just fine on Win93 2nd Ed, Me, 2000, XP

Regards,

--
Dino Buljubasic
Software Developer
http://rivusglobal.com

"Fergus Cooney" <fi******@tesco.net> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
Hi Dino,

Long file name (LFN) support is the job of the OS - using whatever file system it has. Try it on a floppy - <that> certainly won't be NTFS!! ;-)

On FAT, long file names work by using additional directory entries for the long name and having a reference from that to the file's <actual> directory entry which will be in the ancient 8.3 format. This allows non-LFN supporting OS's to play with files without regard to the long filename.

Regards,
Fergus

Nov 20 '05 #3

P: n/a
Hi Dino,

Sorry, if it works with everthing except Win98 (1st ed) then I'm not the
one with the answer. :-( I went straight from Win95 to Win2000 with great joy
that I didn't have to get involved with the intermediates.

I can't see that you'd be doing anything wrong in your code, so it must be
a Win98 bug that was fixed in the 2nd ed.. Perhaps there's a Knowledge Base
article on MSDN?

Regards,
Fergus
Nov 20 '05 #4

P: n/a
Thanks Fergus
"Fergus Cooney" <fi******@tesco.net> wrote in message
news:OL**************@TK2MSFTNGP10.phx.gbl...
Hi Dino,

Sorry, if it works with everthing except Win98 (1st ed) then I'm not the one with the answer. :-( I went straight from Win95 to Win2000 with great joy that I didn't have to get involved with the intermediates.

I can't see that you'd be doing anything wrong in your code, so it must be a Win98 bug that was fixed in the 2nd ed.. Perhaps there's a Knowledge Base article on MSDN?

Regards,
Fergus

Nov 20 '05 #5

P: n/a
Hello, Dino:

As Fergus said, the long file name support is native for Windows 95 and later and has nothing to do with the format of the disk/partition.
If your program is installed with a short file name (TesTe~1.exe) is because the installation program is not compatible with long file names (almost all 16 bit programs are not LFN aware). You can add a batch file to rename the file after the installation or do it manually. Note that DOS has not LFN support outside the Windows GUI.
It's impossible to disable de long file name support. If the Windows 98 system does not support long file names, the system may have a huge problem and may need reinstalling.

Regards.
"Dino M. Buljubasic" <di*************@rivusglobal.com> escribió en el mensaje news:CUIbb.149$vz6.103@edtnps84...
| Thanks Fergus,
|
| I thought the same. However, I am having a problem when trying to update my
| applicaton on Win98 (not 2nd edition, or Me).
|
| When I install my application, it will be installed as TestTe~1.exe (and
| original name is TestTesting.exe). Now when I do auto update, I do date
| comparison to find out which one is newer version, so thet is the place
| where my autoupdate does not find the file TestTesting.exe because it is
| written as TestTe~1.exe.
|
| I thought it can only be the file name length. What else could it be? It
| works just fine on Win93 2nd Ed, Me, 2000, XP
|
| Regards,
|
| --
| Dino Buljubasic
| Software Developer
| http://rivusglobal.com
|
| "Fergus Cooney" <fi******@tesco.net> wrote in message
| news:%2****************@TK2MSFTNGP09.phx.gbl...
| > Hi Dino,
| >
| > Long file name (LFN) support is the job of the OS - using whatever
| file
| > system it has. Try it on a floppy - <that> certainly won't be NTFS!! ;-)
| >
| > On FAT, long file names work by using additional directory entries for
| the
| > long name and having a reference from that to the file's <actual>
| directory
| > entry which will be in the ancient 8.3 format. This allows non-LFN
| supporting
| > OS's to play with files without regard to the long filename.
| >
| > Regards,
| > Fergus
| >
| >
|
|
Nov 20 '05 #6

P: n/a
The installation program I use is the one I made for my deployment. It is
Windows Installer and it supprts long file named for sure. It installs the
program with its full name, I have checked that. However, I noticed that on
win98 below 2nd ed, the file name gets cut to 8 characters.

Thanks for your help.

--
Dino Buljubasic
Software Developer
http://rivusglobal.com

"José Manuel Agüero" <jm******@vodafone.es> wrote in message
news:ug*************@TK2MSFTNGP09.phx.gbl...
Hello, Dino:

As Fergus said, the long file name support is native for Windows 95 and
later and has nothing to do with the format of the disk/partition.
If your program is installed with a short file name (TesTe~1.exe) is because
the installation program is not compatible with long file names (almost all
16 bit programs are not LFN aware). You can add a batch file to rename the
file after the installation or do it manually. Note that DOS has not LFN
support outside the Windows GUI.
It's impossible to disable de long file name support. If the Windows 98
system does not support long file names, the system may have a huge problem
and may need reinstalling.

Regards.
"Dino M. Buljubasic" <di*************@rivusglobal.com> escribió en el
mensaje news:CUIbb.149$vz6.103@edtnps84...
| Thanks Fergus,
|
| I thought the same. However, I am having a problem when trying to update
my
| applicaton on Win98 (not 2nd edition, or Me).
|
| When I install my application, it will be installed as TestTe~1.exe (and
| original name is TestTesting.exe). Now when I do auto update, I do date
| comparison to find out which one is newer version, so thet is the place
| where my autoupdate does not find the file TestTesting.exe because it is
| written as TestTe~1.exe.
|
| I thought it can only be the file name length. What else could it be? It
| works just fine on Win93 2nd Ed, Me, 2000, XP
|
| Regards,
|
| --
| Dino Buljubasic
| Software Developer
| http://rivusglobal.com
|
| "Fergus Cooney" <fi******@tesco.net> wrote in message
| news:%2****************@TK2MSFTNGP09.phx.gbl...
| > Hi Dino,
| >
| > Long file name (LFN) support is the job of the OS - using whatever
| file
| > system it has. Try it on a floppy - <that> certainly won't be NTFS!! ;-)
| >
| > On FAT, long file names work by using additional directory entries
for
| the
| > long name and having a reference from that to the file's <actual>
| directory
| > entry which will be in the ancient 8.3 format. This allows non-LFN
| supporting
| > OS's to play with files without regard to the long filename.
| >
| > Regards,
| > Fergus
| >
| >
|
|
Nov 20 '05 #7

P: n/a
Hi, Dino:

I haven't seen that behavior before and I don't know what can be hapening.
It happens in more Windows 98 Gold systems? That could point to an incompatibility of the installer.
The system you're having trouble with has other files with long file names in the hard disk? It could be a problem with the file system (or any virus, or antivirus, or any third party utility, ...). Have you tried to disable the filename tunneling? It's in the system control panel, Performance tab, Filesystem button, Troubleshoot tab, Disable preserve long file names for old programs (sorry for the translation, I only know the Spanish version) (you will have to reboot).

That's all I can think of. Hope it helps.

Regards.
"Dino M. Buljubasic" <di*************@rivusglobal.com> escribió en el mensaje news:NE*******************@news1.telusplanet.net.. .
| The installation program I use is the one I made for my deployment. It is
| Windows Installer and it supprts long file named for sure. It installs the
| program with its full name, I have checked that. However, I noticed that on
| win98 below 2nd ed, the file name gets cut to 8 characters.
|
| Thanks for your help.
|
| --
| Dino Buljubasic
| Software Developer
| http://rivusglobal.com
|
| "José Manuel Agüero" <jm******@vodafone.es> wrote in message
| news:ug*************@TK2MSFTNGP09.phx.gbl...
| Hello, Dino:
|
| As Fergus said, the long file name support is native for Windows 95 and
| later and has nothing to do with the format of the disk/partition.
| If your program is installed with a short file name (TesTe~1.exe) is because
| the installation program is not compatible with long file names (almost all
| 16 bit programs are not LFN aware). You can add a batch file to rename the
| file after the installation or do it manually. Note that DOS has not LFN
| support outside the Windows GUI.
| It's impossible to disable de long file name support. If the Windows 98
| system does not support long file names, the system may have a huge problem
| and may need reinstalling.
|
| Regards.
|
|
| "Dino M. Buljubasic" <di*************@rivusglobal.com> escribió en el
| mensaje news:CUIbb.149$vz6.103@edtnps84...
| | Thanks Fergus,
| |
| | I thought the same. However, I am having a problem when trying to update
| my
| | applicaton on Win98 (not 2nd edition, or Me).
| |
| | When I install my application, it will be installed as TestTe~1.exe (and
| | original name is TestTesting.exe). Now when I do auto update, I do date
| | comparison to find out which one is newer version, so thet is the place
| | where my autoupdate does not find the file TestTesting.exe because it is
| | written as TestTe~1.exe.
| |
| | I thought it can only be the file name length. What else could it be? It
| | works just fine on Win93 2nd Ed, Me, 2000, XP
| |
| | Regards,
| |
| | --
| | Dino Buljubasic
| | Software Developer
| | http://rivusglobal.com
| |
| | "Fergus Cooney" <fi******@tesco.net> wrote in message
| | news:%2****************@TK2MSFTNGP09.phx.gbl...
| | > Hi Dino,
| | >
| | > Long file name (LFN) support is the job of the OS - using whatever
| | file
| | > system it has. Try it on a floppy - <that> certainly won't be NTFS!! ;-)
| | >
| | > On FAT, long file names work by using additional directory entries
| for
| | the
| | > long name and having a reference from that to the file's <actual>
| | directory
| | > entry which will be in the ancient 8.3 format. This allows non-LFN
| | supporting
| | > OS's to play with files without regard to the long filename.
| | >
| | > Regards,
| | > Fergus
| | >
| | >
| |
| |
|
|
Nov 20 '05 #8

This discussion thread is closed

Replies have been disabled for this discussion.