Is Xbr4 Expected Or Canned?

[finalman]

Is team xbr still working on xbr4 or has the team disbanded in favour of freeboot and therefore no xbr4, or is it still in the cards for a xbr4 release?

[slasherking823]

this is only the 100th thread I have seen about this...

[ReverseAffect]

as of now freeboot is in affect.......
xbr was just a temp stand in because of freeboot when it first came out ,can only work with 2 nands...
now that freeboot works with 1 nand ,what would you think?

[yasn]

Sorry, also probably asked 100times before:
so you suggest migrating from XBR to Freeboot?

I'm happy with a simple yes or no, but if you've time:
what are the benefits of freeboot over xbr?

Freeboot is based on newest kernel I (only until natal comes out, I guess), but anything more?
What is possible with freeboot that ain't with XBR?

[ddxcb]

The only thing i miss about xbreboot is the clean block structure. but thats the only thing tho. xD

[nevernow]

As of now, the only benefit of migration is the ability to use the new USB mass storage functionality. Personally, I won't upgrade until the 16GB limit for such functionality is removed or games start requiring a 9199 kernel.

[neonpolaris]

Eventually games will require you to have the 9199 dash. You can modify the games around that (depending on the game), but if you have the newest dash you won't have to.

[idog]

Freestyle Dash 2.0 has some functionality which requires the Memory Access feature in freeboot. That's one of the reasons (that and USB device support for savegames) I do my jtags with Freeboot 0.32 now

[neonpolaris]

Now that you mention that, I suddenly realize that my Cygnos has a reason to exist again. One NAND for memory access features, one for xbox1 compatibility.

Not that I've ever played an xbox1 game on my 360, but who knows when I might feel nostalgic.

Any idea what these features of Freestyle Dash 2.0 will be?

[damox]

Any idea what these features of Freestyle Dash 2.0 will be?

Things like; returning to FSD from in game.

[neonpolaris]

That's got to be the best possible feature to add to a replacement dash.

[cory1492]

I won't upgrade until the 16GB limit for such functionality is removed or games start requiring a 9199 kernel.

I wouldn't hold my breath on that one; afaik the limit isn't just some arbitrary number that can be magically ignored.

Things like; returning to FSD from in game.

Now that you mention that, I suddenly realize that my Cygnos has a reason to exist again. One NAND for memory access features, one for xbox1 compatibility.

http://helldoc.blogspot.com/2010/05/update.html
Not a FSD feature, and won't be a need to choose between compatibility and memory unlock.

[nevernow]

I won't upgrade until the 16GB limit for such functionality is removed or games start requiring a 9199 kernel.

I wouldn't hold my breath on that one; afaik the limit isn't just some arbitrary number that can be magically ignored.

In fact, I don't take it for granted; I meant that such a feature alone would motivate me to upgrade immediately, while I haven't felt the need to do so until now.
By the way, would you share your knowledge about the issue?

[Gazcoigne]

I won't upgrade until the 16GB limit for such functionality is removed or games start requiring a 9199 kernel.

I wouldn't hold my breath on that one; afaik the limit isn't just some arbitrary number that can be magically ignored.

what makes you think that this particular restriction is harder to patch than lets say the hypervisor etc?

give it time it will most likely be removed, same as the restrictions on hdd size.

not speaking from experience here, moreso from probability, im sure the experts will chip in and clarify this.

[jester]

not speaking from experience here, moreso from probability, im sure the experts will chip in and clarify this.

He is an expert, I would trust what he said on the matter.

[cory1492]

what makes you think that this particular restriction is harder to patch than lets say the hypervisor etc?

give it time it will most likely be removed, same as the restrictions on hdd size.

not speaking from experience here, moreso from probability, im sure the experts will chip in and clarify this.

The restriction on HDD size wasn't removed, the driver itself has always supported varying drive sizes - what was "removed" was the reliance on HDD security descriptor with signed data, where if the drive firmware didn't match the security descriptor you got a Exx screen.

The Usb Mu is a file system in a file which is in a file system on a device; the Mass driver (raw interface to Mass device) mounts the FAT volume (the file system on the Mass device) which mounts the FATx volume contained in spanned files - all on a relatively slow Mass device on a relatively slow USB bus. As with GOD/SVOD or LIVE/PIRS containers, the volume driver is only going to be able to cache so much descriptor for random accesses within the spanned volume files, and that may not be the only limit, the FAT descriptor (the bit that is able to describe where files are physically in the volume) may be limited in how much it can describe and whatever cluster linking method they use for fragments could easily be another limit.

I've purposely not touched on the functions that actually create the device, I believe someone could come up with a PC app that does just that without touching dash at all. I 100% agree it's not impossible, but I think it would be easier to abuse the drivers into thinking a regular usb stick is a MU than it would be to try and lift this limit without having the driver source and DDK - and even then MU do have some (plausibly artificial) imposed restrictions after the Datel stuff (I've never looked into what they changed to do this datel exemption.) Either way, I don't expect a magic nop to change it.

[nevernow]

Thanks for this post.

[ZerOneX]

with freeboot 9199, xbreboot is not necessary for now.

[neonpolaris]

http://helldoc.blogspot.com/2010/05/update.html
Not a FSD feature, and won't be a need to choose between compatibility and memory unlock.

Ok, so it's not a feature of FSD directly.  But from your own link:

All I can tell is that if you dont have the latest freeboot with memory hack yet, it wont work!

Has there been a solution for the official xbox1 emu and the memory hack to coexist?

[q36]

yes the new dashlaunch patches should fix the mem patch/xb1 emu issues.