Bob,
Does this mean that you have set the affinity mask to 0 for Windows Classic,
or left it at the default (1).

I am commissioning a Windows 2003 Server site currently, running on a IBM
Xeon box, and had problems with the FB5.02 server randomly crashing with:

ILVSSERV (Client) Tue Feb 15 13:27:58 2005
C:\Program Files\Firebird\Firebird_1_5\bin\fbserver.exe: terminated
abnormally (4294967295)

Changing to Classic has cured the crashing, and am monitoring stability of
new configuration.

regards
John

----- Original Message -----
From: "Bob Murdoch" <mailgroups@...>
To: <firebird-support@yahoogroups.com>
Sent: Thursday, February 24, 2005 6:04 AM
Subject: RE: [firebird-support] Does 1.5 Classic on Windows suffer from the
HT problem?


>
> Chris,
>
>> -----Original Message-----
>> From: cg_bland [mailto:chris.bland@...]
>> Sent: Tuesday, February 22, 2005 2:29 PM
>>
>> Finally, if things go ahead, we will be deploying Windows
>> Classic in a production environment. We are testing at the
>> moment - however, has anyone else had good/bad experiences
>> with Windows Classic?
>
> I've had wonderful success with Classic on a Windows 2003 server, with
> dual cpu's and HT enabled (looks like 4 cpu's). You do not want to do
> anything with CPU Affinity. Let each FB process run on the CPU it is
> assigned.
>
> The only thing you will want to do when switching from SS to CS is
> perhaps change the buffers. Otherwise, each connection (process in
> CS) will default to something like 75MB of RAM. I chose 2048 for the
> buffer setting, and it's worked well (gfix -b 2048 -user sysdba
> -password masterkey <database>).
>
> Bob M..
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>
>