All Activity

I have things ready for Navi's Quest, but for some reason I cannot get the assets needed to make the Zelda 3 run without throwing an incorrect assets error I was hoping someone could pm me a working copy

Very good! where exactly did you connect the charger?

Here's the reddit post from a few weeks ago. And the github from that post. I haven't tried it. Did you see the message I sent about the other Zelda artwork?

So how did you end up fixing it? I installed the softmod and then tried the TSOP flash M8Plus. It is booting into the loop now.

The RAM chip on the top of the board, nearest to the AV port.... On the side oy that RAM that's closest to the AV port, there are two pins in the middle of that row that might have a spec bridging them. It appears that way in two separate pics....

Can someone link me to a working Zelda3 please? I want to take some screenshots for the artwork

If your chip is wired properly and it functions, you should be able to cold boot an installation disk like Hexen or similar. To be honest, that soldering looks rough.....

Added CelesteX artwork.

This code ain't good apparently. It looks decent but apparently it's no good for the engine to have this in it. Guess for loops aren't too bad after all?

You could use a raw copy mode in a PC based back up software. It will depending on version/software, create a back up file on another drive to then be used to make your clone, and then you write it to the new drive. Or the better option would be to clone straight to the new drive. The. You’ll have the 1Tb drive setup and contents on the 2Tb drive and should be able to then create aG drive with the spare space. I use Acronis, It does have the clone in place ability, and if it can al least recognise a file partition type it can expand the image onto the new drive. Not tried it that way as normally just straight up clone then create a new partition for the space. with some drive formats on older board controllers you can change the drive Type number so the card can correctly see and report the drive contents. That way the OS can see it and then the back up software also sees it. Use that method on Amiga and similar era hardware as there was no set type standard back then as everyone was still fighting it out. Amiga use type 76 and a few other computer types use 77 for example.

A brief history prior to repair would definitely be beneficial. As to the lpc some of those looked a bit off and one or two looked like cold solder joints. They can work though….right up until the point that they stop. Lol. I’ve seen it happen where many console or other electronic has worked for years with bad solder joints and then it up and stopped abruptly. Especially with poor or cold solder joints.

True. I'm honestly surprised it ever worked with that LPC soldered the way it was. I dunno how I haven't thought of that. What IS the history of this thing? Regardless of all, if it WAS working, I'd be interested to know why XeniumOS can't even load when booted with the eject button. It looks like D0 wasn't even being triggered by the time you got it.

Did your friend tell you what happened to the console to require this repair? Was it something he did or was it a pick-up? Any more history on the problem might help. If by some chance he tried to flash the Xenium a wrong way, it could require programming again.

Here’s what I get when pushing eject button with mod. Mod red led comes on then off, then on again, then off, then on and stays on. You can hear HDD start to work. No bios boot. Seems it’s trying to boot HDD but stops. So, most likely bad mod chip or HDD is screwed up. I really don’t know how to eliminate one.

Alternatively, you could use the Chimp application to clone a new drive directly from your old one. This could take a good bit of time depending on what's on your older hdd. You'll need a molex y-Splitter for this method.

Use 128kb clusters for 1TB Partitions. Here is a detailed guide to follow.

I dunno if you saw, but I built a Devkit incorporating the SuperIO and internalizing it as neatly as I could. Check it out. I'm proud of it and show it off as much as possible.

XBPartitioner, for sure. I think FATX can only do 1TB partitions. XBP is more fully featured in many regards. I think @KaosEngineer could give you advice there. He's pretty familiar with it. (Hopefully he'll be by soon.) Whatever you do, before you start formatting anything, back up ALL your partitions, just in case. One partition by one. You will find info here on how to format a 2TB partition. Make sure to pay attention to your cluster size! I actually plan to do this with my Origins-based image. It has all the games spread across 2 partitions (F and G) and I wanna get rid of that and make my master image a 2TB F. Edit: It seems that trying to format over 1TB causes issues with corruption with cluster sizing of 512 - 1024. I don't know why. Kaos, could you explain that for us?

This "just format it..." is where I've still been lost for the last 2 hours. I've got a similar project where I want to take a 500GB HDD image that's currently on a 1TB drive and make use of the blank space. I've got everything on F copied off fine, I just have no idea how to actually wipe and re-partition a single partition. F can go away and be reborn as a new biggerer F partition, FATXplorer just doesn't do this. Or at least I don't see a way to. I've been looking at Chimp and XBPartitioner, seen those both mentioned.

I never really left. Just took a long pause from anything xbox to focus on school and work.

Bump* I haven't tested it yet on my engine but I believe it'll be more working using this method than a bunch of for-loops. #include <iostream> using namespace std; class CObject { public: void ExecuteDeb(int num) { printf("Printing! %i ", num); } }; class CObjectLinker { public: CObject* objs; int numObjs; CObjectLinker(int num) { numObjs = num; objs = new CObject[numObjs]; } void StartExecute() { int number = numObjs; keepExecuting(number); } void keepExecuting(int& curNum) { objs[curNum].ExecuteDeb(curNum); curNum--; if(curNum < 0) return; keepExecuting(curNum); } }; int main(int argc, char *argv[]) { CObjectLinker linker(4); linker.StartExecute(); } This was a test to see if I can execute multiple objects with a countdown method instead of the usual. If And For/While takes some speed away when used a lot so I was experimenting and came up with this. Any thoughts?

Since you are now fragging, I think we can assume that your LPC rework got the chip to be able to trigger D0 through the wire. That's why your TSOP boots when the chip is unsocketed and your dashboard boots with the locking error. You are still unable to boot your modded dash and bios which would bypass a locking error entirely. You are triggering an LPC boot, but your chip is not giving the bios over successfully, so the chip may be defective in some way. The D0 point is not a ground itself. It is a lead to the MCPX for triggering a chip (LPC) boot. IT is grounded in order to force a chip boot. That's why it's going to the Xenium. The chip is grounding the D0 point (pointing to the MCPX) at boot in order to tell the console to boot from it and load a bios through the LPC instead of the onboard flash (TSOP). That's how it works. All chips require this. Shitty chips like the Aladdin do not have a working D0 pad on them which requires you to take that wire and run it from that point on the bottom of the board to aground point anywhere on the console. I use a screwhole ground on the top of the board, but that's just me. If the chip is dead, then you should be able to throw another one on the header, yes. Are you able to boot/power-on with the eject button? That should load XeniumOS. I would assume that a bios was already configured to load based on the fact that the HDD is unlocked and it already had the chip in it, but it's worth a shot.

Regardless of popular belief, I have seen many thrown errors on hard modded consoles. Especially if the hdd is locked to another console, has improper files installed, or simply dying. I find it's always best to start with the simple tests just to rule them out. Instead of immediately jumping to resoldering stuff. We're steering back to a few months ago it seems, by overlooking simple solutions and instantly diving in deep. Im just saying

I can find ZERO trace of this anywhere online by part number. I did find the raptor PCI card, but not this. @GoTeamScotch Are there drivers for the Raptor card that you have found?

ok, after reflowing the header, I power it up and now all I get is green and red ring and no boot. mod is lit red. If I remove the mod I get Factory boot with 05 error. It will not boot at all with mod plugged in. Also, I checked the D0 wire point of solder on bottom of motherboard and it is not a ground. I've attached a pic of bottom D0 solder point. I don't know anything about this mod, but it must have worked at one time as it is. If mod is bad can I just install another?