long file name problem?

[Single_electron]

I am using Windows XP embedded SP2 with features 2007. One operating system I
built works fine except that long file names will be truncated to 8
characters. And this caused erros for one of my applications. For example, my
application will need MCS5xx32_B2300.DLL but I see MCS5XX~1.DLL under
windows. I believe this caused the above problem. I appreciate your help to
let me know which component(s) should be added to get rid of this problem.

Thanks,

Changyi

[Henry Markov]

I don't think this problem is related to missing/wrong components. I think
we need more information about how you built your system. One possibility
is that when you transferred files from the build environment to the target
for FBA, you used a technique that did not support long file names (e.g.
DOS). Please describe how your files were moved both before and after FBA.

HM

"Single_electron" <Single_...@discussions.microsoft.com> wrote in
message news:DEDA4E4D-C6E0-44FB...@microsoft.com...

[Single_electron]

Hi, Henry,

I built and copied the Run Time Image under "C:\Windows Embedded Images" to
a CF card first. Then the embeddded PC ran through FBA and system booted up
without any problem. Then I installed my Labview application (Labview Runtime
support installed first). When I try to run my application, and my
application started to looking for MCS5xx32_B2300.DLL but my application
installation generated MCS5XX~1.DLL instead. I tested my application on full
version windows XP professional, no problem at all.

Thanks,

Changyi

[Henry Markov]

Changyi,
Your doing a couple of things that I don't know very much about so hopefully
an acutal expert with help out. Running FBA directly from the CF device is
unusual since that would be very slow and result in many write cycles that
shorten the life of the flash. It's much more common to run FBA on a hard
drive if possible. Since you installed Labview and your application after
FBA, did you do an fbareseal on your image? Since you are apparently
running the image from flash, are you using EWF?

The problem may be in the way the Labview installer views the flash that you
are installing on to. Lacking certain hardware support, flash is generally
viewed as removable storage. Maybe the installer is getting confused by
that fact and somehow you get short file names. Just a guess.

HM

"Single_electron" <Singlee...@discussions.microsoft.com> wrote in
message news:F841616A-50B2-4C0E...@microsoft.com...

[Single_electron]

Henry,

Thanks for your inputs. My installation application contains the files in a
compressed format with filenames stored with 8.3 formatting. On installation,
the files are decompressed and the full filenames restored. But the embedded
operating system I built can't restore the full filenames.

Changyi

[Daniel Fird]

I have been suffering from accessing, managing and even renaming files that have more than 255 characters over a long time. I have tried various ways but failed. Then I have searched this problem in internet. Then I have found a solution. This software is very easy to use. Named Long path Tool. To use the program all you need to do is to download this program online and save all the settings to your computer. This program is compatible with Windows NT, 2000, XP, Vista and Windows 7. you can find it from longpathtool(dot)com.

>> On Tuesday, October 23, 2007 11:56 AM Henry Markov wrote:

>> I don't think this problem is related to missing/wrong components. I think
>> we need more information about how you built your system. One possibility
>> is that when you transferred files from the build environment to the target
>> for FBA, you used a technique that did not support long file names (e.g.
>> DOS). Please describe how your files were moved both before and after FBA.
>>
>> HM
>>
>> "Single_electron" <Single_...@discussions.microsoft.com> wrote in
>> message news:DEDA4E4D-C6E0-44FB...@microsoft.com...

>>> On Tuesday, October 23, 2007 7:17 PM Singleelectro wrote:

>>> Hi, Henry,
>>>
>>> I built and copied the Run Time Image under "C:\Windows Embedded Images" to
>>> a CF card first. Then the embeddded PC ran through FBA and system booted up
>>> without any problem. Then I installed my Labview application (Labview Runtime
>>> support installed first). When I try to run my application, and my
>>> application started to looking for MCS5xx32_B2300.DLL but my application
>>> installation generated MCS5XX~1.DLL instead. I tested my application on full
>>> version windows XP professional, no problem at all.
>>>
>>> Thanks,
>>>
>>> Changyi
>>>
>>> "Henry Markov" wrote:

>>>> On Tuesday, October 23, 2007 8:56 PM Henry Markov wrote:

>>>> Changyi,
>>>> Your doing a couple of things that I don't know very much about so hopefully
>>>> an acutal expert with help out. Running FBA directly from the CF device is
>>>> unusual since that would be very slow and result in many write cycles that
>>>> shorten the life of the flash. It's much more common to run FBA on a hard
>>>> drive if possible. Since you installed Labview and your application after
>>>> FBA, did you do an fbareseal on your image? Since you are apparently
>>>> running the image from flash, are you using EWF?
>>>>
>>>> The problem may be in the way the Labview installer views the flash that you
>>>> are installing on to. Lacking certain hardware support, flash is generally
>>>> viewed as removable storage. Maybe the installer is getting confused by
>>>> that fact and somehow you get short file names. Just a guess.
>>>>
>>>> HM
>>>>
>>>> "Single_electron" <Singlee...@discussions.microsoft.com> wrote in
>>>> message news:F841616A-50B2-4C0E...@microsoft.com...