All you do is run the dashlaunch updater, it will update the patches, install launch.xex and copy launch.ini from the HDD to the NAND. Because you have internal memory, you'll need dashlaunch 2.01 or above. However, if it were me i'd avoid using the BB internal memory because of the potential NAND corruption issues which keep poping up.

 

Is this teh same drive you were having the same issue with before in a rather long thread?

All you do is copy dashlaunch to a directory on the HDD, have launch.ini in the root of the drive and then run dashlaunch and it does the rest. Perhaps your Xenon has Dashlaunch 1.0 and your Jasper has 2.xx and it's causing issues as the format of the launch.ini has changed.

On all the X360's I have here, they ignore all the dashlaunch settings on the HDD if you boot with a USB memory stick inserted.

 

You shouldn't be using the internal memory of your Jasper unless you know how to reflash via USB or LPT. It's known that on occasion using the internal memory will corrupt the nand.

As for the issue with the HDD, i've no idea. I'd refer you to the suggestions from your previous thread. Personally I'd wipe the HDD, then start from fresh. Because it's a JTAG it doesn't need the layout of the drive as the retails so, meaning if you do that you can use the drives full capacity. Failing that, i'd swap enclosures.

 

Change LHdd to Hdd.