ok, I flashed freeboot 0.032 and dashlaunch successfully to my falcon. I used flash_installer to flash launch.ini and lauch.xex to nand. dashlauch is confirmed working as I got freestyle to boot before nxe by pressing X. kxam.patch is in hdd root and so is another launch.ini. In launch.ini under patches, I have patch1 = hdd:\kxam.patch.

Despite all this, I have the same problem as the other folks here. I can see a game but not connect to it, it just times out. this happens in every single game I try.

what I realised was that in cod4 mw2, I dont have the tu6 and those people who do in kai cant see me and I cant see them. But, if we have the same old version, the connection just times out. though, from what I understand, if it times out, the patch is not working? right?

So what's missing...??

@redringofbox
My example ini didn't have that, and I have the newest dash launch from xbins.
My example ini had xexmenu and freestyle dash. :S

I've used kai for about 6 years (before 360). You don't need a jtag to use it, you don't even need a 360 (it can even be a PSP, xbox1, etc...). So, what you should try to do is just get it working with 2 normal xbox's (with or without dvdrom mods matters not). Then, install the patch and see if it was really the patch. 8 times out of 10 it is a firewall. The other 2 times it is because you didn't read the manual for kai (you forward port 30000 to your PC's ip, _NOT_ to your xbox's ip). Also, there is a configure tool for kai in the install directory, it doesn't actually have to be port 30000. It works for the old kai client and the new we based one. Also, some virus programs can actually get in the way too, just in case you have a overbearing virus program, might want to check that.

Again, get it working without the patch, then try the patch.

Off Topic: I have a post in the dash launch thread about my xbox continuously rebooting right as it tries to load the dash, any help is welcomed. I would like to try kai with people farther away. And being you have to have dashlaunch installed correctly, I cannot do that. Unless, there is a way to apply the patch without dashlaunch?

I get the feeling that not many have this working. For all the hipe there doesn't seem to be a lot of users on Kai and this has nothing to do with the console when just in the Kai UI. If you can't see anyone in there then there's no chance of having a match.

I'm keen for some matches, my kai tag is Haydos but we have some different 360 gamertags also

As far as hosting or joining, Ive had no real problem unless the ping is real bad (+350ms, I'm in Oz BTW) and apart from the setting up I only have mw2 disc installed via nxe, TU6 update in cache and all the maps work including stimulus and resurgence. I installed these manually. Weird I thought you had to have default etc updated for these to work.

hmm I could have sworn that was in the example ini. My mistake, sorry about that. But it is either in the readme or the launch.ini that you can find all the combinations and the buttons you can use. I can't really check right now as my computer recently got a nice little Trojan and I had to reformat it and I lost most of my stuff.

Haygar- You shouldn't have to manually patch default.xex I've got TU6 in my cache and MW2 installed via Xexmenu and I can join just fine.

@Haygar
I've been able to run most of my games from a USB drive with the TU's in the Cache folder, including MW2, L4D2 was the only game I had to go and manually patch.
@Julets
Ofcourse Kai works normally with other consoles, but you can't play Halo 3 or MW2 on an Orig Xbox can you? Yes, alot of people are having trouble but what they should do is download a full dump through Xellous's HTTP Web Menu, open BestPig's FreeBoot Toolbox and select custom patch. If you have a 512 you must disable the auto-detect option and pick your board manually. Click create freeboot, and around 80% it should open a freeboot folder, you just put the dashlaunch patch in the bin folder and then you use the flashinstaller in xexmenu to install the ini to your nand. works for me.

its so good to know that cod4 mw2 can be updated alone with the tu6 file in the cache folder. I knew that all the tuts said to also overwrite the default_mp.xex.(mine is in GOD format), since this rules out most of the problem, for me, i guess its down to forwarding port 30000 to pc (i had it to xbox) . but really, did anyone here actually get the patch working? I have not read of successful results yet.

Yes throughout this entire topic people have been posting that it works(including myself) I'm sure if it didn't work or was a hoax we would know by now.

It works fine for me. As long as you have freeboot with dashlaunch 1.0 (launch.xex in flash, and i put the ini on hdd), the ping patch on hdd, the same title update, and your port 30000 forwarded (i connect my 360 to my laptop and give it an ip, subnet, default gateway and dns while forwarding the port to my laptop's ip, not using internet connection sharing either), in the 360's settings manually give it an ip, subnet, and gateway, it will work.

well ive got my laptop to 360 and bridged connections. kai says reachable. i am yet to try to forward the port to the laptop and not 360.

about the .ini file: what are your settings, I left default blank and had to add on [patches], is that necessary?

Don't get too excited. I tried to take my Jtag online (after I updated to freeboot) and the second it tried to connect during setup, I got a message saying it was banned for ToS violations. (I wanted to connect it so I could recover my XBL account and get some game updates, but oh well.) Your's could be banned just as fast.

1. You don't even need to bridge the connections. Just do what i said above and it will work
2. My default is set to launch freestyle, and x launches xexmenu, and no you don't need to add anything to patches

i've never put a [Patch] area in a launch.ini file

Just this:
[QuickLaunchButtons]
Default = LHdd:\Game\FreestyleDash.xex
BUT_X = LHdd:\Content\0000000000000000\C0DE9999\00080000\C0DE99990F586558

the min it booted FSD i was able to connect to games.

Just like ninja said use the Xellous dump.

There's a mini tut i did on page 10 that worked for me.

-=c

anyone have any experience with this, dash launch seems to only boot with my ini, to fsd, when launch.xex is on my usb disk. I have it in the nand installed with flash_installer as well, but that doesnt seem to work. I have the .ini everywhere.

Well, scratch that, all of my games have been giving me problems with just having the TU. Grr, I have to go and patch each one as I go now, royal PITA.
The two games I've had problems connecting with are Borderlands and Blur, both times the hosts had pings >200 so I guess that must've been it.
@Holyjewsus
The priority for Dash Launch is USB>HDD>NAND.

in my experience, having launch.xex on the root of my harddrive caused the box to freeze on bootup.
just need launch.ini on USB/HDD

launch.xex only on the nand with flash_installer.

i know this probably didn't help much but just my experience.

check to make sure your .ini's are all the same/accurate.

-=c

I don't even know whether launch.xex/launch.ini is needed for the Kxam.patch to work, as long as dashlaunch itself has been built into your freeboot image and you have the patch at HDD1/Kxam.patch.
All port forward info is available here http://portforward.com/
Choose your equipment,skip the ad, and after that right at the bottom is the Kai Link setup info

FINALLY, I got it to work!!! The prob was the port forwarding to pc and not xbox.
since i got 2 routers (adsl modem and linksys router), I just opened port 30000 onto the linksys router.
I bridged connection so the router indirectly assigns ip to my 360 automatically (and the port is open for all devices)
(note: tu6 is necessary in cod4mw2)

I have not tried any other game because no one is online.

anyway, thanks for the help, see you all on kai...

for me dash launch is not working. I can see the launch.xex on the flash and launch.ini on my root of my both internal and external drive. also its configure properly. holding X not booted to FSD. so clearly Dashlaunch not working. Can anyone shade some light??

deff works great

but the patch makes dash launch freeze sometimes

You shouldn't have to build a new image (especially if you had the nand option checked) And you will have to run the installer at least once or it(dashlaunch) won't be there.


It's always worth saving ur KV (they're in very limited supply and in the future you may be able to do some very cool things that have nothing to do with MW2 or lobbys) Either way it's important to have Xbox Live blocked in ur settings as once it's banned (only takes an hour or 3) it will modify ur nand (not as big concern nowadays) and if it keeps trying to log on post fixing ur nand u r console will go on untrusted list and that will cause u issues with new games that have you on their list..(there's a workaround but it's a massive pain in the proverbial)


Make sure when you do ur build you have nand checked, It will boot from nand, but without a drive of some description (with the actual app - fsd) and an accompaning .ini/and FSD to boot from it will default to NXE or worse.
It's always better to have a seperate .ini etc.. for each drive as dashlaunch doesn't like to traverse drives.

I've also noticed that dashlaunch DOESN't Mount UsbMU's properly like it claims to they just default to USB0 etc.. and having one plugged-in (even after boot) can stuff up ur .ini after the UsbMu gets mounted as a normal USB and enumerates the one ur trying to boot off. Doh'

Hope this helps/Dan

Can anyone confirm this? I have freeboot .32 and dashlaunch installed (i think) but have not inserted the launch.xex into the nand. I built freeboot with freeboot toolbox and had the custom freeboot box checked, and when the dialogue box popped up about me selecting cutom freeboot, I put the patch from dsahlaunch into the patch folder.

I am not able to join any game with ping over 30, I can see them in the lobby list, but I get a "connecting to Host..." countdown and then an error, I assume from the high ping.

any help is appreciated.

I have never had any success without launch.xex flashed to the NAND, so I presume--without going back and looking at the documentation--that it is a requirement.

Directly from the dashlaunch readme:
****
at time of this writing, this is ONLY compatible with freeBOOT 0.03x
releases built with the included patch set which expects launch.xex
to be installed to system flash.
****

So yes launch.xex must be in the flash for dashlaunch to work, and yes the ping patch needs dashlaunch to be working properly in order to work correctly. It doesn't need the launch.ini though but you should have one anyway.

installing launch.xex and launch.ini did it. thanks gang

Well I did say that I did not know whether it was necessary. Now we all know it is, doh!

And I stand corrected.

A question for you. This patch it works in console with jtag only? Or in all the consoles without jtag???

seeing as the only way to put it on and patch it, its for jtag only

Sorry for bringing up an old topic, but I have an RGH console and just installed xlink kai.. played a bit and everything was fine.. could it be that this patch isn't needed anymore? It could be that the guy who hacked my console already applied the patch, but I doubt it.

-edit-
If anyone else is ever wondering about the same thing - DashLaunch's 'pingpatch = true' does the job for you I read through dashlaunch's fix history before but I didn't notice that anywhere so I posted here..