AliCE died

[Moose or Chuck]

Fatal Application Error<br>Exception 0xc0000005<br>Address: 00011328

[Moose or Chuck]

Oh, and it completely blanks out the start menu/bar, so that it's unusable. At first I thought it may be WISBar causing a conflict, but it wasn't...

[Phantom]

EasyCE hides the taskbar and re-enables it when the application is terminated. If an 'unvoluntary termination' occurs, you're left without a taskbar.<br><br>Anyway, can I have a bit more info here? I've four questions:<br>1. What's your device?<br>2. How much free ram do you have?<br>3. Does it always crash right at the start?<br>4. Can you verify that the folder that the application is installed to contains an alice subfolder with some .txt files?<br><br>On my iPaq, the app runs great, but there seems to be one line missing at the bottom of the screen. Since this line IS drawn on the PC, this could mean that EasyCE is writing outside the screen for whatever reason. Perhaps this is because the framebuffer address reported by GAPI actually points to the top-left corner of the screen, wich would mean that the bottom-left corner of the screen is actually address -319? Just a guess.<br><br>- Jacco.

[Moose or Chuck]

1. CASIO E-125 MIPS @ 180MHz<br>2. 21.33MB Program / 4.62MB Storage<br>3. Yes<br>4. Yes, quite a few .txt files<br><br>Oh, and no matter what I do, it will not install on my Storage Card through ActiveSync (3.1).<br><br>And yes, the iPaq uses a landscape type screening address, whereas the Casio does not. [EDIT] But you already knew that, because it's in your EasyCE routines.

[Phantom]

I know the iPaq uses a landscape layout internally; problem is, does GAPI return the address of the lower left corner when you call GXBeginDraw, or the upper left corner? I believe I read somewhere once that GAPI *always* returns the upper left corner, and that would mean that the frame buffer on the iPaq actually starts 320 pixels before that. I don't take that into account with EasyCE.

[Digby]

Yep, GXBeginDraw returns the address for pixel (0,0) in portrait orientation.  The start of the actual frame buffer is:<br><br>WORD *pwScnBuf = (WORD*)GXBeginDraw() - 319;<br><br>

[Moose or Chuck]

So, will it work on my E-125 yet or not?

[Phantom]

Moose,<br><br>Ehm, this will only improve EasyCE apps on iPaq. The E125 has an internal buffer that is oriented like you expect (portrait), so this tip will not help to fix the E-125 version. Does anyone have an E-125 with a USB cable for debugging? I have absolutely no clue why AliCE wouldn't work on the E-125.<br><br>Digby: Thanks a lot for the info. EasyCE will be updated. New EasyCE sources will be posted with the sources for spritesunlimited somewhere next week.<br><br>- Jacco.

[RICoder]

Interesting little app.  You used eVC++ I assume.  See, now we need to get someone with too much time on their hands to port Prolog to CE, then I will be happy.  If that happens, then you can right some real AI stuff...<br><br>Probably won't happen though...and I'm not doing it.

[Phantom]

Is Prolog still being used for AI? Alice (not mine, but the original) won last years Loebner contest, and it's written in Java.

[RICoder]

Dude, Prolog is not only still alive, but is now OO AND COM+ compliant.  I use it in Expert System development.  Definately worth the effort to learn for ALL programmers, teaches you new ways of looking at things...ya know?

[eminefes]

Damn, the same problem happens on my EM-500.  The error comes up and the taskbar disappears (I'm also using Wisbar).  I was looking forward to playing it too

[Moose or Chuck]

i've got an E-125 and usb cable, but i'm not to adept at VC++ but if you want straight VC++ Debugging i may be able to tell you wtf is wrong