Hold on a second
You have a JTAG hacked xenon and it works wonders other than probably being so noisy it is not funny.
You got a new Jasper that is not JTAG hacked
Your "xenon" hard drive is in fact a 500 gig drive and will not work in the Jasper- if the Jasper is not hacked then it is pointless trying as 360 hard drives are not locked but they do need to certain types and "hacked" even then. At this point in time there are no official 500 gig drives so
If your new Jasper is JTAG hacked (I take it your very last post, #53 in this topic, means you tested it out with a working albeit regular/small hard drive) then we have an actual problem, ignore update folders as that means nothing here.
To answer your other question and lead the hunt for solutions we have about 3 main ways of auto booting something-
1 is to fiddle with the options and have it boot of CD and jump to something else (part of the dash).
2 is to abuse a jumper containers thing.
3 is the easiest, most versatile/useful and for those reasons most common (especially as of the last few months now patches are made/based around it) is to use something called dashlaunch. Most current guides include it and any JTAG hacker that keeps up with things (arguably any that is doing a good job) will include it with one they send out.
Dashlaunch however had a major version bump and several tweaks not so long ago (that your Jasper probably was bundled with) and that included some ini file tweaks and bugfixes which may have caught you out here. Similarly if it has some patches they might be for XBR or pre 9199 (doubtful but we are trying things) and that will cause a crash as you have probably just overwritten useful/critical parts of the memory.
To decide what launches dashlaunch uses an ini file (more on that in the package which you can find on xbins) which can be found in one of 3 places, in order of which one gets read first you have
USB drives
Hard drives
Onboard flash
Various NFOs and useful data on the features, functions and fun of dash launch
http://www.xbins.org/index.php?action=sear...p;Submit=Search
Most people are pointed towards the USB option as it is easy enough to rip out a USB stick if someone fails to work properly. Hard drives can be tricky to access if you have hosed up the ini on that (which is nice to have a USB fallback) and flash is for those that swap hard drives and know what they are doing.
Step one (that might not need any more steps) would probably be to grab the dashlaunch installer (2.0 brought a nice 360 side installer you can run rather than fiddling with and flashing NAND images- grab the 2.01 version though) and install that on both 360s. That might solve you problem but do have a USB flash drive (you can use a real hard drive if you really want) to hand so you can pull things back and sort things out and similarly if your xenon is older it might cause the same issue as you are seeing now (good news if it is as that means fixing is as simple as deleting a file).
Next we mess around with ini files- the nfo and downloads have examples, formats and the like. I would build a new one myself but try the other stuff first before we have to start fiddling around with things.
Option 2- you find an old official hard drive and kick the 500 into an external caddy/enclosure (you can pick them up for about $10 USD and done properly you can probably even power it from USB, you can probably shift the old one if it is official for about $10 as well if you wanted). It will probably never work in an official xbox and hacked 360s are not fussy about where their data comes from not to mention it is even easier to fiddle with than FTP (although that is still an option). You will probably have to change the line in the ini file saying HDD to USB though and maybe reinstall freestyle dash (of fiddle with FSD's ini/config) files depending on how it set itself up- the 2.0 line probably as of next version/release being a good reason to jump up)
