Subject Re: [firebird-support] Re: OT :: Win2003 SP1 and Delphi 7
Author Helen Borrie
At 02:32 AM 3/09/2005 +0000, you wrote:
>--- In, Helen Borrie <helebor@t...>
> >
> > From Ann Lynnworth, of HREF, in the WebHub list:
> >
> > After installing SP1 on Win2003 you *may* find difficulties with
> > Delphi 7, e.g. Project Options dialog gives an access violation and
> > opens, not even for the default new project.
> >
> > There is a workaround, and that is to go into Control Panel > System >
> > Advanced > Performance > Data Execution Prevention "DEP" and select the
> > first radio button:
> >
> > "Turn on DEP for essential Windows programs and services only"
> >
> > Click [ok], close all dialogs, and reboot.
> >
> > ./heLen
>Hi Helen,
>Should we be disabling DEP for Firebird on win2003?

Hey, don't shoot the messenger, Adam! I'm reporting what Ann observed
**might** occur and how to work around it. The WebHub list members by
nature have their servers open to the Web. Surfers who enter a WebHub site
send a request to start an instance of a server-based application. The app
itself controls session security, again, by the nature of WebHub. I could
see how an all-stops DEP would be a showstopper and why Ann's workaround
makes sense. I don't have Win2003 and, in any case, my web setup here is
strictly an intranet.

>With the exception of the Firebird control panel applet not working, we
>have had no issues with running our (Delphi) product or Firebird on our 2003
>hosted servers, so I am not too sure what you mean.

I don't *mean* anything. The message was marked "OT" (= off-topic, not
known as a Firebird issue...). This isn't a Microsoft or networking
support list, yet some M$ or networking issues frequently play a part in
making Firebird dysfunctional.

>Apparently others have had issue with using "localhost", and others have
>had issues with Shadowing, and others with the file system permissions
>(the same sorts of problems you get with linux file system permissions).

True. It struck me that this most recent localhost issue might be related
in some way to the installation of a M$ service pack, as occurred with XP
SP2 (?), where the capability for the loopback ports to be assigned to
localhost was blocked off and required a patch from M$ to fix it.