I have a client/server app that I modify the codebase for the EDB Server slightly, removing access to settings and adding an application launch shortcut from within the server.

Under XE2, both the client and server apps have been happy working on Windows 2000 SP4.

Now that all my 3rd party prerequisites are in place with my XE3, I brought my projects forward to XE3, recompiled and fixed a few warnings and such.  Everything seemed to work great.

When I distributed the applications, the server wouldn't run at all.  Checking the event logs it looks like some API's changed or aren't there that EDB Server needs (directly/indirectly).  

XE3 does state that XP is the lowest common denominator.  I don't remember if XE2 said same, however all of our applications are running on Win2K without issue, providing they are on SP4 and have IE6 installed.

Mainly thought I would share in the experience, for those who need to support Win2K or older OS's.

As far I know, XE3 applications don't anymore work on Windows 2000 as it has
static links to new dll's which were not available on Win2000.

This statement os from the EMB forum:

>>Except in this case, it actually does mean "will not run on".  There are
>>static linkages to Win32 API functions that do not exist in Win2000.  For
>>example, XE3 introduces a new TThread.GetSystemTimes() method that calls
>>the Winapi.GetSystemTimes() function, which does not exist on Win2000.  If
>>your project uses the System.Classes unit, even if it does not use the
>>TThread class, the app will not run on Win2000, it will complain about the
>>missing function import because Winapi.GetSystemTimes() is not being
>>delay-loaded by the RTL.<<

Regards
Rolf

"Lance Rasmussen" schrieb im Newsbeitrag
news:C6FB6D3A-A29D-4155-BECE-144F73330EF6@news.elevatesoft.com...

I have a client/server app that I modify the codebase for the EDB Server
slightly, removing access to settings and adding an application launch
shortcut from within the server.

Under XE2, both the client and server apps have been happy working on
Windows 2000 SP4.

Now that all my 3rd party prerequisites are in place with my XE3, I brought
my projects forward to XE3, recompiled and fixed a few warnings and such.
Everything seemed to work great.

When I distributed the applications, the server wouldn't run at all.
Checking the event logs it looks like some API's changed or aren't there
that EDB Server needs (directly/indirectly).

XE3 does state that XP is the lowest common denominator.  I don't remember
if XE2 said same, however all of our applications are running on Win2K
without issue, providing they are on SP4 and have IE6 installed.

Mainly thought I would share in the experience, for those who need to
support Win2K or older OS's.

Lance,

<< Mainly thought I would share in the experience, for those who need to
support Win2K or older OS's. >>

Thanks, very useful information.

Tim Young
Elevate Software
www.elevatesoft.com