Search the Community

Hello all! here is my Softmod Tutorial...! Originally made in 2006, uploaded to torrents, updated and reborn in 2018 as an OGXbox.com Exclusive! anywhore... its written in an easy to follow "noob-blog-style" just in case you are wondering why its so lame... UPDATING FILES FOR DOWNLOAD!! also additionally here are some essential xbox tools for modding/softmodding that are extremely hard to find these days due to most xbox scene sites and forums being dead. I have had them for over 12 years on a unused backup drive. UPDATING FILES FOR DOWNLOAD!! As always all files have been scanned for security threats by VirusTotal.com to rule out any contamination, with the exception of one false-positive in "Xplorer360 v0.9 Beta 6.zip". ** Keep in mind that these tools were made on and for xp/7 32bit windows, they may or may not work or work properly on 32 or 64 bit win 7/8/10, I recommend win xp/7 32bit virtual installation via VMware or virtualbox. Enjoy!

hey everyone i did a search and couldnt find what i was looking for, but i have a chipped 1.4 xbox and just upgraded the hdd to a 1tb sata and my F drive is supposed to show whatever its supposed to show i cant remember the number right now maybe 900gigs or something, anyway unleashx only shows 123mb for F and yes i did combine the F and the one below it to make it the biggest and it shows up correctly in xbox partitioner but not unleashx, is there a fix for this?

Hello everybody I am new here and new with Xbox at all i just get xbox crystall ( belive its 1.5 or 1.6 have no idea how to check it without opening) and i thought that i wana softmoded it (for a start) my colegue said i gona find help here so i try can annybody give me some clues how to check is my xbox 1.5 or 1.6 or 1.6b how to start ( i found that i need a special cable for usb stick and splinter cell game for special save) is that the only one way to soft mod? it so many diferent videos (i am not a lazy i star reading about it seen some video but hope maybe sb here give me a helpfull hand) Thanks.

Hi. I’m new to the community. I’m KaRMiG, from dominican republic. retro console enthusiast, I hope to gain a lot of friends and contribute to these forums in any way I can. thanks for reading!

hi i just bought a xbox that was soft modded with soft mod delux v3 and im trying to open up in original xbox dash board but theirs nothing their givers me a code 21 can any one help me i dont know where to start with this

Hey everyone, just recently got back into console modding after not touching a console in 10 years. Back then I primarily messed with 360's for my friends and anyone willing to pay me. Now I am more interested in building for myself to have "The Ultimate System". Excited about learning how the scene has developed over the years and finding this community. I assume like most here, I am a gamer. I can't seem to stop playing EverQuest 2 (13 years) and I play various shooters and single player "play through" games. In time I am sure I will have loads of questions and will look for feedback on ideas. Thus far I have 3 OG Xboxs and have TSOP'd one of them but havent really done much else. Glad to be here. Happy Modding!

Hello Folks, I try to intsall a XBIT 1.5 Chip in a 1.6b console. I was having a pretty bad time, since most of the information is gone due to forums and websites are not available in 2018 anymore... But thanks to the wayback machine, I managed to get some information about the installation process of the chip. Well, it looks like that the chip is/was only compatible to v1.0 to 1.5 and the 1.6 revision was not out when this chip was released (I've read somewhere, that there is a 1.6 adaptor board). Anyway, thanks to google, I found out that it should be possible to use that chip in a 1.6 console, but I'm unsure if they used the 1.6 adaptor. After rebuilding the LPC port, I installed the chip as usual (Double checked the pinouts from thechip and the LPC port), left d0 unconnected since I've read, that this is not necessary on 1.6 consoles and performed a LFRAME cut. I flashed evolution-x m8 1.6b bios to the chip with a virutal installation of windows xp (the softwate really sucks and won't work on WIN10...) Well, all I get is the christmas light (Console turning on and off 3 times and flashes red/green) without any video signal. If I bridge the LFRAME signal with tweezeers, the console boots as usual. This either means, that either the connection between the console and the chip is wrong or the chip is broken and I don't know how to find that out. I tried multiple thing, like reconnectnig the LFRAME, soldering in D0, used the 1.5 pinout for soldering, used the 1.6 soldering (but without the adaptor). At the time, I think the chip is broken, because flashing works, but validating the files gives me an error. As said before, I read on a german forum, that you can actually use any not 1.6 compatible chip with a 1.6 console by cutting the LFRAME and not connecting the d0 point. Won't work for me Has anyone some tips, help, suggestion for me? Thanks in advanve!

Hi everybody, first time here in SO long. I've had a modded Xbox since 2003 which I just turned back on after I heard out about the clock capacitor problem. Mine was ok (I was able to remove it and clean up alright) but having it back on I've found the hard drive to be quite loud and maybe not running so great. I wanted to replace the hard drive but I'm not sure if my old Chameleon modchip throws a wrench into the tutorials I've been looking at. If possible the method of hotswapping the DVD drive with the new HDD and cloning the original drive seems easiest. Any suggestions before I start fumbling through this are very much appreciated! And I have all the stats on my current setup if needed. Thanks so much for the help!!

Picked up a $5 Xbox off of local buy and sell site in Ontario Canada. Got the Xbox working notice it had a modchip got the modchip working it was a xenium chip.. when I was in the mod chip options I noticed that there was a bunch of skins five in total. I contacted a few of my friends who told me that these are very hard to come across some may even say rare. So now I upload to everyone in the forms here. Please download and enjoy these beautiful hard to find skins. And please share and pass these around. Thank u Frank XeniumOS skins.7z

Looking for a X3 LCD front panel. What's out there? Message me if you have one available. I do have some trades available and paypal. Located in New Hampshire, United States.

Ok so I feel like XPR would be fairly straight forward if I could get XPR Express to work in windows 10. In my windows XP VM, i got it to extract an XPR, but compiling no. I didnt mess around or read up too much on it though. Now, for XMV, I recently found this thread on xbox-hq with a promising program. However, I ran a virus total on the program and it came up as like 8/60 positive for viruses. I also ran it through an online sandbox, and what it did, didnt seem malicious. Does anyone out there have an easy method for creating XMV videos and extracting/compiling XPR files? I would really like to get everything working on windows 10. I hate VMs. XMV program i am talking about. The "ANY2XMV.7" file is linked close to the bottom in a mediafire link http://www.xbox-hq.com/html/postt27126.html Virustotal results https://www.virustotal.com/#/file/f148339ea9e4e59e15b58ab33fee3ef9842cb9813c7fc1598d104f19eab6bf45/detection Sandbox Analysis https://www.hybrid-analysis.com/sample/f148339ea9e4e59e15b58ab33fee3ef9842cb9813c7fc1598d104f19eab6bf45?environmentId=100

I recently acquired an Xbox with this modchip. I would like to reuse it another Xbox but cannot seem to find any info on it. I am guessing its a Team Xecuter model.......Anyone have a link to a tutorial for install and flashing?

Only recently ive been looking at this manufacturing proces part where they get the kernel on the motherboard. "our" Blake Clements @OGXbox Admin linked me at facebook to the following url: http://www.ogxbox.com/archive/xboxsecurity.html look at the Modchip part. It states that But I do not know if this is said based on the observation mentioned or based on internal Microsoft or flextronics manufacturing personal. Blake also said that: So, the LPC port was used for programming? A bed of nails (pogo pins) should and probably be used to connect the write enable pins on the motherboard to enable the flash writing of the then onboard tsop. I do not know for sure if this is posible but I rather for now asume it was. because we cant flash tsop today whne the xbox has been booted from LPC (modchip boots can only flash modchip, not the tsop, even of you remove the modchip prior to flashing) Connecting to lpc and connecting the write enable lines using pogopins could be done, altho I dont know how they would write to flash from LPC. the MCPX doesnt allow flash write in a LPC boot right? maybe a unkown mode? anyway, pure onboard tsop writing by connecting to the tsop directly would be a pain, but posible with fine pitched pins. not sure if the board would allow that with the mcpx on the same wires. All logic I can come up with is that MS would send their kernel to the tsop manufactorer and let them preprogram all tsops before soldering. then at the factory MS could use a bed of pogopins and a "recovery disk" to install a newer kernel if they wanted as long as the xbox booted from tsop. any other sources or interviews that claim or verify either side are welcome. movies and pictures of this proces too. most details I know came or will be added to: http://xboxdevwiki.net/Manufacturing_Process

Version 3.2500.1 CodeAsm REDACTED (Mail, pm or chat for more info) Tweeter twit CodeAsm_ 5-5-2015 [Incomplete version list Xbox, These are not the versions you are looking for.] [Some note removed or altered for internet storage savety. ] ???? XDK Alpha I SDK xxxxx ???? Alpha II Feb 2001, while mfc is 4/4/01 Mfc: 4/4/01 xxxxxxxxxxxxxxxxxxxxxx ???? XDK May 2000 xxxxxxx 3113 3146.2 Leaked (REC?)ISO 1-11-2000 November XDK 3146.3 ALPHA December 2000 XDK 15-12-2000 December XDK (also 16-12) ISO is 11.2 MB (11,810,816 bytes)xxxxxx xxxxx note*) 3223.1 ISO is 13.3 MB (14,024,704 bytes)xxxxxx 3224 February 2001 XDK and SDK , REC own 3306 3308 3331.1 March 2001 XDK and SDK xxxxxxxRecovery (nice side way dash) (7-03-2001 April XDK) 3332.1 LeakLeak video 01, REC, old style dash 3424.1 April 2001 XDK and SDK (03.01.01 - New for April XDK release) 3507 3514 3521.1 <<< Microsoft Xbox XDK (1.0.3521.1) (2001-05) > May 2001 XDK and SDK symbols 3604 3618 3633.1 Alpha SDK SYM (June 01) 3722 3813 3821 3823.1 Oldest for DVT3 (fixing an DVT3 on xxxxxxxxx) Oldest acording to xxxxxx for DVT3 3845\ 3907 3911 August XDK 2001 (( Final Hardware Recovery) (build on WIN2000 5. 2134/2195 ? 5.1.2258.400) xxxxxxxxxxxxxxxxxxxt 2001 final x08-46850 ----------------------------------------------------------------- Retail? ------------------------------------------------------------------- 3925.1 Retail? XDK xxxxxx 3944 < 4000 4023 4024 4028 4033 4034.1 (internet source KERNEL MCPX is X3 httxxxxxxxxxxxxxxxxd=50 (dash may be higher...) 4039 < 4119 4120 4121 4125 4134.? < 4134.6 01/29/2002 December 2001 XDK with Intergrated Hotfixes Release Histoxxxxx 4134.7 03/19/2002 December 2001 XDK with Intergrated Hotfixes Release History '' 4224 < 4228 4229 4234 4235 4242 01/19/2002 February 2002 XDK 4242.2 03/15/2002 February 2002 XDK with Intergrated Hotfixes '' 4300 4344 4346 4348 4354 4361 02/28/2002 March 2002 XDK Accession SDK ownSDK (Accession) 4361.2 03/15/2002 March 2002 XDK with Intergrated Hotfixes 4400 (xxxxxx source ?) Barnabas XDK, SDK 4432 03/29/2002 April 2002 XDK 4504.1 2002 Live Beta (kernel and dash) internet source (MCPX-X2 code asswell) 4531 04/28/2002 May 2002 XDK 4604.1 2002 Live beta consolexxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx: N 4627.1 06/05/2002 June 2002 XDK June WAM SDK 4721 06/26/2002 Juli 2002 XDK 4817 Kernel only? source interwebs, MCPX is X3 htxxxxxxxxxxxxxxx=50 4818 4831 07/31/2002 August 2002 XDK 4831.5 08/23/2002 August 2002 XDK with Intergrated Hotfixes 4831.6 08/29/2002 August 2002 XDK with Intergrated Hotfixes 4831.8 09/12/2002 August 2002 XDK with Intergrated Hotfixes 4831.9 10/18/2002 August 2002 XDK with Intergrated Hotfixes 4928 08/28/2002 September 2002 XDK parts 4928.2 09/12/2002 September 2002 XDK with Intergrated Hotfixes 4928.3 10/03/2002 September 2002 XDK with Intergrated Hotfixes parts 4928.4 10/18/2002 September 2002 XDK with Intergrated Hotfixes 4928.7 03/18/2003 September 2002 XDK with Intergrated Hotfixes recovery 5028 10/04/2002 October 2002 XDK 5028.3 10/18/2002 October 2002 XDK with Intergrated Hotfixes 5028.4 03/18/2003 October 2002 XDK with Intergrated Hotfixes iso? 5101 < Internet source 5120.1 10/31/2002 November 2002 XDK (parts andxxxxxxxx?) 5120.3 03/18/2003 November 2002 XDK with Intergrated Hotfixes 5120.4 04/09/2003 November 2002 XDK with Intergrated Hotfixes 5209 ARCDDASH, Segaboot (other libs are: 5028) 5233.1 12/12/2002 December 2002 XDK 5233.3 02/17/2003 December 2002 XDK with Intergrated Hotfixes 5233.4 03/18/2003 December 2002 XDK with Intergrated Hotfixes 5233.5 04/09/2003 December 2002 XDK with Intergrated Hotfixes 5344.1 02/04/2003 February 2003 XDK 5344.2 02/17/2003 February 2003 XDK with Intergrated Hotfixes 5344.3 03/18/2003 February 2003 XDK with Intergrated Hotfixes 5344.4 04/09/2003 February 2003 XDK with Intergrated Hotfixes 5455.1 04/18/2003 April 2003 XDK with Intergrated Hotfixes XDK 5455.2 04/18/2003 April 2003 XDK with Intergrated Hotfixes 5530 < Internet source 5558.1 05/30/2003 June 2003 XDK Recovery own 5558.2 06/20/2003 June 2003 XDK with Intergrated Hotfixes 5558.4 10/03/2003 June 2003 XDK with Intergrated Hotfixes 5659.1 07/30/2003 August 2003 XDK Recovery own, XDK also 5659.2 09/30/2003 August 2003 XDK with Intergrated Hotfixes 5659.3 (could be that this is the recovery? 5659.4 10/03/2003 August 2003 XDK with Intergrated Hotfixes 5659.5 11/20/2003 August 2003 XDK with Intergrated Hotfixes 5713 < Internet source 5788.1 11/11/2003 November 2003 XDK XDK Setup 5838 (kernel) < Internet source. 5849.0 recoveries [xxxx] 5849.1 and SDK REC 5849.6 (remote)recoveries [xxxxxxxxe] 5933.1 and SDK Remote recoverie [lxxxxxxxxve] (I own a version aswell) 5960.01 DAS (internet source txxxxxxxxxxxxxxxxx I got the 3146.3 iso from assemblergames, I noticed: A regular CDFS (not xbox) iso. DOS files (modded DOS 7.1 (win 98)) in the root A very NT-like boot sector. If you've seen those videos of early xbox alpha devkits, note the flash of 'Starting..' - that's io.sys. -------------------------------------------Xbox 360 ------------------------------------------------------- 2.0.nnnnn.n XX where xx is the newest board supported AlphaTower Xenon nov 2005 Zephyr may 2007 Falcon aug 2007 Opus july 2008 Jasper nov 2008 Jasper/Kronos mid 2009 Trinity/Velje may 2010 Corona aug 2011 SDK's: XDKSetupXenon6274.exe XDKSetupXenon8276.exe XDKSetupXenon11164.1 XDKSetupXenon11427 XDKSetupXenon11511 XDKSetupXenon11626 Recoveries: XDKRecoveryXenon111641Setup.exe XDKRecoveryXenon11164Setup.exe XDKRecoveryXenon11511Setup.exe XDKRecoveryXenon11775Setup.exe XDKRecoveryXenon120871Internal.exe XDKRecoveryXenon20353.exe XDKRecoveryXenon20764.10.exe XDKRecoveryXenon21076.6.exe Non remote recoveries: 1888_Xenon_Recovery.iso 4929_Xenon_Recovery.iso 5426_Xenon_Recovery.iso 7776_Xenon_Recovery.iso 7978_Xenon_Recovery.iso 8276_Xenon_Recovery.iso 9328_Xenon_Recovery.iso 9328.0_Xenon_Recovery.iso 9328.5_Xenon_Recovery.iso 9328.9_Xenon_Recovery.iso //2 versions: 1st) 483.700.736 bytes, MD5: 7C3E4F6620F76E19095623735F8180F0 2nd) 301.434.880 bytes, MD5: BDDF51AB55DE08FD223564BB0D0C49A4. first is hacked up and bricks your shit. 6995.1_Xenon_Recovery.iso 11164.1_Xenon_Recovery.iso 11164.3_Xenon_Recovery.iso 11775.3_Xenon_Recovery.iso 20353_Xenon_Recovery.iso 20871.2_Xenon_Recovery.iso //and 20871.2_Xenon_Recovery_with_Symbols.zip XDK's: XDKSetupXenon6274.exe XDKSetupXenon6534.exe XDKSetupXenon7645.1 XDKSetupXenon8276.exe XDKSetupXenon11164.3.exe XDKSetupXenon20871.2.exe XDKSetupXenon21076.11.exe XDKSetupXenon21119.0.exe //? need to verify other fanciful files: xdk-xna-extensions.msi //add XNA extensions to XDK, leaked from dev site XDK Kernel Version Flash Version Comment (Most are XeDK, other just version numbers) --------------------------------------------------------------------------------- 2.0.0198.0 2.0.????.0 First XDK Launcher Alpha 1 2.0.0417.0 ?????????? Giano code May (27) 2004 2.0.0418.0 ?????????? Giano code May (27) 2004 2.0.0422.0 ?????????? Giano code May (27) 2004 2.0.1232.0 2.0.????.0 Second XDK Launcher Alpha 2 2.0.1616.7 2.0.????.0 Seen on beta 007 kit. 2.0.1640.0 2.0.????.0 Seen on beta kit. 2.0.1746.1 2.0.????.0 Seen on a beta kit. First with keyvaults. 2.0.1800.0 2.0.????.0 ??? Nov 22, 2005 2.0.1810.5 2.0.????.0 XeDK 2.0.1838.0 2.0.1838.0 XeDK 2.0.1838.1 BETA 2.0.1838.1 Beta Launcher 2.0.1839.2 2.0.????.0 XeDK release Dashboard 2.0.1861.0 2.0.1861.0 XeDK (First w/ XEX2) 2.0.1888.0 2.0.1888.0 XeDK 2.0.2099.9 2.0.????.0 XeDK 2.0.2099.11 BETA 2.0.????.0 XeDK - Seen on a beta kit. 2.0.2135.0 2.0.????.0 XeDK 2.0.2255.0 2.0.????.0 ??? Jan 30, 2006 2.0.2417.0 2.0.2241.0 XeDK 2.0.2638.0 2.0.2258.0 XeDK 2.0.2638.0 2.0.2419.0 XeDK 2.0.2920.0 2.0.2832.0 XeDK - Remote includes 1888, 2241, 2255, 2258 and 2832 2.0.3215.0 2.0.2853.0 XeDK 2.0.3424.0 2.0.2858.0 XeDK 2.0.4314.0 2.0.4308.0 XeDK 2.0.4548.0 2.0.????.0 ??? 2.0.4802.0 2.0.????.0 XeDK 2.0.4929.0 2.0.4548.0 XeDK 2.0.5426.0 2.0.4548.0 XeDK - Last recovery KK exploit works 2.0.5632.0 2.0.4548.0 XeDK - Remote includes 4548 and 5632 2.0.5787.0 2.0.????.0 XeDK - ISO image in game format 2.0.6132.0 2.0.5759.0 XeDK 2.0.6274.0 2.0.5759.0 XeDK 2.0.6534.0 2.0.5759.0 XeDK - Remote includes 5787 (no 5759 ?) 2.0.6534.4 2.0.6683.0 XeDK 2.0.6707.0 2.0.????.0 XeDK 2.0.6995.0 2.0.6690.0 XeDK 2.0.6995.1 2.0.6690.0 XeDK 2.0.7645.0 2.0.6690.0 XeDK - Remote includes 6690 2.0.7645.1 2.0.6690.0 XeDK 2.0.7776.0 2.0.6719.0 XeDK 2.0.7776.1 2.0.6719.0 XeDK 2.0.7978.0 2.0.7342.0 XeDK - First on NXE 2.0.7978.3 2.0.7359.0 XeDK 2.0.8276.0 2.0.7366.0 XeDK 2.0.8953.0 2.0.????.0 XeDK 2.0.8955.0 2.0.????.0 ??? 2.0.8955.1 2.0.????.0 ??? 2.0.9177.0 2.0.9177.0 XeDK - Seen on beta XDK S, has a dumb flash number 2.0.9328.0 2.0.8464.0 XeDK - Remote includes 8464 and 7366 2.0.9328.5 2.0.8498.0 XeDK 2.0.9328.8 2.0.????.0 XeDK 2.0.9328.9 2.0.8955.0 XeDK - DO NOT RUN THE LEAKED ISO RECOVERY it was edited by TheFallen93 (afaik) and others to brick kits. You can find the real 9328.9 iso around though with filesize 301,434,880 bytes 2.0.11164.0 2.0.9189.0 XeDK 2.0.11164.1 2.0.9189.0 XeDK 2.0.11511.0 2.0.11025.0 XeDK 2.0.11626.0 2.0.?????.0 XeDK 2.0.11626.1 2.0.?????.0 XeDK 2.0.11763.0 2.0.12334.0 Rare Prototype Kinect Dashboard 2.0.11775.0 2.0.?????.0 XeDK 2.0.11775.3 2.0.12387.0 XeDK - ISO leaked from chinese forums, remote includes 12387 and 9199 2.0.11776.3 2.0.?????.0 XeDK 2.0.12087.1 2.0.?????.0 XeDK 2.0.12293.0 2.0.?????.0 XeDK 2.0.12387.0 2.0.?????.0 XeDK 2.0.15574.0 2.0.?????.0 ??? (ebay source) 2.0.16756.0 2.0.?????.0 ??? 2.0.17150.0 2.0.?????.0 ??? Dec 11, 2014 (wiki) 2.0.20353.0 2.0.12611.0 XeDK - Remote leaked from MS server 2.0.20353.2 2.0.12625.0 XeDK 2.0.20500.1 2.0.13139.0 XeDK 2.0.20764.10 2.0.13146.0 XeDK 2.0.21076.6 2.0.14699.0 XeDK 2.0.21119.0 2.0.14719.0 XeDK 2.0.21119.10 2.0.?????.0 XeDK 2.0.21173.8 2.0.15574.0 XeDK 2.0.21173.8 2.0.16154.0 XeDK 2.0.21250.2 2.0.16197.0 XeDK 2.0.21250.7 2.0.16202.0 XeDK RANDOM NOTES: 9328.9_Xenon_Recovery.iso //2 versions: 1st) 483.700.736 bytes, MD5: 7C3E4F6620F76E19095623735F8180F0 2nd) 301.434.880 bytes, MD5: BDDF51AB55DE08FD223564BB0D0C49A4. first is hacked up and bricks your shit. other fanciful files: xdk-xna-extensions.msi //adds XNA extensions to XDK, leaked from XDS how to remove digital signatures and help protect the guilty EXES (XDKSetupXenonxxxx.exe, XDKRecoveryXenonxxxx.exe) open EXE in hex editor and search for (in hex) A21E801C if more than one thing appears search for 5A30583033060A2B06010401823702010F3025030100A020A21E801C once you find that, either delete or null everything that comes after the 1C funny, this can also be used in reverse to identify the leakers, or tell if you have originals nvm this part: Xenon_Recovery, Xenon_Recovery.iso, _Xenon_Recovery, _Xenon_Recovery.iso, xxxx_Xenon_Recovery_with_Symbols.zip, _Xenon_Recovery_with_Symbols.zip, Xenon_Recovery_with_Symbols.zip, XDKSetupXenon, XDKSetupXenon.exe, XDKRecoveryXenon, XDKRecoveryXenon.exe, 11164.1_Xenon_Recovery.iso , 11164.3_Xenon_Recovery.iso, XDKRecoveryXenon20353.exe, 20353_Xenon_Recovery.iso, 1888_Xenon_Recovery.iso, 5426_Xenon_Recovery.iso, 4929_Xenon_Recovery.iso https://xds.xbox.com/xbox360/data/1033/xdksoftware/download/XDKSetupXenon9328.9.exe https://xds.xbox.com/xbox360/data/1033/xdksoftware/download/XDKSetupXenon11164.1.exe https://xds.xbox.com/xbox360/data/1033/xdksoftware/download/snorkel.exe ----------------------------------- Xbox one ------------------------------------------------------------- Giano (21 December 2010, kernel only) Durango ----------------------- ----------------------- Wordlist ----------------------- ---------------------- XDK Xbox Devolepment kit (xbox part) SDK Software Devolepment kit (PC) REC Recovery SYM Symbols KER Kernel DAS Dashboard FIL File (a loose file has been identified with this version LIB Library (part of xbe or software kit in wich diferences version.) DOC A documentation notion of official source NOT A unofficial notion of this version, still reverencing an MS source INC Incorrect number, probebly homebrew

Its a shame i didnt find this sooner but im happy to have it here. thank you for keeping this forum together. New here this is a great looking community/collection of useful information etc..

I was wondering if anybody else has been able to emulate either the Final Fantasy VII nes english patched rom for the nes, or the Secret of Evermore 2 player patched rom at all? I can get the Secret of evermore 2p rom to run but it only wants to play off of the first controller..

Goodday my dear strangers ! I'm Lincourt from Canada, and I want to learn more about OGXBOX modding. I already have a modded XBOX but I don't even know how to transfer an .Iso on it ! I'm here to learn ! Have a great day !!

XLink Kai: XLink Kai is a system link tunneling application for consoles that can trick a Xbox, Xbox 360, Playstation 2, Playstation 3, PSP or Gamecube into thinking it's connected to a local area network, when actually it is connected to an international orbital server. Any System Link enabled game can then be played in this state with users all around the world. In other words, it is a global LAN network. There are 2 servers currently operating, located in Chicago & Ottawa. You can download the program from https://www.teamxlink.co.uk. Setting up your console: The best method of connecting your console to XLink is hardwiring both to your router via an ethernet cable. Another popular method is connecting your Xbox to your PC with a crossover cable, & having your PC contact your router wirelessly. View the XLink quick start guide for a full list of ways to connect your console & PC together, complete with diagrams. Using XLink Kai: Firstly, you need a Xtag, it's pretty much XLink's version of a Xbox Live "Gamertag", you can make one on the XLink Kai website. Using XLink is easy enough, there are rooms called "game arenas" for every System Link compatible game, every player in the same arena will be connected to each other & can play with each other. Simply host & join system link matches as normal when you're inside them, & you should be able to get a game started. XLink also has a private arena feature, which lets a set arena admin control who they want in the game, & can also help with bypassing orbital de-sync glitches. You can create your very own private arena by clicking the pencil icon in the Web UI. XLink also has something called "Status". This is useless now unless you want to tell other people whether your hosting a match, dedicating one, or just joining one. If you have the game "Halo 2" on Xbox, then I strongly recommend you test your XLink set up by going into the "Latin America" arena & checking if you can see & join any matches. Port Forwarding: Before you use XLink however, YOU MUST PORT FORWARD. Even if the program doesn't crash on you when you try to start it, it will be unstable as hell if you don't. There are 2 ways to port forward for XLink. The first & most easiest is called UPNP port forwarding, automatic port forwarding or dynamic port forwarding. Simply enable UPNP on your router configuration page (if it supports it), then go into the XLink Configuration menu & switch port 30000 to 0. If everything goes right, XLink should start up & in the metrics section, under port, it should have a number that is not 30000 or 0. The Newer versions of XLink have this enabled by default. If UPNP doesn't work for you, then you'll have to port forward manually. You have to set up a static IP address first http://www.howtogeek.com/howto/19249/. Next, go to your router configuration page & go to a section known as "Port Forwarding" or "Virtual Server", you can usually find it in Advanced settings. Port Forwarding is different for every router, you can find out how to port forward for yours here http://portforward.com/. There is even a step by step port forwarding guide for XLink on that site. Port Forward "30000" on "UDP" protocol. Changing Your Orbital Server: The latest version of XLink Kai (7.4.29) has a built in orb changer from the system tray, the following is for people running legacy versions or who would like to change their orbital servers manually Sometimes, the orbital servers are out of sync with each other, so you will not be able to connect to players on the orbital that the orbital you're on is out of sync to. You can fix this by switching to a different orbital server. First, close XLink Kai completely, not just the Web UI. Then, go to "Run" for Windows or "Terminal" for Mac & Linux & insert one of these commands (assuming you are on Windows 32 bit): "C:\Program Files\XLink Kai\kaiEngine.exe" --orb ADVANCED_LA "C:\Program Files\XLink Kai\kaiEngine.exe" --orb ADVANCED_QUEBEC "C:\Program Files\XLink Kai\kaiEngine.exe" --orb ADVANCED_SIXTHGENGAMING ADVANCED_LA ADVANCED_QUEBEC ADVACED_SIXTHGENGAMING Make sure you copy the whole line, not just what's in the quotation marks. If you have XLink Kai installed somewhere else, then just change the path accordingly, Windows 64 bit users will have the default installation location as: "C:\Program Files (x86)\XLink Kai\kaiEngine.exe", not "C:\Program Files\XLink Kai\kaiEngine.exe". Mac users will have XLink installed at "/Applications/kaiengine.app/Contents/MacOS/kaiengine" by default on older versions of XLink & /Applications/XLink\ Kai.app/Contents/MacOS/kaiengine from version 7.4.28 upwards. Brief Firewall Info: Certain software firewalls will block XLink Kai from running properly, these include Avast! & Zone Alarm. You can get around this by setting XLink as an exception in your software firewall's configuration menu, or disabling them while you're playing. Compatibility: The latest version of XLink fixes compatibility issues. The following only applies to version 7.4.26 & older. If you are using Windows 7, right click on Start Kai, go to properties, & make sure under compatibility, it says Windows XP Service Pack 2 (although SP3 also works for some people), for Windows 8, it must be SP3. You have to also run the program in administrator mode. Troubleshooting: First of all, make sure your console & computer are connected to each other correctly. Hardwiring both to your router is recommended. Note that most issues can often be fixed by simply cycling orbitals, restarting XLink, restarting your router & as a last resort restarting your computer. If your issue still isn't resolved after that, try the suggestions in this section of the guide Try get as many people on the same orbital as possible while playing to minimize orbital de-sync issues. : 7.4.26 & older: (If you are using Windows 7/8, make sure you have set the compatibility mode to Windows XP SP2 for 7 & SP3 for 8, & are also running XLink in administrator mode.) If everything is good with compatibility, check your port forwarding & firewalls. If everything looks okay, I recommend just doing a clean reinstall of Kai https://teamxlink.co.uk/forum/viewto...77884db6ed8a97. If the problem still occurs, it will probably be something to do with the packet capture component, switch between pdssk & winpcap in the XLink configuration menu to see if it helps. : This will usually happen if you have not port forwarded properly. It could also happen when you're using particular orbitals, in which case switching will help. If your internet "hiccups", then you will be dropped from Kai as well. : Make sure both your computer & Xbox is connected to your router via an ethernet cable (unless you are using a bridge set up with a promiscous mode network card). It could also be an issue with a firewall, or your port forwarding. Also make sure PAT is switched off in Kai's configuration menu. : Restart XLink. This is a glitch that seems to occur less in the newest version. You'll need to restart or else you won't be able to play with the person whose console you detected. : It's a firewall issue or your PC is on wireless. : The person who is not being detected by the other person leave & rejoin the room. If that doesn't work, switch orbitals. Private arenas can also help with this. : Port Forwarding or Firewall issue usually. It could also be an orbital de-sync. Both players try switching to the same orbital, if that doesn't work, restart your router & tell the player who's ping you can't see to restart his too. : Port Forwarding or Firewall issue. : This would be incredibly odd if you are using a wired connection from your Xbox to your router & your router to your PC. If you still can't see your Xbox, try entering your Xbox's MAC address into XLink's properties. Also, remember that you have to search for games to detect your console. If you're using another method, try restarting your router & if it still doesn't work, then switch into method the dual hardwire method of connection. : If everything from the above checks out, it's more than likely going to be something to do with the Mac address. On the 360 Dashboard navigate to - System Settings>Network Settings>Configure Network>Additional Settings Tab>Advanced Settings>Alternative MAC Address Use: 00125A as the first 6 digits & randomly fill in the last 6 unique digits in any combination of 0-9 or A-E with the second digit in each number pair being an even number, A,C,or, E. Example: Paired: 00 12 5A 34 78 12 As Entered On 360: 00125A347812 : Try a different orbital. What is XBSlink?: XBSlink is a program for playing system link/LAN enabled games online on various platforms, including Xbox, Xbox 360, PS2 & PS3 (It can also theoretically be used for PC games). When it comes to Original Xbox online gaming, it’s a good alternative to XLink Kai as it’s completely P2P. The program is best on Windows. Mac OSX & Linux versions exist but they require you to use MonoDevelop (see below). For more info, visit XBSlink’s website http://www.seuffert.biz/xbslink/ Download Link: The latest version of XBSlink (0.9.6.0) has a few issues establishing a connection between multiple users at a time. Version 0.9.5.3 works perfectly however, & I’ve personally never had a single issue with it. I’ve uploaded it here http://theisozone.com/downloads/misc...-version-0953/ Console Set Up: The best method of connecting your console to XBSlink is hardwiring both to your router via an ethernet cable. Another popular method is connecting your Xbox to your PC with a ethernet cable capable of doing crossover, & having your PC contact your router wirelessly. Using XBSlink: There are 2 ways to use XBSlink, direct IP address connection & ‘clouds’. Either way you need to start your engine first. Go into settings & under the ‘network’ tab, select your capture device. This is the network adapter your Xbox is connected to & in most cases should be your local area network adapter. Next, under ‘Bind to IP’, select your computer’s internal IP address. Check ‘use UPnP NAT (automatic port forwarding)’ if your router supports it, otherwise, you’ll need to manually forward port 31415 on TCP & UDP protocols. You have to set up a static IP address first http://www.howtogeek.com/howto/19249/. Next, go to the Clouds tab & change the Cloud list to ‘xbslink.baseq.fr', then hit Start Engine. Clouds: XBSlink clouds are the easiest way to play games online. Click ‘load’ (right of the cloud list url) to retrieve a list of active clouds, double click on them to join. If they require passwords, you can enter them at the bottom of the GUI. You also can create clouds this way, just enter the name of your cloud, as well as the maximum number for people you want to be able to join it & a password for it if you wish. You can also connect to other players directly via their IP address. Just enter their IP in the ‘Remote Host’ box & click ‘directly connect to remote host’. Once other users are connected to you, you should be able to see them under the ‘info’ tab. Search for system games on your console. If everything is working, you will be able to see your console’s MAC Address under ‘found devices’ at the bottom of the GUI. When other users do the same, their names will become highlighted green. Everyone you play with must have a green name AND VICE VERSA for you to be able to connect to them. Brief Firewall Info: Certain software firewalls will block XBSlink from running properly, these include Avast! & Zone Alarm. You can get around this by setting XBSlink as an exception in your software firewall's configuration menu, or disabling them while you're playing. XBSlink on OSX & Linux: XBSlink runs on Mac OSX & Linux too but you need to use MonoDevelop to use it. You can download XBSlink for your respective OS here: Now you can either install libpcap v1.1.1 http://www.tcpdump.org/ (if you don’t already have it) or edit SharpPcap.dll.config in your XBSlink directory, changing every instance of “libpcap.so.1.1.1” to your version of libpcap. You also need to download Mono Runtime & Mono Develop from here http://www.go-mono.com/mono-downloads/download.html Get the latest stable versions. To start XBSlink, you first have to open terminal & cd to the directory containing XBSlink, this is where xbslink.exe is located (type “cd [path]” e.g. “cd Users/[yourname]/Downloads/Release”). Next, type "sudo mono XBSlink.exe" into terminal & enter your admin password when it prompts you to. If everything went right, the GUI should start up & you should be able to start using XBSlink as normal now.

No bugs in here, just questions.