And there it is, dumping roms for the 83 plus series works. I will need some cooperation with other people to make the 73,82,83,85,86 work since I don't own them, but its a start!

I just uploaded to codeplex. If you guys could grab it and do some testing, make sure I didn't break anything important, test the new rom dumper see that it actually works for you, etc I'd be very grateful. If all goes well, I'll bang out a readme and submit to ticalc later tonight

The ROM dumper is integrated directly in Wabbitemu? Does it require additional softwares such as Rom8x? I might test but I am unsure if I will have much time yet until next weekend.

correct. I've modified the rom8x source to work better and am using wabbit as a front end for it. Look under help->setup wizard to better see what i mean.

Great job on the new features (and bugfixes)! Wabbit is so useful now...

Just a little update for ThePenguin77, all but one of the things you reported to me is fixed. For normal users the cool part is the darkening keypresses are back! Powerusers, the debugger is a little more stable, i think i fixed the mem leak on buttons, i made the mem map in hex, the gradient is drawn so it is easier to see the lines, the profiler doesnt hang when you close out of it, and the run menu actually does stuff. also i dont think maximizing jacks memory usage up anymore, or at least i cannot reproduce. I should also note that a couple version ago i added more interrupt info (IM mode, i and r regs)

i think i fixed the mem leak on buttons, i made the mem map in hex, the gradient is drawn so it is easier to see the lines, the profiler doesnt hang when you close out of it, and the run menu actually does stuff. also i dont think maximizing jacks memory usage up anymore, or at least i cannot reproduce.

Those The one i didn't fix is an issue with keys getting trapped in the down state when the debugger opens faster than you can release

ROM Dumping works perfectly!

it is a bit more difficult then on TILP where all I need to do is drag and say "ok"

Thanks DeepThought, you definitely helped catch a lot of those little naggy issues. Also
WHOOOOOOOOOOOOOOOOOOOOOO
anyone who has seen me elsewhere on the forums or on IRC, or IRL probably has known about the memory leak bug i have been trying to resolve. Well i think I may have a reason. I thought for a sec and realized that it only occurs in the 32 bit build of Wabbit. The exact same code compiled to 64 bit works fantastically. And both of my machines are 64 bit. anyone see where this is going? I postulate that it only occurs on 64 bit OSes running 32 bit code. I checked and there is no leak in my 32 bit XP vm!!!! I need people to test. If you have a 64 bit machine, try and confirm the leak exists (open task manager and see if wabbitemus memory steadily climbs) and more importantly if you are on a 32 bit machine tell me if the 32 bit build has this issue. If my theory is true, then I will submit to ticalc.org, the second i get confirmation of this

I also propose a race. I will try to fix the cutout skin before someone proves me wrong. READYSETGO!

I'm on XP with a 32 bit system and the starting memory usage was 7544 and then five minutes later and playing with it for a bit it seemed to top at 8556, though I thought I saw it at over 9000 (no, not a meme reference) at one point but it must've gone back down (obviously).

Hmm did you see it increasing by 8s if you let it just sit there not playing with it? It would be quite unfortunate if you did