Search the Community
Showing results for tags 'js99er'.
Found 3 results
ok, this is something I have been thinking about: a universal way for a program (Basic, assembly, ...) to detect on what emulator/platform it is running on. My proposal is to add a fake device (DSR) e.g. "PLATFORM." that gives read-only access to a DIS/VAR 80 file that has a specific syntax. Line 1: Platform type. Possible values "EMULATOR", "HARDWARE" Line 2: Platform identification number: 0=TI-99/4a, 1=TinyPC, 100=mame, 101=classic99, 103=JS99'er Line 3: Platform name Line 4: Platform version Line 5: Platform capabilities (*) Example 1: JS99'er EMULATOR 102 JS99'er 8.6.2 ... Example 2: Classic99 EMULATOR 101 Classic 99 v399.047 ... Example 3: TinyPC HARDWARE 1 Tiny-99/4a v3 ... Now I am aware that on the real deal (or on mame without embedding the fake platform device) there is no "PLATFORM." device, but in that case you can act accordingly. Thinking about it further, what if having multiple devices? Perhaps something like 'PLATFORM.TIPI' or 'PLATFORM.RAMDISK' ? When having a GPL based DSRLNK you could also detect FG99 if it had such DSR? Where it gets really interesting is the optional platform capabilities string. Suppose you would be able to detect platform specific settings like (SAMS enabled, F18a enabled, etc.). What do you think?
Will .dsk files created on js99er run on the Real Iron? I use js99er on my chromebook and I have a .dsk that I have been saving my stupid little program experiments on for the past few months. I got the bright idea of transferring the .dsk file to a thumbdrive > to my pc > to the compact flash for the nano using Ti99DIR. Only half the programs work on the real iron. They ALL work on js99er just fine, and also on Classic99 just fine. Why would only "some" of the programs work and not others? They are all just regular Extended Basic short snippits of things I was experimenting with. They show up when I do a "Catalog" of the .dsk, but they refuse to load with a OLD DSK#.PROGRAM NAME Some do, others give me a error message. I/O Error 02.
Hi, all, I'm practicing assembly language with the Editor/Assembler, using the xdt99 cross-assembler with Emacs on a Mac and running it on js99er.net for the emulator. So far, everything has gone very smoothly...but this one weird bug: If I have a period in a TEXT directive string, I get unpredictable VDP results when I display it using VMBW. For example, I printed my name to the screen (along with some other text), with the text set as: MSG2 TEXT 'Timothy S. Hamilton' The other strings printed to the screen just fine with VMBW, but this one came up with the last byte displayed as a space: Timothy S. Hamilto Thinking I'd miscounted the bytes by one, I tried other combinations of characters. It turned out it was the period causing the problem. Later, after putting it back in, sending this same string to VMBW caused the screen to flash with colored noise. Another time, it made it go blank, with a solid color on the border. [Edit: It was another version of the string that caused the flashing, with one or two characters changed, but with the period still there. I haven't tried replicating that particular behavior since then.] I thought it might be some glitch in encoding the period, so I opened up my assembly source file in E/A directly and put the period in there. It displayed the period just fine. Does anybody have a suggestion as to what might be causing this and how to get around it?