PS2 what exactly does lenschanger do?

[helltoast]

this is probably a stupid question but I've meaning to replace the aging 400b laser on my V4 with a 400c.

what I'm unclear on is what exactly lenschanger does to the eeprom. I'm aware of the mechacon bugs on later models, and I'm worried lenschanger is gonna retroactively make my machine... buggier.

or is the mechacon firmware stored somewhere else? is it even possible to patch it from the software side? or is it irrelevant because lenschanger doesn't mess with it?

 

[Berion]

Before flashing, You can make backup of current nvm.

 

[helltoast]

Before flashing, You can make backup of current nvm.

thanks, I'm aware. but the issues with the later mechacon versions could take years to manifest.

I guess what I'm asking is if lenschanger "updates" the mechacon firmware to the newer, buggy version.

 

[Berion]

As far as I know, not. It changing only config. There is BOOT ROM with PS2 firmware, DVD ROM which probably contains drive firmware and EPROM which contains drive config. But I cannot say for sure so better wait for someone who understand stuff on this level.

 

[helltoast]

As far as I know, not. It changing only config. There is BOOT ROM with PS2 firmware, DVD ROM which probably contains drive firmware and EPROM which contains drive config. But I cannot say for sure so better wait for someone who understand stuff on this level.

I see. no problem, thanks for your input. I don't know what lenschanger does, exactly, but I do know it uses data from other consoles. what I'm thinking is, what if it flashes my V4 with data from a V10 with the buggy mechacon? would the issue with overheating BAs transfer over to my V4 as well?

anyway, thanks again.

 

[TnA]

this is probably a stupid question but I've meaning to replace the aging 400b laser on my V4 with a 400c.

Go ahead! Don't forget to remove the anti-static solder-joint/"dot"!

what I'm unclear on is what exactly lenschanger does to the eeprom. I'm aware of the mechacon bugs on later models, and I'm worried lenschanger is gonna retroactively make my machine... buggier.

It works on your unit... It changes some Bytes in the NVM of the MechaCon.

or is the mechacon firmware stored somewhere else?

Well,... IN the MechaCon?!!

is it even possible to patch it from the software side?

Currently "No!",... We do not even know, if it is rewritable or not, but I suppose it is not.

or is it irrelevant because lenschanger doesn't mess with it?

Exactly! It doesn't mess with the Firmware, but only changes the settings in the "Non-Volatile Memory" (the settings-section).

thanks, I'm aware. but the issues with the later mechacon versions could take years to manifest.

Huh? No... It should be noticable immediately on the "Dragon-Units", AFAIK!

I guess what I'm asking is if lenschanger "updates" the mechacon firmware to the newer, buggy version.

First of all... It is NOT the MechaCon-Firmware which is "buggy", but the support of the app for modifying the settings on these is buggy!
Second... It doesn't change ANYTHING in regard to the MechaCon-Firmware, but only "settings" on the NVM!

As far as I know, not. It changing only config.

Yerp, AFAIK that's correct!

There is BOOT ROM with PS2 firmware, DVD ROM which probably contains drive firmware and EPROM which contains drive config. But I cannot say for sure so better wait for someone who understand stuff on this level.

No, the DVD ROM does NOT contain a drive-firmware, but the DVD-Player-Software (which starts when a Video-DVD is inserted)!

I see. no problem, thanks for your input. I don't know what lenschanger does, exactly, but I do know it uses data from other consoles. what I'm thinking is, what if it flashes my V4 with data from a V10 with the buggy mechacon?

It doesn't do it this way...

would the issue with overheating BAs transfer over to my V4 as well?

That is a TOTALLY unrelated HARDWARE-issue... (to my knowledge)
To answer your question... "No!" (because it is neither a software-issue, nor does Lenschanger "flash it over" like you think.)

 

[helltoast]

Go ahead! Don't forget to remove the anti-static solder-joint/"dot"!


It works on your unit... It changes some Bytes in the NVM of the MechaCon.


Well,... IN the MechaCon?!!


Currently "No!",... We do not even know, if it is rewritable or not, but I suppose it is not.


Exactly! It doesn't mess with the Firmware, but only changes the settings in the "Non-Volatile Memory" (the settings-section).


Huh? No... It should be noticable immediately on the "Dragon-Units", AFAIK!


First of all... It is NOT the MechaCon-Firmware which is "buggy", but the support of the app for modifying the settings on these is buggy!
Second... It doesn't change ANYTHING in regard to the MechaCon-Firmware, but only "settings" on the NVM!


Yerp, AFAIK that's correct!


No, the DVD ROM does NOT contain a drive-firmware, but the DVD-Player-Software (which starts when a Video-DVD is inserted)!


It doesn't do it this way...


That is a TOTALLY unrelated HARDWARE-issue... (to my knowledge)
To answer your question... "No!" (because it is neither a software-issue, nor does Lenschanger "flash it over" like you think.)

thank you very much for your help. I've been going back and forth on replacing that 400b with a 400c because of this. I assumed what you said was the case, but wanted to be sure, lest I end up burning my V4.

 

[TnA]

Just make an NVM-Dump, like @Berion wrote. You can flash it back on those older models (IF anything "out of order" happens).

Make sure to use a newer version of Lenschanger as well!