Print

[seaweavil]

QUOTE(budtoka420 @ Apr 10 2011, 03:57 PM)

run the 2.21 installer on your jtag and when it asks you to change settings say yes and say no when it asks you to block microsoft dns aggressively

Hmm I don't get that option when I run the installer? It just gives me the option to flash the freeboot updates the first time and then the second time it tells me I already have the updates.

Is it possible that because I am still on 12611 dash that I don't get that option menu? Do I have to have 12625?

This post has been edited by seaweavil: Yesterday, 10:09 PM

[Aldanga]

You need to have launch.ini on one of your storage devices. If it doesn't exist it won't ask you to change settings.

[seaweavil]

QUOTE(Aldanga @ Apr 10 2011, 04:18 PM)

You need to have launch.ini on one of your storage devices. If it doesn't exist it won't ask you to change settings.

Ok thanks. I will just revert to my old nand and an earlier version then. Last time I messed around with the launch.ini I had all kinds of problems.

Actually I went ahead and tried it. Worked out pretty well. I just with there was an option to have that installed without a launch.ini file. Just makes me nervous I guess after the bad experience I had previously with it. Thanks for all the help guys!

This post has been edited by seaweavil: Yesterday, 10:53 PM

[schubi]

do xbox1 games work with this version of dashlaunch ?

[Aldanga]

They work for me.

[Aldanga]

Yes.

[ade2]

QUOTE(Velocimodz @ Apr 13 2011, 07:05 AM)

I'm having issues with this new version, everytime I do the update, it appears to write all 3 files to flash, but it never loads the correct options. I have this in my .ini on the root of USB.
So it should be loading from Hdd:\FSD 2.0\default.xex by default, I have checked the shortcuts a million times and it is definitely correct and the same as I always use. It only boots to NXE. Even if I have a USB hdd with FSD 2.0 on it and hold X during startup, it still only boots NXE. I can run the shortcut manually thru xex menu so that is fine also.

Tried first on a Jasper and it corrupting the launch.ini file, after each dashlaunch update the .ini would be an empty file, all settings disappeared.

Can anyone think of what could be wrong here? Its got me stumped.

I would try without a space in the folder name, if you haven't tried that...

[Velocimodz]

QUOTE(ade2 @ Apr 13 2011, 01:27 PM)

I would try without a space in the folder name, if you haven't tried that...

Yeah I have tried that and it worked. Strange that it never happened on other machines before tho.

Thanks buddy.

Can you confirm it allows games that require a higher dash 12655 to play on a 12611 freeboot? I haven't got any new games to try it with, but I presume thats what the hashcheck removing is about?

[Sturmie]

I updated to 12611 back a few months back and use XexMenu 1.1 to only play games from the hard drive...if i want to play something new, like YooStar 2, do I need something like this new version of Dash Launch?  I apologize for the newb question, I obviously don't play my JTAGGED system that often and have been reading up on Dash Launch...still trying to figure out if I NEED it or not.

Thanks...Sturmie

[korruptcow]

I downloaded 2.21 from the usual xbins when i extract the folders in the installed directory i only get default.xex usually there is a media folder and a files folder in there too? Was this changed in this version or do i have a dodgy version of the patch? i don't want to flash until i find out

[Aldanga]

That's all there is.

[drvsbsm]

When I ran dashlaunch 2.0 last week It upgraded me to 12625 now, For some reason this took me back to 12611 can some one explain so I can get back to 12625?  Some newer games require 12625 correct?

[cory1492]

QUOTE(drvsbsm @ Apr 14 2011, 07:57 PM)

When I ran dashlaunch 2.0 last week It upgraded me to 12625 now, For some reason this took me back to 12611 can some one explain so I can get back to 12625?  Some newer games require 12625 correct?

Dash launch doesn't upgrade or downgrade your firmware... it updates itself and the patch set based on what firmware you're console is on. If it really went from 12625 to 12611, I'd be looking under the bed and such for the "evil reflashing elves" that used to stick to just stealing socks...

QUOTE(toybox @ Apr 15 2011, 09:08 AM)

Without Dash Launch it works just fine, but after installing i receive " fatal crash intercepted " error
until my console blacks out. It still reacts to the controller but repeats " fatal crash intercepted ".

If you could set the dumpfile option in the ini to something like
dumpfile = Hdd:\crashlog.txt
it will dump the crash causes to that file in the root of the partition with /content folder on it, which could (maybe) help to find the issue. After doing that, you can also try
exchandler = false
And see if it improves the behaviour. Keep in mind, the ini file has to be somewhere it can be found at console boot up, and if a USB HDD is causing issues that won't be the place to put it.

[toybox]

LOG:

CODE

------------------------------------------------------------------------
TIME: 12:00:35 GMT Tue, Nov 22, 2005
------------------------------------------------------------------------
Unhandled Exception (last chance):
The thread tried to read from or write to a virtual address for which
it does not have access.
------------------------------------------------------------------------
Faulting Module Info:
    FullName       : \Device\Flash\xam.xex
    BaseName       : xam.xex
    PEName         : xamc.dll
    ImageBase      : 817E0000
    SizeOfFullImage: 00550000
    EntryPoint     : 81872100
------------------------------------------------------------------------
    EADDR: 0x8193612C
    ECODE: 0xC0000005
    EFLAG: 0 (cont)
    NPARM: 2
         PARAM 00: 0x00000001
         PARAM 01: 0x00000000
    CFLAG: 0x00000017
------------------------------------------------------------------------
Control Registers:
    MSR: 0x00009030 IAR: 0x8193612C
    LR : 0x8193611C CTR: 0x0000000000000000
------------------------------------------------------------------------
Integer Registers:
    CR : 0x24000088 XER: 0x20000000
    r0 : 0x0000000000000003 r1 : 0x000000007A07EEE0 r2 : 0x0000000000000000
    r3 : 0x0000000000000000 r4 : 0x0000000081C1E19A r5 : 0x0000000000000008
    r6 : 0x0000000000000065 r7 : 0x0000000000000008 r8 : 0x0000000081C1E193
    r9 : 0x0000000000000000 r10: 0x0000000081C23518 r11: 0xFFFFFFFFFFFFFFFF
    r12: 0x000000008193611C r13: 0x0000000080183000 r14: 0x0000000000000000
    r15: 0x0000000000000000 r16: 0x0000000000000000 r17: 0x0000000000000000
    r18: 0x0000000000000000 r19: 0x0000000000000000 r20: 0x0000000080065C10
    r21: 0x0000000081C1E184 r22: 0x000000000000000D r23: 0x0000000000000000
    r24: 0x0000000081C23178 r25: 0x0000000000000006 r26: 0x0000000000000008
    r27: 0x0000000081C1E193 r28: 0x0000000000000000 r29: 0x0000000081C231F0
    r30: 0x000000000000000A r31: 0x0000000081C1E19D
------------------------------------------------------------------------
Call Stack:
    0x8193612C (EADDR)
    0x8193611C (LR)
    0x819362E0
    0x81BC46E0
    0x81BC4CAC
    0x81BC4F74
    0x81B86C24
    0x81A3BC14
    0x81A25E28
    0x818D4BB0
    0x818D5470
    0x8188FE74
    0x818905A8
    0x81890828
    0x80065C3C
    0x8007548C
------------------------------------------------------------------------
Dump Done
------------------------------------------------------------------------

This keeps repeating. One Boot less than a minute > 2,5MB of TXT.

It seems i am not alone, i found a post at pastebin from a guest > http://pastebin.com/kGACp24G.

[toybox]

Ok... i found the problem ... nasty old ping patch was still on both Hdd's and caused the problem.

Removed > Problem solved