FSD or Dash Launch Problem

[beelicious]

Hi ive got a jtag jasper 256mb with usb external HDD on kinect dash, everytime i boot into FSD it crashes. Any one else have/had this problem? also got a Xenon with the same FSD and Dash Launch but with 120gb M$ that works fine (external usb problem?)

Have tried Dash Launch 2.06 and now using 2.07, reinstalled FSD umpteen times.

copy of my Dash Launch.ini :

[QuickLaunchButtons]
Default = Usb0:\default.xex
LBump = Content\0000000000000000\C0DE9999\00080000\C0DE99990F586558


[Settings]
pingpatch = true
contpatch = true
fatalreboot = true
regionspoof = true

Thanks

 

[J2G]

Make sure Freestyle dash is named >> FSD on the root of your USB drive and copy whats below see does that work..

[QuickLaunchButtons]
Default = Usb0:\FSD\default.xex
LBump = Content\0000000000000000\C0DE9999\00080000\C0DE999 90F586558


[Settings]
pingpatch = true
contpatch = true
fatalreboot = true
regionspoof = true

 

[big_ted]

normally if a default.xex is on the root of the usb you'll boot e71. it needs to go in a directory.

Ted

 

[beelicious]

Nope still no luck it dont atempt to boot into fsd now. Could it be something to do with kinect sensor? :s. The wierd thing is it booted into fsd when i had a dongle in front usb, but the problem is i need kinect,usb hdd and wired controler pluged in. Any other ideas? or any one else solved this problem with simerler set up?

Thanks

 

[J2G]

No matter where you plug it in it will still show as Usb0, everything got to do with fsd should be in one folder on the root of your Usb drive and named FSD the launch.ini on the root aswell try leaving out the 0 on Usb so it looks like this >>>.

[QuickLaunchButtons]
Default = Usb:\FSD\default.xex
LBump = Content\0000000000000000\C0DE9999\00080000\C0DE999 90F586558


[Settings]
pingpatch = true
contpatch = true
fatalreboot = true
regionspoof = true

All that done rerun the dashlauch installer reboot see does that sort it if not im out of ideas unless the kinect is doing something to it plug it out see does it boot to FSD if it does you know you have a conflict then...