>I have a FPW 2.6 application I inherited. My workstations configuration is different from the original developer's in that the project now resides on the "D" drive.
>
>On the startup screen is the line
>
>@ 15.625,61.833 SAY ;
>(LOCFILE("misc\silo256s.bmp","BMP|ICO|PCT|ICN", "Where is silo256s?" ));
>BITMAP ;
>SIZE 9.375,41.667
>
>
>The BMP file is included in the project.
>
>When I installed an update on a user's computer, this line causes their CD Drive to spin and produces an IO error. If there is a disk in the drive, it will spin and the picture will appear properly.
>
>Short of moving the project to my "C" drive and re-compiling, how can I get this behavior to stop??
>
>Thanks to all............Rich

I remember this from my 2.6 days and we got around it by doing what you said. Move the application to the C drive and compile there. We had all our apps out on a network drive. When the developer wanted to update it they would check it out to their c drive. Make their mods then rebuild the exe. Then check the app back into the network drive. If they would make their mods on the network drive and build the exe then they would get the error you are talking about.