Omnimaga

Calculator Community => TI Calculators => General Calculator Help => Topic started by: Hayleia on August 05, 2014, 10:47:28 am

Title: Force TilEm to send to archive ?
Post by: Hayleia on August 05, 2014, 10:47:28 am
So I have two >10KB files I'd like to send to the emulator. The problem is that the sum of their sizes is over the amount of RAM. Obviously, I can and have to send them to archive. But how can I do that in command line with tilem ? For now I do "tilem2 file" and I don't see where I decide where I want my file to go.
Title: Re: Force TilEm to send to archive ?
Post by: willrandship on August 05, 2014, 07:52:33 pm
If they're separate files, you should be able to send them individually, then archive them in turn. ie Send, Archive, Send, Archive. I don't think the CLI interface has send-to-archive as a feature, unfortunately.
Title: Re: Force TilEm to send to archive ?
Post by: Streetwalrus on August 05, 2014, 07:59:32 pm
Tilem has link cable emulation for Tilp and other libti* based tools like titools. The latter supports sending to archive.
Title: Re: Force TilEm to send to archive ?
Post by: Hayleia on August 06, 2014, 02:28:20 am
If they're separate files, you should be able to send them individually, then archive them in turn. ie Send, Archive, Send, Archive. I don't think the CLI interface has send-to-archive as a feature, unfortunately.
Yeah, but thats not the goal. In fact, I have a script that edits both Axe source files in vim, then tok8xes them, then sends them to TilEm (who says "error memory") then opens a macro in TilEm to automatically compile the source into an executable, all of that before I even have time to reach the "Preferences menu" to set Tilem's speed back to normal.
If I send both files one by one, it completely kills the speed.

Tilem has link cable emulation for Tilp and other libti* based tools like titools. The latter supports sending to archive.
Ok, but why does Tilem receive in Archive on my netbook but not on my other computer ? Some people told me that even the old version of TiLP I installed on the "problematic computer" supports sending to Archive.
Title: Re: Force TilEm to send to archive ?
Post by: ben_g on August 06, 2014, 10:41:04 am
iirc weather files should be sent to the archive or to RAM is stored in the .8xp files themselves. You may be able to change that flag on the software you use to pack the files in the 8xp format (assuming you regenerate those files ofthen).
Title: Re: Force TilEm to send to archive ?
Post by: Hayleia on August 06, 2014, 11:19:38 am
I know that, and this flag is activated since I use tok8x -a. I know that flag works because using tok8x -a then sending to TilEm indeed sends to archive, while not using the -a option sends to RAM... but that's on my netbook, not on my main PC (plus, I can't do it with appvars since I don't generate them with tok8x). So I think I am really looking for a way to force when sending, not a workaround that could send to archive.
Title: Re: Force TilEm to send to archive ?
Post by: Hayleia on August 07, 2014, 06:47:36 am
So I killed Ubuntu 13.04, installed Lubuntu 14.04 instead (among other things :P) and now sending to archive using the flag mentionned by ben_g works.

However, I still think that forcing to send to archive would be a great feature when we can't modify that byte as easily as with tok8x (for example when we want to send an appvar and not a program).
Title: Re: Force TilEm to send to archive ?
Post by: Streetwalrus on August 07, 2014, 08:29:08 am
How about you make the change and submit a patch then. :P
Title: Re: Force TilEm to send to archive ?
Post by: Hayleia on August 07, 2014, 09:55:42 am
Do you really think I am able to read/modify other people's code ? -.-
Title: Re: Force TilEm to send to archive ?
Post by: DJ Omnimaga on August 07, 2014, 12:22:19 pm
YEah i remember that the archive flag was stored inside the program before, which caused problems with emulators such as PindurTI, which didn't accept any file that had the flag ON. On the other hand, I hated when emulators forced groups to be ungrouped as they are sent or sent things to RAM no matter what, because it made certain games particularly hard, if not impossible to install.