I recently upgraded a laptop running NT(366 MHz PII, 256 MB RAM) to W2K,
where I have v4.1.1 (downloaded binary built in May) with Exceed and Exceed
3D 6.2. IThat version of DX ran well on that system after getting past the
usual configuration issues with Windows when it had NT. I continue to run
the same version on other NT systems (V4/SP4) without difficulty. But now
I am havbing problems on that laptop.
Under W2K, the ui crashes regularly, but NOT always. It happens more often
with modestly or more complex applications when the ui is started in
-menubar or -image mode, but much less often in -edit mode. When this does
occur, the error is always the same:
instruction at 0x002ab373 references memory at 0x00000004, which can't
be "read"
When this happens, the exec continues to run. This does lead to same
entertaining behavior if it occurs when the sequencer is running -- image
windows continue to get updated, but you can't do anything to stop it. The
ui process is frozen, and you can't even kill the process from the task
manager. I have to kill the exceed process to end the ui.
Any suggestions? Has there been a more recent build more completely tested
on W2K? I've never seen this problem on NT or W98 systems. Thanks.
