I know that I will be a little bit long, but that's the only way to be precise.
So please, maybe someone out there can help me, since th NI Knowledge Base
didn't ...
We use ComponentWorks 2.0.1 and we also got 3.0.1 update.
My computer runs Windows98SE (German version) on an INTEL Pentium III - 600
MHz.
Using Visual Basic 6.0 (SP4) and trying to "Make EXE" the compiler stops
when displaying "Writing EXE" at about 80% gauge. The error message will
always be (I try to translate, since I use a German OS):
"This application was closed due to an critical error". And: "VB6 caused
an critical error 10H in module CW3DGRPH.OCX at 016f:07c5a14e. ..."
If I click "Close" the whole VB6 environment will close. If I click "debug"
C++ comes up and says: "Unhandled exception in VB6.EXE (CW3DGRPH.OCX): 0xC0000090:
Float Invalid Operation". In the disassembly line stands: "07C5A14E fld
qword ptr [esi+200h]"
What did I try to resolve the problem?
1. I installed a "clean" Windows 98 (First edition!), installed my components
and VB6. The error did NOT occurre! After installing a newer dated application
(Outlook Express) the error came. So I guess it will deal with some overwritten
dll or so.
2. I installed Win98 SE and the error always occurred.
For Your information: I named my Windows directory "C:\WIN" and teh System
directory is "C:\WIN\SYSTEM".
3. I reinstalled CW2.0.1 and tried using CW3.0.1. No change. I still couldn't
make the exe file.
The OCX files seem to be registered properly.
(BTW: Any other application not using Component Works can be made to EXE
files.)
4. In my office others are working on this project too. They use Windows
95, Win2000 and Win NT4 WITHOUT any trouble. None is using Windows 98SE.
I am almost changing to Win 2000, but first I don't think it is a secure
way to handle the problem. Who knows, if it appears some day again when any
specific dll or so had been changed in the system folder? And second, I might
need a hardware based OS some day in near future and wish to have Win98 SE
again on my disk.
In all above cases the error message was the same.
Thank You in advance.
Siegfried Wessler