>>Probably it is caused by the known bug (same behavior) in VFP. The app that keeps looking after bmps must be rebuilded from C: (ie all files on the C drive).
>>
>>Vlad
>>
>>>I'm having trouble with FF 3.0+ looking for its internal bmps on the D: drive (D:\work_fpw\bmps...).
>>>
>>>FF launches fine on computers with no drive D:. It crashes with CD-ROMs using the D: letter and not having a CD inserted.
>>>
>>>Users are understandably annoyed by this. Do I need to rebuild FF after having manually changed the bmp locations ?
>>>
>>>Also, why should FF care about physical drives if the bmps are bound into the app ?
>>>
>>>Any assistance would be greatly appreciated.
>>>
>>>Henry
>
>
>Yes, this is the case. We will have a new build coming out shortly that does not have this problem. IOW, we made sure to rebuild with no CDROM or other external drives in the environment.
>
>Bill

From my tests: you should have all files on drive C. It's not enough to not have CD-ROM drives or other external drives.

Vlad