KaosEngineer

Have you had a component cable connected and the 480p and/or higher resolutions enabled? If so, you need to reconnect the component cable so you can disable them else the game still tries to output in a higher-resolution mode even when the composite cable is connected. Update: If it runs from the disc, one would think it would do the same from the HDD. The UnleashX settings don't change values stored in the configuration EEPROM. Its video settings only affect the dashboard itself not any other app that you run from it.

Will have to find stock of the chip too. Seems the ATTiny11L is obsolete (0 stock available from many resellers) and the 12L is available in SOIC-8 (surface mount packaging). The ATTiny13-20SU will most likely work. The 13's have a lot more features built-in than required for the adapter design and cost more: $0.97 (cut tape) or $0.99 (tube) each vs. $0.59 for the ATTiny12L. The ATTiny13-20PU ($1.29 ea) is in an 8-pin DIP package for socket or thru hole installation while the -20SU is in a SOIC-8 package - surface mount. The ATTiny13 operates on a supply voltage from 2.7-5.5Vdc and at a faster clock rate (20MHz max clock frequency) than either the 11L (2MHz max) or 12L (4MHz max).

That I don't know, the 8164 adapter from xbxo8164adapter.com ages ago used an ATTiny11L instead of a 13. I'm not sure why there are many diagrams showing an ATTiny13 instead of the 11L. The 11L runs off of 2.7-5.5Vdc (3.3Vdc in the diagrams) while the standard ATTiny11 from 4.0-5.5Vdc. I'll need to download the ATTiny13's datasheet(s) that show all the different versions and see what I can determine from them.

Are you asking or telling?

Boot into the X3 Config Live menu using the working X3 modchip, reflash a 2MB BIOS file (2 x the X3 1MB BIOS file) to the hotswapped FRAGing X3CE. You can use FTP or the file stored on the Xbox's HDD. Prepare a 2MB X3 BIOS dot BIN file. 1. Start CMD.EXE prompt window 2. Execute the command: copy /b X3BIOS.BIN + X3BIOS.BIN 2MBX3BIOS.BIN change the names to match the files you have for the X3 BIOS's dot bin file. The output, 2MBX3BIOS.BIN. file can be named what you want with the dot bin extension. If the filename has a space in it, you will have to surround the name in double quotes (e.g., "X3 3294.bin"). If you use the file stored on the Xbox HDD, you'll have to upload it to the console so you can browse to it when you select that option. The latest X3 BIOS is 3294: X3 3294.bin for v1.0-1.5 consoles and X3 3294 v16plus.bin for v1.6/1.6b consoles. Update: What happens if you try to boot the console from the FRAGing X3CE's Backup/Recovery BIOS? Power on the console by pressing both the Power and Eject buttons on the front panel - FlashBIOS 3.0.1 or 3.0.3 should boot.

Best start a new topic with your query to get an answer instead of hijacking someone else's question. Go here and click on the Start new topic button.

That's one of @N163LPH03N1X's skins. He's a member here. Not sure where he's keeping them now. His UnleashX skins were available here: https://n163lph03n1x.wixsite.com/home/unleashx-hd Update: Looks like they still are; however, some like Dark Tech, well Dark Tech Enhanced, require a subscription to download. Click the Support Link at the top of his website and fill in the form to request his subscription required - free themes. He does have some premium skins that require a $5.00 CAD donation each.

You have to have a partition table on the HDD and the BIOS must have LBA48 patch v3 installed. The standard configuration for an LBA48 .67 BIOS is partition 6 (F) up to 137GB and partition 7 (G) takes the rest. Without using XBPartitioner v1.3 to write a partition table the the hard drive, a .67 BIOS will only have F of ~120.5GB's and G the remainder no matter how you have the drive setup. The LBA48 patched, .67, BIOS has fixed values set for the drive/partition starting locations when no partition table present. If the table is present, the BIOS overrides the fixed .67 configuration values with those values read from the partition table.

Here's another schematic of the adapter. Still uses a ATTiny13 but has one of the signal line names relabeled. LDVD to pin 2 instead of LDIN. Pin 3 of the ATTiny13 is now labeled LDVD instead of LDIN. Source Code Check of All ATTiny13 Input and Output Signal Pins Pin 1 - output - PB5 (0x20) of the ATTiny13, LDOUT, matches the source code: .equ LDOUT = 0x20 Pin 2 - input - PB3 (0x08) of the ATTiny13, LDCD, matches the source code: .equ LDCD = 0x08 Pin 3 - input - PB4 (0x10) of the ATTiny13, LDVD, matches the source code: .equ LDVD = 0x10 Pin 4 = GND Pin 5 - output - PB0 (0x01) of the ATTiny13, READY, matches the source code: .equ LDOUT_READY = 0x01 Pin 6 - output - PB1 (0x02) of the ATTiny13, TRAYOUT, matches the source code: .equ LDOUT_TRAYOUT = 0x02 Pin 7 - input - PB2 (0x04) of the ATTiny13, LDIN, matches the source code: .equ LDIN = 0x04 Pin 8 - Vcc - 3.3Vdc source from GDR-8164B controller PCB pad. The GDR-8164B receives power from the Xbox's 12-pin DVD Power and Signal cable: 5Vdc 12Vdc, and Ground. With this adapter, the Molex power connector on the DVD drive is not used.

I still don't think it's quite right. DIP8 pin numbers 1 8 2 7 3 6 4 5 Why's 8 next to pin 5 and LDIN doesn't connect to pin 8. Am I seeing it wrong? Can you make pin 1 of the DIP8 package a square pad. I see the silkscreen dot so assuming the pinout I've shown above for the PCB. Pin 8 is 3.3Vdc power supply for the ATTIny11L, not LDIN. LDIN is either pin 2 or 3 can't see it from the RED pcb picture posted above but it's on the black and white PCB pics above connected to pin 2. Also, silkscreen labels on top in ALL UPPERCASE or lowercase for the GDR-8164B PCB signal names.

@treliyvan can you provide a link to a picture of this blue skin?

What's the main screen of XBpartitioner v1.3 look like? post a pic showing your Xbox's HDD settings. What is the size of the F drive? What cluster size is being used?

Oh, I found an installation manual for the xbox8164adapter too. http://www.konsolenchips.de/download/xbox/lg-8164_adapter_manual.pdf Attached below as well: lg-8164_adapter_manual.pdf

All the info posted thus far has been about a SOLDERing required adapter not the TalisMoon solderless adapter. I did find a post by @N64 freak some 4 1/2 years ago at assemblergames.com that just happened to have tutorials and other info to mod the Samsung SD-616T, LG GDR-8163B and GDR-8164B DVD drives for the ogXbox. Looks like the source code for the the xbox8164adapter is included. I've not completely deciphered the source code to verify if the pin 1 to LDOUT mod is supported. I'm not sure if this assembler source code is for the now defunct www.xbox8164adapter.com's microcontroller but here it is [comments translated from German to English using translate.google.com]: Note: The [ code ] ... [ /code ] tags seem to mess up the starting location of some of the lines, added additional spaces in front of them for some unknown reason, and I can't edit inside the code section to remove them. I think all lines should start in the first column but maybe not. ; *************************************************************************************** ; * Control program for mapping the control signals of an LG-GDR8164 DVD drive * ; * for operation in an XBox Classic. * ; * * ; * created on 17.01.2007 by David Rummel * ; * last change on 25.01.2007 * ; * * ; * Version 0.9 * ; * * ; * This program is released under the GNU General Public License and * ; * may be distributed and changed under this license. * ; *************************************************************************************** ; Includes ... .include "8515def.inc" ; Constant ... .equ TRUE = 0x01 .equ FALSE = 0x00 .equ LDIN = 0x04 .equ LDOUT = 0x20 .equ LDCD = 0x08 .equ LDVD = 0x10 .equ LDNOTHING = 0x00 .equ LDOUT_TRAYOUT = 0x02 .equ LDOUT_READY = 0x01 .equ LDOUT_NOTHING = 0x00 ; Register definitions ... .def Temp = R16 .def LD_INPUT = R17 .def LD_OUTPUT = R18 .def WAS_CLOSED = R19 .org 0x0000 ; the output mask is set ... ldi temp, 0x03 out DDRB, temp ; the initial state of the DVD-ROM is set as "closed", should that not apply ; is the right already determined at the next loop pass ... ldi WAS_CLOSED, TRUE ; here begins the endless loop ... LOOP: ; read in which levels are applied to the individual pins, including the two outputs in LD_INPUT, PINB ; read in which levels are present at the outputs ... in LD_OUTPUT, PORTB ; subtracting the output values from the on + output values gives the input values .... sub LD_INPUT, LD_OUTPUT ; is only on the LDCD pin voltage on ... cpi LD_INPUT, LDCD ; is a disk inserted ... breq GT_IN_READY ; same applies to the LDVD pin cpi LD_INPUT, LDVD breq GT_IN_READY ; if there is no voltage on a pin, no CD is inserted ... cpi LD_INPUT, LDNOTHING breq GT_IN_NOCD ; If the voltage is applied to the pin LDOUT, the drive is running straight or ... cpi LD_INPUT, LDOUT breq GT_MOVING ; If the LDIN AND LDOUT pins are connected to the pins, the CD drawer is extended ... cpi LD_INPUT, LDIN + LDOUT breq GT_OUT ; was none of the previous cases occurred is the CD / DVD just read ... ; (probably voltage to LDCD and LDVD) rjmp GT_CHECK ; is a CD / DVD inserted ... GT_IN_READY: ; the corresponding output values are stored in the Temp register ... ldi Temp, LDOUT_TRAYOUT + LDOUT_READY ; and spent ... out PORTB, temp ; It also states that the drive is currently closed ... ldi WAS_CLOSED, TRUE ; and it jumps back to the beginning ... rjmp LOOP ; analogously, for the states "drive empty" ... GT_IN_NOCD: ldi Temp, LDOUT_TRAYOUT out PORTB, temp ldi WAS_CLOSED, TRUE rjmp LOOP ; "CD / DVD is being read in" ... GT_CHECK: ldi Temp, LDOUT_NOTHING out PORTB, temp ldi WAS_CLOSED, TRUE rjmp LOOP ; and "CD drawer open" proceed ... GT_OUT: ldi Temp, LDOUT_NOTHING out PORTB, temp ldi WAS_CLOSED, FALSE rjmp LOOP ; when the drive is being opened or closed ... GT_MOVING: ; still needs to be checked if the drive was just closed ... cpi WAS_CLOSED, TRUE ; is that the case, go to GT_OPENING ... breq GT_OPENING ; otherwise the port will be set to show "Drive is closing" ... ldi Temp, LDOUT_TRAYOUT out PORTB, temp rjmp LOOP ; the drive is just opened ... GT_OPENING: ; READY is issued ... ldi Temp, LDOUT_READY out PORTB, temp ; and it goes back to the beginning ... rjmp LOOP The assembled code in lg.hex to program the microcontroller. Is it to be a ATTiny11L, 12L or 13L? Plus a couple of pics already seen but attached here for completeness. Update: The source code above is not for the diagram above. The code includes reading the LDVD status which this diagram does not use. And, the LG GDR-8164B adapter firmware flasher (previously posted in this forum thread from a different source): xbox8164flasher_v1.0.rar Looks like this is different than the 8050L firmware used to reflash the LG GDR-8163B DVD drive.

You'll need to read the configuration EEPROM's data to build a new locked HDD with the MS dashboard install (XboxHDM23USB beta 2 and Clean C and E files for Xbox archives). Or, use the Beta 3 version of XboxHDM23USB that installs a no-original-game-disc-required softmod installer to the HDD. Beta 3 is pre-configured with the files to copy to the new Xbox HDD's C drive unlike beta 2 that needs the files added from the second archive mentioned to add them to the HDM/C and HDM/E folders before prepping the new HDD. You need the eeprom.bin file for each Xbox as it has a unique key stored inside used to generate the locking password for the hard drive. Update: If you have a working modded console, you can use Chimp 261812 to clone the HDD to prep a new HDD for another Xbox. You still need to read the configuration EEPROM's data and copy it to Y:\eeprom.bin one at a time for each different Xbox to lock the HDD. Upload each Xbox's eeprom.bin file to Y: to be used to lock each console's new cloned HDD. Lock the new (SLAVE) HDD with the eeprom.bin file stored on Y:. The operation to perform this action is in the Slave drive menu of Chimp.

Then, it's not v1.3. Where did you download it from? Updated versions fix problems in older versions. V1.3 is the latest available.

Here's another forum with an 8164B mod: https://www.elektroda.pl/rtvforum/topic2481040.html

Found a copy of the firmware here: http://www.xbox360-forum.de/lg-gdr-8164-b-firmware-flash-tool-8164b-firmware-6600.html The Wayback Machine didn't seem to have a copy of it from the original source: http://www.xbox8164adapter.com/download/xbox8164flasher_v1.0.rar There should be a copy of the firmware on xbins FTP server. Attached here as well just in case other sites lose it: xbox8164flasher_v1.0.rar

The schematic diagram is on page 3 of the posted forum. I've also attached it below: Source: https://www.htmh.de/attachment/354-8164-1-jpg/ After a bit of deductive reasoning, the "hier das schaltbild klick" translated to English "the picture - click" by Warlock-XBOX on page 5 of the forum to an image seems like it should show the one above but errs on the Wayback Machine to see it. (The current web site doesn't work either. It results in displaying a page not found error.) Some other images from the previously posted forum:

There's information on modding an LG GDR-8164b here: https://www.htmh.de/forum/thread/865-lg-gdr-8164-xbox8164-adapter/ Read through all the pages as there were slight modifications and better schematics provided in later pages. I've only went through the first three of six pages. You don't need an Atmel Tiny12L chip just some 24-30AWG insulated wire (Kynar insulated wire-wrap wire will work) , 1N4148 switching diodes, 1K Ohm resistors and a BC547 NPN transistor wired to the correct pads on the DVD drives controller board and the 12 pin header to mate with the Xbox's power/signal cable connector. Plus, flashing the firmware so it can read original Xbox game discs - found at the usual place. P.S. There is a board layout for the PCB you've shown or at least one very close to it. I've not found the code to program the Atmel chip but with larry's mod you don't need it.

Check @Kekule's web site: https://www.chimericsystems.com/product/lpc-rebuild He has several ogXbox modding products available too.

It will work. I don't recall any new options being added to the config file with the 5003 to Beta a.k.a. 5004 update.

It doesn't make much difference in the Xbox. The BIOS/Kernel does not seem to use the higher speeds a different cable provides. However, for many people using a SATA HDD / IDE-to-SATA adapter combo, an 80-wire 40-pin high-speed cable is required for the drive to work reliably. Otherwise, error 07 sometimes occurs. Change the IDE cable to the high-speed one; the error goes away.

Print the TIF from the archive as it's a higher resolution, 3296 x 2232 pixel 150dpi image than what I attached at 1/4 the resolution - an 824 x 558 pixel 72dpi jpeg.

Yes, that will work and cheaper than the 18" StarTech cable too.