Tim,

>>Okay, that relates to the account used for running the edbsrvr service, i.e. in your
case the Local System account.  You'll need to make sure that this account has the proper
read/write access to the location of the .ini file, and the .ini file itself.

I thought "Local System" was a built in "Super User" that had all read/write privileges
and it is not possible to change the privileges.

I have ordered the book "Microsoft Windows Vista Inside Out"  (which was reviewed in the
Blaise Pascal magazine) which will hopefully explain some of these finer points.

Makes you long for the days of CP/M - but you are not old enough to know about CP/M.

Richard Harding

Richard,

<< I thought "Local System" was a built in "Super User" that had all
read/write privileges and it is not possible to change the privileges. >>

I don't believe that this is the case, by default, under Vista with respect
to the user folders.

<< I have ordered the book "Microsoft Windows Vista Inside Out"  (which was
reviewed in the Blaise Pascal magazine) which will hopefully explain some of
these finer points. >>

Yes, that will probably help a bit.  I've been avoiding Vista like the
plague because I can't afford the drop in productivity yet.

<< Makes you long for the days of CP/M - but you are not old enough to know
about CP/M. >>

I was close - started in 1986 at the age of sixteen, but that was with DOS
3.x on an HP Vectra 286 with an (gasp) EGA monitor and expanded memory of
2MB.  It even had one of those whopping big 1.2MB floppy drives.

--
Tim Young
Elevate Software
www.elevatesoft.com

Richard Harding wrote:

<< Following Raul's suggestion, I set edbsrvr.exe to run as an administrator in the
compatibility options and it now installs.  (Should I need to do this?) >>

Exactly the same problem in Windows Server 2008 (configured as a Terminal Server), solved by setting edbsrvr.exe to run as an administrator thanks to this thread. Also had same problem/solution with DBIsam server.

Thanks,
Ian Turner