Topic: Devkit (Read 296 times)

DanXbix · « **on:** March 16, 2008, 09:12:00 PM »

(IMG:style_emoticons/default/blink.gif) i am wondering if there is any more pics of the latest dev kits (dash 6883 latest)

Any news of any things developed with the lucky owner of these units?
XDK on the xbox1 was leaked did microsoft ever find out who did it?

scuba156 · « **Reply #1 on:** March 17, 2008, 06:16:00 AM »

they may have, i dont know.

the 360 SDK is already out there (not for the pblic, but a few hackers have it AFAIK) but will NOT be used to create any public homebrew for the 360 due to many legal reasons. theres modders want to stay away from the courts, and create there own software to create homebrew games

DanXbix · « **Reply #2 on:** March 17, 2008, 05:29:00 PM »

like xbox 1 they should develop a OPENSDK that should at least start something
i know we cant use it yet as there is no real way of booting code, but at least hackers would have a head start
at developing for it.

scuba156 · « **Reply #3 on:** March 17, 2008, 08:31:00 PM »

from what ive heard, they have used an XDK to create a bootloader (to run unsigned code) but as it uses the XDK, it becomes illegal.

the openXDK wasnt very powerful (hence why all the of good homebrew apps were created using an XDK, instead of the openXDK

Libtoem · « **Reply #4 on:** March 18, 2008, 11:48:00 PM »

Well yes people do make homebrew for use on the 360 dev kit,but you wont see anything until the retail 360 is crack.Once the 360 is cracked than the 360 sdk will get leaked,it will be xbox 1 all over agian,the xbox 360 scene would get flodded with homebrew,but if it ever does happen.

scuba156 · « **Reply #5 on:** March 19, 2008, 02:00:00 PM »

no that will not happen, the SDK is already available to people (im not going to name anyone and it may cause them being harrased for it), BUT it will NOT be used for any public releases of xbox 360 homebrew

and i wasnt talking about these people having the ability to run unsigned code of a devkit either....

if they did make public releases of homebrew built with an XeXDK, then it opens them up to lawsuits and obviously they dont fancy being sued

This post has been edited by scuba156: Mar 19 2008, 09:03 PM

Libtoem · « **Reply #6 on:** March 19, 2008, 04:42:00 PM »

QUOTE(scuba156 @ Mar 19 2008, 10:36 PM)

no that will not happen, the SDK is already available to people (im not going to name anyone and it may cause them being harrased for it), BUT it will NOT be used for any public releases of xbox 360 homebrew

and i wasnt talking about these people having the ability to run unsigned code of a devkit either....

if they did make public releases of homebrew built with an XeXDK, then it opens them up to lawsuits and obviously they dont fancy being sued

Don't you remember what happened to xbox 1,and yes it will happen to the retail 360 if it gets fully hacked.
Thats why you haven't seen any public homebrew.I've been in the 360 dev scene for a couple of years now,but the retail 360 is far from running unsigned code.For right now if people want a modded 360 than there best bet is to get a 360 dev/debug kit,that kit works wonders.

scuba156 · « **Reply #7 on:** March 19, 2008, 05:48:00 PM »

yes i do remember what happened with the xbox. and any decent homebrew used an MS XDK, which made the homebrew apps illegal. they are refusing to take this route with the 360, they do not want to use a MS XeXDK for creating homebrew on the 360. basically, they dont want to be sued just so other people can have homebrew. its just not work it for them. i think your mis reading what im saying

i suggest you go read up on xboxhacker.net

bootloaders have been created for a retail xbox 360 that will run on it, but its built using a MS XeXDK

This post has been edited by scuba156: Mar 20 2008, 12:49 AM

Libtoem · « **Reply #8 on:** March 19, 2008, 05:58:00 PM »

Yes I do read over at xbox-hacker all the time,Im a member over there.I know what your saying,and yes I know the risk of people using the 360 sdk to create homebrew.But all Im saying is if it gets leaked on the net than there's nothing we can do.And the good thing is that everyone I know who has the sdk will not leak it,same for for the people who you know.Hell I bet we know the same people.

This post has been edited by Libtoem: Mar 20 2008, 12:59 AM

scuba156 · « **Reply #9 on:** March 19, 2008, 06:11:00 PM »

they most likely are

sorry, i didnt realise you were talking about in the event of it being leaked. to me, it seemed like you were saying that the people who have it now are going to create public homebrew with it. and i (now) completly agree with you on that point.

even though im impatient, im glad that they are taking the legal route and that no one will leak the XeXDK. for one, it gives this community a better name as it is no longer illegal.

by going this route, i would expect to see homebrew starting to pop up in about 1.5 - 2.5 years if intrest doesnt drop (which it most likely will due to the new wii hacks, i really cant wait to get some native homebrew running on the wii, which funnily enough is what im typing this on right now)

Libtoem · « **Reply #10 on:** March 20, 2008, 05:47:00 PM »

Well the good thing is that MS does not supply the 360 sdk on disc like they did with the xbox 1 sdk,the devs have to get it from xds.xbox.com,which is a highly guarded site.And I have noticed game reviewer's will sometimes get a recovery disc and just Xbox 360 Neighborhood exe,for taking screenshots.And more so reviewers will just get a demo kit that only has the retail dash installed so they cant mess with the xdk dash,PN and such.

scuba156 · « **Reply #11 on:** March 21, 2008, 05:17:00 AM »

while MS has been trying to keep the lid on this jar airtight as you said, 90% of the time, there is always some way to get around it (not that i want it to be leaked though), the question is if someone will be able to find that way and then actually start sharing it.

i can understand them having tight security for the SDK, but i could imagine them leaving a hole somewhere in the consoles security. they cannot deny that with the xbox being fully hacked, it brought them alot more sales. they are a business after all and in the end, all businesses are in it for the money, but they do have to protect the interests of investors and developers too

satviewer2000 · « **Reply #12 on:** March 26, 2008, 12:02:00 AM »

QUOTE(scuba156 @ Mar 21 2008, 12:53 PM)

while MS has been trying to keep the lid on this jar airtight as you said, 90% of the time, there is always some way to get around it (not that i want it to be leaked though), the question is if someone will be able to find that way and then actually start sharing it.

i can understand them having tight security for the SDK, but i could imagine them leaving a hole somewhere in the consoles security. they cannot deny that with the xbox being fully hacked, it brought them alot more sales. they are a business after all and in the end, all businesses are in it for the money, but they do have to protect the interests of investors and developers too

Wasn't it true that MS actually LOST money on every XBox1 sold? It was basically a PC for far less than what a simlarly powered PC would have cost at the time. I believe their business model was to make money by selling software, licenses, accessories, etc, NOT by selling the console itself. So selling a fully hackable console didn't make much business sense. Even if the whole world had bought Xbox1, MS would still only be able to break even (if that).

This post has been edited by satviewer2000: Mar 26 2008, 07:08 AM

scuba156 · « **Reply #13 on:** March 26, 2008, 01:00:00 AM »

yes they did loose money per console. but by having a hackable system such as it was, it increased the user base of the console. even people who got a modded console brought games for it

This post has been edited by scuba156: Mar 26 2008, 08:01 AM

Author Topic: Devkit (Read 296 times)