Sorry for missing info...
This is only on an older machine. It's running an ATI Rage Pro Turbo, with DX 8.1 (of course), and updated drivers to support it. This is a Windows 98 machine with a Pentium 2, and 256 MB of RAM... That is probably the cause.
It's the editor itself that is crashing. Before this error, I was getting a runtime error 1504, at line 0, which is before the first line I can enter any code.
The errors work this way:
The program will actually go through the first part of the compilation process, alerting me of any errors in the code.
Once the code is ready to be ran, the error in my first post on this thread shows up as soon as I hit compile.
This is after the updated drivers (Direct3D didn't work with DX 8.1, but did with DX 7 before.. after both work).
Before the drivers were updated, it would actually completely compile, and would open the window for my app... As soon as the window opened, the runtime error would occur.
Really, even being an old machine, everything should be working, from the sound of DBPro requirements. The only problem should come when I try to use texel or pixel shaders. Not only are they not use din my code (yet), but even if they were, the errors occur when it tries to run at line zero, so that wouldn't be the bug.
This is only on my work machine. The one at home (Win2k Pro SP 2, 1 Gig Thunderbird, GF 4 MX 440, 768 megs, DX 8.1) works fine. That's why I say it's annoying, and not enfuriating 8) At least I can see my work somewhere. Will just have to code at work, then look at what I've done when I get home, unless someone knows a fix.
In the first post, note "EDITOR executed an invalid instruction in" Editor is the DBPro IDE interface. Looks like it's trying to access memory reserved for OS communication to the BIOS chip. I have no clue why it would do that... Memory referenced must be different on the other machine... No OS would allow any program to access that part of memory.
Anyway sorry for the vagueness of the first post.
