By flipnile
Sun Dec 11, 2005 6:32 pm
Lampdog wrote:Is this going to escalate into derrogatory indirect
insults here or what? It shouldn't. Let's quit now.
You're right, fam. Sorry about that.
Lampdog wrote:Is this going to escalate into derrogatory indirect
insults here or what? It shouldn't. Let's quit now.
mpc3000 wrote:After 5 pages I am not in the mood to make quotes, so I will summarize some thoughts.all of what you said is fair, in a sense but if you do not know exactly where this code came from and/or don't know exactly what's in it, why take the risk of something happening to your machine. because it is possible (not saying it will) for something to damage the hardware and components. if i was the one who wrote an alternative os for my mpc, then i wouldn't hesitate because i know what's in the code. as far as linux, if i didn't like part of the code or if part of the code messed up my hardware then i would just rewrite that part of the code, again, knowing what's in it. but since i don't know the person who wrote this alternative os, i wouldn't install it in my machine. (that's just my opinion)
Messing your MPC:
It is possible to boot into any OS without permanently writing to flash. Is this by design a "test-like" environment that is not too different than your typical Linux Live CD. This a pretty safe operation that is available on any flash OS MPC. I've used this quite a bit when modify/testing OS's without using up limited write cycles of the flash.
Hacking your own OS:
To say that a software cracking group is going to port the MPC2500 OS to the MPC1000 is pretty naive. Reverse engineering an OS is very different from cracking software.
Bulding your own OS:
This is getting simpler every year. The development tools to write an OS from scratch are not that hard to get. Some are even free.
DJ Premier wrote:...A lot of new cats out now do not know the history.


soyo wrote:any one tried yet?


sparq wrote:mpc3000 wrote:After 5 pages I am not in the mood to make quotes, so I will summarize some thoughts.all of what you said is fair, in a sense but if you do not know exactly where this code came from and/or don't know exactly what's in it, why take the risk of something happening to your machine. because it is possible (not saying it will) for something to damage the hardware and components. if i was the one who wrote an alternative os for my mpc, then i wouldn't hesitate because i know what's in the code. as far as linux, if i didn't like part of the code or if part of the code messed up my hardware then i would just rewrite that part of the code, again, knowing what's in it. but since i don't know the person who wrote this alternative os, i wouldn't install it in my machine. (that's just my opinion)
Bulding your own OS:
This is getting simpler every year. The development tools to write an OS from scratch are not that hard to get. Some are even free.

djobserv wrote:honestly the interface is wack, big up to the person who took the time to work it out but your better off using the intutative mpc 1.07 interface


