Dr.Gonzo

Connect the HD 360 to your computer and use the Party Buffalo Drive Explorer, to get access to your 360 HD File System.

If you have a lot of Games on your HD, it could be a problem to load the HD full with TUs. Aurora needs a lot of time to boot up, If you have a lot of TUs on your HD.

 

Also hosting this content is the problem. I know that these are the main problems.

Swizzy has explained the problem with storing of DLC Content stuff on Xbox Unity, to you in detail in the past. At first there are legal problems.

Comp packs are like DLC, in connection with a license condition, which you must agree.

In the past it was mentioned, that there will be no support in the Future for Compatiblity Packs over Xboxunity, because of Copyright issues.

(too late

The network software would have to support this feature.

Nope. The console did not work as a router.

In the past Libxenon was locked to 700MHZ, and there was only one core available. But that's a long time ago. Al Cores are can be used directly, with full clock speed.

Yeap, the development was stopped a long time ago.

The Xeon Emulator runs only one Game (Halo Combat Evolved) and not error free, Cxbx is not directly an emulator, it convert a Xbox 1 Game, to a Windows executable. DxBx  runs some XDK Samples and precious few Games. There is no real  Xbox 1 Homebrew Emulator. Perhaps someone released a fully working Xbox 1 Emulator, in the future, but I do not believe it.

It's all possible, it's just a matter of thinking far enough outside of the box... but, that kind of things are hard to do when you've got someone breathing down your neck wanting results like yesterday...

it's a debatable point, how it runs then. Just to emulate the CPU instruction Set x86 and the Direct3D API, is not enough (maybe if the Xbox 1 Game Coders, have worked in the past, much with Abstraction Layers). If this had not been a big problem, Microsoft had developed Patches for all Xbox 1 Games certainly too in the past (which very hardware near programmed) and we have already a fully operative (homebrew) Xbox 1 emulator for 360/PC.

The 360 would be able to cover much more xbox 1 games. That is a big company which is able to do it.

Some of the Xbox 1 Games are very close to the hardware programmed and used special low level Features on Xbox 1 hardware. It is not all about an emulator feasible, because there are technical limitations, you can not just bypass easily. Of course, Microsoft have good programmers, but they can't do magic.

He is using an ODE, to play Isos from Hd on retail mode, without flashing the DvD Drive. (Probable for Xbox Live)

Yeap, I am using the build-in Wlan Card of my Corona V2. Between my router and my 360 is a single wall. Your settings must not be wrong. It could be possible too, that foreign Wifi stations interfere your Wlan signals.

You can try to change the position of the router, but I would not expect too much. I reach over wireless not more than 4 - 5 mb/sec. Wireless is on 360 just very slowly.

In his case, its obviously, why he get banned.

@moses_373

The Xbox 360 uses a driver design for (internal / external) HD stuff, that is designed for 32-bit. You cant addressing more except 2 TB. To use a HD over 2 TB, the Xbox 360 should have the ability, to addressing  Logical Blocks  with 64 Bit.

Yes, well that was the problem. But thats why programming has always alternative ways. The "optional" GUI (files) could be loaded from internal/external hdd (into the RAM). That would be my first idea but i guess people thought about it. Now i need the missing public explanation. Otherwise people can't learn stuff.

 

Well Swizzy said so, i did not But what you say is also right. The main thing is that we can compare the xdk and libxenon documentation. And then you can guess so why xdk is a little bit better, i saw both. And like i said, we did not need libxenon, because we could do all with xdk. My opinion on libxenon, it came too late, it has not good enough documentation and it could not proove its power as it also was not pushed well enough. That's what we see as enduser. There is no offense, that's just our perspective which has to be accepted. Otherwise you have to try to explain and deliver proper answers.

If you work as a coder you see the demand. But sometimes you say that is not possible or a bad idea. You know your code but you have to put yourself into the brains of your consumers and think of how they are seeing your product without knowing how it works. It helps sometimes to satisfy the people. And thats done by explaining in a good way.

And currently im satisfied enough

Thanks for your answers.

You do not understand the reason of Libxenon !

Libxenon was created to program code on 360, without violate the Law. All the SDK stuff and the generated binaries from the SDK are illegal, if you are not the rightful owner.

The advantage of the original Xbox 360 SDK is, that you have an  excelente documentation about every API, all is explained in detail. You have for many stuff development libraries. It taking a lot of work off the hands. In Libxenon there is nothing , you have to do a lot things by yourself. But the programing itself is the same.

 

I dont know why you are failing pushing homebrew-connection or why you are not up2date with dashlaunch news in this site right now. Im not sure whether you're interested in public, in this work or not, or you may be lazy or just buzy?

The post of new XeBuild versions and other important things, is the matter of the Leader/Admins of this Forum. And dear Saywaking, a.k.a Saywa...

I would look at your attitude and how do you talk to other users. Otherwise, your time here will be just shortly as to Xboxhacks.de times.

 

 We have both versions. Libxenon which one sucks and xdk which rocks. Swizzy is right. The documentation of libxenon sucks. Thats why it died. And when i see xdk has also anything to accomplish goals im asking myself: why do we have another system on top of that? I just would like to focus on xdk only and i bet this is enough for anything. I asked once tuxuser about a GUI for xell. He said there was no enough memory if i remember correctly.

That the documentation Libxenon is bad, you can not judge, because you have no clue about the whole matter and you never have programmed a line Code in your life. The main problem is, that the 360 (JTAG) Hack and Libxenon, came very late in the lifetime of the 360, and the Homebrew-Scene was not like same as the Xbox 1 time, we have see new Homebrew Content, every weak.

Of course the Xbox 360 Kernel have various functions and supports the concept of virtual memory.  However unlike to Windows, the hard drive is not used as a backing space. That means that game usage of memory, cannot exceed the physical  Memory size of the 360.

You're wrong about the architecture here, Xbox 360 is PPC64 not x86/64 (like Xbox and Xbox One) and although XDK is the SDK the hardware is also referred to as XDK... and anything built using those tools are often referred to as "XDK homebrew"

 

I now that the Xbox 360 use the Power PC architecture. I'm assuming that the MS Compiler generally produce very fast, PPC code too.

I have expressed myself wrong.

It's not about having more power, but to be able to access hardware directly. This can provide significant Timing advantage, in different cases. It depends exactly on the application.

Linux coding is also simplier i heard of but when we want to see examples its not good enough yet.

The Coding of programs itself, is completely independent of any platform. The programming is actually the same, as long as you use any system-specific functions.

The XDK/SDK is only a development environment (it contains the compiler, linker, debugger, and so on). You have on Libxenon environment tools too. Which are better, I cant say, but It is not unknown, that MS has very good Compiler. They produce very fast code on X86/64.

On Xbox 360 you cant directly access the hardware, because you have between the executive hardware and your code, various hardware/software abstraction layer. The (S)HAL needs computing power too. With Libxenon you are closer to the Hardware, and you have more computing power available,  because many (S)HAL are not present.

I mean it's safer than  you move all the stuff with a file Manager by yourself. This was not referring to your post.

Its from Homebrew-Connection.org. HC is the official support forum for XeBuild too. I guess that JPizzle will create an official posting shortly on RMS.

Use the buffalo party drive explorer (or similar). It has a backup function inside, to backup your complete Xbox 360 HD.

Its the easiest and safest way.