JTAG How Can You Stop Dashlaunch Breaking Xexmenu On Jtag?

mcornbill

mcornbill

VIP Member
Jan 2, 2003
176
0
Birmingham, UK
Hi Guys

Ok so I've done a few jtags now and am still learning, but I have a problem everytime I install dashlaunch 2.22.

My usual jtag and software installation steps are as follows:

1. I use the CoolShrimp tool to create myself a Freeboot 13599 image and flash the NAND
2. I attach a standard Xbox 20gb hdd and put XexMenu 1.1 disc into the DVD drive
3. I copy over XexMenu to the hard drive
4. I load XexMenu and use ftp to transfer over all other programs (Freestyle Dash 2, Dashlaunch etc)

Now at this point everything will work fine. Standard boot into Freeboot, eject boot into Xell. However I don't want Freeboot to be the default dashboard, I want it to be FSD2. After reading around the forums I came across Dashlaunch 2.22, and how you can edit its 'launch.ini' file to assign what you want to boot as default. This is the only reason I'm putting dashlaunch on. So I assign FSD2 to be default, save the 'launch.ini' file in the root of the hard drive, launch the dashlaunch installer xex from the hard drive, run through the various options saying yes to everything and no to configure new options. Then after this the console successfully boots to FSD2 as default, Freeboot if holding down RB on the pad, just what I want.

But then trying to launch XexMenu from either FSD2 or Freeboot throws a 'Fatal Crash Interception' error. I never get any of these errors if I don't install dashlaunch. I've read threads on how dashlaunch can break XexMenu, but still none the wiser with how to fix it. In fact, if there's another way of having FSD2 as my main dash and Freeboot as the secondary one, without having to install dashlaunch I'll take it!

Sorry if it's a lengthy one but I'm a stickler for detail! If anybody can help I'll be sending good vibes from Brum :)

Cheers
Mark
 
mcornbill

mcornbill

VIP Member
Jan 2, 2003
176
0
Birmingham, UK
Hi frazzeld

Nice one for the quick response.

Just been reading Johhny2good's tut, I note there's a dashlaunch 2.23 with a bug fix for FB 13599. Maybe that was my problem as I've been using 2.22? But I'm pretty sure I tried this with a FB 13146 dash and had the same problem.

With the dashlaunch install I say yes to everything but not to making new settings, the last question it asks you I believe. Then yes I have this ini file:

Code: 
; launch.xex V2.0 config file
; parsed by simpleIni http://code.jellycan.com/simpleini/
; currently supported devices and paths:
; internal hard disk    Hdd:\
; usb memory stick      Usb:\
; memory unit           Mu:\
; USB memory unit       UsbMu:\
; big block NAND mu     FlashMu:\
; CD/DVD                Dvd:\     (not recommended to use this one)
; buttons can point to any xex, or any CON with default.xex in it on any of the above devices
; note that Right Bumper is ALWAYS default to return NXE
; if you want to assign an additional one, use the path Sfc:\dash.xex ie:
; BUT_A = Sfc:\dash.xex

; example entry
Default = Hdd:\fsd2\default.xex
[QuickLaunchButtons]
BUT_A = 
BUT_B = 
BUT_X = 
BUT_Y = 
Start = 
Back  = 
LBump = 
; Default is what loads when you hold no buttons
; leave this blank if you want NXE as default
Default = 

; at boot time, default can be overridden based on how the console is turned on
; if you start with wired/wireless/IR guide button, this item if existing will be used instead of default
; note that the Guide item is ALWAYS overridden by option: remotenxe = true
Guide = 
; if you power on with the button on the front of the console, this item will be used instead of default
Power = 

; example plugin entry
; plugin1 = Usb:\plugin\aplugin.xex
[Plugins]
plugin1 = 
plugin2 = 
plugin3 = 
plugin4 = 
plugin5 = 

[Settings]
; if true, brining up miniblade in NXE and then pressing Y will cause launch.xex to relaunch for you
; note you must release Y button then press desired QuickLaunchButtons after or use default item
; if not present default is TRUE
nxemini = true

; if true ping limit will be removed for system link play (thanks FBDev!)
; if not present default is FALSE
pingpatch = true

; if true (most) xbla will no longer need yaris patching (thanks mojobojo!)
; if not present default is FALSE
contpatch = false

; Normally when a fatal error occurs the xbox will just freeze, setting this to false will cause a reboot or powerdown
; setting to TRUE will also disable the unhandled exception filter which tries to intercept recoverable unhandled exceptions with exit to dash
; if not present default is FALSE
fatalfreeze = false

; when fatalfreeze is set to false, setting this to true will cause the box to reboot (hard reboot), setting it to false will instead have the box shut down
; note that this option does NOTHING when fatalfreeze is set to true
; if not present default is FALSE
fatalreboot = false

; when fatalfreeze is set to false and fatalreboot is set to true, setting this to true will cause the box to reboot (soft reboot) the way it was intended to
; ONLY set this to true if using blackaddr's reboot fix for SMC, else on reboot you will get E71 and corrupted dash/video/etc settings
; note that this option does NOTHING when fatalfreeze is set to true
; if not present default is FALSE
safereboot = false

; when set to true, it is possible to hold RB when launching a game to have the region that the game gets from xam spoofed
; if not present this is set to FALSE
regionspoof = false

; when regionspoof is true, you set your region here in hex, for examle devkit would be region = 0x7fff
; if not present but regionspoof is set to true, this is set to 0x7FFF
region = 0x7FFF

; when set to false, ejecting a dvd video or game returns you to your default item, set to true to auto exit to NXE
; if not present this is set to FALSE
dvdexitdash = false

; when set to false, using the exit item in an XBLA game returns you to your default item, set to true to exit to NXE arcade menu
; if not present this is set to FALSE
xblaexitdash = false

; when set to true, using miniblades system setting options will not exit to NXE
; if not present this is set to FALSE
nosysexit = false

; when set to true, miniblades will not appear... ever (requested as child saftey measure)
; note that using this option overrides everything in dash launch that relies on miniblade exits to function
; if not present this is set to FALSE
nohud = false

; when set to false, xbox will be capable of finding system updaters
; if not present this is set to TRUE
noupdater = true

; when set to true,  dash launch will put all debug strings out to uart
; if not present this is set to FALSE
debugout = false

; when set to false, dash launch will not attempt to handle last chance unhandled exceptions
; if set to false, exceptions will also not be dumped to the dumpfile
; if not present this is set to TRUE
exchandler = true

; by default this only dumps to UART, setting a file here will cause unhandled exception info to be dumped
; as text to a file. Same path restraints as the quick launch buttons.
; if exchandler is set to false, this option does nothing.
; note that this uses the first drive of the class found, so if you use usb: and have more than one usb device
; it may wind up on any of the usb devices depending on which was enumerated first. The path for the file is only
; checked on boot, so the device must be present at power on and at crash time for this to be effective
; ie: dumpfile = Usb:\crashlog.txt
dumpfile = 

; this value sets the number of times that buttons are checked for on bootup, as well as how long it checks for buttons
; and thus extends the length of time the boot animation will be displayed onscreen
; 0x5A is approximately 6s window for button detection, 0x2A approximately 2s - if set too short auto profile login breaks
; if set too long other wonky things happen
; note this value is interpreted as hexidecimal, valid range is 0 to 0xFFFFFFFF
; if not set this value will be put to 0x2A (42)
bootdelay = 0x2A

; if set to true, this will block the console from resolving LIVE related dns
; if not set this value will be TRUE
liveblock = true

; if liveblock is set to true, this will block the console from resolving all MS related dns
; setting this to TRUE will also block apps like freestyle from accessing things like cover images
; *** note that if NO INI is present for launch.xex, this is set to TRUE
; if not set this value will be FALSE
livestrong = false

; when set to TRUE the X (guide) and power button on IR remotes will cause the xbox to boot to NXE instead of default item
; note that powering on with the windows/start button automatically goes to NXE's media center now regardless of how this is set
; if not set this value will be FALSE
remotenxe = false

; all comments and fields in this file are optional, you can remove anything you don't need - section headers []
; are required for any used options under the section

; sorry for any double negatives :p

; njoy, cOz
Cheers
Mark
 
Martin C

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
I didn't think Dashlaunch 2.22 supported 13599?

v2.22
- resolving 'localhost' when the router forwards it to the internet or there is
no network at all... bad idea game devs... fixed (Yars', maybe others)
- button handler now more reliably removes Y and A mishandling when held on
miniblade exits
- added new note to readme regarding update prompts and avatar data missing
- hopefully extracted new games are now working fine, instead of GOD only
- potential bug corrected in 12611/12625 patch sets
- add 13146 compatibility
- all patch sets updated to fully remove xex bound checks (ie: default.xex
on root of USB causing E71)
- "remotenxe" option added to ini(thx adihash!)
- windows button on remote always boots to NXE/media center now(thx adihash!)
- added "guide" and "power" path options to set boot time default override
- changed kxam.patch, first .long must be the kernel version the patches match
- added a check to kxam.patch data to abort on invalid address
- added "nohud" option
- added installer check to verify at least the 1BL segment of patches before
installing, will re-ask and warn of possible corruption/brick
Click to expand...
Nope - thought so!
 
mcornbill

mcornbill

VIP Member
Jan 2, 2003
176
0
Birmingham, UK
Martin C said:
I didn't think Dashlaunch 2.22 supported 13599?



Nope - thought so!
Click to expand...
No I just noticed that tonight Martin, but as I mentioned before I'm pretty sure I tried this with a 13146 image and still had the same problems.

I am going to flash the nand again and start from scratch tomorrow using Johhny2Good's tut and new dashlaunch 2.23, hopefully all will be resolved then.

Cheers
Mark
 
You must log in or register to reply here.