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

Use a Keyboard?

On another note: If it messes something up, you are doing something seriously wrong.
 
TnA said:
Use a Keyboard?

On another note: If it messes something up, you are doing something seriously wrong.
Click to expand...

That's what I did (using the keyboard), don't you think? I'm doing exactly the sme thing I did before and unlike then it's messing the OSDSYS.

60fpshacksrock said:
Notepad++ is better. You can edit without it ruining the structure.
Click to expand...

But it was working before with Notepad. Maybe the wLE version is different this time and because of that it can mess the OSDSYS?
 
The question is, editing by what exactly? You cannot use anything than simple text editors. So e.g not MS Word, LibreOffice, OpenOffice, Wordpad etc. The idea is that You cannot use any text formatting symbols but only those in pure ASCII.

I do not remember but FMCB accepting enter symbol as 0D0A but also 0A. Yet encoded as Windows1250, so no e.g any of UTF.

edit: Notepad is fully ok (at least one used in Windows 7), and gedit used in all Gnome-like desktop environments for Linux.

On top of that, CNF parser hasn't changed since 2006 (?) year. ;)
 
Berion said:
The question is, editing by what exactly? You cannot use anything than simple text editors. So e.g not MS Word, LibreOffice, OpenOffice, Wordpad etc. The idea is that You cannot use any text formatting symbols but only those in pure ASCII.

I do not remember but FMCB accepting enter symbol as 0D0A but also 0A. Yet encoded as Windows1250, so no e.g any of UTF.

edit: Notepad is fully ok (at least one used in Windows 7), and gedit used in all Gnome-like desktop environments for Linux.

On top of that, CNF parser hasn't changed since 2006 (?) year. ;)
Click to expand...

I only changed the entry's names to match the current version of the apps and typed the full apps name in Notepad and it worked before.

I'm using Windows 11's Notepad.
 
Last edited:
I'm not a Windows 10 user (I really really hate that OS), so I don't know what MS did with Notepad in this rolling release system kind, ;p maybe it will forcefully switch to UTF-8 and that's why he killed Your config? I dunno. Better would be if You attach broken CNF so we can judge by our eyes instead of debating. :P
 
Berion said:
I'm not a Windows 10 user (I really really hate that OS), so I don't know what MS did with Notepad in this rolling release system kind, ;p maybe it will forcefully switch to UTF-8 and that's why he killed Your config? I dunno. Better would be if You attach broken CNF so we can judge by our eyes instead of debating. :P
Click to expand...

It was working fine before in Windows 11 and now it isn't.
 
Windows10User said:
That's what I did (using the keyboard), don't you think? I'm doing exactly the sme thing I did before and unlike then it's messing the OSDSYS.



But it was working before with Notepad. Maybe the wLE version is different this time and because of that it can mess the OSDSYS?
Click to expand...

I thought you meant notepad in Windows.
 
Take a look at this option in notepad++
Edit ---> EOL conversion ---> Windows (CR LF)
Edit ---> EOL conversion ---> Unix (LF)

You should not change the format, open the original file to check it and use the same format when saving it
 
sandungas said:
Take a look at this option in notepad++
Edit ---> EOL conversion ---> Windows (CR LF)
Edit ---> EOL conversion ---> Unix (LF)

You should not change the format, open the original file to check it and use the same format when saving it
Click to expand...

What do you mean by not changing the format? When I edit the FREEMCB file, I never change its file extension (CNF).
 
The EOL format (end of line)
Unix files uses only 1 character at the end of every line of the document... while windows uses 2 characters
There are some text editors that changes the EOL format automatically to windows style because you are running them on windows... but this "breaks" the file
 
sandungas said:
The EOL format (end of line)
Unix files uses only 1 character at the end of every line of the document... while windows uses 2 characters
There are some text editors that changes the EOL format automatically to windows style because you are running them on windows... but this "breaks" the file
Click to expand...

Ok, but I don't understand why Notepad didn't break it before and now it does.
 
1) Open the original file in notepad++ and check which option is highlighted in:
Edit ---> EOL conversion

2) Open your "broken" file in notepad++ and check which option is highlighted in:
Edit ---> EOL conversion

3) If the EOL setting differs (one of them is unix and the other is windows)... thats the reason why is broken
 
sandungas said:
Take a look at this option in notepad++
Edit ---> EOL conversion ---> Windows (CR LF)
Edit ---> EOL conversion ---> Unix (LF)

You should not change the format, open the original file to check it and use the same format when saving it
Click to expand...

Can I do it in Notepad? I don't want to install a program just to edit this file.
 
Windows10User said:
That's what I did (using the keyboard), don't you think?
Click to expand...
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...

But it was working before with Notepad. Maybe the wLE version is different this time and because of that it can mess the OSDSYS?
Click to expand...
wLE version doesn't matter at all in regards to the OSDSYS.

Berion said:
top of that, CNF parser hasn't changed since 2006 (?) year. ;)
Click to expand...
2008

Windows10User said:
What do you mean by not changing the format? When I edit the FREEMCB file, I never change its file extension (CNF).
Click to expand...
A file extension does not define the file-type/format... Facepalm...
 
You must log in or register to reply here.

Similar threads

Back
Top