Boy, I know calc84maniac, myself, and some others have awaited this for a long time now. I tried it out quickly, and it certainly seems to be in a basic functioning state. Of course a number of features haven't been made compatible yet, like taking screenshots, but I did manually take this one of calc84maniac's stupendous technological achievement, Steins;Gate, to show off that the hardware emulation is working at least fairly well:

You likely already know about most issues, but I'll mention two that I've discovered.

First, MicrOS does not function properly, which could suggest any number of bugs. DrDnar all but completely throws out the OS and reboots the calculator himself, so I'm guessing at least one of the low-level hardware aspects of its initialization procedure is causing issues. Perhaps DrDnar can be contacted and recruited to help debug its support, and/or you could try yourself with the full source included in the download.

Second, the performance! It's likely that you simply haven't gotten around to implementing the screen in a properly optimizer manner, but I'm seeing generally slow emulation, and unless my eyes are deceiving me, possibly a decent amount of frame skipping on top. If you'd like any assistance in understanding the (much more complicated than the 83+/84+) driver, I might be able to answer questions, or you could probably ask in IRC or make a dedicated topic to get responses from more knowledgeable people.

But a natively running 84+CSE emulator is a huge boon, so thanks for the good work, and keep it up!

Thanks for all the quick feedback. At this point most everything in the OS should be working, since it only uses a small subset of the LCD functions, which has been my primary goal up to this point.
Getting Micros working is my current state of business. Its getting into an infinite loop during initialization, something to do with setting the backlight levels. I'm hoping that once I get that working, I'll have decent hardware emulation. Having the source to that has been very helpful. I'm also hoping to use that to extend BootFree.
Performance for the LCD should not be bad at all however, it's frames are currently synced to Wabbit's display rate rather than publishing its own. This is likely what you're seeing, as data will not be updated quite when you expected.
I may hit up people at some point with hardware questions but for now I think I have a handle on most of it. Obviously the current version isn't very useful as an emulator yet, but I did want to let you guys know that its getting there, and semi functioning. I'm hopeful that I'll have something decently usable in the next week, depending on Clzdg and my schedules'.

Actually, I am surprised you were even able to send APPS at all, since that didn't work for me

I'm curious, which apps did you send and what error did you get? App sending should be working just fine, since its only a slight alteration to the current method of loading apps.

Also, it would be nice if we could setup the LCD to 320x240 instead of 230x155

You can, you just can't do it with the skin. I'm considering setups with a larger skin, but by default I think this will is how it will look.

For completeness here's a list of known issues:

• Port 24 is not quite correct
• Double wide pixels don't work currently
• Partial image support has issues
• Currently the lcd is always reported as active
• Interlacing does not display correctly
• Not sure if ORG mode is implemented correctly
• No backlight implementation
• GIFs broken for all calculators
• Variables are not listed
• Debugger has no useful information about the new LCD

I've had this problem, too. I think it is partially the OS that isn't accepting the apps, but I'm not sure. My fix has been to make a dummy program (or real program) archive it, then garbage collect, then send the app.

As promised, I've got a new version to test. I think I have the important parts of the new hardware working. http://buckeyedude.zapto.org/Revsoft/Wabbitemu/Beta/Wabbitemu.exe
The two important things not currently working are the variable tree (meaning no variable exporting), and the debugger has nothing useful for the new LCD.

Let me know what issues you encounter, or any useful things you need.

BuckeyeDude

I tried making a ROM with the wizard and it doesn't really work? The screen stays black.

Oh good point, my bootcode still has some issues. I forgot I added that option.

Question, do we really need the ability to capture 640x480 screenshots?

Btw emulation seems perfect for this game. The only difference is the lack of scanline emulation, so the ghosts flickers differently than on the real calc.

EDIT: Actually i notice that some colors are wrong in screenshots, but I guess it's inevitable considering the calc has 16 or 18 bit colors, yet GIFs only have 8.

Double size GIFs were pretty much free, so they are in there. The default is 2x for the 96x64 calcs, and I haven't resolved how I'm going to handle that setting for the new LCD. As for GIF colors, unfortunately they are not perfect yet. I have a new algorithm that I want to try, but for now its just using the web safe palette + 40 custom colors.
I agree, the flickering is a little too obvious right now. I'm working on improving the LCD accuracy, trying to get it closer to how the real calc works. Clzdg and I were talking about doing some frame blurring, but my first attempt looked awful so I left it out.

Also bug report: The ASM Tunnel isn't emulated properly, yet mine is emulated fine:

(At first I tried playing through the entire game anyway but this gave me an headache lol)

Btw will there be an option to use xLIBC color palette for screenshots? (which is limited to 256 colors)

Good catches. I've posted an updated version that fixes the tunnel problem with LCD scrolling, and should have better GIF palettes now. GIF sizes now default to 1x for color and 2x for everything else, and this setting will be saved now too. 84PCSE should show variables on calc and allow exporting.

BuckeyeDude

As Juju said, ROM-creation-created ROMs still fail to boot. Do you know when this can be fixed?