I JUST GOT 2.2.2 TO REPLACE MY 2.2.0 VERSION.
When I compile a file that worked fine before it aborts immediately WITH A MESSAGE:

"UNABLE TO OPEN: C:\FPC\2.2.2\BIN\i86-WIN32\fp.cfg

Yet this file exists in this directory. Whats wrong?

THANKS JY

Hi John!

I saw someone else that posted a similar issue. Are you using Vista? If so, this might help:

* **Right-click** (not the usual left-click) the FPC folder from My Computer and select "Options" from the drop-down list (bottom entry).

* There are 4 tabs at the top of the new window, one of them says "Security". Select that one and click the "Edit..." button (a window may pop up, asking for your permission to continue - Yes, continue...).

* There's a list of groups/users and underneith that, a list of access rights. First make sure there's a group called "Users" in that first list (it should say something like "Users (John-PC\Users)"). If it isn't there, click the "Add..." button, in the next window click "Object Types.." and select (checkmark) "Users" then hit OK on this and the previous window.

* If "Users" is already in the list, highlight it and from the list below select the "Full Control" in the "Allow" column - it will automatically select "Modify" as well, but will leave "Special Permissions" unselected. That;s ok, so leave it as that and click the "OK" button. A window will show what it's doing - applying these new security settings to the FPC folder and all subfolders / files.

Now remember that in doing so, any user (Standard OR Administrator) on your computer can add/edit/delete folders and files in your FPC folder. If that's too much of a security risk for you, either upgrade your own user account to have Administrator rights (Start -> type "User" and select "User Accounts" from the program list -> Select "Change your account type") -OR- you can specifically select the FP.CFG file and apply these settings as outlined above to just that file instead of the whole FPC folder.

Hope that did the trick for you, but use at your own risk ;-)

-- Mike

Thanks for all the info but I'm using XP. I can open the fp.cfg with notepad.

JY

Has anyone else ever seen this problem? Is this just a bug in 2.2.2 ? The file is clearly where it is supposed to be and accessible from other programs.
Is this message erroneous or misleading? It does prevent compiling anything.

What could cause this?

JY

Just an update I removed FPC with Add/Remove programs which didn't remove everything.
It left the bin directory with fp.cfg alone. I reinstalled 2.2.0 which would not launch but just
blinked on screen. I deleted the FPC root directory and everything below it. I reinstalled
2.2.0 and it works. I have regularly seen this failure to launch behavior about once a month.
I delete the files in C:\FPC\2.2.0\BIN\i86-WIN32\ and then re-install. Re-installing without
removing those files doesn't work.

I also routinely see unusual behavior during debug. In routine debugging suddenly breakpoints
don't break anymore. I exit FPC and restart to return to normal operation. SImilarly the watching
of record structures just quits. Restart fixes that to. I was hoping 2.2.2 might fix these problems.
But it won't even run for me.

I have a rather ordinary setup here that runs most things without trouble.

Never the less I'm a great fan of FPC.

JY

The debug problem is not really in our hands. We use the GNU debugger, and if the GNU team (not exactly a cheering crowd of pascal fans) breaks things for Pascal, then we are pretty much powerless.

Secondly, can you look in the fp.cfg file using notepad, and see if there is a -Opentiom option somewhere in it ? If so, remove it. This option is no longer supported.

Thirdly, you might consider simply (re)moving the file. As far as I know (don't use the text mode IDE) the IDE will look for this file also in the current directory.

Michael.

It is extremely unlikely the above symptoms (both the ones described for 2.2.0 and 2.2.2) have anything to do whatsoever with Pascal support in gdb. It sounds much more like bugs in the internal debugger interface of the IDE (and as for the 2.2.2 symptom, I read that as "the 2.2.2 IDE won't even run for me").

in fact, gdb's Pascal support has been extremely stable (I've seen less than a handful regressions during the last 10 years). And that while the first basic Pascal test cases for gdb were only added during the last couple of years (by Pierre).

Jonas

Hey. I just went inside the file and deleted all the "-Opentium3" lines and it worked. Not really sure about the reason but it worked =). Cheers
Lude