Official TI-Boy CSE Alpha Thread

[DJ Omnimaga]

Oh, weird. I wonder why this could happen?

[merthsoft]

Yeah, I wasn't able to save in Pokemon Blue. In Zelda it did save, though.

[calc84maniac]

Hmm, I just started up the Pokemon Red app on my calculator and I got the same issue. Well, I guess I only lightly tested Pokemon, after all. I'll have to see if I can track down this problem.

Edit: Heh, I had to think outside the box to figure this one out. I was certain I got my saving code right, and I checked it and rechecked it... but it turns out the problem is actually in the code for loading from archived appvars (which doesn't affect 8KB save files because the appvar gets unarchived first), which was writing the save data to the wrong RAM pages. I'll try to push out a new version soon.

Edit 2: In response to Runer's earlier question, I mainly limited the app names because I didn't want people doing things like making two apps called PokemonR and PokemonB, which would happen to use the same save file names.

Edit 3: Here's a release of Alpha 0.0.02. This should fix the loading issue, and also, makeapp no longer gives warnings for app pages beginning with FFh.

[Streetwalrus]

Holy crap that is epic

[Runer112]

Edit 2: In response to Runer's earlier question, I mainly limited the app names because I didn't want people doing things like making two apps called PokemonR and PokemonB, which would happen to use the same save file names.

If the user specifies an 8-character name for a ROM that has a 32KB cartridge, just echo out a (appropriately flashy) warning mentioning this. I think the ability to have 8-character names if you're made aware of the issue greatly outweighs the likelihood of someone ignoring the warning message, making two apps with 32KB cartridges that differ only by the last letter, and sending them both to their calculator and trying to run them. And if they ignore the warning message and screw up their save, that's their own fault.

Also, if you do take up my suggestion to save emulator settings in an appvar and think this still could be an issue, you could block out the possibility of this occurring entirely by saving the application name with the emulator metadata. Then you can check that the appvars being loaded by TI-Boy correspond to the app of the correct name.

[calc84maniac]

Edit 2: In response to Runer's earlier question, I mainly limited the app names because I didn't want people doing things like making two apps called PokemonR and PokemonB, which would happen to use the same save file names.

If the user specifies an 8-character name for a ROM that has a 32KB cartridge, just echo out a (appropriately flashy) warning mentioning this. I think the ability to have 8-character names if you're made aware of the issue greatly outweighs the likelihood of someone ignoring the warning message, making two apps with 32KB cartridges that differ only by the last letter, and sending them both to their calculator and trying to run them.

Also, if you do take up my suggestion to save emulator settings in an appvar and think this still could be an issue, you could block out the possibility of this occurring entirely by saving the application name with the emulator metadata. Then you can check that the appvars being loaded by TI-Boy correspond to the app of the correct name.

Hmm, this also reminds me that I need to include a tool (or tools) to convert appvars to .sav files and vice versa.

[TIfanx1999]

That, would be fantastic!

[rw24]

Actually, I was going to name them PokemonB and PokemonR.

Hmm, I just started up the Pokemon Red app on my calculator and I got the same issue. Well, I guess I only lightly tested Pokemon, after all. I'll have to see if I can track down this problem.

Edit: Heh, I had to think outside the box to figure this one out. I was certain I got my saving code right, and I checked it and rechecked it... but it turns out the problem is actually in the code for loading from archived appvars (which doesn't affect 8KB save files because the appvar gets unarchived first), which was writing the save data to the wrong RAM pages. I'll try to push out a new version soon.

Edit 2: In response to Runer's earlier question, I mainly limited the app names because I didn't want people doing things like making two apps called PokemonR and PokemonB, which would happen to use the same save file names.

Edit 3: Here's a release of Alpha 0.0.02. This should fix the loading issue, and also, makeapp no longer gives warnings for app pages beginning with FFh.

[calc84maniac]

Please don't post links to applications containing copyrighted content.

I did download it though, and confirmed it won't send via TI-Connect. It also crashed TILP. Interesting.

Edit: I wonder if perhaps TILP doesn't support apps above 2MB. Maybe Rabbitsign doesn't, either.

[Runer112]

I had trouble sending Pokemon Silver, as well. But I pulled out the good old silverlink and sure enough it worked, although it took about half an hour.

[calc84maniac]

By the way, the error I'm getting with TI-Connect is "The I/O operation has aborted because of either a thread exit or an application request. (800703E3)"

Also, I heard the USB reconnection sound, which was kind of odd. I'll give it a try with silverlink.

[rw24]

That's weird, because someone in the It's Coming topic said it worked...

[calc84maniac]

That's weird, because someone in the It's Coming topic said it worked...

If you're talking about Runer112, he was only able to send it with the SilverLink cable, and I was able to as well. Direct USB doesn't seem to work for anyone as far as I tell (seems like it might be some TI-OS bug).

[Matrefeytontias]

I never could send anything to my CSE via.USB, so it must be TI-Connect being shit again (I mean, not that it's surprising).

[merthsoft]

I used direct USB with no problems. I sent Zelda and Pokemon.