when I upload the ROM image, it succeeds, but the calculator screen is the same color it was before I uploaded the ROM image. All buttons I press on and above the calculator fail to turn it on. The only way I can get the calculator to turn on is by uploading a program. The first time I try uploading the program, the program will not upload but the calculator will turn on. The second time I upload the program, it will work.
When I am logged in, the same problem occurs, with the same solution along with another: I can press "Refresh emulator variable list" and the calculator will turn on.

When I attempt to reload my ROM image, it says

Code:
and then
Code:

However, there are some more that I have noticed relating to SourceCoder and jsTIfied. The buttons "File to jsTIfied", "Project to jsTIfied", and "File from jsTIfied" (found in SourceCoder) do nothing.

Is it possible to code jsTIfied so that it does delete the old ROM? Or even better, so that it doesn't forget the old one at all?

Additionally, why is Internet Explorer one of the recommended browsers?

And now I am going into computer science that I don't understand, but: is it possible to compress a .rom file to a size small enough to fit in Internet Explorer's DOM storage, and code jsTIfied to automatically extract the file?

Is it possible to code jsTIfied so that it does delete the old ROM? Or even better, so that it doesn't forget the old one at all?

Additionally, why is Internet Explorer one of the recommended browsers?

And what about the other errors, like SourceCoder? Are those fixable?

They work fine for me. What browser, version, and OS are you using?

Huh? It only stores one ROM at a time.

Firefox may be encountering that same error because it's not deleting the ROM that is there before uploading a new one and thus going over the limited DOM storage.

The ROM is stored compressed on all browsers.

Regarding ROM compression to fit inside IE. If it could the decompression wouldn't be possible due to legal issues and the nature of DOM. Your ROM file can not be legally uploaded to our server so we take advantage of DOM storage which is a local storage on your browser. The ROM "uploads" but it uploads to DOM and stays on your computer (and the browsers cache). So, you'll need to upload your ROM for each device (tablet, laptop, desktop, phone, laptop 2, etc).

I didn't see any errors regarding jsTIfied and SC3 in your post. If you are talking about SC3 erros in general, there's another topic for that. But yes, those are fixable. Make sure you provide as much information as possible when reporting errors.

That's it for bugs that I have noticed pertaining only to jsTIfied. However, there are some more that I have noticed relating to SourceCoder and jsTIfied. The buttons "File to jsTIfied", "Project to jsTIfied", and "File from jsTIfied" (found in SourceCoder) do nothing. In addition, jsTIfied does not let me load a program from SourceCoder. I am forced to download the program from SourceCoder onto my computer and upload it to jsTIfied.

I wrote the emulator; I'm afraid some of comicIDIOT's responses are slightly misguided.

Sorry if this has been dealt with elsewhere, but will jsTIfied run on Chromebooks? Even offline?

If so, would you consider posting directions on how to the load the correct *.ROM file, etc.?

With literally hundreds of thousands of Chromebooks being purchased by schools this year, you would really be doing us teachers, and our kids, a great service!

Thanx!!

Is jsTIfied ever going to support the TI-86?

Adding support for wholly different calculators would be much more work than implementing 86 LCD controller support
It should indeed be a separate code base, since the intersection between the code for TI-Z80 support and the code for Prizm / 9860G support would be small.

That's not to say that no emulator for Casio calcs on which users can enjoy arbitrary native code execution should be done.
It could be interesting to leverage emscripten.

Leverage emscripten on which existing native code emulator?

[23:10:53] <DrDnar> I'd say do something like ED Fx = soft break point in set x (0-15), ED Cx = trace event in set x with zero arguments, ED Dx = trace event in set x with 1 byte argument, ED Ex = trace event in set x with 2 byte argument
[23:13:13] <DrDnar> The argument is specified by the next instruction: ED Cx = log register 0 = B, 1 = C ... 5 = L, 6 = (HL), 7 = A, 8 = BC, 9 = DE, 10 = HL, 11 = SP, 12 = I, 13 = R, 14 = IFF, 15 = IM
[23:13:16] <DrDnar> Hmm.
[23:13:29] <DrDnar> I guess there's no reason to have the ED Ex thing
[23:13:57] <DrDnar> I'm suggesting logging, proper tracing requires that you log every CALL and JP and whatnot.
[23:14:54] <DrDnar> With this system, you can run the code on hardware unmodified, because the new instructions are 8-cycle NOPs on hardware.