PS2 Editing the OSDSYS' entries with Notepad makes OSDSYS messed up

[Windows10User]

I already answered you... OFFER REJECTED! I DO THINK!

But yes... You obviously did not think AT ALL, before hammering that answer into your reply-Window.

Use... A... USB-Keyboard... on... a... PS2...


wLE version doesn't matter at all in regards to the OSDSYS.


2008


A file extension does not define the file-type/format... Facepalm...

I don't have a keyboard to use.

How can you explain it editting with Notepad worked before?

 

[Berion]

I already told You what could be every possible reasons why after editing, FMCB rejecting or parsing wrongly the FREEMCB.CNF. If You don't understand that, just attach the broken CNF on the forum.

Notepad is totally fine to edit, at least on Windows 7 (personally PC, is my only way of editing config files from PS2 and I never have any problems). Latest Notepads from W10 or 11 support also UTF8, so You probably used this encoding now, while didn't then. Just blind shot.

 

[TnA]

I don't have a keyboard to use.

O.k.

How can you explain it editting with Notepad worked before?

How can I know what changed on your setup? I can't!


Why don't you simply upload the config?

 

[Windows10User]

I already told You what could be every possible reasons why after editing, FMCB rejecting or parsing wrongly the FREEMCB.CNF. If You don't understand that, just attach the broken CNF on the forum.

Notepad is totally fine to edit, at least on Windows 7 (personally PC, is my only way of editing config files from PS2 and I never have any problems). Latest Notepads from W10 or 11 support also UTF8, so You probably used this encoding now, while didn't then. Just blind shot.

Ok, but I'm using the same FMCB version as well as Notepad for Windows 11 in both cases and bedore it worked and now it doesn't.

O.k.


How can I know what changed on your setup? I can't!


Why don't you simply upload the config?

That's the problem, nothing changed. Because I can't access it right now.

 

[Berion]

Something must changed, or else it would just works. :P

 

[Windows10User]

Something must changed, or else it would just works. :P

It's really weird.

 

[Berion]

I don't see anything weird here.

Until You tell more about Your environment or just attach file, You will stay with unresolved problem.

 

[60fpshacksrock]

And I did.

You said wLE in the post I quoted which is why I thought you meant that text editor.

 

[Windows10User]

I don't see anything weird here.

Until You tell more about Your environment or just attach file, You will stay with unresolved problem.

Environment, what do you mean? It's Windows 11.

 

[Berion]

Lack of detail. Besides that, judging by Your other posts, You are physical unable to figure this out. So just attached CNF which is broken and I can tell what exactly is not right, which will tell You what to not to do in future and by that, what was cause of breaking specification. Otherwise, it is just beating dead horse.

 

[Windows10User]

Lack of detail. Besides that, judging by Your other posts, You are physical unable to figure this out. So just attached CNF which is broken and I can tell what exactly is not right, which will tell You what to not to do in future and by that, what was cause of breaking specification. Otherwise, it is just beating dead horse.

I used Notepad in Windows 11 21H2 Enterprise x64 Build 22000.832. It looks like I'm not the only physical unable to figure this out.

 

[Berion]

Who else?

 

[Windows10User]

Who else?

Well, some of my threads weren't answered or I was told they didn't know the answer.

 

[Berion]

In case of FREEMCB.CNF, I told You in post no.5 that this can be encoding issue and/or enter symbols type. You didn't checked that. I said that You should attach the broken file here so we could look at it. You didn't do that. So my role here has ended. Good luck then. :P

 

[Windows10User]

In case of FREEMCB.CNF, I told You in post no.5 that this can be encoding issue and/or enter symbols type. You didn't checked that. I said that You should attach the broken file here so we could look at it. You didn't do that. So my role here has ended. Good luck then. :P

I typed the same text as before, so it can't be the symbol's fault. I don't know how to check encoding issues, and like I said, I typed exactly the same text, so it can't be an encoding issue and I can't access that file now.

 

[TnA]

Well, some of my threads weren't answered or I was told they didn't know the answer.

Bullshit!

I typed the same text as before, so it can't be the symbol's fault.

You have just proven, that you didn't understand anything you have been told about encoding...

I don't know how to check encoding issues,

Yeah... Obviously... Hence you could simply attach the file after x request, but you won't and rather kick the dead horse for hours/days to come.

and like I said,

You didn't "say" anything, but "wrote"...

I typed exactly the same text,

Doesn't matter Jackshit... Do you comprehend?

so it can't be an encoding issue

More BS from someone who doesn't know what he is "talking"/writing about...

and I can't access that file now.

Then this thread is DONE and soon to be closed.

 

[Peppe90]

I can't access that file now.

I join the suggestion for you to upload the file when you can, so we'll be able to help you. Until then is useless to keep dealing without the host.

And btw, I also came across some problems through the years using windows notepad (with different cfg/ini files from many apps, not only Ps2 related).
It is not good in preserving the file's structure, so depending on your edits it can works perfectly for 100 times, then the 101 you'll break something.

Notepad++ (as 60fpshacksrock firstly suggested you) is the recommended program for editing cfg/ini files. I never had a single problem since I'm using it.

 

[Berion]

I typed the same text as before, so it can't be the symbol's fault. I don't know how to check encoding issues, and like I said, I typed exactly the same text, so it can't be an encoding issue and I can't access that file now.

You don't understand what encoding means and works.

As You know, data in our devices is written in binary code, but to make it a lot easier readable, we converting them to hex code. So, in UTF-8, ASCII symbols using one byte, while other two bytes (e.g Polish symbols taking two). In Windows-1250, always only one. PS2 homebrew supporting only pure ASCII e.g from Windows-1250 and similar. Another thing is, that OSDSYS using his own codepage (so FMCB also) which is ASCII + markers for another which exist in its font. If You mess with this, You get gibberish in menu or even FMCB reject parsing file (depend of mismatches between what You did and what can be used). As You can see, the same symbol can be written differently in binary.

Another factor is how enter symbols is written. There are three common types: 0A, 0D and 0D0A. CNF parser support only Windows type, which is 0D0A. Everything else used and You lose enters which leads to unexpected by me results.

And now, in some of Notepad version in Windows 10 it starts support UTF8. And it is possible that it writing it by default since some build (as Win10 and 11 are rolling releases...) or You not intentionally switch to it by some keyboard shortcut. I guessing because I don't using it.

The best for You is stop using such limited applications like Notepad and switch to something more advanced like Notepad++, EditPad Pro, SlimlimeText etc. etc.

 

[Windows10User]

Bullshit!

You have just proven, that you didn't understand anything you have been told about encoding...

Yeah... Obviously... Hence you could simply attach the file after x request, but you won't and rather kick the dead horse for hours/days to come.


You didn't "say" anything, but "wrote"...


Doesn't matter Jackshit... Do you comprehend?

More BS from someone who doesn't know what he is "talking"/writing about...


Then this thread is DONE and soon to be closed.

No, it's not, asshole. What about the PS5's external HDD issue?

Me or you, dumbass? It doesn't matter jackshit if I understand anything about encoding or not. What matters is that it was working before when I did EXACTLY the same thing as now.

Why would I need to do that when before it worked and like I said, I couldn't access the PS2 at that time.

"Wrote"? With a pencil or a pen?

Yes, it does, you idiot.

Me or you, you blind shit? "Writing" with a pencil or a pen?

No, it's not, otherwise a lot more threads would be close.

I join the suggestion for you to upload the file when you can, so we'll be able to help you. Until then is useless to keep dealing without the host.

And btw, I also came across some problems through the years using windows notepad (with different cfg/ini files from many apps, not only Ps2 related).
It is not good in preserving the file's structure, so depending on your edits it can works perfectly for 100 times, then the 101 you'll break something.

Notepad++ (as 60fpshacksrock firstly suggested you) is the recommended program for editing cfg/ini files. I never had a single problem since I'm using it.

You don't understand what encoding means and works.

As You know, data in our devices is written in binary code, but to make it a lot easier readable, we converting them to hex code. So, in UTF-8, ASCII symbols using one byte, while other two bytes (e.g Polish symbols taking two). In Windows-1250, always only one. PS2 homebrew supporting only pure ASCII e.g from Windows-1250 and similar. Another thing is, that OSDSYS using his own codepage (so FMCB also) which is ASCII + markers for another which exist in its font. If You mess with this, You get gibberish in menu or even FMCB reject parsing file (depend of mismatches between what You did and what can be used). As You can see, the same symbol can be written differently in binary.

Another factor is how enter symbols is written. There are three common types: 0A, 0D and 0D0A. CNF parser support only Windows type, which is 0D0A. Everything else used and You lose enters which leads to unexpected by me results.

And now, in some of Notepad version in Windows 10 it starts support UTF8. And it is possible that it writing it by default since some build (as Win10 and 11 are rolling releases...) or You not intentionally switch to it by some keyboard shortcut. I guessing because I don't using it.

The best for You is stop using such limited applications like Notepad and switch to something more advanced like Notepad++, EditPad Pro, SlimlimeText etc. etc.

Again, it doesn't matter if if I understand what encoding means and how it works or not since I did exactly the same thing as before (I used the same Notepad version) and it worked back then.

EDIT: I used Notepad++ and I had no problems this time but like I said before, Notepad previously worked without problems so I hope Notepad++ will continue working.

 

[LoKKeR]

You can tell that no one here has worked as an embedded engineer or even on Linux.
The issue is that the notepads are interpreting the text file with Windows ending lines while the FMCB software uses Unix ending lines to read the configuration file. Simply switch the line ending mode to Unix at the bottom next to the characters map UTF-8 option and you will be fine.