Unable to Open Include File

[ozarkshermit]

I know this question has been posted numerous times, and I have done several searches relating to it, but I cannot solve this problem.
I'm using PBP 2.6. I have several programs that use DT's interrupts with no problem. I am in the process of setting up another old computer (Windows XP). Programs using DT_INTS-14.BAS, REENTER PBP.BAS, and ALLDIGITAL.PBP Includes run just fine. When I try to use DT-INTS-18.BAS and REENTER PBP-18.BAS, I get the error, only on that computer. My other computer is also Windows XP.

All of the Includes are in PBP root directory ( also put them in PBP Include directory as well - probably not needed.)

I am totally at a loss as to what could be causing this - - any suggestions?

Ken

[HenrikOlsson]

Have you verified that the file extension is .bas and not .pbp?
As long as the file is in the PBP folder or in the same folder as the source file from which you include the other file(s) it should work.

/Henrik.

[ozarkshermit]

Thanks Henrik :

Yes, the extension is ,bas. I wonder if it has something to do with the computer - -
I am running two other XP's using the same programs, etc. Both work just fine. Perhaps I will try deleting all the related include files and re-load them. This is not the end of the world for me, just a real PITA, not to mention my desire to find out why.

[Scampy]

Any reason why you are running such an old OS on the PC's

[ozarkshermit]

No reason at all. I'm satisfied with them.

[Scampy]

You do know how vulnerable XP is these days - Updates stopped years ago !

[sayzer]

Here is my point:

Check file attributes;

Right click the files that work; see how their attributes are applied; and apply the same attributes to other two that do not work.

[ozarkshermit]

First of all, thanks to everyone that responded.

I FOUND THE PROBLEM ! !

These tired old eyes are not what they used to be. Turns out, the Include file REENTERPBP-18.BAS had TWO DOTS between 18 and BAS

(ReenterPBP-18..BAS)

I had copied and pasted the files numerous times, but just perpetuated the problem. Not sure what caused the other warning, perhaps this caused that as well - - Anyway, all is good.

Thanks again for everyone's suggestions