Print

[Brenf86]

runtime erro 339 on xbox 360 toolbox 3.0
I have my hitachi drive and everything all connected. When I click to go on toolbox 3.0 it gives me this error message.

Component "MSCONCLT.OCX" or one of its dependancies not correctly registered: a msising file or invalid.

Any ideas what this means and how to fix it.

Thanks

[nitussi]

QUOTE(Brenf86 @ Jan 1 2007, 02:22 PM)

runtime erro 339 on xbox 360 toolbox 3.0
I have my hitachi drive and everything all connected. When I click to go on toolbox 3.0 it gives me this error message.

Component "MSCONCLT.OCX" or one of its dependancies not correctly registered: a msising file or invalid.

Any ideas what this means and how to fix it.

Thanks

It did that to me on a computer i did a fresh XP install, but i dont know why. I had to use another computer.

i would like to know how to fix it too.

[Commando677]

I have a wierd issue with one of my backups.

I successfully flashed my 78 with the toolbox v3.
I put in the backup and it boots just fine then when it is loading to go ingame I get the disc is dirty error, but if I let it sit there the game finnishes loading and starts playing in the background, so it does work it was just slow it seems. My question is there anyway to get the disc error screen to go away without being dumped back into the dashboard or a way to stop it from popping up at all.

[Brenf86]

I'm using a computer I got today. Its new. I dunno why its doing it. It worked fine on my old computer but I didn't have a sata port.

[KIPPERMAN32]

QUOTE(Brenf86 @ Jan 1 2007, 09:43 PM)

I'm using a computer I got today. Its new. I dunno why its doing it. It worked fine on my old computer but I didn't have a sata port.

install this

HERE


should sort it.

[Brenf86]

Thanks flashed it finnaly.

What do I do with the original.bin and hacked.bin files. Will I need them again in the future.

Thanks woooo

[Crazy 8s]

QUOTE(Brenf86 @ Jan 1 2007, 10:43 PM)

Thanks flashed it finnaly.

What do I do with the original.bin and hacked.bin files. Will I need them again in the future.

Thanks woooo

Keep them safe, especially the original.bin file as you may need to restore your original firmware one day

[Schmo]

Just want to report another complete success using Slax 2.1 on a brand new 0078.  My old box semi-died with graphic artifacting after several minutes of play, it was an MS25.  (I am parting it out and selling the uneeded stuff from my new core system that I am using to replace the XBOX )

What I am using that has worked perfectly for the Hitachi 0078 AND the Samsun MS25 is an ABIT AV8 which has the VIA K8T800 Pro/VT8237 chipset.  

For the Hitachi: I used Slax2.1 to get the drive into mode B and then rebooted into Windows Vista and the drive was recognized without a problem.  All firmware dumping, verifying and patching worked flawlessly.

For the Samsung: Boot off a USB thumb drive and use the stock MTKFLASH to read and flash the firmware without problems.

So, now I have my box back together with the Hitachi running fine and I also flashed the Samsung with the same key and spoofed the firmware as an 0078 so theoretically, I could use that drive in there too.

I am torn as to whether to:
1) Keep the Hitachi in there and sell the Samsung (that would help recoup most cost on my replacement box)
2) Keep the Hitachi in there and just hold on to the Samsung
3) Put the Samsung in and sell the Hitachi
4) Put the Samsung in and keep the Hitachi.

I am at the point where I think I am going to do Number 2.  Sure the money is nice but having options in the future is nice and I think keeping the original drive is the best thing to do long term in case more strict checks get implemented in a dashboard update.

[manicminer]

guys,

sorry if this has been answered, but i couldn't find it.

i am having problems with the 78fk

i have an asus k8v-mx board with via onboard, a si3114 and a via vt6421a (not all in at the same time)

the onboard via will not get into mode b using slax 2.0 or 2.1
the via vt6421a will not get into mode b using slax 2.0 or 2.1
the si3114 will get it into mode b, then when i get into windows and try the flash, it ALWAYS fails at the checksum stage!!!!!!!!!!!!

please help.

Someone please tell me what board/sata combo i need and i'll go and buy it

thanks

This post has been edited by manicminer: Jan 2 2007, 04:21 PM

[tintan21]

I may have answered my own question

You cant make backups with the 78 drive with some testing I did on 3 disks
I used the slax 2.0 cd to put the drive in mode B then hooked up the 360usb module to the drive and inserted the original game extracted the SS with DVDINFO (which I think is not correct) merged the SS with the ISO with (SS Merger) and gave me a DVD file then I used DVD Decryper to burn I edited the text layer as per the tutorial saved and burned 3 times no Go!!!

My next question is If I extract the ISO using the HotSwap method like it shows in (clevermods) do I even have to extract the SS?? because it states the after you extract the ISO that it is an exact copy of the the original with dummy files and all. Please someone reply.

[OcnewB]

Well if you are good, maybe you could help me. I got the 0078FK in mode b using slax 2.1 I reboot, and it shows up in windows explorer. So far so good.
i run the maximus 3.0. I can see the drive and when i insert a game it will dump the firmware, then i get the same q you have: checksum validation. However when I click compare the checksum, it doesnt compare/validate (WTF?). So well i think hmm well lets go further (cuz i didnt see it in the youtube vid).So I skip the validation and use/open the orginal.bin file I just created. I start the next routine and create the hacked.bin file. Then i start the patch routine and -oh my- another warning appears. It seems that there are many (more than normal? (at least twice so many differences as in the tutorials and video)) differences and it asks me if i would like to keep original keys on the drive!? If i press yes and i start the patch process it gives an error and my pc hangs completely. If i press no and start patching my pc hangs.
WHats happening?>
Willing to give more information if needed.

p.s. i use winxp ga7n400pro nforce2 sil3512 satalink controller.

This post has been edited by OcnewB: Jan 3 2007, 09:59 PM

[sr_sparky]

QUOTE(OcnewB @ Jan 4 2007, 03:26 AM)

Well if you are good, maybe you could help me. I got the 0078FK in mode b using slax 2.1 I reboot, and it shows up in windows explorer. So far so good.
i run the maximus 3.0. I can see the drive and when i insert a game it will dump the firmware, then i get the same q you have: checksum validation. However when I click compare the checksum, it doesnt compare/validate (WTF?). So well i think hmm well lets go further (cuz i didnt see it in the youtube vid).So I skip the validation and use/open the orginal.bin file I just created. I start the next routine and create the hacked.bin file. Then i start the patch routine and -oh my- another warning appears. It seems that there are many (more than normal? (at least twice so many differences as in the tutorials and video)) differences and it asks me if i would like to keep original keys on the drive!? If i press yes and i start the patch process it gives an error and my pc hangs completely. If i press no and start patching my pc hangs.
WHats happening?>
Willing to give more information if needed.

p.s. i use winxp ga7n400pro nforce2 sil3512 satalink controller.

Does nobody read readme files anymore?

QUOTE

  RAWDUMP does not work fine with SIL chipsets yet, be aware of use
   the validate checksum feature to avoid bad dumps and bricks. We
   will be working on SIL chipsets later.

and

QUOTE

KNOWN ISSUES:
--------------
If the context menu is not shown when you right-click over a file just
open the application and do Options-Disable Windows Menu and then
Options-Enable Windows Context Menu.  Also RAWDUMP does not work
fine with SIL chipsets, be aware of use the validate checksum feature
to avoid bad dumps and bricks

I would suggest getting a via pci card, or use a different computer.

[OcnewB]

1st: I used: winxp ga7n400pro nforce2 sil3512 satalink controller.

I got the 0078FK in mode b using slax 2.1 I reboot, and it shows up in windows explorer. So far so good.
i run the maximus 3.0. I can see the drive and when i insert a game it will dump the firmware, then i get the same q you have: checksum validation. However when I click compare the checksum, it doesnt compare/validate (WTF?). So well i think hmm well lets go further (cuz i didnt see it in the youtube vid).So I skip the validation and use/open the orginal.bin file I just created. I start the patch routine and create the hacked.bin file. Then i start the compare differences and patch routine and -oh my- another warning appears. It seems that there are many (more than normal? (at least twice so many differences as in the tutorials and video)) differences and it asks me if i would like to keep original keys on the drive!? If i press yes and i start the patch process it gives an error and my pc hangs completely. If i press no and start patching my pc hangs.

QUOTE(sr_sparky @ Jan 3 2007, 10:54 PM)

Does nobody read readme files anymore?
and
I would suggest getting a via pci card, or use a different computer.

Apperas Sil Controllers are not good for the 0078 Drive So:

i bought a promise pci sata controller and the story continues

With the drivers installed, disabled onboard sata and connected the drive to the new promise controller. the pc wouldnt even go past the sata detection and hung. So i thought well it would go to modeb while using onboard so for getting it in modeb i use the onboard and for flashing i use the promise (smart eh ;-)). There we go:

I enable the onboard sata (sil) connect the drive to that one, put drive in mode b with slax and reboot. Now the drive is in modeb, while booting i switch the drive to the new promise sata controller. It is recognized in windows and it is in modeb. Hurray! Now the checksum validates (so the FW dump is correct (as opposed to the fw dump that the SIL controller made)) and i start the patch routine and OH NO!! behold, another new error:

Not all patches were resolved, Cannot continue

What the hell? So someone got an idea?

This post has been edited by OcnewB: Jan 4 2007, 02:01 PM

[PalmiNio]

Well done flashning my friends 78 now.

Done on  HP d.4196.se using the ATI SB400 SATA controller. Dunno what chip but in Slax 2 something with SiL showed up. In Slax i did never get to the login screen but that didn't matter.

First try the comp freezed using the dubbel close and one more while closing. Used the one close then force close and everything worked with a sharm.

Thanx alot to all behind the programs and the guides and the test on this forum

[conmebol]

Opened my xbox360  for the first time yesterday. Of course it was hitachi 078, but I ended up having little problem flashing it with my ICH8 sata from my motherboard. It recognized it right away on the BIOS. Thank you for the awesome program.