Infectus Modchip Forum

Ohhhhhh...

DOWNLOAD LINK:
http://www.infectus.biz/downloads/Argon-Wasabus-D2C2-BETA2.rar (http://www.infectus.biz/downloads/Argon-Wasabus-D2C2-BETA2.rar)

finally we are ready to start BETA2 firmware testing... this ZIP FILE has inside all necessary to test ARGON on the new D2C2 boards... and not only this!!!

This firmware include the D2C support with ALL THE OLD BUGS FIXED, so is good for all users that didn't install ARGON 9 WIRES before cause the EJECT etc bugs reported!! :)

I remember to all to read carefull the README.TXT file in the RAR file... !!! This is a BETA2 version, not final version, we are waiting here all the results on D2C boards and D2C2 boards...

BYE BYE

THANKS!

Thank You  ;D

With all the complaining on how long this has been taking I would have suspected allot more post then this. Granted it was only posted around an hour ago but I would think the way half had posted in the other thread they would be checking every 5 seconds for the update.

hi there, is the dat file missing in the archive.? or am i missing something here......

wasabus_a125argon.dat

You will need to note that this beta release will only work on the 250 chips (red dot)

oh.....well thats knackered that then...... >:(

Thanks :)

But wasn't BETA3 the one the betatesters deemed to find very stable ?

Thanks for your great work.

At last.... thank you !  :)

Right now the BETA is working only on A3P250... we need to work on only one ACTEL MODEL before porting the code on A3P125...

BYE

This is the final beta we received + support and latest (1.2?) wasabus for standard D2C

AHHHHH ANOTHER IMPORTANT THING!!!

We will release in the next hours a new update for the problem of the BOOTING SEQUENCE... I mean the problem where is necessary to turn off and on the console for a correct game booting...

So I suggest to test this update after BOOTING, about possibles issues with games etc... and wait the next release for to fix the boot issue..

BYE

so when will this be ported over for a3p125.???

Like mentioned after enough positive feedback

Dunno if place for it is here but...
I'm using a clip. When applying clip the Wii has typical D2C2 behaviour before flash update (short cd spin, blu led) .
But after flash update : NO spinning drive, no flashing LED. Unable to eject CD.
Drives plays DEAD. After Clip removal Wii is working again...

i have sodlered 9 wires way not clip but having same things

drive inside wont read disc
power off and on
sometimes blue led lights up then game boots

sometimes it wont

when try to change discs disc goes out and drive wont take another have to cycle power then

I had the same, but if you erase the SPI flash its spinning again ;)

find something out

when led wont go on here i press reset button instead of power cycle and it boots fine

power wii on put disc in blue led stays off then i power cycle blue led still stays off it tries to start spin the disc when its starting to spin i press reset button and it works tried now 6 times

Well, of course this bug (and some others maybe) needs to be fixed, but I'm glad they have released this beta version. Now we know a final and stable solution is almost there. At least, I think and hope it is.

thanks for finally releasing the firmware...  250 and beta is better then nothing...  Guess it's back to the old waiting game for me unless I fumble through my chips and find a 250.. don't think it will happen though.

You guys found any major bugs yet?

 I haven't tested anything yet, but the 'booting' bug seems to be the only major bug until now. So that's not bad...

OHHHH , All chips I have here are 125 version , how much time will need to wait ?  ::)

Well, I think you have to wait forever, because they only release firmware for the 125 and 250, whahaha  :P

Guess this is a mistake of you...

like it lol....... ::)

Well.. NED-ITA just started 15 minutes ago, so I think we won't have to wait for a firmware update tonight (unless the Origa brothers don't like soccer ;)).

                      Yes, thank you for the A3P125 models
 >:(

 :D :D :D :D

holland 2 - 0 italy

sssssh, don't piss them off ;)  (hup holland hup  :P)

he he he

Yes and greeetings from Holland hahahahahaha  ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D

En op naar de 4-0

i have a 13 wire install, i found the original post misleading, is this suitable for my install or does it require a 9 wire mod with an spi flash?

Wasabus is 9 wire/SPI only.

Wahoo.. just found a 'red dot'... :D .. Off to test!

Ouch 3-0. I'm sorry Italy we are just too good ;D

 ;D ;D ;D ;D ;D ;D ;D ;D

I think we just blew our last chance on getting a fixed firmware tonight :D
(ah well, 3-0 is worth it ;) )

not only tonight I think....

Ok just been testing this firmware on a LEH176... standard D2C.  I know this is beta but thought that it would atleast spin a disk.

I've tried turning it on with eject, resetting .. powering off, hard powering, soft powering and the best I got was It ejected the disk halfway and I had to pull it out the rest.

I also kept on the injectus and also took it off using all the booting methods above... if I turn it on by inserting a disk it may take it but then not spin or allow the ejecting of the disk.

I noticed that the blue light did come on the once when it sucked in the disk but not since...

I just reprogrammed the chip with 1.1 and it works fine.

Might just be the D2C v1 that it sucks with.. I'll try a D2C2 and report back.

Chris

Tried erasing and flashing again ? See http://www.infectus.biz/forum/index.php?topic=2035.msg14028#msg14028

Well, same experience on a D2C2. This really sucks.

Thanks Moely.. i did try reflash the entire chip and then just double flashing the SPI.. even tried erasing the SPI and try and boot but below is the only way I could get any response (note that this drive works fine with Wasabus 1.1)

Ok I've figured at least something out and been able to get the disk to spin up every single time... This involves simply keeping the infectus and connection to your computer..  Once the console is switched on you can disconnect the infectus and/or usb and eject/insert disks til your heart is content.

the moment you power off the console and try turn it back on again you can not insert or eject disks and nothing spins... again, (disconnect the power before plugging injectus in) plug in infectus then the USB and whollah...  boots up.

I must note that no disk has booted but stopped after about 5 seconds.. occasionally it will double spin (click spin, stop, click, spin for 5 seconds then stop) but still no booting.

I'm a little disappointed as I was under the impression that Infectus had been working on this for the past couple of weeks but it simply appears that this is a rush release derived by dumping D2Pros recently released D2C2 compliant modchips and then reverse engineering the Actel.

I don't want to flame just yet as I do appreciate the beta release but it would be really nice if some of the initial 10 beta testers would pop in and state how or if they got this code to boot and under which chipsets.

For the moment I'm not going to waste anymore time and just hope that the above may help someone. 

Chris

Thats a point why does the file say "d2pro_D2C2_f.BIN" ?

OMG.. just noticed that as well.. talk about blatant copying buggy firmware..  :o

LOL , just d2pro hacked dump ;D

As krazy said in wiinewz.. sure, they've dumped the SPI but they've still had to configure the Actel from scratch which is a feat in itself.

To be honest I don't really care anymore, I just want a working modchip preferably the Argon and preferably soon.

I think spaghetti's gonna hit the fan when Infectus realise the coders (or maybe Oscar) forgot to change the name of the SPI flash.. lol

I have same problems with an old d2c drive.
It works well with wasabus1.1 but it doesn't boot any disk with this new release.

Maybe we have to program argon modchip with the 1.1 version of .dat and after we have to load the wasabus beta2 fw .bin?

Thanx.

First they loose to Holland, then this.. not a good night for them ;)

You can't mix and match the .bin and .dat files I'm afraid.

Maybe I'll waste some more time in the morning by trying this on a D2C2-Japanese.

Will post my results in the morning.

Am I correct in saying that no one has actually successfully booted a back up on this yet?

As a side note.. D2Pro is still having issues as well. More people start reporting the D2Pro chip KILLED the drive.. Hopefully Infectus forgot to copy the part of D2Pro's firmware that is responsible for that part...

I think that's the hardware and not the code itself...  there are literally 10x of thousands of D2Pros out there that are D2C2 compliant and only 2 maybe 3 people have experienced this problem.

Not to say it's not an issue for D2Pro but I really don't think it's in the code.

This d2pro problems looks so scarry...  :o
Guys post some info about Argon D2C2 installs and wii serials too  :D

I FLASH MY ARGON WITH WASABUS BETA2. MY DRIVE IS A D2C2 THE DRIVE IS DEAD IT WILL NOT LOAD ANY GAME WITH THE PROGRAMMER DISCONNECT BUT WHEN I CONNECT THE PROGRAMMER TO THE MODCHIP AND COMPUTER IT LOAD THE GAMES, DONT BOOT ANY BACKUPS BUT WORKS WITH ORIGINALS.

 :'(

I've tried 2 d2c2's with no luck, no spin, only spins when injectus is connected. this is cactus

www.consolefreakz.com

ok so it works after all, just need to program the chips with the infectus programmer included in the zip file, even though the previous ones seem to program it ok it won't work, reflashed with new programmer and everything is dandy.

Only problem is, as stated in the readme, games won't boot unless you switch the console off and back on every time you change discs. But a good start none the less team infectus.
www.consolefreakz.com

same issues as previously for us - just now need for boot issue to be fixed and I will start putting smiles on customers faces :)

please remember fellow testers;

i. flash ONLY with flashing software inside .zip file
ii. both injectus switches off before flash
iii. disconnect and reconnect injectus between flashes
iv. disconnect injectus injectus after final flash

not following the correct programming steps can seriously mix up your results

anyone had success booting SSBB? I've tried a few copies and they all just sit there and click

If I get OK or SUCCES after each flashing step, all is good, right ?

What I did :

Unpack the archive.
Start up the programmer exe.
Connect Injectus without chip.
Programmer detect and want to update injectus. I press OK.
I shut down exe and start it again.
Pull out USB and plug it in again.
Connect Argon to Injectus.
Program the wasabus dat. Takes a while. Shut down the Actel after it is flashed okay.
At this time, the SPI is still 'Unknown'.
I try to Erase the flash, but it crashes with exception (makes sense, since SPI is Unknown).
Restart programmer exe, now it recognizes the SPI Flash.
Erase the SPI Flash.
And write the flash with D2Pro_D2C2_f.bin :)
Gives me a dialog that it went okay, I shut down the programmer and disconnect the Argon.

(at that time it was 2am and time for bed ;) )

edit : Ok, seems to work okay most of the time, but the booting issue is really annoying. Any idea on how many hours Oscar was referring to when he said a fix would be out in the 'next hours' ? :)

All that talk about afraid releasing stuf becouse people will copy from Infectus team???
They do the same.......

But who cares if it works greate and keeps updating/fixing bugs

the major thing all members would note here, is that the dev team has a beta3 stage and a working FW (limited to red dot 250pin but worked, buggy but worked ^^).

So like i say in a previous post, with the next beta stages, there's a probability that they release a stable firmware near the 16th of june 2008. it's impossible to release before a bug free FW (or they are the best reverse engineers and coders i've ever seen ^^)

if we are at 75% of a stable release, there's 25% left to go, this is how it worked, whatever you code. the last 25% are the hardest one to optimize and debug !  :P

I'm Speculating on a stable release near the 16th of june and the 21th of june.

PS : i'm not a team dev coder, neither a beta tester. Just speculating around you ^^ and have some strong coding experience

Oscar ? The next hours ? You've had 16 hours so far...  eager to test the bootfix :)

Please help, what am I doing wrong ? I still get a 'dead' drive when I program the Argon as mentioned here. I have tried everything (power off, power on, reset etc. etc.). I definitively use the new programmer.exe file. When I disconnect the Argon the drive works fine.
It is a D2C2 drive.

I already have modded more than hundred D2C drives with success (Argon 13/17 wire). I am sure the soldering and all connections are OK. I checked it with a multimeter and microscope.

I just asked him and he said this evening (their time I presume)

DEV are working on BOOTING BUG... the target is to release this evening a new update... but like you know is difficoult to predict...

Sure you don't need to wait days... :)

BYE

Thanks for the update. If you need another betatester.. just PM ;)

Yo , how about Aragon 125 version ? I have like 100 chips here all of them 125 version.  :-\
wasabus-d2c2-beta2-a3p125.dat WANTED


Yeah me too, I did some thousands installs, since a PS1 ( I have some demo pic's if need ).

still ripping the d2pro code from the actel lol.......

I repeat my earlier request and hope someone can answer this:

Please help, what am I doing wrong ? I still get a 'dead' drive when I program the Argon as mentioned here. I have tried everything (power off, power on, reset etc. etc.). I definitively use the new programmer.exe file. When I disconnect the Argon the drive works fine.
It is a D2C2 drive.

I already have modded more than hundred D2C drives with success (Argon 13/17 wire). I am sure the soldering and all connections are OK. I checked it with a multimeter and microscope.


There are more pro modders with the same problem !!

False... I have in this moment the new firm in a old D2C with chipset GC2-D1A and not read any game... the reader is death. Why??

http://www.infectus.biz/downloads/Argon-Wasabus-D2C2-BETA2.5.rar (http://www.infectus.biz/downloads/Argon-Wasabus-D2C2-BETA2.5.rar)

Hi guys...

there the new UPDATE of BIN! :) Support of SSBB and all DL games... about BOOTING'S PROBLEMS we need to wait some hours for next release... sure tomorrow news...

BYE

Thanks

and what about old d2c support? does this version work, such as wasabus 1.1?

cheers Oscar

i will give this a try, as the one i tried yesterday, didn't want to work at all in my latest console.

I see the .bin file has now been renamed  ;D

Thanks Oscar...   I can't believe that the only improvement between beta 2 and beta 5 is that it now supports 1 additional game that is on dual-layer...

Not really a priority but will check it out and report back later tonight.

I tried quantronics method of loading the code to a T and had no joy as stated earlier.. could only get the drive to respond if the USB & injectus connected.

Will report back.

It's beta 2.5.. not 5...

my mistake..  why give us 2.5.. give us 3?

i have the same problem.
i could only get the drive to respond if the USB & injectus are connected.
no backup will boot.

my console is a LEH 188xxxxxxx with D2C2.

your bigbaerchen

well this is the same as d2pro....they just updated there spi for ssbb....lol......

i program the chip with this new beta version 2.5 and no run with the D2C 2 boards.
the serial is LEF10093208 9

anybody can run this modchip with d2c2 boards

too...

too....

no, same problem.... didn't try to connect injectus and USB yet, but should not be necessary  :-[.

I think 10 beta testers around the world aren't enough...

 :D
Tried D2C and D2C2 LEH1858xxxx, it seems all right for me EXCLUDING  boot and eject problems as exactly said by Oscar, but they will be resolved tomorrow (we hope... )
 we wait for ... ;D ;D ;D

I tested it too, no good news from my side though:

LEH1623xxxx
The Wii doesn't show any activity without programmer attached.
The Wii doesn't show any activity with programmer attached, but not connected to the PC.
The Wii doesn't show any activity with programmer attached, just plain connected to the PC.
The Wii works normally connected to the PC, BUT ONLY when infectus programmer program is running!! Though no backups working here, originals do work!
Checked all connections with a multimeter and are OK!

I can't get this error to occur for me

I really wish I had some Korean D2C2 Consoles as they seem to the the MOST D2C2 consoles on the planet - anyo

anyways, from the LAH-2046xxxx side of the globe - all is STILL good

Any testers out there (from the chosen ten that is ;)) with LEH/LEF ?

That's a D2C. Do you get the same results with a D2C2 ?

Get the same problems, got two d2c2 drives.
 - Only spinning whem jtag programmer connected.
 - If not connected drive is "dead", but after a while sometimes he raises from the dead and spins :)


 But never booted a copie!

Greetz

I had a similar situation on both D2C and D2C2 but you can get a copy working by doing the following:

- Insert DVD game copy in drive
- Set Wii in standby
- Connect JTAG to Argon and PC
- Turn Wii on, drive will not spin yet
- Start infectusprogrammer.exe (only startup, no programming or so)
  Drive will spin and stop
- After drive stops, close Infectusprogrammer.exe
- Press reset button on Wii. It will boot the game copy

This works for me most of the time. But when will all these boot problems will be fixed...?

I don't have any D2C2's I am sure that are D2C2's, but I am having doubts about this one, it could be one of the early D2C2's

ROFLMAO, but a GOOD FIND! This means it is a simple problem in the coding. Thanks for that! I am sure Infectus programming team can get this problem worked out with that nfo.

On D2C2 Wi LEH189XXXXXXXi:

result using beta 2.5:

- Drive "dead", nothing works (EG. ejecting, spinning)


So It's seems like this BETA 2.5 doesn't work at all :-\

WTF ? How in the hell did you came up with that idea ? Kudos for the find though ;)

Well, maybe I had some luck... but I also have read all the comments on this thread; Someone said someting about using the reset button and other people about connecting the JTAG programmer. So you could say I have combined these experiences and tried some things. But it's funny it works though  :)

Nice :)

However, I sure hope they solve these issues fast, because it's gonna be one hell of a task explaining this sequence to customers  ;D

Get mixed results with the boot sequence!
Almost evry time i exit InfectusProgrammer.exe the drive stops directly with spinning and plays "dead".
But when i start the InfectusProgrammer.exe the drive spins like hell, but no copy reading!
Weird problem :)

uhmmmm. are you sure you're install is ok, because when I start the infectusprogrammer.exe the drive does actually spin but after a few seconds it stops. But I have to say I only tried it on D2C2 (not also on D2C like I said before).

I have used the latest 2.5 beta version of the firmware. And I think on the installation diagram point C is somewhat confusing. You have to use the via right next to the arrow, not the one that is underneath the arrow. And of course shorten C & D on the PCB.

Yes, install is 100% ok!
But i wait till tomorow hopefully the boot fix is then ready!
Otherwise i will test it tomorrow again!

Yes, of course this method is not very useful for customers, but for us it's better than nothing.

Nice find Moely.  It's kinda shit that these so called '10 beta testers from around the world' can't help with some input in these forums.

Is Quantronics a beta tester?  I thought I seen a post earlier saying that the beta released is the same he was given??

Anyway collectively I think everyone has wasted a fuck load of time and Infectus probably don't take any of these suggestions on board directly.

Let's just hope they can sort their shit out soon and before the 16th of June!

Chris

Yes, it still amazes me that it takes such a long time for them to develop a stable and good working firmware for D2C2 models , while D2Pro already has a good solution. However, I heard that there were some issues with these chips about DVD drives being killed. But probably they are PCB/Component related, aren't they ? Bad solder points ?

Anyhow, I don't think I will change to D2Pro's, but it would be nice if Infectus Team comes with a stable solution soon. Some customers want to have their Wii modded asap and don't care what chip is built in as long as it works fine. So Oscar and companions, please hurry !

Hi, I am sorry to sound like such a noob (but really, I am). I was wondering, is there any way that I can possibly use a dvd to install this update? I believe that I have a GC-D2C2 board, and cannot run any discs. Originals and backups both don't work. Would a dvd update still work? Is this possible? I bought injectus, but I am currently experiencing difficulties opening my wii (a screw seems to have been stripped). Any help is greatly appreciated!

Sorry bud, your gonna have to find a way to crack that wii open. The only way to program the Argoin is via Jtag with Injectus. Might try a power drill or a dremel to cut the head off the screw.

Btw, assuming you installed the chip...Your saying that after the install you put the whole wii back together without testing it first?

Darn, that's bad news. Thanks for the info though.. Yeah, I didn't test it first. I used a wii-clip. I am a big noob when it comes to modding (especially with wiis). To test, do I just hook everything up to a tv and attempt to use it (basically starting the wii without the case)? Well, the screws that I am having trouble with are the little black triwings that connect the face of the wii (dvd slot) to the side. I guess that I will try the superglue/allen wrench trick. Do you know of any others?

I am stuck on trying to program the chip!! Load dat 2.5, program chip, takes a long time but it recognizes SPI, erase, then write..error everytime. Do I need to install chip first? does the newest firmware even work on old d2c or should I stick with the 1.1 "final" version. Also how do you do the alternate install? Do I need to clean the points on the bottom of the board first, I can't get the solder to stick?? thanks.. oh argon chip is the 250 red dot

FLASH MY ARGON WITH WASABUS BETA 2.5 THE, BACKUPS GIVE ME A BLACK SCREEN ERROR EJECT THE DISC AND TURN THE WII OFF. AND NOW ORIGINALS DON'T WORK THE BLUE LIGHT ON THE ARGON CHIP STAY  ON.
ORIGINAL GAMES WORK WHEN I CONNECT THE MODCHIP TO PROGRAMMER AND COMPUTER.
BOARD D2C2

D2Pro is having lots of issues (still eject problems, killing drives, etc).
Argon .. ah well.. you all read this topic.. so you know :)

Really wondering if this will be solved correctly. Also, I would like to know how exactly Infectus is reusing D2Pro's firmware. Decompile, read, understand and create a fixed Argon version ? Or just decompile, recompile and hope for the best ? Read between the lines and you'll know my fears ;)

Already tried this ? :

http://www.infectus.biz/forum/index.php?topic=2035.msg14136#msg14136

ok, it's not a nice solution, but at least something is functioning.

Hello, wake up please  ;) ....

I have installed a LOT of Argons on D2C boards, without using the easy solder points.

Below is a picture of my install of the Argon SPI modchip (2.5 beta fw) on the D2C2 board :

(http://www.proconsoles.com/pics/5.jpg)

I did the following:

1) Burned Super Mario Galaxy (PAL) on 8x speed with my Pioneer 111d burner on Verbatim DVD-R media, with Imgburn 2.4.1.0

2) Put Wii on standby (red led)

3) Turned it on, green led, drive made noice in 2 phases for about 3 seconds.

4) Inserted the backup, which did NOT spin

5) Removed power cable from Wii

6) Inserted power cable


Below the results of some tests after inserting power cable, without programmer connected to Jtag cable :

- After 6) , power led turned yellow (no network was configured), turned wii on, green led, nothing happened (waited 10 seconds)
1 time
- After 6) , power led turned red, turned wii on, green led, nothing happened (waited 10 seconds)
7 times

Then I connected the Injectus programmer (both switches to OFF) without USB cable, and did the same tests :

- After 6) , power led turned red, turned wii on, green led, heart a very short click, hoped drive would spin but nothing happened (waited 10 seconds)
8 times this happened

Then I put switch 1 to ON :

- After 6) , power led turned green, heart a very short click, hoped drive would spin but nothing happened (waited 10 seconds)
1 time

- After 6) , power led turned red, turned wii on, green led, heart a very short click, hoped drive would spin but nothing happened (waited 10 seconds)
8 times

- After 6) , power led turned red, turned wii on, green led, nothing happened (waited 10 seconds)
1 time

Then I put switch 1 to OFF and switch 2 to ON :

- After 6) , power led turned green, heart a very short click, hoped drive would spin but nothing happened (waited 10 seconds)
1 time

- After 6) , power led turned red, turned wii on, green led, heart a very short click, hoped drive would spin but nothing happened (waited 10 seconds)
4 times

- After 6) , power led turned red, turned wii on, green led, nothing happened (waited 10 seconds)
4 times

Turned both switched to ON :

- After 6) , power led turned green, heart a very short click, hoped drive would spin but nothing happened (waited 10 seconds)
1 time

- After 6) , power led turned red, turned wii on, green led, heart a very short click, hoped drive would spin but nothing happened (waited 10 seconds)
1 time

- After 6) , power led turned red, turned wii on, green led, nothing happened (waited 10 seconds)
8 times

Then I turned both switches to OFF, and connected programmer with good USB cable to a PC which is up and running :

- After 6) , power led turned red, turned wii on, green led, heart a very short click, hoped drive would spin but nothing happened (waited 10 seconds)
1 time

- After 6) , power led turned red, turned wii on, green led, nothing happened (waited 10 seconds)
9 times

Switch 1 to ON and switch 2 to OFF:

- After 6) , power led turned red, turned wii on, green led, nothing happened (waited 10 seconds) (sometimes it took a while before the red led turned on, and sometimes the red led did not turn on)
10 times

Switch 1 to OFF and switch 2 to ON :

- After 6) , power led turned red, turned wii on, green led, nothing happened (waited 10 seconds) (sometimes it took a while before the red led turned on, and sometimes the red led did not turn on)
10 times

Switch 1 to ON and switch 2 to ON :

- After 6) , power led turned red, turned wii on, green led, nothing happened (waited 10 seconds) (sometimes it took a while before the red led turned on, and sometimes the red led did not turn on)
10 times

I keep doing some tests, but I have some feeling that it has to do with power consumption of the Argon modchip.
Maybe the D2C2 boards need more power then the D2C boards, and leaving less power for the board, which is malfunctioning then.

I say, it could be a cause, is there somebody who could  attach an external power supply to the Argon modchip and do some tests ?

Moely, maybe you ?
I will call you later today.

You could bridge/or use another wii's 3.3V and GND to perform this test. Obviously you would need both wii's to be open and powered up.

2x 1.5 batteries + croc clips should do it

Got D2C2 Wii for sure cos my D2Ckey+Wii_clip not work in this drive, but works in other D2C Wii.

Got Argon250+SPI
Success update to Actel and SPI

Mixed results.

1. When and if Wii decides to let copy disc in, it plays.
2. If Wii let the copy disc in and no spin, it no play + no eject. (Must power down holding PWR on Wii.)
3. Must PWR up several times then the copy disc will spin, which usually means I can load game or eject disc. But if I eject disc and reinsert it, it stops spin and no eject again. (Must PWR down Wii and then PWR up Wii several times before it works.

Nice try. Keep trying.  :)

this sounds much the same as d2pro v2 chip....only the d2pro sounds a lot more reliable....

just chipped a d2c2 wii with the d2pro v2 chip and i would say 90% of the time it boots up fine, no problems,

but on eject and inserting a new disk , the drive will:

a: either lock up completely and will not accept a disk , needing a power cycle to bring it back to normal

b: accepts a disk , then doesnt read it, then drive locks up, same as above , power cycle needed.

this is so random that as i say it works 90% of the time.

other than that it works....tested it for a few hours today and played all of my backups....

so there you go......put up with the problems or stay away until a update is out....

ok, update or not, please give us some news....
And if you don't want to give any news today, please don't use the word SURE next time. It creates false expectations.

They are wearing us down.. till the point we just .. don't... care... ;)

Try this power connection point. I have been using it pretty much since I started installing (500 drives ago) and havent run into a problem yet. I also use it with the D2Pro V2 on the D2C2 boards and after 25 or so drives have had no eject issues.  I dont know if it will help, but you never know.

http://img165.imageshack.us/img165/3241/argonaltpowerdb1.jpg

(I would have posted the image here but im not much for html)

@biklotus : do you have a pic of an installed d2pro (on d2c2) ? Will be receiving a few shortly and if you say you have no errors at all with them, I might as well learn from the master  ;D

So you are connecting it to the +5v now? Is that safe, I mean doesn't that burn the chip?

NO its not the +5v look at the picture  ;D

Ahhh, now I see lol, well good I asked :P

I can only say..

testet 3 Argons ( new ones with SPI ) and flashed the new 2.0 Beta bios on it.
LEH 189xxxx console worked. But have to insert game, turn off console, turn on console.
i flashed on the same Chip the 2,5 bios . nothing worked.
I deinstalled the same chips and installed them in LEH 156xxx console. nothing worked.
I flashed Beta bios 2.0 bios... nmothing worked.
I flahed again the old Wasabus 1.1 bios for the 3 older wiis LEH 156xxx.. Nothing worked..
what the fuck ??  the argons dont work anymore !! i will try the old 17 wires bios again
i installed D2pro in all 6 wiis with green label on the same cables.
Every one worked.

Is that your promised BIOS ???

You should try again to find a better solution then that
we installed allready over 60 D2pro green label chips in LEH 188xxxx and higher consoles. They do all work !!!

I did the test, with the Argon SPI power taken from another Wii board.

Following config:
- Argon SPI programmed with 2.5 beta
- no programmer connected to Jtag cable
- Super Mario Galaxy PAL DVD-R in the drive

1) Connected the power at the back, led turned red
2) Turned Wii on, led turned green, nothing happened with the drive, went to home menu, and after 3-12 seconds I saw the message:

"An error has occurred. Press
the Eject Button and remove
the disc, then turn the Wii
console off and refer to the
Wii Operations Manual for
help troubleshooting."

This happened all the time (tried 10 times)

When I turned the other Wii off, so that the Argon did not have any power, nothing happened when going to the Wii menu.
And when I went to Disc Channel, I saw the message :

"Please insert a disc." with the image of the discs standing still.
This happened all the time (tried 10 times)

Strange, strange, strange, what I also was thinking about, that Nintendo implemented a very little program into the bios, which detects the modchip, and every time th Wii starts up, that it executes another routine to confuse us all......

But anyhow, taking an external power source for the Argon, is not the solution.

If Nintendo has done that the d2pro wouldn’t work either, and the chip is working!

STOP crying...its a BETA, a snapshot of the firmware which the developers are working on.

So stop everyone posting that the fw is not woking.

Yes, you're absolutely right. But it is quite frustrating that they aren't able to develop a stable firmware yet, while D2Pro already has finished theirs one or two weeks ago. I think most of us want to stay loyal towards the Infectus team and the Argon modchip, but our customers don't want to wait if they know there is another working solution. They don't care whether it is an Argon or D2Pro or whatever. Most important for them is that it works. So we are almost forced to switch to D2Pro, although we would rather stay with the Argon chip.

Anyhow, I hope there will be a final stable release soon and would appreciate it very much if Oscar would give some feedback/news more frequently, especially when he explicitly has promised this. Yesterday he said there would be a new release in a few hours or at least some news for SURE today. Well, haven't heard anything yet.

you've got to wait until 16th of june 2008 . The dev team don't read your post at all ! you loose your time, just give D2Pro to customers and then when Infectus will release their (semi) stable firmware in less than 1 week now, just give 2 more time Argon than D2pro ^_^

Why have they just 10 beta testers ? because they are not very numerous in the team coding !!!! keep that in mind !

What want customers ? Argon ?! why not, but it's still not working yet on D2C2, soo give them some working chipsets (which kills some DVD Reader... :p )

Team infectus ! do your best, i'm sure you can do it ! ;D

Did you know that many of the screws on the Wii require a special "tri-wing" screwdriver (available from mod-chip sites for about $4) and a normal Phillips screwdriver will not work?

yeah I was also curious how you could strip a screw in a Wii... ;)

On another note, keep up the good work infectus, at least we hear from you once in a while and it's good to see our chips being developed further. For all the whining people here I guess you should just order a batch of d2pros for your desperate customers (i guess with the warning it may kill their drive) until the firmware is out or just patiently wait. It is a shady business where state-of-the-art coding is required for the constant Nintendo vs. Modchip battle, and customers should also realize this, no point in complaining to Oscar as I'm sure the team is working as hard as they can. If u don't wanna wait, fine, but don't complain about not reaching deadlines and take up everybody's time.

Latest news from infectus team:
today they should receive some "not working" wii's.
So be patient! Soon they'll fix main bugs.

Thanks for the info, did you get this from direct contact as a reseller?

Learn Italian : http://www.infectus.biz/forum/index.php?topic=2036.msg14249#msg14249

Lol, well now you got me there with this remark, I get it! Niet zo vervelend doen tegen je mede-Hollander lol!

Vrijdagavond zijn we weer 1 volk ;)

als ze winnen ???
Why doesn't infectus post in the english forum ,but instead in the italien forum.
We want answers too.  :(
But i am sure they will deliver a stable firmware soon.

Wij zullen winnen!  :P
Anyway I'm pretty sure Infectus doesn't read that shit at all. He's just too busy.
But don't worry guys. I'll keep on translating future news for you.

zeker zullen wij winnen! :P

thanks for keeping us posted, interesting news is always welcome!! :D

Also if we don't answer here, we read every day.  We have answer at only one post in italian section. These days are very busy for us.

Now a little question for who has tried the new beta.  Which version of programmer have you used to update and write the flash (Help->About)?

The one that was provided in the rar file. 3.9.4.4

Same here, haven't tried the other ones. Would you advise it to try that? As it takes a lot of time to flash and all, I don't wanna waste my precious time on another dud :P no offense though.

No, do not waste your time.
3.9.4.4 version is the right one because it corrects a severe issue while writing flash.
Older versions only lead to malfunction.
Infectus just explained that in the italian forum.

We have try now a no working wii.  Without touch any solder or reprogram it, we have fixed the problem moving one wire.

Look the (bad) image to understand what i mean.

(http://img90.imageshack.us/img90/7821/okgy2.jpg)

(http://img133.imageshack.us/img133/3585/koge8.jpg)

So, if your drive is dead, try to move this wire in some other position.

We'll find where is the real problem, but at the moment you can try moving the wire too.

Ok, we will try, but this does not solve the booting problems I guess...?
This solution is for people with a drive that does not respond at all, I assume ?

Is the OK good and KO not good? sry but it just isn't clear this way, KO is Knock Out from my pov so lol.

And did you guys solder it to the leg? Not on the normal point?

So it's noise on the clockwire causing problems ?
Maybe this an idea. Rotate the chip 180 degrees, having the jtag face the right side.
Now remove the three wires on the IC and connect them to the underside alternative via-points. Now you have room enough for the other wires on the topside to make sure the wires don't cross.

I will test this again myself tonight (now at work). If in the meantime you guys could release a bootfix (al be it beta), this would be great :-)

What i suggest is try to move the wires in some other position. Not only like the photo, but try others if it not work.

My install is almost same as the "OK" pic above. I try moving that wire and it works better. The drive still locks up. I found if I count to 10 after shut Wii down, then power on it will spin and boot disc and I can play no probs. I can also eject the disc. But reinsert will lock drive again. Suppose counting to 10 then power on again will not kill me for now.  :)

Are you on beta2 or 2.5 ?

Who are you? Mike Tyson dutch version?  ;D
In this context KO means the opposite of OK (read it right to left).

I am using beta2. Is beta2.5 better? I don't see it. Where can i download beta2.5?

IF i use V2.5 on my D2C drive it doesn't spin unless i have the jtag connected to the PC and the programmr on but if i go back to version 2.0 it at least works without the JTAG connected but only got a backup to run once on V2.0

http://www.infectus.biz/downloads/Argon-Wasabus-D2C2-BETA2.5.rar

Supposedly has DL support, but seems to work worse than 2.0..

To use argon , injectus  must to be NOT CONNECTED!!!

OK

with my D2C drive using beta2.0 i can get it to work all the time now execpt fot the boot sequence problem by messing around with the cables and making sure none were close to each other before that the drive wouldn't spin at all only every 1 out of 10

Try waiting 10 seconds b4 power up again. (Leave disc inside Wii)

Yes if i leave disc in drive then reset all is fine


Anyone have any idea why i need jtag connected to get drive to spin using v2.5

My wii is a D2C2 with serial LEH1888xxx.
I have soldered the cables without crossing and trying different length of cable to point C but the drive is still "dead".
It only reacts when i connect the injectus to Argon and to PC.

your
bigbaerchen

Some PS2 chips used to be very picky with the clock wire. I used very thin coax wire for the clock with the shield soldered to ground. Maybe this kind of wire could help.

K this is a little off topic for this post but i'm gonna ask anyways...How do I "downgrade" my argon back to the 13+4 1.8 FW? Basicly im having no luck with the 9 wire stuff and I can't give buggy wii's back to my customers.

Anyways, I know I can simply reflash the chip with the 1.8 but im wondering if I have to change the bin file and if so where can I get the original bin from? I have a couple people comming in later today so im hoping I can get this sorted before they show up.

with the 13 wire install you only have to worry about the 13 wires. The bin isn't used.

i've got a d2c1 (got a serial number under my "g2c..") and did a 9 wire install with the d2pro_D2C2_f.BIN on it and i'm expieriencing the boot problems too, moving the wire helped me to boot up my drive again witch didn't move before with the other previous software.
i can't eject my copy dvd anymore i can't c it in in the wii menu cause it sais its not recognized, tommorrow i'm gonna try to get an original in there and make it work
guess i better solder it to the leg then to the alt point if i look at your install with same problem.

tommorow i will receive some argons with spi from Proconsoles (thnx Eddy)
So finally i can jump in this thread to help figuring out what is wrong
i have several Revision D2c2 boards (dark colour coating) d2c with letter beneat etc etc  and lots of ideas what could be going wrong

in the GOOD old ps2 time we had also lots of problems with noise on the line
(fellow collega's rember the DMs3 ?)

the only thing i am afraid of is that it is a timing issue with the clock
and while Infectus promis us that no new chip is needed i guess that a clock on the chip good be very helpfull instead of the onboard clock we are using now

i have lots of old mods laying around and will try to build a crystal on the argon to see what results that will give

grtz
MABCOM

the problem with putting a resonator or clock onboard is syncing issues (exact same issue)

so i dont think putting an onboard clock with solve all problems, it will just move them to another point of failure

Any word on DVD Update feature?? How can you easily upgrade/downgrade from wasabus 1.1 to the newer firmwares. Once the chip is installed in the wii, the programmer doesnt recogize the chip anymore. I have tested all three firmwares but each time had to take out the chip to reprogram it and ended back with wasabus 1.1 cause it works the best. Also do u need to use a different version of the infectusprogrommer software with each firmware or can I stick with the lastet version for programming?

got a LEH19xxxxxx wii yesterday, and it has GC2-D2C with second line of text

but also has APCB D3 94V-0 printed

tried beta 2.0 no disc spin and 2.5 no disc spin

also tried wasabus 1.1 firmware for normal d2c models but no go

any ideas?

When the chip is installed in the Wii, you can update it without problem with the JTAG programmer, but you have to turn the power of the Wii on (preferably without a disc in the drive). Otherwise the programmer is 'too weak' to power all the Wii electronics, because the modchip is connected to the 3V of the Wii. And no, it is not dangerous to do this; everybody does it this way.

First connect the flatcable to Argon and programmer without any power (also no standby) on the Wii and USB cable disconnected. Then connect power to your Wii and switch it on and connect USB cable to PC.