I was actually surprised to see it was getting ported since we were trying to keep good relations with TI, but I guess that considering what they are doing, I don't see why we should really care that much. Plus it's nice if we can run multiple OS versions at once on one calc.Exactly. TI won't change their position so I don't see a reason why it shouldn't be updated. And TI announced that they will block Ndless before this version of OSLauncher was released.
But in its current state, it's unlikely to be able to run the CAS OS on the non-CAS CX model, because this doesn't work anymore (for now) for the Clickpad & Touchpad series.Yes, for now, but I still have hope to get it to work :P
Basically my code works, I can launch DummyOS and it works fine, but OS 3.1 CAS reboots.
I really don't think that releasing this was a good idea.I disagree ;)
Maybe it would have taken years, but TI could eventually have changed their mind after they see we don't do anything against their interest.AFAWCT, TI would in no way have changed their mind ;)
Now they'll think they can't trust us.It seems very clear that Melendy Lovett has never thought TI could trust anyone in the open development community.
Moreover, it is a matter of days before Ndless is blocked so I really don't get the point of releasing it now ???Well, I won't update to OS 3.2 untill there will (maybe) be a new ndless version; The use of Ndless is much higher than the use of Lua and I don't want to be limited by TI.
QuoteNow they'll think they can't trust us.It seems very clear that Melendy Lovett has never thought TI could trust anyone in the open development community.
(BTW, downrates don't exist anymore :) )Yes, I saw that right after posting. But what will happen to people with a negative respect ?
And, did us being overly nice prevent TI from trying to tamper with our freedom to tinker ? Not in the slightest way.I can't remember the exact phrase but it might be something like "the world wasn't created in one day" (or maybe it is Rome, idk :P)
Well, she trusts the community to also produce contents with the official tools they give, which has been greatly improved with Lua ;)Yes, Lua has improved a lot, but I'll only give Ndless up when all games (and I didn't say "all programs") from Ndless run with Lua ;)
produce contents with the official tools they give, which has been greatly improved with Lua ;)Well... before Lua, without Ndless, the Nspire's abilities were so low that anything is a major improvement over the sorry state of the Nspire before the spring of 2011 ;)
I think that if we only released games on 4 or 5 consecutive versions of Ndless, they would start changing their mind.Er... they care only about teachers, and the vast majority of teachers hates games, so making games is definitely not the way to make TI change their mind about our freedom to tinker ;)
Yes, Lua has improved a lot, but I'll only give Ndless up when all games (and I didn't say "all programs") from Ndless run with Lua ;)That is to say, never :D
ANOTHER EDIT:
No os I have tried so far works. Even non-cas os.
I feel sorry for myself that all os freeze at the clock screen. Everybody else is getting oslauncher working, why can't I? Maybe it's because I have 50% battery life left, or maybe oslauncher is messed up, or I forgot to noverclock my nspire?
Why are there no downrates?
I didn't mean to get pissed off about my negative respect, if that is the reason for no more downrates.
Also in response to Hayleia I don't think it matters anymore if it's a good idea to release this or not. The harm was already done with PTT patches and fake mem clears on the TI-83+ years ago and since then, TI has taken a strong stance against third-party hacking and when TI-Planet people tried to convince TI that Ndless was not meant to cheat, it was already too late.Yeah, they might never change their mind :-\. I was just pointing out the fact that it is sure that they will not change their mind if OS Launcher keeps being updated, not saying that discontinuing it would change their mind in one day.
I would say that at this point, what matters the most is that no cheating tool comes out on the Casio PRIZM, since Casio has given us a chance that, IMHO, we should not blow up.I agree. Even if it is less powerful, it will always be able to run programs, without waiting for months before the jailbreak. I need to buy one by the way :P
Was the icon problem present before?Yup, it has always been present.
Here is an updated version that supports file extensions. It will still use /documents/ndless/phoenix.raw.zip.tns if it is launched directly.
And it has a theoretical CX support, but launching official OSes still fails.
SilverOne on TI-Planet has discovered that launching any OSes < 3.1.0 will work when OSLauncher is in the ndless/startup folder, so launching CAS OSes on non-CAS devices should be reliable now (link (http://tiplanet.org/forum/viewtopic.php?f=43&t=9235&p=123899#p123899), but the menus will be messed up). Sadly, this method doesn't work on CX calcs (tested in emulator).
I wouldnt think a TI-89 emulator in a program could be that bad... as long as it still required a rom i cant see the legal troublesI think the "bad thing" they are talking about was OSLauncher, not the 68k emu. But maybe the 68k emu is a "bad thing" too since it can bring the CAS to a calc that doesn't have it. At least it is not its main purpose, unlike OSLauncher.
At least it is not its main purpose, unlike OSLauncher.Wrong, you should know better. It's sad to see members of the community misunderstanding OSLauncher that grossly, and misrepresenting its purpose...
Wrong, you should know better. It's pretty sad to see members of the community misunderstanding OSLauncher that grossly, and misrepresenting its purpose...Sorry, I didn't express my self right. I was not talking about the purpose of the program but about the purpose of users. Of course some of them want to downgrade for some reasons, but you have to agree that most of them are using this to put the CAS on a non-CAS calc ;)
As I've explained multiple times:
* the main purpose of OSLauncher is not to bring CAS functionality to the CAS-capable model sold as non-CAS, it is to hot-launch arbitrary OS. Besides, OSLauncher was released alongside with DummyOS, and without any instructions on running the CAS OS on the CAS-capable model sold as non-CAS;
* OSLauncher is absolutely no threat to the acceptance of the Nspire in standardized testing...
But needless to say, launching the CAS OS on the CAS-capable model sold as non-CAS was a testcase that I executed on my calculator :)
Still, It's not our fault if the CAS OS runs unmodified (well, at least, when one manages to achieve a successful launch) with OSLauncher.
I'm one of the very few persons of the community who can't be blamed for the fact people didn't make alternative OS for the Nspire (making DummyOS much less dummy, simply by porting an existing OS to the Nspire, etc.): I released OSLauncher, after all. But nobody cares about the Nspire...
If the original pupose was not too launch a CAS OS, then could you write code to block any CAS OS?As I have probably already explained as well, anybody could add code to that effect, but it would be useless because anybody could remove that code ;)
Actually I kinda got confused with PTTKiller here (which was the file that got taken down). My bad.
Ndless is already a PTTKiller. Just put things in ndless/startup/ folder and it will be launched at startup even in PTT mode.No, Ndless has the possibility to kill PTT but PTTKiller does kill it. And once again (truly this time), Ndless purpose is not to kill PTT while PTTKiller's purpose is.
Problem ?
There were already enough bad things said about Omnimaga elsewhere in the TI community in the past.Indeed, but wouldn't the unacceptable move of censoring free speech and distribution of ideas and code, about our basic user rights to run whatever we please on our calculators (freedom to tinker), result in more bad things said about Omnimaga, and making Omnimaga less relevant ? :)
Ndless is already a PTTKiller. Just put things in ndless/startup/ folder and it will be launched at startup even in PTT mode.No, Ndless has the possibility to kill PTT but PTTKiller does kill it. And once again (truly this time), Ndless purpose is not to kill PTT while PTTKiller's purpose is.
Problem ?
rename("/documents/myfolder", "/exammode/usr/myfolder");The staff will indeed have to make a decision on the matter - being good citizens caring about their fellow users' rights, or keeping to side with TI in not caring about users' rights :)I believe the issue was not related to this but rather on facilitating some way to cheat, which Netham (I think it was him?) said Omnimaga is against.
one line of CYes, and this line of C was not put in Ndless, but in PTTKiller, so Ndless is not a PTTKiller.Code: [Select]rename("/documents/myfolder", "/exammode/usr/myfolder");
I can't see how more simple it could be. PTTKiller is just an already-made code, it is not difficult to understand, even for newbies who never programmed.
QuoteThere were already enough bad things said about Omnimaga elsewhere in the TI community in the past.Indeed, but wouldn't the unacceptable move of censoring free speech and distribution of ideas and code, about our basic user rights to run whatever we please on our calculators (freedom to tinker), result in more bad things said about Omnimaga, and making Omnimaga less relevant ? :)
Perhaps the censorship exercised in the PTTKiller episode has already resulted in bad things said about Omnimaga...
The staff will indeed have to make a decision on the matter - being good citizens caring about their fellow users' rights, or keeping to side with TI in not caring about users' rights :)
It's the staff that decides how Omni is ran and you cannot dictate how the team should run their own site nor force them to run it the way you want.I know, I do run a site as well, and the first time I was moderator on a message board was about ten years ago :)
What is frowned upon is helping people cheat on tests and bypassing school calc restrictions.It's up to the users of said methods to face the consequences of their actions (if any), and also up to the whole idea of standardized testing not to be so disconnected from real-world usage of calculators. That does, however, not mean that discussion and programs should be actively censored.
I know, I do run a site as well, and the first time I was moderator on a message board was about ten years ago :)And the last time you moderated a message was with me, complaining about what I am complaining now ;)
one line of CYes, and this line of C was not put in Ndless, but in PTTKiller, so Ndless is not a PTTKiller.Code: [Select]rename("/documents/myfolder", "/exammode/usr/myfolder");
I can't see how more simple it could be. PTTKiller is just an already-made code, it is not difficult to understand, even for newbies who never programmed.
There is the same difference between a human and a human with a gun: one can hurt, not the other.
What people don"t understand is that PTTKiller doesn't do anything special, anything that requires extensive OS hacking skills.And what you don't understand is that if Ndless gets permanently blocked, all your work on Theme Editor for example is useless.
If PTTKiller is already in Ndless, then why was a standalone PTTKiller ever published? ???It is not that PTTKiller is already in Ndless, it is that Ndless almost does not need extra code to kill PTT
On the other hand, Hayleia, regardless of if PTTKiller existed or not, I doubt TI would ever change their mind about Ndless. :P They already made up their mind about ASM and C way back in 2006. That said, maybe if we play nice they'll not permanently block Ndless yet? (Seeing how OS 3.2 can still be downgraded back to the very OS that can run Ndless 3.1, despite coming out several months after Ndless 3.1, it almost seems like TI doesn't mind us running Ndless to a certain extent)Yes, that is my point of view. Let's not kill the opportunity TI didn't give us yet ;)
if Ndless gets permanently blockedWhich is very unlikely in the first place ;)
That said, maybe if we play nice they'll not permanently block Ndless yet?As you know, we have already played overly nice to TI, without receiving anything in return ;)
(Seeing how OS 3.2 can still be downgraded back to the very OS that can run Ndless 3.1, despite coming out several months after Ndless 3.1, it almost seems like TI doesn't mind us running Ndless to a certain extent)No. TI let users downgrade to OS 3.1 because OS 3.2 regresses on some things (and they know about it), not at all because they want to let people access native code. OS 3.2 is an unfinished, defective product, and they didn't have a choice: they needed to let people downgrade.
It won't be useless. Finding things like that is a game for me. I don't mind if it will be blocked.What people don"t understand is that PTTKiller doesn't do anything special, anything that requires extensive OS hacking skills.And what you don't understand is that if Ndless gets permanently blocked, all your work on Theme Editor for example is useless.
Moreover, I don't care about the simplicity of PTTKiller, I only care about what it does, and in my opinion it should not be called PTTKiller but NspireCommunityKiller.To my mind, TI is just stupid to have put a PTT mode in the "public" OS. Why can't they make a compilation flag in order to generate PTT OSes and let the "public" OSes access ASM/C ? It just takes a few dozens seconds to install an OS, even faster if it is smaller.
Whenever I try to do step 10 under Install nLaunch, the link software and my calculator both freezeIt's natural that the linking software freezes, and it can occur that the calculator freezes. Try again :)
Are there any (free) alternatives to the link software?Yes, but TILP II freezes all the same when the calculator fails to reply, following the exploit triggering.
Could the moderators add a red note at the beginning of the first post, indicating that this has been superseded by nLaunch / nLaunch CX / nLaunchy (fork maintained at TI-Planet, which adds CM-C OS support and "switcher" capability) ? TIA.Done ;)