>>>>>Hmm, can't think of much else to try. I'm assuming you're doing all of your testing while logged in as a local administrator, and that all NT Service Packs are applied?
>>>>
>>>>Yes, SP 6a and the administrator account.
>>>>Today I tried to run my application through Citrix. We have an online demo of "Journal III" on our website. And that worked.
>>>>So there is a way to run fox on a fast CPU, through Citrix :-).
>>>>
>>>>I tried to set tempfiles to another drive, no difference.
>>>
>>>It's strange! While I have not heard of anyone having trouble running FPW2.6 on NT before, maybe no-one has done so on such fast hardware.
>>>
>>>Maybe someone else with a similar situation could let us know if *they* can do it.
>>
>>There might be a solution!
>>When you install WINNT you can choose what kind of computer you have. On these computers the choice was something like "Uniprocessor ...", If you choose Standard-PC instead, you get a system that can run Fox2.6 and other 16-b programs.
>>And why then? It have something to do with support for APIC and MPS. It's a different hal.dll that installs when you choose Standard-PC.
>>I have seen this solution on the DELL-computer.
>>It can on some computers be possible to disable APIC-support in BIOS.
>
>I assume you mean "ACPI" (Advanced Configuration and Power Interface) http://www.microsoft.com/windows2000/en/professional/help/default.asp?url=/windows2000/en/professional/help/pwrmn_acpi_overview.htm
>
>If you have success in disabling this, that's good. My understanding is that NT does not support ACPI anyways, and it does not support Plug & Play, so sometimes you have to configure hardware manually (interrupts, etc.). Still, I'm somewhat surprised that turning off ACPI would help - I'd expect NT to not boot at all, or to have some devices not functioning if its installation was not compatible with the ACPI BIOS setting. If NT booted properly, however, I'd expect applications (16- or 32-bit) to run properly.
>
>If by "MPS" you mean multi-processor support, NT supports this transparently and it should make absolutely no difference to whether 16-bit apps run on it.

Hi again,
no it should be APIC (Advanced Programmable Interrupt Controller)
http://www.microsoft.com/hwdev/platform/proc/io-apic.asp .
Here is a another link to read: http://support.microsoft.com/default.aspx?scid=KB;en-us;123732&
It's not exactly my problem but the workaround is the same.