Disfunctional version nov 2011?

Nov 25, 2011 at 8:36 AM

Hi all,

Yesterday I downloaded version nov. 2011 and today I did the same at school. But in the first usage in front of my class, Wabbitemu appeared to be frozen and non-responsive.
I tried again and again, starting and stopping the program. Same behaviour. On the XP machines here, the latest version is not reliable.
If log files would help to solve this problem, please tell me what to do.

Mathteacher

Developer
Nov 29, 2011 at 5:04 PM

Hello,

Sorry for the issue with the new version. I've tested under XP, and there doesn't seem to be any issue I can replicate, but I'm guessing its related to the change I made to the skin. Are you using the cutout skin mode?

BuckeyeDude

Nov 30, 2011 at 10:48 PM

Sure. Always cutout skin.

Dec 1, 2011 at 1:06 AM

I have downloaded Wabbitemu 64-bit 1.5.11.4 this morning 11/30/2011. I have noticed that the graphing functionality does not work. I'm completely new to this sw, so maybe I have to do something not obvious to me to enable graphing?

Thanks

franK

Developer
Dec 1, 2011 at 11:54 PM

Hey Frank,

Once you have your calculator setup it should be the exact same as a normal calculator. Can you walk me through what what you did to get a ROM and what you're doing in wabbit to try and graph something?

BuckeyeDude

Jan 14, 2012 at 3:46 PM

Hi BuckeyeDude,

for me it's just the other way: the last version which was working correctly here was the one from Nov 4th 2011, all newer versions since December have big problems!

Anytime in December you implemented a new option "Open debugger on flash error" and if this option is ON (which it is by default) then no matter which ROM image I load, the debugger is opening at each program start. It looks as if these neweer Wabbitemu version can't read the usual ROM images anymore (but all previous versions upto 4th Dec had no problems with them). So the only way to run the new Wabbitemu is to deactivate this option - but then I'm wondering what this 'feature' should be good for!?

In the last December version the debugger didn't work at all anymore (just crashing), but in your first new version this year this bug was corrected. Unfortunately since yesterday there's again a new problem: now you've added this 'looking for updates' feature, and when I run Wabbitemu on my computers which are not connected to the internet I always get this annoying error popup window (because there's no internet connection). Couldn't you imagine that many users start Wabbitemu while being offline or on computers without internet connection??? :-(

Sorry to say this, but Wabbitemu is getting worse with every new release since 2 months, fortunately I still have this old 4th Nov version which works fine, but all your newer versions are almost unusable (or at least very annoying).

 

Franz

 

Developer
Jan 15, 2012 at 12:44 AM

Hi Franz,

Sorry about all the issues. Lets see if I can't get some of them fixed. First I've changed it so that by default opening the debugger on invalid flash commands is off. Same with breaking on execution violations. These are important debugging tools for developers and in theory should never happen. Unfortunately it appears it does, so devs can turn it on themselves. I'm a little confused though. Once you uncheck these options, do you still have issues with your ROM? If you do what ROM version are you using and what issues do you have using the ROM?

Second the automatic check for updates doesn't have the error box anymore. It was only suppose to show on the manual check for updates not the automatic check.

BuckeyeDude

Jan 15, 2012 at 11:10 AM

Hi BuckeyeDude,

first many thanks for todays new release - now the error message when
being offline has gone and also switching off "Open debugger on ..."
is indeed a good idea. :-)

Now I've redownloaded again all ROM images to be sure that my stored
images aren't damaged in any way before I made a new complete test with
this new Wabbitemu version.
BTW, if you want to know exactly which versions I'm using here - here's
the site from where I've downloaded all my 'original' (?) ROMs:
http://www.emunews.eu/?page_id=10
(you've to scroll down to get to the TI images)

Here's the list of ROMs I'm using here (all with Wabbitemu 32-bit under Win7) -
the first list are the 'original' ROMs from the site mentioned above:
TI-73     1.60
TI-82     19.0
TI-83     1.10
TI-83+    1.16
TI-83+SE  1.16
TI-84+    2.43
TI-84+SE  2.41
TI-85     10.0
TI-86     1.6

And this second list are the neweset flash-files from the TI-website,
of which I made ROM images myself with a previous Wabbitemu (anytime
in Oct. 2011(:
TI-73     1.91
TI-83+    1.19
TI-84+    2.55

Now for the results of my tests:
When "Open debugger on invalid flash command" is switch OFF, then all
of the ROMs listed above can be loaded (and the calculator switched on)
without any problems, in other words: everything is working fine!

If this option "Open debugger on invalid flash command" is switched ON,
then the debugger automatically open whenever I load and switch on one
of the following ROMs:
all 73/82/83 'original' ROMs and the 73 ROM made from flash!

The 'original' 84/85/86 and the 83/84 made from flash work correctly,
i.e. do not call the debugger.

I've also tried to create a new 73 ROM from the TI-flashfile (because
that's the only one of the selfmade ROMs that doesn't work), but when
I try to create a ROM file from this 73 flashfile the new Wabbitemu
completely crashes: during this creation process it suddenly opens the
debugger, and the debugger then is going crazy and has to be canceled
by the Windows taskmanager.

So it seems you've changed anything in the Wabbitemu versions since
Dec 2011, so that it now treats any ROM/flash commands as illegal and
opens the debugger (if this option is on) - as I already mentioned
the version from 4th Nov 2011 (and earlier ones) did not have these
problems at all.

And the second thing is that now it can't create a ROM image from a
flashfile anymore (at least not for the TI-73), and also this has
worked in my old versions (upto Nov 2011).

I hope this long post will be helpful for you in solving these
remaining problems. ;-)

Franz