Suggestions

[leofox]

I have a few suggestions for the OS you are making.

Maybe you can include NimbusOS as the program interface, and if it's OK with rebel.socom, his basic prog editor. THAT WOULD ROCK!

Reply: I happen to like the current interface, it's really DOSsy . And I already plan on having a plain text editor.

[rebel.socom]

to help asm programmers who want to use there own inturrupt routine, put somewhere between addresses $0000 - $00FC jp $ADDRESS

doing the will let asm programers use im 1 for there interrupt routines using code something like this

di
im 1
ld a,$FC ;

in ur source put
.org $00FC
jp $ADDRESS ; some where in ram

i dont know how u plan on structuring the mem but i hope u understud what i ment.

BTW do u have an Instant mesanger sigma

[jvdthwip]

I have a suggestion for CSX.

How about you make a prog editor that almost perfectly mimics the TI-OS basic editor, but lets you disassemble, edit, and compile asm programs on-calc.

Since CSX will command-line based, you will have to do "edit sample.prg" instead of using the PRGM button, but that's OK. While in the editor, you could make the PRGM button bring up a list of Tokens (like JR, INC, ADD, etc.), just like the BASIC editor.

In addition, you could make the Catalog (when viewed in the editor), bring up a list of rom calls that can be searched alphabetically.

[leofox]

i have another suggestion: use another extension for asm programs than for basic programs, like .prg for basic and .asm for assembly.

You seem certain that it will support Basic...

[rebel.socom]

or why not just make them two different objects and program can be 5 and asm can be 6. ... o wait i dont know a thing about how he sets up the vat. or if he has one... ;)

That way is stupid. Files are differentiated by their extension.

[jvdthwip]

Here's another idea...

If CSX will ever support variables, BASIC programs, et cetera, you could make 3 powerdown options:

• Powerdown:
The normal 2nd+On Powerdown (Called with the key hook, a command, or a menu with the other 2 options)

• Shutdown:
The device can display "Shutting Down", delete all variables, garbage collect, archive the entire contents of RAM into a reserved spot in archive (optional, but practical- to prevent loss of memory during any battery replacement), and then powerdown. The next time the device turns on, you could display "Starting Up", and then COPY RAM back again, but leave a copy in archive as a "System Recovery Point" (similar to what Omnicalc does with RestoreMem()) which would get replaced at the next shutdown. (called with a command or menu with the other options)

• Restart:
The same as "Shutdown", but automatically repowers up (or doesn't powerdown at all). Practical if a user wants a quick calc-cleanup or wants to set a system recovery point and/or garbage collect before testing a possibly unstable prog. (called with a command or menu with the other options)


EDIT:
One more idea:
CSX could keep EVERYTHING in archive. Similar to what Mirage does when "allow writeback in progs" is unchecked. Of course, that would not allow saving (especially for variables and such, but if you aren't going to make use of basic progs...), but saving can be taken care of with the use off appvars. (Of course EVERY program that requires saving would need to be reconfigured for the use of appvars... Oh well, I guess this isn't a very good idea after all.

[rebel.socom]

I think thats an awosome idea. Maybe not all 83+ users would like that because of the some what low amount of archive, that is compired to the SE which i will never use all of .

[basic101]

When will u make it compadable w/84 and can APPS still be the same/work?. Does it use RAM and ROM, if it only uses RAM do you use the hidden RAM also?

[leofox]

I think you should ditch the command line thing, but since that would kill the whole idea of CSX,
maybe you could make it so that programmers can make there own GUI's for it.

[basic101]

it doent work on 84, i need a certificate?

[DarkerLine]

[leofox]

[basic101]

it wont get to that point, not even start!!!

[Mike_k]

I think I know what your problem is. What you need to do is open up TiConnect. THen click on device explorer. Once the device explorer opens, click on "Tools" (I think it is) menu at the top menu bar. One of the options should be "TIOS Downloader" Click that one, then it takes you into a wizard type OS installer. This is how I got my CSX on.

On a note to something above about apps: The reason we would never be able to use apps, is because we CANNOT (illegal to) copy code that TI has made for their OS. The B_CALL is specific to the compiler and Ti, thus we wouldn't be able to legally add support for "B_CALL". If you wanted to make apps compatibal, make your own "bcall", C_CALL or something, and recompile all apps with C_CALL in them. Then you would of course need to actually MAKE all of the 'C_CALL's in pure z80 ASM

[DarkerLine]

[Darth Android]

correct, you can use bcall all you want. so long as you write the bcall routine your self (which is a big pain, considering what has to be done)

so to emulate an app, build the ram structure just like the tios, then put the appropriate page into $4000-$7FFF and make sure you have a working bcall routine that has all the bcall used in that app and make sure any thing that could be used to identify whether a ti-os or a custom one is installed returns liek the tios. but no, ti would be extremely unhappy about this.

[sgm]

[DarkerLine]

Say more.

[sgm]

[leofox]

so if you want to have full support for asm programs that use rom calls, you have to code them all by yourself :S???