After seeing Joshua (MMFDomain & CrapWare)'s interactive novel engine, I went back to check on an application (that does the same thing) I had made a few months ago that I was holding on to until I felt like using before I released it.
The engine is compiled and runs off of an ini in a data folder, and I know it used to work. However, when I went to run it today I get an error (KBFEv100.exe has generated errors and will be shut down by windows).
So went back and checked the source, seems this is triggered when I try to load an image with the Overlay Redux extension. Now, it used to work, and I hadn't done anything to the compiled engine since then. So I assume it's something somewhere that's changed since. I've tried multiple versions of CNCS232.dll, that's not it. Probably. I should add that it still works when I run it from MMF, as long as I don't change the problem event. When I do, MMF dies.
One thing I should note is that the error I get is one that Win2k likes to throw a tantrum with, so the engine would probably work on anyone else's machine. However, I was wondering if anyone has any ideas as to what the cause might be, because there's no way I can test a demo file if I want to release the fiction engine.
Is this an engine you compiled a while ago that used to work and now doesn't? Or did you compile it once and it worked, but now you compile it and it doesn't?
If it's only been a problem since re-compiling it then maybe there's a problem with the version of Overlay you have? I know you've probs considered this all though.
However if this is the original file you compiled, then it must be something with the running environment that has changed. File corruption of the actual project is unlikely if the error is in both compiled and cca versions.
You said 'MMF dies' when you change the cca and run it from MMF? Dies in what way? Does it just hang, or does it give you the same kind of error as before?
Or d'you mean that editing that event actually hangs MMF in the editor itself. If that happened then I'd say it were a corrupted CCA or a problem with MMF itself.
You said about Win2k - does that mean you've tested it on other machines?
Does the operating system you use have an Applog? It's the one thing I miss from Win98, lol. If you've got one, try looking in the windows\applog\ folder for a 'KBFEv100.LG#' file (where # is the drive letter that your file lives on). I dunno if you've ever used the applog, but lines beginning with 'o' mean 'file opened'. Those files are assigned a file handle. From then on they're referred to in the file by that handle. A line beginning with 'r' means 'bytes read', and it tells you which bytes have been read from which handle. A 'c' means the handle has been cleared from memory.
Presumably the last item in the list will be whatever caused the crash. It may point to a dll or cox file or something.
The app was previously compiled. The compiled file used to work, but now it doesn't. On my machine, anyway. I'm pretty sure if it were run on something other than Win2k it would work, because Win2k is a bitch.
When I do open up the source, I can delete lines that try to load an image into Overlay Redux and compile a working file (for a given value of 'working'). However, if I try to edit the event (say, to change the calculation or simply point to an existing file), MMF generates an error. It's the same wonderfully verbose W2k error.
I don't think there's an applog. W2k has some similar tools but they're pretty useless.
Advertisement
Post Reply
Edited by the Author.
