Usb Advance testing

[dlanor]

Thx dlanor - it seems that my chip is not a MI clone - Triangle and Circle for menu and R1 for dev 1 don't do a thing- ahhhhhhhhhhh.
I am trying to find out from the installer what i have but he says he installs many chips and it could be one of several - but he thought it was a MI clone.

Ok. That makes it very hard to give relevant advice though, as the mod-chip details are crucial to what you can or can't do.

Yep - i tried intalling just a launchelf file with the compiler and then booting with a psx cd - no good ( looks like exploits don't work as you say).

I didn't think it could work, but it's good to clear up that side issue.

Btw your uLaunchELF v3.41t is much better than the one i was using ( i had v 3.41 modified with "stinky's all in one installer" )
Thx for that - a great tool for editing and copying from other mc and usb drive.

I'm glad you like it. But let me clarify that it is not just my project. Others too take part in it, though unfortunately not the one who created it. (A japanese guy named Mirakichi.)

If my chip is not an MI clone then i guess there may be another way of entering dev mode and a menu. Do all chips ( clones included ) have these basic features or am i just hoping?

Not all, but the good modern ones do. And of course, those are the ones imitated by the clone-makers too. I don't think your chip can be very old anyway, as I don't think such a chip could work at all with the new PStwo models.

The DMS chips (both DMS3 and DMS4) will start an ELF stored as "mc0:/BOOT/BOOT.ELF" if you hold down the 'Triangle' button during startup/reset. Note that this uses the same folder as the MI chip, but with a different command button.

If that too fails, then I'm all out of ideas again...

Best regards: dlanor

[jimd]

Back again - well i have finally found the chip that i have:
http://www.modsupplier.com/catalog/p...v20-p-155.htmlIt seeems that this chip has been replaced by the PS2 Modbo v2.1 as the 2.0wasn't using the Matrix Infinity firmware v1.54 properly.
My installer has said that he will exchange the chip for me but before i do i have a couple more questions ( sorry ).
1. If the old chip is removed and the new one installed am i likely to have any other issues - i.e. with the console being "messed around with" - assuming that the installer knows what he is doing ( which i think he does lol).
2. If i have a fully working PS2 Modbo v2.1 chip which allows dev 1 mode ( but not the change of the macrovision fix) will i be able to run usb advance from the mc0:boot/boot.elf dev 1 method? i.e. could you clarify: does running usb advance through dev 1 mco not need the macrovision fix turned off?
3. When viewing the mc0:boot/boot.elf file with the sony playstation2 browser( browsing the mc) it appears as "corrupt data" - but when viewing with the launchelf browser it appears correct. Is this normal or could this be part of my problem?
Thx very much for your help.

[dlanor]

Back again - well i have finally found the chip that i have:
http://www.modsupplier.com/catalog/p...v20-p-155.htmlIt seeems that this chip has been replaced by the PS2 Modbo v2.1 as the 2.0wasn't using the Matrix Infinity firmware v1.54 properly.

Ok, I guess that explains some of the odd results you got.

My installer has said that he will exchange the chip for me but before i do i have a couple more questions ( sorry ).
1. If the old chip is removed and the new one installed am i likely to have any other issues - i.e. with the console being "messed around with" - assuming that the installer knows what he is doing ( which i think he does lol).

Given that assumption, a new chip should work as well as the old one. (Hopefully better, if the chip is a better type.)

2. If i have a fully working PS2 Modbo v2.1 chip which allows dev 1 mode ( but not the change of the macrovision fix) will i be able to run usb advance from the mc0:boot/boot.elf dev 1 method?

No. Never with a Modbo, or any similar clone.

i.e. could you clarify: does running usb advance through dev 1 mco not need the macrovision fix turned off?

Mod-chip features of this kind will remain active regardless of the software you run. That is the whole point of their normal use, as they must survive the console initialization performed by normal games. The only proper way to turn off such features is through the firmware itself, and that part of the firmware is not supported by the Modbo chip, due to hardware differencies from the real MI chip.

3. When viewing the mc0:boot/boot.elf file with the sony playstation2 browser( browsing the mc) it appears as "corrupt data" - but when viewing with the launchelf browser it appears correct. Is this normal or could this be part of my problem?

That is perfectly normal. The PS2 browser expects all folders on MC to contain a file named "icon.sys" which contains the game 'Title' to be shown by that browser, and also defines what icons to display, by naming three icon files (most saves use the same file for all three). I'm appending a simple icon set that I use for LaunchELF myself. (No eye-candy at all, just functional.)
Just copy the two files from that ZIP into the "mc0:/BOOT/" folder to make the PS2 browser accept it as a valid save.

Thx very much for your help.

You're welcome, but I'd feel better about it if my advice had actually solved your main problem...

At this point all I can do is to urge you to get a real MI chip installed.

That guy who installed your old chip did agree to install a new one, though unfortunately still a clone. But perhaps he can be persuaded to install a real MI chip instead. He'll probably argue against it, because those are a bit more expensive, but he might agree if you offer to pay the price difference of the chips. I know that's an unplanned expense for you, but it's still a lot better than going elsewhere and have to pay for the whole job, installation and all.

Trust me, once you do get a real MI chip properly installed, it's something you'll never regret.

Best regards: dlanor

[jimd]

Thx for the info and the files.
I think you are right a genuine Mi chip is what i need - i just have to negotiate with my installer. Just one question with the real MI chip - When running Usb advance and disabling the macrovision fix - is this fix disabled the whole time that the usb games are played or just during boot up of the usb advance program? My thoughts are - if the fix is meant to be on will it damage the chip and/or console if it is switched off for longer periods?

I have tried to install your icon with the launchelf browser but when i browse to my usb pen the application just freezes ( The list of browsable items include: mco , mc1 , cdfs , hdd , mass - i presume mass is the right one )
I know that the usb pen works with my ps2 as i can copy game saves to and from it with action replay max . Am i doing something wrong or missing something here?
Regards Jimd

[dlanor]

Just one question with the real MI chip - When running Usb advance and disabling the macrovision fix - is this fix disabled the whole time that the usb games are played or just during boot up of the usb advance program? My thoughts are - if the fix is meant to be on will it damage the chip and/or console if it is switched off for longer periods?

Having it permanently OFF will not cause any harm at all.
It will remain OFF until you turn it ON again in the configuration menu.

I have tried to install your icon with the launchelf browser but when i browse to my usb pen the application just freezes ( The list of browsable items include: mco , mc1 , cdfs , hdd , mass - i presume mass is the right one )

Yes, 'mass:' is the USB device.

I know that the usb pen works with my ps2 as i can copy game saves to and from it with action replay max.

That proves nothing, as ARMAX does not use normal homebrew drivers. It is those drivers you need compatibility with (also used by USBAdvance).

If you wish you can switch to the latest LaunchELF version v3.41u, which allows you to configure it to use another USBD.IRX than the one embedded in the ELF file. This way you can try drivers from game disks, but I doubt you can use the ones of ARMAX, as they seem a bit odd compared to normal ones.

If you do try using an external USBD.IRX, note that you need to copy it to MC first, then configure LaunchELF to use it at next startup, and finally restart LaunchELF (which must also be configured for IOP reset).

Am i doing something wrong or missing something here?

Hard to say really. Considering earlier posts in this thread you should already have ensured the basics required for compatibility. These being: Only one single partition per USB device, and that must use FAT32.

Another possible problem is if you don't have IOP reset active for LaunchELF, but as you just installed v3.41t that should not be the case, since that version has it active by default.

I'm almost out of ideas at this stage. You may be so unlucky that your USB drive is incompatible with the homebrew drivers. Then again, this could just be another example of how the bad mod-chip causes abnormal results.

Best regards: dlanor

[jimd]

Hi dlanor
My genuine MI chip is on its way - Thx for the advice.
I have still been unable to get launchelf ( and i guess - ultimately Usb advance) to recognise my Usb drive. The problem ,it seems from your info, is in locating and installing the correct USBD.IRX driver file. Reading through this and other forums it seems to be a common problem ,with no step by step solution. Looking at several game files i haven't seen any USBD.IRX files - i guess if they are there - they are imbedded within another file. As mentioned AR Max works fine with usb so they must have one hidden somewhere too.
If possible could you point me in the right direction - where to get one and if needed -how to extract. Also - as usb drives form an integral part of Ps2 browsing it might be worth including some common USBD.IRX drivers with a future launchelf package.
Thx again
Jim