« previous next »
Pages: 1 [2]   Go Down

Author Topic: OSLauncher Help  (Read 15730 times)

0 Members and 2 Guests are viewing this topic.

Offline Odo007

  • LV0 Newcomer (Next: 5)
  • Posts: 2
  • Rating: +0/-0
    • View Profile
Re: OSLauncher Help
« Reply #15 on: August 31, 2011, 02:19:34 am »
Yeah! I got it to work after many tries, just to notice that i had to downgrade to 2.0.1.60!!!

I had 2.1.0.631 and I got stuck at the black screen with the watch on it. (Should have RTFM... but hey! There isn't one:)

In the emulator this was the last message it printed in the console:
(nonCas)
* P3 mode battery door detection
(Cas)
* P1R2 mode battery door detection

However 2.1.0.631 CAS did startup ONCE in the emulator and show "* P3 mode battery door detection". Which I don't know what it means. I might have a bash at making 2.1 work but with 3.0 out I might check that one out.

Now I am a happy bunnie!  :w00t: Even though I have 2.0.1.60, but I guess there's not much difference to 2.1 couldn't find quickly the release notes for 2.1 to see whats the difference between them...

Thanks Lionel for OSL, Goplat for the emu and all the other ppl who worked on NDless and opened up this platform!

You ROCK!  :thumbsup:
Logged

Offline Lionel Debroux

  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2135
  • Rating: +290/-45
    • View Profile
    • TI-Chess Team
Re: OSLauncher Help
« Reply #16 on: August 31, 2011, 04:05:49 am »
Indeed, there's no manual distributed alongside OSLauncher. I wasn't going to officially describe how to run the CAS OS on the machine sold as non-CAS, but perfectly CAS-capable :)

TI-Planet, which replaces TI-Bank, is now online, so you can find OSLauncher, the program for decompressing boot2 and decrypting the OS suitable for Clickpad & Touchpad :)
Logged
Member of the TI-Chess Team.
Co-maintainer of GCC4TI (GCC4TI online documentation), TILP and TIEmu.
Co-admin of TI-Planet.

Offline Odo007

  • LV0 Newcomer (Next: 5)
  • Posts: 2
  • Rating: +0/-0
    • View Profile
Re: OSLauncher Help
« Reply #17 on: August 31, 2011, 12:07:48 pm »
Quote from: Lionel Debroux on August 31, 2011, 04:05:49 am
Indeed, there's no manual distributed alongside OSLauncher. I wasn't going to officially describe how to run the CAS OS on the machine sold as non-CAS, but perfectly CAS-capable :)
I know, I meant it as a joke...

Quote from: Lionel Debroux on August 31, 2011, 04:05:49 am
TI-Planet, which replaces TI-Bank, is now online, so you can find OSLauncher, the program for decompressing boot2 and decrypting the OS suitable for Clickpad & Touchpad :)
Yeah I know about TIPlanet, but I had to do it the hard way with GDB and all that!

In any case, it's awesome that it works!
Logged

Offline Yeong

  • Not a bridge
  • LV12 Extreme Poster (Next: 5000)
  • ************
  • Posts: 3739
  • Rating: +278/-12
  • Survivor of Apocalypse
    • View Profile
Re: OSLauncher Help
« Reply #18 on: September 01, 2011, 08:40:32 pm »
Does OSLauncher support 3.0.2 so I can put both 2.1 and 3.0.2?
Logged
Sig wipe!

Offline willrandship

  • Omnimagus of the Multi-Base.
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2953
  • Rating: +98/-13
  • Insert sugar to begin programming subroutine.
    • View Profile
Re: OSLauncher Help
« Reply #19 on: September 01, 2011, 08:45:51 pm »
Since OSLauncher doesn't need to worry about signing (Since you can just run any boot2 you want)  couldn't we try out some OS mods with this? I bet the OS itself (nucleus RTOS and its gui) support a ton of stuff TI cut out, like having other types of applications, or shells.

Remember OS 1.2, from the old prototypes?  That actually had some pretty cool features in it.
Logged

Offline Lionel Debroux

  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2135
  • Rating: +290/-45
    • View Profile
    • TI-Chess Team
Re: OSLauncher Help
« Reply #20 on: September 02, 2011, 03:48:51 am »
Due to the way TI made their OS, launching a different OS version (e.g. CAS 2.1.0.631 on non-CAS 1.7.2741) fails for most versions. So it's probably safe to say that OSLauncher does not support OS 3.0.1.1753 and 3.0.2.1791.

And yes, OSLauncher-type programs could perform arbitrary patching before launching the OS.
This has use cases that obviously belong to the well-acknowledged right to do what we want with the hardware we own, such as installing Ndless. However, other usages, such as a weak form of faking the PTT mode (which would not resist to reboot anyway), ought to be possible as well.
Logged
Member of the TI-Chess Team.
Co-maintainer of GCC4TI (GCC4TI online documentation), TILP and TIEmu.
Co-admin of TI-Planet.

Offline willrandship

  • Omnimagus of the Multi-Base.
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2953
  • Rating: +98/-13
  • Insert sugar to begin programming subroutine.
    • View Profile
Re: OSLauncher Help
« Reply #21 on: September 02, 2011, 10:12:18 pm »
well, there are plenty of other reasons to want to patch the OS as well, like the AMS patches for the 89 that fixed bugs and increased speed.

So wait, if it can't boot other OS versions....doesn't that mean CAS on non-CAS (or vice versa) is its only current purpose? :P
Logged

Offline Lionel Debroux

  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2135
  • Rating: +290/-45
    • View Profile
    • TI-Chess Team
Re: OSLauncher Help
« Reply #22 on: September 03, 2011, 01:53:59 am »
Quote
well, there are plenty of other reasons to want to patch the OS as well, like the AMS patches for the 89 that fixed bugs and increased speed.
Indeed. But with Phoenix, we are very far from the level of familiarity that we have with AMS.

Quote
So wait, if it can't boot other OS versions....doesn't that mean CAS on non-CAS (or vice versa) is its only current purpose?
Theoretically, the purpose of OSLauncher is booting arbitrary OS. I have purposefully released a toy OS at the same time as OSLauncher, named DummyOS :)
But since DummyOS is completely useless, for practical matters, the main purpose of OSLauncher is, indeed, launching Phoenix version x from Phoenix version x. AFAIK, nobody has tried to find exactly why launching Phoenix version y from Phoenix version x, with x != y, fails, but a possible cause is known: mismatches between the OS and the other files in the filesystem, e.g. the string IDs of the commands...

On AMS, TI kept the string IDs consistent across AMS versions, added new strings at the end, and provided the XR_stringPtr ROM_CALL for themselves, and users, to get the localized string corresponding to the given ID...
However, on Phoenix, examining primary_tag_list shows that the string IDs change from one version to another. This is yet another proof that Phoenix is explicitly designed and implemented in order to make native code programming hard...
Logged
Member of the TI-Chess Team.
Co-maintainer of GCC4TI (GCC4TI online documentation), TILP and TIEmu.
Co-admin of TI-Planet.

Offline Silver Shadow

  • Beta Tester
  • LV8 Addict (Next: 1000)
  • ********
  • Posts: 817
  • Rating: +27/-7
    • View Profile
Re: OSLauncher Help
« Reply #23 on: September 03, 2011, 04:57:00 am »
I did some testing and I got some weird results for OS 2.1.

On 2.0.1, OSLauncher successfully launched 2.0.1 CAS every time. However, on OS 2.1, it refused to launch both the 2.1 CAS and 2.1 non-CAS.
« Last Edit: September 04, 2011, 05:29:11 am by Silver Shadow »
Logged
Former Coder of Tomorrow

Offline willrandship

  • Omnimagus of the Multi-Base.
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2953
  • Rating: +98/-13
  • Insert sugar to begin programming subroutine.
    • View Profile
Re: OSLauncher Help
« Reply #24 on: September 03, 2011, 02:44:28 pm »
Well, maybe there's a good reason for the changing string IDs, such as keeping them alphabetically sorted even when you add new ones. Plus, if the SDK they use is updated for every release, then it would stay code compatible.

I wish it could just run linux :P
Logged

Offline Lionel Debroux

  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2135
  • Rating: +290/-45
    • View Profile
    • TI-Chess Team
Re: OSLauncher Help
« Reply #25 on: September 04, 2011, 02:09:24 am »
Quote
Well, maybe there's a good reason for the changing string IDs, such as keeping them alphabetically sorted even when you add new ones.
That's probably what they do indeed. But it completely breaks direct backwards compatibility (which, from the user's point of view, is usually a desirable feature).
Quote
Plus, if the SDK they use is updated for every release, then it would stay code compatible.
Yes, but only after rebuild, unlike the TI-68k series.
Logged
Member of the TI-Chess Team.
Co-maintainer of GCC4TI (GCC4TI online documentation), TILP and TIEmu.
Co-admin of TI-Planet.

Offline willrandship

  • Omnimagus of the Multi-Base.
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2953
  • Rating: +98/-13
  • Insert sugar to begin programming subroutine.
    • View Profile
Re: OSLauncher Help
« Reply #26 on: September 10, 2011, 12:50:13 am »
But, they don't have any intended third party developers anyways, so they don't really care if they throw us a loop once in a while by accident.

The 68k line, on the other hand, was open to 3rd party asm programming for a long time.
Logged
Pages: 1 [2]   Go Up
« previous next »