next »

[LordX]

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

LOL , just d2pro hacked dump

[crisdo98]

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

LOL , just d2pro hacked dump

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

[sfrangebob]

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

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.

[idog]

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

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

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

[crisdo98]

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?

[idog]

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...

[crisdo98]

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.

[LordX]

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

[THE1GAMESTOP]

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.

 

[burnzy]

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

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

www.consolefreakz.com

[burnzy]

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

[quantronics]

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

[burnzy]

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

[idog]

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

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' ?

[mike234]

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

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