Print

[ZBeeblebrox]

From info_launch.ini:

; if true ping limit will be removed for system link play (thanks FBDev!)
; if not present default is FALSE
pingpatch = false
; if true (most) xbla will no longer need yaris patching (thanks mojobojo!)
; if not present default is FALSE
contpatch = false

Does this mean we no longer require the Ping Limit/Unlicensed Content patch file "kxam.patch" in the root of the hard drive anymore? I'm guessing the code is now included in "patches_[console].bin" file and simply setting the conditions to "true" in the "launch.ini" file will activate those patches? If so, should we delete that file from the drive to avoid conflicts?

Edit: Just experimented (what little I can) and found that adding those settings to "launch.ini" and deleting the "kxam.patch" file from the HDD still results in "System Link Patched" showing up under the Profile name on the main menu. I have no "Unlicensed Content" to test, nor do I use XlinkKai to test the Ping Patch, but I assume they are working. My Thanks go out to the Dashlaunch Team!

[ZerOneX]

.. just tested it right now... very easy to install and amazing features!! Thank you.

[Sonic-NKT]

Just installed it and its working fine! Thank you very much...

btw, there was a freeboot/dash launch patch released some time ago that fixed the internal MU Problem on BB Jasper units, is this integrated in 2.0 too? couldnt find it on the changelog....

[emk]

Hmm cant get it to install. Flashing gives error fffffffd.

*fixed* Reuploaded the whole folder again and it worked.

[doerek]

QUOTE(sudmah @ Sep 17 2010, 12:34 AM)

- added xell loader to patch set and included a xex to load xell

can you guys clear something up plz . . does this mean running xell at full cpu speed as its a .xex moving linux forward or am im mixing this up? would test myself but only have xbr. thanks

...i think that would be to cool to be true

[krizalid]

There's still one little issue that it's no big problem but that will help if it was corrected.

When in NXE you want to play DVD Movie it boots to DEFAULT;XEX from DashLaunch Config.

You must press and Hold RB so that the movie plays.

[AndiRS]

i can not load .xex from usb at startup - it just boots nxe

launch.ini und die .xex are on the usb device and launch.ini points at the right direction

what could be wrong? or is it just a bug?

edit: members from other forums confirmed this issue

[soulwarrior]

QUOTE(AndiRS @ Sep 19 2010, 07:27 AM)

i can not load .xex from usb at startup - it just boots nxe

launch.ini und die .xex are on the usb device and launch.ini points at the right direction

what could be wrong? or is it just a bug?

edit: members from other forums confirmed this issue

Yeah same problem here.

[AndiRS]

ok, i hope the dev reads this  

[Sonic-NKT]

would be very cool if this would allow fullspeed linux again without the old kingkong exploit and old dash....
hope someone puts an updated linux distro together with the latest patches for the 360
it would be very cool to have a virtual Partition on the 360 harddrive for linux, so you dont have to use 2 HDDs

[cory1492]

QUOTE(AndiRS @ Sep 19 2010, 05:27 AM)

i can not load .xex from usb at startup - it just boots nxe

launch.ini und die .xex are on the usb device and launch.ini points at the right direction

what could be wrong? or is it just a bug?

edit: members from other forums confirmed this issue

What is the ini value that is causing problems? are you using multiple USB drives with other ini in place (!remember! launch uses the first ini it finds)? what type of USB drive are you using (HDD or flash)?

I'm using a pair of lexar 4G and a kingston 2G usb thumbstick, and have had no such issue loading xex from them (with both Usb: and UsbMu:)

[AndiRS]

im using a 8gb kingston thumbstick and no other device is connected

the value i use is:

Default = Usb:\Applications\Freestyle 2.0\default.xex

and of course fsd2 is in that place

[cory1492]

CODE

parsing: Default
lpath: Usb:\Applications\Freestyle 2.0\default.xex
Mount: dlaunch:\Applications\Freestyle 2.0\default.xex
launch.xex: mount \Device\Mass0\ to dlaunch: sta:Success
FOUND! dlaunch:\Applications\Freestyle 2.0\default.xex

I used your config entry on launch.ini file at root of the usb stick, and freestyle started for me just fine.

The only things I can think of, is that you need to have the category [QuickLaunchButtons] above your default entry, that you must save the file as UTF-8 or ascii (not unicode). Aside from the fact the path needs to be correct of course, on windows looking at the memory stick I have:
"K:\applications\Freestyle 2.0\default.xex"

Nice to see that spaces and case don't seem to botch things up in the path names

krizalid: bug noted, it should get fixed hopefully in short order. From what I understand this bug was reported before with regards to launching dvd from freestyle, but no one seemed to know how to do that...

[cory1492]

To get debug text I used a cygnos and added some DbgPrint() to the code.

I use notepad++ 5.7 (http://notepad-plus-plus.org/), in the encoding menu I have it set to "ANSI" - if this turns out to be the problem for you I will see about getting multibyte enabled in simpleini, should make for less problems all around.

[AndiRS]

unfortunately this doesnt help... but thanks