This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - Runer112
Pages: 1 2 [3] 4 5 ... 153
31
« on: August 14, 2016, 06:09:41 pm »
Thanks for the reports, I have noted the issues in my todo list.
32
« on: August 12, 2016, 06:51:51 pm »
So, I've been thinking. About Axe. I have a couple ideas on changes.
1. Push over into a 3rd app page. Since you are optimizing heavily and can barely fit memkit in, it seems inevitable that the parser will push over into the 3rd page. It seems like a matter of time, and 1.3.0 would be a good time to implement it. This would allow more room for new features and possibly the implementation of other axioms.
If I wanted to add more than one or two features, this would probably be necessary. Throughout my heavy optimization process, I became more familiar with the layout of the Axe application and how it's split across two pages, so extending that to three may not be as challenging now. The one thing I'd be worried about is the one extra page being too much to ask of users with very limited archive space, especially basic 83+ users. 2. Add a way for axioms to be implemented in the parser. Perhaps a series of questions or some kind of application process would work.
It's not an official, but the way exists: just ask me. This of course depends on me actually adding them and making a new release, which I've been rather sluggish about lately.
33
« on: August 12, 2016, 05:53:22 pm »
Perhaps the boot code flash test may help by either revealing a problem or magically fixing one? Also, have you tried sending other OS files, even different versions? Perhaps the one you have is somehow invalid? Beyond that, I'd wait a bit for the replies of those more knowledgeable about the boot code and hardware, but you may be approaching panic level 6.
34
« on: August 12, 2016, 09:47:10 am »
Thanks!
Is there any way to combine two files that fit in ram individually, but together can't? I have 2 very large text files, and can't find a way to combine them.
You can combine them with a computer-side editor, as you don't have a RAM limitation there. The only limitation you'll still have is that it has to fit in a ROM sector, which means it can be at most about 65500 bytes.
35
« on: July 09, 2016, 05:03:02 pm »
What's the best way to store data in an axiom?
I don't want to use free ram...
Is there a way to include data in an axiom? My attempts so far have been unsuccessful.
Do I need to use relative offsets?
You can do this by adding the data as another "command." AxiomSDK.txt explains how to do this: ;____FIELD 4____
;Description: Command type
;Size: 1 byte
;Bits: bit 0 ==> Subroutine instead of inline routine
; bit 1 ==> Command requires the r modifier
; bit 2 ==> Command requires the rr modifier
; bit 3 ==> Additional argument comes before a store token
; bit 4 ==> Puts the data pointer in hl (disables auto-replacements)
That may not be worded especially well, but it basically means that using the "command" in an Axe program would simply load a pointer to the data in hl rather than call it as code. Also, you can reference it from other commands in the Axiom using the usual replacement scheme, REP_NEXT \ ld hl,sub_AxiomXX. And if you don't want the user to be able to access the data themselves: ;____FIELD 3____
;Description: Token to match
;Size: 2 bytes
;Explanation: If its only a 1 byte token, make the second byte 0.
; If its a 2 byte token, the prefix token should come first.
; Leave $0000 if this can only be called from other commands.
36
« on: July 08, 2016, 06:07:13 pm »
If you're referring to the monochrome 83+/84+, Mimas is an excellent on-calc assembler. If you're referring to the 84+CSE or 84+CE, you're out of luck (you could technically write machine code, but I highly advise against this).
37
« on: July 07, 2016, 03:30:28 pm »
You're not assembling that in eZ80 mode, are you? Because I think the seemingly cryptic "Undocumented" error message actually means it encountered an undocumented instruction in the Axiom, which Axe considers an error. The ld de,(hl) instruction you've used a couple of times was added for the eZ80 and is undocumented (does nothing, really) on the z80. If assembling in z80 mode, this instruction should have failed to assemble.
38
« on: July 07, 2016, 01:56:49 pm »
I have a TI 84+ SE with OS 2.55MP
DoorsCS7 is installed.
2.55MP might be the source of the stability issues.
I run zStart with 2.55MP with no issues.
39
« on: July 06, 2016, 09:54:19 am »
Pokemon Purple have been abandoned?
I can't definitively say anything about the state of this project, but it would definitely be nice if it's still in progress. In the meantime, if you're looking for a finished Pokemon game for the 83+/84+, I would recommend Pokemon Topaz. To avoid hijacking this thread, though, any further discussion about Pokemon Topaz should happen in its thread.
40
« on: July 05, 2016, 03:05:08 pm »
Could you be more descriptive about how it doesn't work? Does it crash? Does it freeze? Does it produce unexpected output? Wouldn't it be that your code is never run because you skip over it via 'Goto A'?
Axe doesn't have real library support, so you traditionally just import the "library" program at compile time like that and jump over all of it. It looks silly, but it's actually legit.
41
« on: July 01, 2016, 04:09:22 pm »
As I'm writing some test programs I found an error I can't figure out how to fix.
I am using SPASM-ng and when trying to compile it errors saying "unregistered opticode hl"
I am using it as "pop hl" Am I missing something?
It may just be the includes file, as I have already had to change bcall to b_call in the includes file.
Without context, I don't have much of an idea of what could cause this... is the line not indented with at least one space or tab? That would be my only guess. Otherwise, could you post the snippet, or ideally the full program that is producing this error? The axiom readme says that the last argument is in hl. After that they are in the stack in descending order. That means if hl holds the nth argument, after pop-ing to hl, hl would hold the n-1th argument. Right?
Correct. Commas in function calls are essentially just compiled to push hl. Is there any way to compare 2 two byte numbers (without comparing each byte separately) My idea was to subtract them, but it doesn't seem to work...
Subtracting should work. But keep in mind that there's no 16-bit subtract instruction, only 16-bit subtract with carry, sbc hl,rr. To get the correct result, the carry flag must be unset. If you're sure that the code leading up to this will always unset the carry flag, you're all set. If not, you need to explicitly unset the carry flag with an instruction like or a. If you want to restore the original value of hl after the comparison, follow the subtraction with add hl,rr. Note that this doesn't affect the zero or sign flag and will set carry only if sbc hl,rr set it as well, so all useful flags for comparisons should be unaffected.
42
« on: July 01, 2016, 11:15:21 am »
Yes, but if the program is archived, this function don't work 
Yes, that's generally true. But I'd recommend trying zStart. It's a utility program that does many things, including editing archived programs, which works with Axe's error goto feature. It also provides lots of helpful editor hooks like jumping to labels by name and shortcuts to compile your program without even leaving editor. Also, zStart can be configured to run automatically after RAM clears, so all of its hooks and behaviors can reinstate themselves without needing to run it every time.
43
« on: July 01, 2016, 09:23:41 am »
When I say a debugger line per line, I would say when I compile, I try to compile line per line and disp the error message for the line 
The compile error screen doesn't present the context for the error, but pressing just about any key except CLEAR will go to the exact location of the error in the program editor. Does this not serve the purpose you're requesting?
44
« on: June 30, 2016, 07:51:48 pm »
You mean an assembler? I use SPASM-ng, which has the nice bonus of being able to assemble eZ80. It's basically just a non-dead version of SPASM.
45
« on: June 28, 2016, 04:28:13 pm »
I would like create an Axiom with Mimas but my Axiom don't work when I launch one 
What doesn't work? It still sounds like you're trying to execute the Axiom, which as I mentioned in my last reply, doesn't make sense. It's a library, not an executable.
Pages: 1 2 [3] 4 5 ... 153
|
Show Posts
