Print

[hazed69]

is there anyway to tell if my nand already has dashlaunch before trying to build another nand

[Aldanga]

If you have freeBOOT 0.032, you have dashlaunch. It's built into v0.032.

[hazed69]

ok good!
why cant i get this thing too default freeboot?

[Aldanga]

[hazed69]

QUOTE(hazed69 @ Aug 2 2010, 11:23 PM)

ok good!
why cant i get this thing too default freeboot?

 (IMG:style_emoticons/default/uhh.gif) freeboot lmao i mean Freestyle

[Aldanga]

Have you used the flash installer and flashed launch.xex and launch.ini to your HDD?

[hazed69]

i have flash installer on thr root in a folder name flashinstaller and in there i have the launch exe and the launch ini plus i have the ini in the root of hdd and i went ahead and flash them to my nand wich i see it in under flash folder


[QuickLaunchButtons]
BUT_X = LHdd1:\XeXMenu\default.xex
BUT_B = LHdd1:\XM360\XM360.xex
Default = LHdd1:\Freestyle 2.0\default.xex

[f0xrolder]

so my jasper 16mB console with Freeboot 2.0.9199 installed should work also?? Or not???

xexmenu is a nxe or god container file in 000000000000\code9999\00080000\xexmenucode etc.. on my console show up in game tab as a demo and doesnt run from an xex and i have fsd2 alpha on the external usb hdd at \fsd2 alpha\default.xex

tried to get it to boot directly to fsd2 alpha by editing the launch.ini file and flashing that and launch.xex to the nand which it did with no luck still goes straight to xbox dash, and have copied both launch ini and xex to the root of the 60GB hdd and external usb hdd with no luck either.

First attempt
[QuickLaunchButtons]
BUT_X = Usb0:\fsd2 alpha\default.xex
Default = Hdd1:\Content\0000000000000000\C0DE9999\00070000\FreestyleDash

second effort
[QuickLaunchButtons]
BUT_X = LUsb:\fsd2 alpha\default.xex
Default = LHdd:\Content\0000000000000000\C0DE9999\00070000\FreestyleDash

Any ideas any1??? Maybe changing default to the xex instead of the container might work. Didnt muck around with it anymore tho as i was hoping for some insight.

[WarriorSan]

[c0z] released an update for Dash Launch v1.0 for jasper BB 256mb / 512mb users so they can finally safely use their internal memory. Please note that you first backup everything you got on the internal memory because after the re-flash it’s getting formatted...

From the readme:

QUOTE

Changes from dash launch 1.0 patch set:
-Jasper big block machines need only apply
   - fixes flash MU corruption issues

   *note that flash mu is contained in:
   blocks 0x10 thru the end of block 0x15B
   blocks 0x200 to end of NAND
   
   in small block notation (for nandpro) this is:
   blocks 0x80 thru the end of block 0xAD8
   blocks 0x1000 to end of NAND

   if you update at some point in the future, keep this in mind.

[cOz]

This post has been edited by WarriorSan: Aug 7 2010, 12:48 PM

[dschu012]

QUOTE(hazed69 @ Aug 3 2010, 01:03 AM)

i have flash installer on thr root in a folder name flashinstaller and in there i have the launch exe and the launch ini plus i have the ini in the root of hdd and i went ahead and flash them to my nand wich i see it in under flash folder
[QuickLaunchButtons]
BUT_X = LHdd1:\XeXMenu\default.xex
BUT_B = LHdd1:\XM360\XM360.xex
Default = LHdd1:\Freestyle 2.0\default.xex

Don't flash launch.ini to nand. When I did I could never get stuff to boot. You just need the one launch.ini in the root of your hdd.

[hazed69]

QUOTE(dschu012 @ Aug 7 2010, 05:24 PM)

Don't flash launch.ini to nand. When I did I could never get stuff to boot. You just need the one launch.ini in the root of your hdd.

well do I need to reflash my NAND or can I just delete ini and launch exe in the flash folder?

[finalman]

QUOTE(WarriorSan @ Aug 7 2010, 12:36 PM)

[c0z] released an update for Dash Launch v1.0 for jasper BB 256mb / 512mb users so they can finally safely use their internal memory. Please note that you first backup everything you got on the internal memory because after the re-flash it’s getting formatted...

From the readme:

Changes from dash launch 1.0 patch set:
-Jasper big block machines need only apply
- fixes flash MU corruption issues

*note that flash mu is contained in:
blocks 0x10 thru the end of block 0x15B
blocks 0x200 to end of NAND

in small block notation (for nandpro) this is:
blocks 0x80 thru the end of block 0xAD8
blocks 0x1000 to end of NAND

if you update at some point in the future, keep this in mind.

[cOz]

Where do we get this from? I can't find it on xbins.

[cory1492]

QUOTE(hazed69 @ Aug 7 2010, 12:35 PM)

well do I need to reflash my NAND or can I just delete ini and launch exe in the flash folder?

just put one on your hdd or on your usb, it uses whichever it finds first with flash being the last place it looks.

[danthaman673]

QUOTE(f0xrolder @ Aug 3 2010, 10:37 AM)

so my jasper 16mB console with Freeboot 2.0.9199 installed should work also?? Or not???

xexmenu is a nxe or god container file in 000000000000\code9999\00080000\xexmenucode etc.. on my console show up in game tab as a demo and doesnt run from an xex and i have fsd2 alpha on the external usb hdd at \fsd2 alpha\default.xex

tried to get it to boot directly to fsd2 alpha by editing the launch.ini file and flashing that and launch.xex to the nand which it did with no luck still goes straight to xbox dash, and have copied both launch ini and xex to the root of the 60GB hdd and external usb hdd with no luck either.

First attempt
[QuickLaunchButtons]
BUT_X = Usb0:\fsd2 alpha\default.xex
Default = Hdd1:\Content\0000000000000000\C0DE9999\00070000\FreestyleDash

second effort
[QuickLaunchButtons]
BUT_X = LUsb:\fsd2 alpha\default.xex
Default = LHdd:\Content\0000000000000000\C0DE9999\00070000\FreestyleDash

Any ideas any1??? Maybe changing default to the xex instead of the container might work. Didnt muck around with it anymore tho as i was hoping for some insight.

 Try renaming the fsd2 alpha folder to: FSD2Alpha (no space) also watch cases and save in UTF-8 also cut and paste ur paths, they seem wrong for freestyle, get ur default working off the HDD with something like xexmenu using the example.ini and then use flash installer to flash ur newer .ini Also if the dashlaunch patches were incorrectly applied it can cause issues, If ur using bestpig's toolbox then I find checking then Nand option worx best (Don't forget to flash ur UTF-8 .ini from the flash installer folder afterwards)

Good to hear the fixed BB, no if they could only fix all the other probs we have with dashlaunch eg; USBmu's being mounted as USB (so .ini's fail when friends bring over their profile's on a USBmu etc.. - Huge pain) And that thing it does on several of my personal consoles where it goes back to NXE when it's not meant to anbd then wont boot unsigned code eg; Can't launch Xexmneu 1.1 is the error I get when trying to go back to what
I was doing. (Not using any buttons only default

It's an awesome bit of code, I just wish they could iron-out the faults (there's more ,not all 100% casued by Dashlaunch eg; strange shutdowns and other stuff - But I have to go cook dinner...)

Brgds/Dan

This post has been edited by danthaman673: Aug 8 2010, 12:26 PM

[cory1492]

QUOTE(f0xrolder @ Aug 2 2010, 07:07 PM)

[QuickLaunchButtons]
BUT_X = LUsb:\fsd2 alpha\default.xex
Default = LHdd:\Content\0000000000000000\C0DE9999\00070000\FreestyleDash

Any ideas any1??? Maybe changing default to the xex instead of the container might work. Didnt muck around with it anymore tho as i was hoping for some insight.

There is a good reason why samples were included... you're forgetting the enumeration number on USB

CODE

; HDD use: LHdd:\
; USB use: LUsb0:\ LUsb1:\ LUsb2:\
; Memory Unit use: LMu0:\ LMu1:\
; USB memory unit partition use: LMuu0:\ LMuu1:\ LMuu2:\

danthaman is right too, I don't think spaces in folder names or file names is 'proper' for the OS.

QUOTE(danthaman673 @ Aug 8 2010, 05:22 AM)

Good to hear the fixed BB, no if they could only fix all the other probs we have with dashlaunch eg; USBmu's being mounted as USB (so .ini's fail when friends bring over their profile's on a USBmu etc.. - Huge pain) And that thing it does on several of my personal consoles where it goes back to NXE when it's not meant to anbd then wont boot unsigned code eg; Can't launch Xexmneu 1.1 is the error I get when trying to go back to what
I was doing. (Not using any buttons only default

It's an awesome bit of code, I just wish they could iron-out the faults (there's more ,not all 100% casued by Dashlaunch eg; strange shutdowns and other stuff - But I have to go cook dinner...)

Brgds/Dan

See above, the MU partition on a USB stick is NEVER mounted as USB, they each have individual mount points - the problem is, when you have more than one usb device, they don't enumerate per plug socket but basically "whatever I find first is Mass0" (and thus LUsb0/LMuu0) regardless of which socket it is in or whether it was plugged into the machine ever before (and the same is true for MU, not the usb kind though regular MU still are USB devices) - it has something to do with the way usb hubs and such work under NT kernel and really should be up to the end user to sort (ie: plug in the extra/abnormal usb stick AFTER booting the machine.) The same goes for bringing foreign usb sticks with launch.ini on them too, no program can be a mind reader.

As to going back to NXE "when it's not meant to" - usually a disk is involved - especially if it's spun down to idle (ie: playing NXE installed game, leaving a disk in while playing a GOD), I believe it was stated that this is a known bug though I've never seen any issues with running xexmenu con or whatnot after, and I've caused it to happen on purpose a few times by messing with the dvd tray.

Shut down reboots occur on unhandled exceptions. Normally your machine would just freeze, the freeze has little or nothing to do with dash launch (but it is kinda nice to not have to get up to force the machine to turn off.)

This post has been edited by cory1492: Aug 8 2010, 02:19 PM