PS2 PS2-CUSTOM by Edwork91

[edwork91]

Hey I'm edwork91, this is my first repository, hope you enjoy it
https://github.com/edwork91/ps2-custom

 

[Berion]

I don't want be that guy but I feel that I must give You some tips. ;p

On first, GitHub is not file hosting like Mega, SendSpace etc. It is code repository so putting 7zipped files into repository without even any description what is what doesn't have any sense. For binaries it is Release category. But mixing a lot of apps into one repo is bad idea in the first place.

From user point of view: he don't know what files are modified and what this modification contains and why it even want him to download whole repo and check it all.

In example: if You modified SoftDEV2 Installer, You should create Your own repository, forked from @alexparrado, eventually renamed project name and after that put changed files as pull. In such way peoples not only know where to look for original project but also easily track all changes: current and future. As addition, in release section, You can put binaries + src on which they are based off.


Welcome on our forum and nice to see some new soul in PS2 development. ^^

 

[Berion]

PS: Your Memory Card image from "SoftDev1_Hybrid_PAL_All.PS2.Edwork91.7z" will not works on other peoples console and even on another Memory Card, due to how Magic Gate works (if You want boot from OSD Update, not from Fortuna).

SoftDev1 Hybrid
only work for PAL console and 8mb MC
using MC Annihilator v2.

Besides that, You have used traversal attack on MCFS. For what reason? And this logo put in root of MC will be displaying as Corrupted Data on OSDSYS/HDDOSD.

 

[alexparrado]

Hey I'm edwork91, this is my first repository, hope you enjoy it
https://github.com/edwork91/ps2-custom

As @Berion suggested, don't use GitHub to host binary files, unless you are uploading releases compiled from your repo source code.

SoftDev1 hasn't even released by me on GitHub due to it uses binaries from FMCB 1.9, I need to manage these issues before making it public. Although, I shared it for a private group of people, It wasn't mean to be shared in psx-place.

So please don't share SoftDev1-based repacks, you can do it for SoftDev2 and/or OpenTuna by using other service rather than GitHUb or by uploading your own zip file. If you plan to improve SoftDev2 and/or OpenTuna from source code, go ahead use GitHub and fork.

 

[edwork91]

Berion dziękuje za wskazówki miałeś racje wrzuciłem obraz na inna karte i nie działa

Berion, thanks for the tips, you were right I put the picture on another card and it does not work

Moderator edit: English translation using Google Translate. In future posts please also include an English translation. Thank you.

 

[Berion]

Content signing for MC is per physical MC. That's one of the reasons why FMCB isn't distributed as Memory Card image but installer which signing executables on his own.

And You should delete SoftDEV1 archive as it's comes from leak which about author is not happy. :P

PS: This is English message board (because it is one of the international languages and it is international forum). If You have problems with English, use this: https://www.deepl.com/translator

 

[HWNJ]

PS: Your Memory Card image from "SoftDev1_Hybrid_PAL_All.PS2.Edwork91.7z" will not works on other peoples console and even on another Memory Card, due to how Magic Gate works (if You want boot from OSD Update, not from Fortuna).


Besides that, You have used traversal attack on MCFS. For what reason? And this logo put in root of MC will be displaying as Corrupted Data on OSDSYS/HDDOSD.

View attachment 33929

ISOBuster can open MC images!?!?!

Hey I'm edwork91, this is my first repository, hope you enjoy it
https://github.com/edwork91/ps2-custom

I will also be "that guy".
Pal, that's not the way Github is meant to be used

 

[Berion]

ISOBuster can open MC images!?!?!

Yes, all formats and possible sizes:

• In case of PS2 MC cards with and without ECC (but detection based on extension here, not mime type, so to read cards with ECC they must end with *.vm2 or *.ps2, for else read will by trying as none ECC).
• In case of PSX MC cards, just all formats which in reality are raw mc images with different headers which can be simply ignored (used only for detection).
• Also Dreamcast memory cards are supported.
• GameCube would be, but there is nowhere specification describe how to handle them (author do not want read another peoples code and only seldom reverse format by itself like i.e all revisions of ReFS on v4.8).

All of this is in free spectrum range functionality.

If device drivers with MC inside would expose cards as media (accessible by letter or UNC path), IsoBuster would read it from real memory cards too (but none of drivers for DexDrive or PS3MCA doing it unfortunately).