Floating Point Error and the Macromedia Treason

[mrgl]

I work in Windows 98 on a PII 300MgHz Dual Processor computer. I suddenly started getting floating point error in E3D2 that causes my program to shut down.
It occurs randomly while working on a new file; and
It occurs always whenever I try to open an existing E3D file.

A first error window reads:

Exeption: Floating point error - invalid operation
Execption Code: C0000090, Floating point status: 80001
Exception address: 10014386, Exception EIP: 10014388

Click OK and a second error window reads:

Exeption: Floating point error - invalid operation
Execption Code: C0000090, Floating point status: 80001
Exception address: 03BC49EE, Exception EIP: 09BC4A40


Click OK and a windows illegal operation performed this program will be shut down comes up. The details window reads:

E3D caused an exception 10H in module DISTANT LIGHT.X32 at 015f:03bc4a40.
Registers:
EAX=00000020 CS=015f EIP=03bc4a40 EFLGS=00010202
EBX=03bcb180 SS=0167 ESP=0082dd34 EBP=0082dfdc
ECX=00000400 DS=0167 ESI=0082e024 FS=6b5f
EDX=03bcb170 ES=0167 EDI=006c1064 GS=0000
Bytes at CS:EIP:
9b c3 66 a1 76 21 bd 03 66 25 f0 7f 66 0b c0 74
Stack dump:
03bc4999 005f9d08 00521641 0082dd48 047d1c48 74736944 20746e61 6867694c 00000074 00000000 00000000 00000000 00000000 00000000 00000000 00000000

Click shut down and the program shuts down with no other adverse effects.

I don't want to quit using this program because I like it, I spent a long time really learning how to use it efficiently, I don't want to relearn another complicated 3D program, and I paid alot for it. I'm hoping that there is an underground core of E3D users that can fill the gap left by Macromedia's treason.

Please comment even if you don't know the answer.

I hope someone can answer this.

 

[kagran]

This sounds more like a Windows problem than E3D to me. My first reaction would be to run Norton or similar to check for Windows problems. All I did was press the damn button