KaosEngineer

You have to create XISO disc images - a special Xbox disc image format for the Xbox to recognize a disci image you'd burn to blank media (DVD-R), not a standard ISO9660 disc image that most windows ISO tools will create. Qwix and C-Xbox Tool are two xbox-scene Windows apps that can be used to create XISO images from the game's file set.

An original Xbox game disc contains a standard DVD video disc section and a hidden Xbox XDVDFS portion along with a lot of filler and secuity sectors. I believe a majority of the original game discs are dual-layer DVDs. You can tell if they are single-layer or dual-layer by looking for the layer ID(s) printed around the center ring of the disc viewing it from the backside. There will be one for L0 in the ID (single-layer) and possibly L1 if its a two-layer DVD. I believe most all Xbox games are DVD-9 media (dual-layer) discs. You can find the layer IDs for Xbox game disks and media type at http://redump.org/discs/system/xbox/ too. Update: For example, I see 100 Bullets is listed as DVD-5 with only 1 layer ID: ZC1946-DVR-H47A. Thus, single layer media may not have to have L0 in the layer ID but most dual-layer disc layer IDs that I've seen do have L0 and L1 in their IDs. redump.org only provides information about properly dump media images. They do not provide the disc images themselves. Other's have made many such redump-certified (matching hash value) disc images available onine.

If they are .7z file, download 7-zip to extract their content. If these archives are over 5GBs in size they are most likely Redump-style archival disc images of the entire original dual-layer game disc DVD. The XDVDFS portion of those files can be extracted with XDVDMulleter Beta 10.2. This is the set of files for the game. XISO rips save space on hard drives formatted with larger cluster size 32KB or 64KB clusters and allow for those games that use long filenames to be played from the hard drive. A cluster is the minimum amount of space a file will be allocated on the hard drive. Thus, if the games has 100's of smaller than a cluster files, instead of only using the minimum space a DVD sector (2KB) it will use the cluster size (32KB or 64KB). The wasted space adds up.

Looks good to me. @Forlorn Penguin is a member here on OGXbox.com that created this updated version of HeXEn. The size of the archive's content, HeXEn 2018.iso, is correct. Check the extracted contents's MD5 hash. The valid MD5 hash value is: A7F6B52422793CFD9B9CD7C599D5F636 I downloaded it and checked the content. It is the a good file. Note: The RAR file itself's MD5 hash value is 935438551CFAC1E254BC12D751864D4A.

You don't get to download files until after being around for a while with 15 posts or supporting the site with a yearly $5 or $10 subscription.

The case's top X has the same texture/look of the front panel. It's not shiny.

From what I see. Baldbouncer's LPC diagram pin #7 is actually pin 12 in xboxdevwiki's and is connected to ground. There are so many locations that ground can be obtained. However, I believe one of the inner layers of the Xbox's multiplayer PCB is a ground plane and it's connected inside the plated feed-through hole to that layer of the board. You'd have to rip the entire plated section out of the hole to destroy the connection to it. The reason there are feed thru holes all around each of the motherboard mounting screw grounding pads on the top and bottom sides of the motherboard - they connect the pad to the inner ground plane layer of the motherboard. I'm not sure why he pointed out that particular location of the PCB on his diagram for the pin 7 connection.

Do you have a copy of the picture of the LPC debug port with Baldbouncer's pin numbering? Update: Oops, I see it now in the original post. Those white numbers don't show up too well until I zoomed in on the picture. He should have placed larger numbers in the blown up section of the picture.

There is no pin #4 on the LPC debug port. Pin 1 is the square pad and they count moving back and forth across the connector then to the left. Pin Layout Name Pin Pin Name SERIRQ (v1.0) 16 15 3.3V SDA 14 13 SCL GND 12 11 LAD0 LAD1 10 9 3.3V LAD2 8 7 LAD3 5V 6 5 LRESET# PWR (v1.6) 4 3 LFRAME# GND 2 1 LCLK Pin 4 header hole is only present on v1.6's - see https://xboxdevwiki.net/LPC_Debug_Port. It's the power on control signal. Connect the pin to ground then remove the ground connection to power on/off the console.

What's this needed for? IIRC, all signals are present on 1.0/1.1/1.2/1.4 motherboards. There's no rebuild necessary. Do you have a multimeter? Measure for continuity between the LPC debug header feedthru holes to the via you've marked for each.

Use the XBlast OS XBE edition from the archive to flash it from the hard drive stored dot bin BIOS file. Any BIOS compatible with a v1.0 Xbox will work. For a larger hard drive swap, get one that supports both F and G. The 1MB TSOP (thin small outline package) flash chip on 1.0 and 1.1 Xbox motherboards has 4 copies of the stock 256KB BIOS flashed consecutively to fill the entire 1MB.

How do you plan on using such a device on the Xbox? You cannot load additional software to use it. Where do you plan on connecting it?

No IIRC, no game used the clock to control game play.

You can't swap hard drives in Xbox's without first modding the console then NULLing the HDDKey in both consoles. Reason: From the factory, each Xbox has a unique HDDKey that generates a unique password for that Xbox's hard drive. After NULLing the HDDKey, the computed HDD unlocking password will be the same for both Xboxes (actually, anyone else's Xbox where they NULL'd the console's HDDKey too). Thus, allowing HDD swapping between consoles.

The software didn't do quite what I was expecting. Your new post should be at the top of the thread no the one's I moved over? And, now I don't even see your new topic post. It was listed as the last one; however, now it's gone! what? Hopefully, OGXAdmin can straighten things out

256KB M8plus F and G on the HeXEn 2018 disc.

Here's a flowchart to follow to determine your Xbox version. It was created by @xbox7887#6347 on the Homebrew Xbox Discord server Source: https://discordapp.com/channels/297536872589295626/297537827074473984/701922923795185694

Must not be the right points to bridge

Does the menu item for the game have the preview video linked to it? Highlight a game having the problem then press the Start button scroll down to Edit Item... Verify that a path to the Preview video is set. If not, press (A) and browse to the location of the preview video on the hard drive. Press Start to Accept the preview path.

Qwix is used to FTP the files in an XISO format dot iso file to the Xbox without first having to extract them from the ISO file. Softmodded consoles can play games by mounting the XISO dot iso file using NKPatcher's driveimageutils attach application. To the Xbox, the mounted disc image acts just like having the DVD disc loaded into the DVD drive. Hard modded consoles can also mount disc images but the hooks to do so have to be added to the kernel just like softmod do. There are a limited number of modified/hacked BIOSes supported. All original MS BIOSes are supported with a softmodded console. Not all archives you find online contain an XISO format disc image (dot iso file). some are already pre-extracted ready to FTP to a subfolder in the Xbox's Games folder. Other's are archival dumps, so called ReDump disc images - these disc images have been posted by others that have matching hashes of a properly archived disc. Redump.org maintains a database of which disc and the hash values of the properly archived data, not the disc image itself. These Redump disc images are exact duplicates of the original Xbox dual-layer DVD.

Open up the Xbox and take a picture of the modchip and post it so it can be identified for you. Why a 1MB BIOS, most BIOSes are only 256KBs in size? Only a few BIOSes are larger than 256KBs. The X2 5035 is 512KBs and the X3 modchip specific BIOS is 1MB but only runs on an X3 modchip. The 1.0 and 1.1 motherboards have a 1MB flash memory chip on it. Their 1MB flash chip holds 4 copies of the original 256KB stock MS BIOS. The Aladdin line of modchips only has 1 256KB bank. Xecuter X2s have 2 - 512KB BIOS banks. The X3 modchip has 2MBs of flash that can be used split into several different configurations or subsets of 256KB, 512KB, 1MB or a 2MB bank(s) non-overlapping usage to fill its 2MBs: 8-banks of 256KB, 4-512KB banks, 2-1MB banks or 1-2MB bank - no 2MB sized BIOS known to exist. X3 256KB Bank Usage (Numbers indicate the 256KB banks used together for the sizes indicated): 12345678 = 1 - 2MB bank 1234 and 5678 = 2 - 1MB banks (X3 BIOSes are 1MB in size) 12, 34, 56 and 78 = 4 - 512KB banks 1, 2, 3,, 4, 5, 6, 7, 8 = 8 - 256KB banks For example on an X3 modchip, you can flash a 1MB BIOS to Bank 1234, a 512KB BIOS to bank 56 and two 256BK BIOSes to bank 7 and 8. These BIOSes are user selectable via the X3 modchip's front panel bank select switches or through the X3 BIOS's X3Config Live BIOS selection menu. There are many other combinations that can be used as long as each 256KB bank is used only once.

2.1's in the MS XDK? Which XDK version?

Nice! Which version of Deep Exploration are you using? Edit: What fixed the angled display of the text?

Most people just rip the file set instead of an ISO. Saying you CANNOT run them from an ISO file (XISO format file that is). Dismissing the possibility all together. A few games though cannot (well, maybe with a patched default.xbe that opens shortened filename files) be played without burning the XISO to media or mounting the disc image from the hard drive.

Which folder do you have the all of those dot nes file in? Edit: I also thought the Emulators wanted them to be in zip archives, not extracted. Each ROM archived in a separate dot zip file. Try to zip up a few and upload them. See if those show up after scanning.