Hard drive upgrade on soft-modded console... what am I doing wrong?

[codezer0]

So, in a turn of surprise, I managed to find a 120GB PATA drive that isn't being used anywhere, so one of my thoughts was immediately to put it to use for one of the OG Xbox consoles I have laying around here.

So, based on what I'd been able to find so far, I need to be running Chimp on the Xbox, and then b eable to open it up to move the IDE cable and such over... Well, as a test, I managed to FTP over the app to the E:/ drive on the console, and while it doesn't show up in UnleashX, I can launch it via the .xbe... and this is where it gets weird. In the OBS capture, I see a split image of what looks like Gentoo running on the thing, but then if I switch to the actual component video output from the console, it's a solid black screen, and the front of the system's lights cycle around before flashing red off and on. Turning off the console and back on seems to show no harm done, but I can't understand what I'm doing wrong, or if there's something else I should try to be able to do this hard drive upgrade.

I'd still rather get a SATA adapter and slap in a 2tb drive in there for the purpose of ripping all my retail games and also having ample room for the homebrew that enticed me toward a modded Xbox in the first place (e.g. the build of MAME that actually can play Ninja Baseball Bat Man ), and so I don't have to be so dependent on the DVD drive. But I figure I can at least learn how to do it with this one (provided it too works).

 

[DinohScene]

Ehh...
It is best if you FTP all your data to your PC and manually copy them back later onto the newer HDD.
It makes the job of cloning the HDD byte by byte in Chimp quicker and easier.

Hook it up to component and try again.
Make sure you do get the 1.6 build of Chimp for your console if it's 1.6

 

[codezer0]

Ehh...
It is best if you FTP all your data to your PC and manually copy them back later onto the newer HDD.
It makes the job of cloning the HDD byte by byte in Chimp quicker and easier.

Hook it up to component and try again.
Make sure you do get the 1.6 build of Chimp for your console if it's 1.6

Okay, if I do FTP back to my PC, what do I copy from, and where? I'll freely admit I don't know what's stored where on an OG Xbox hard drive. Heck, you should know, I didn't even have a system to toy with until like last year.

 

[DinohScene]

C drive holds the dash, E drive holds saves and DLC and the F and G drives hold games/homebrew (not accesible to a retail dash)

You could just copy over the entire E and F/G drives

 

[codezer0]

Where would ISO's go, in that case? haven't been able to really rip any because OG 8GB storage.

 

[DinohScene]

Ah, well you need to rip the ISO images with qwix to folder rips.
Then FTP them over to F:/Games (once you upgraded your HDD)

 

[DarkGabbz]

Do you already have the full space available if not run xbpartitioner.

 

[DinohScene]

That's not needed on a stock drive.
Unleash X can unlock the 2 GB hidden partition if you got a 10 GB drive but OP asked to upgrade his HDD.

 

[codezer0]

Okay, so basically, I mistook and put the chimp program on the e:/ drive rather than on f or g? That would explain why it wouldn't show up in unleashx.

 

[DinohScene]

Okay, so basically, I mistook and put the chimp program on the e:/ drive rather than on f or g? That would explain why it wouldn't show up in unleashx.

You probably put it in a folder that isn't scanned by the dash yeh.

 

[codezer0]

Okay, so what do I have to do? The system in question is a 1.0. All the systems I've salvaged are either 1.0's or 1.6's, with literally none in between.

When I check the file explorer on the console I'm trying to get the bigger drive into, it doesn't have an F/G drive, it just has... C,D,E,X,Y,Z. That's it. I've reasoned D is the DVD-ROM drive. So, where would I put the app?

Would the 1.6 compatible build of Chimp have a problem on a 1.0 console?

 

[DarkGabbz]

Okay, so what do I have to do? The system in question is a 1.0. All the systems I've salvaged are either 1.0's or 1.6's, with literally none in between.

When I check the file explorer on the console I'm trying to get the bigger drive into, it doesn't have an F/G drive, it just has... C,D,E,X,Y,Z. That's it. I've reasoned D is the DVD-ROM drive. So, where would I put the app?

Would the 1.6 compatible build of Chimp have a problem on a 1.0 console?

E:\apps

--------------------- MERGED ---------------------------

But i also recommend TSOP flashing your xbox (IND-Bios 5004) so that you just need to plug the new hdd in and it will work after you copied the dashboards back on with hexen.

 

[codezer0]

Uhh... yea, my first attempt at TSOP ended with me ruining the board. I'm kinda leery on doing that, even as much as I want to.

 

[DarkGabbz]

Uhh... yea, my first attempt at TSOP ended with me ruining the board. I'm kinda leery on doing that, even as much as I want to.

How can you ruin a board when you bridge 2 points with solder?

 

[codezer0]

How can you ruin a board when you bridge 2 points with solder?

The solder points came off the board itself. So yea, that system was well and fully dead after that. Would like to avoid doing that again.

 

[DinohScene]

How can you ruin a board when you bridge 2 points with solder?

Not everyone can solder two simple points.
Remember that.

Okay, so what do I have to do? The system in question is a 1.0. All the systems I've salvaged are either 1.0's or 1.6's, with literally none in between.

When I check the file explorer on the console I'm trying to get the bigger drive into, it doesn't have an F/G drive, it just has... C,D,E,X,Y,Z. That's it. I've reasoned D is the DVD-ROM drive. So, where would I put the app?

Would the 1.6 compatible build of Chimp have a problem on a 1.0 console?

Put it in E:/apps
No, use the normal chimp for 1.0-1.5 and the 1.6 for 1.6 consoles.
Boot the xbox, then disconnect the DVD drive and hook it up to the second harddrive.
Then boot chimp.

 

[DarkGabbz]

The solder points came off the board itself. So yea, that system was well and fully dead after that. Would like to avoid doing that again.

I had the same issue one time with a cheap soldering iron and then just used the alternate points.

 

[codezer0]

Annoyingly, not been able to find said "normal" version of Chimp. Usually my results only point to the 1.6 version of Chimp when trying to find the latest build. Closest thing I could find to it was a version that claimed to be universal that required burning to a DVD-R.

What I have there now is copied over to E:/app (which was already there), but still didn't show up in the dashboard.

I had the same issue one time with a cheap soldering iron and then just used the alternate points.

Uh, what alternate solder points? I only knew of the two sets of points on both sides of a 1.0 board. Unfortunately, yea, that happened. I still want to TSOP my 1.0 system(s), but I'm scared of repeating that fiasco. Especially since the only other systems I have are 1.6 systems.

 

[DinohScene]

You could temporarily copy it to E:/Games.
See if that works.

Hang on, you sure you got the default.xbe in a folder called Chimp?
Folder structure is like this: E:/apps/chimp/default.xbe

 

[DarkGabbz]

Annoyingly, not been able to find said "normal" version of Chimp. Usually my results only point to the 1.6 version of Chimp when trying to find the latest build. Closest thing I could find to it was a version that claimed to be universal that required burning to a DVD-R.

What I have there now is copied over to E:/app (which was already there), but still didn't show up in the dashboard.


Uh, what alternate solder points? I only knew of the two sets of points on both sides of a 1.0 board. Unfortunately, yea, that happened. I still want to TSOP my 1.0 system(s), but I'm scared of repeating that fiasco. Especially since the only other systems I have are 1.6 systems.

Use "Wrapping Wire" and connect them.