> 2. If you're running Superserver then, to use direct local protocol a la Firebird 1.5 on Vista, you'll need to change the value for IpcName in firebird.conf
>
> from the default
>
> #IpcName = FirebirdIPI
>
> to
>
> IpcName = global\FirebirdIPI
>
> Note, it's case-sensitive and those are upper-case "i", not lower-case "L"; and you'll need to stop and restart Firebird to load a firebird.conf change.

I have tried this, but it doesn't work. This is my situation:

1. I am using Windows Vista Business
2. I install Firebird 1.5.5 running as service
3. I stop Firebird 1.5.5 service
4. I edit firebird.conf in privilege mode to avoid VirtualStore problem
5. I add "IpcName = global\FirebirdIPI" to firebird.conf
6. I save Firebird.conf and start Firebird 1.5.5 service again
7. I logon to an "limited user" account and access a firebird database using local protocol. I still get "unavailable database" using local protocol

If I start my firebird in application mode (e.g: fbserver -a), I manage to access my firebird database using local protocol.

What's wrong with my steps?