NXE2GOD

[dstruktiv]

#xeDev = #freexex

Wrong, XeDev = freexex - the trash that didn't contribute and caused drama.

Everyone in the team now has a purpose and is active whether it be coding, graphics or testing. Website is $#!t we know but we're all working on homebrew instead of the website. I'm going to try whip something up in my down time at work where I can't use the sdk...

So far really positive feedback about V1.0 - Although I was pretty certain it would fix all the issues I wasn't positive as I only have limited games to test with. Looks like it has indeed fixed everything though.

[Lush]

drama = poison

Keep up the great work team!

[dstruktiv]

Website has been updated finally lol it's not much but I just did it quickly in my down time at work, has a nice back end for donations and news etc.
http://xedev.xbins.org/

[Gazcoigne]

i installed NXE2GOD 0.1 on my xenon console when it first hit on my own hdd and it worked flawlessly.

i got a falcon XBR box, so decided to sell the xenon to a friend.

got a new 20gb hdd for him, formatted it clean, created new profile, and installed the 0.2 release same as before with ck3 hdd kit

upon reboot it is not shown in dashboard

then installed xexmenu 1.1, which worked great, and copied NXE2GOD over with that from usb, still no joy

tried also booting xexmenu from disc and loading it from there no joy

i can see the NXE2GOD file in the same dir as xexmenu (0000000000000000/C0DE9999/00080000/)

what am i doing wrong? do i need to clear cache or something?

[skel28]

Gaz, check your ftp settings, I had the same problem as you (after I made my settings active it worked then on my Jasper).

[Gazcoigne]

wow feel a bit sheepish now lol

if i look under the side title of games and demos both XEXMENU and NXE2GOD appear as game demos, but in the first screen you see when entering games library only XEXMENU appears

spent two hours copying files for nothing eeeuuurrrrr!!!!

why is that out of curiosity? both showed on the console before on a different hdd

strange!!

[locvez]

^^ I know how you feel, with a 2.5" 500gb hdd on my xenon i had nxe2god and xexmenu on the games library list so i could get em quick and xm360 in the "demos" list, now i've put in a 3.5" 1tb hdd (with external power source) and all i have is xm360 on my game library and xexmenu and nxe2god on the "demos" list 

nevermind, as long as it works, i can live with the quirks

[sandungas]

i can see the NXE2GOD file in the same dir as xexmenu (0000000000000000/C0DE9999/00080000/)

I have not tested, but...

I guess the problem is that both apps (NXE2GOD & xexmenu) uses the same path... and this path is hardcoded in the file (so we cant move them to another path)

C0DE9999 is the TITLEID (chosed by xexloader developers randomly... and used later on by xexmenu and other apps)
00080000 is the OFFERID (standard LIVE container)

An OFFERID folder cant have 2 executables files (the console will "hide" the one with the older datestamp)
A TITLEID can have different executables (but the executables must be different OFFERID)

------------------------------
The solution is to change the TITLEID with lefluffie of one of them (the edited app will need to be placed in another path)
An alternative solution... change the OFFERID with lefluffie of one of them (this way... both can be putted inside C0DE9999)


***All versions of xexloader & xexmenu has the same "incompatibility problem"... because all shares the same path (hardcoded when the file is created). This is why we cant have 2 different versions of this apps in the same HDD

[dstruktiv]

Then why do all QuickBoot shortcuts show up even though they use the exact same details (Title id/publisher/offer) and are stored in the same folder?  - Good theory though. NXE will list anything as long as the title id and content type match the folder structure.

NXE2GOD was purposely packaged in a demo container as while we're stuck with NXE it seems more logical to organise homebrew under demos and put full games (God containers and QuickBoot shortcuts) under Xbox 360 Games.

I also released it as a standalone xex on xbins though if you want to use ISO2GOD to make it in to a GOD container - Or cheat like QuickBoot does and simply take the existing demo package and hex edit at 0x344 to 00007000 instead of 0008000 (Might have to redo SHA1 after this I can't remember) then put it in C0DE9999\00007000\ - This way you can avoid having the .data folder.

[Crosseye]

I'm not sure if this is an NXE2GOD issue or a system issue, but I thought I might throw it by you to see. I have a 640GB hard drive in the MS shell to use. I installed xexmenu 1.1 from CD in its proper folder on the Hard drive and it works just fine. Then, I copied the Live NXE2GOD from USB using xexmenu to the same folder as xexmenu (C0DE9999-00080000). Now, I can install a game using NXE, but NXE2GOD fails to start from the hard drive with an error to reinstall the game (maybe it says download, don't recall). However, if I run the xex from USB, NXE2GOD works just fine.

Any suggestions? I think this may be a system issue, but I'm not sure why XBR runs fine otherwise if that's the case.

[neonpolaris]

First of all, brilliant work, dstruktiv. This program has worked like a champ since day one, I love it. However, recently I've noticed one quirk. I cloned one of my harddrives onto a new drive to use with my other console. (One JTAG, one RGH) Afterward, any games installed via NXE2GOD would fail to load (associated with the original console) whereas games installed via ISO2GOD still ran fine. I simply reinstalled the games via the dash from the discs and reran NXE2GOD and everything was fine. Is there anyway for NXE2GOD to strip this console specific information out of the container to leave the install more universal, or would this create some other problem?