;-) just to help a bit. I saw you converted the disassembled file to a C file. thats nice... but not very helpful because C, CPP and others are using compilers to optimize the code to a faster and/or smaller size. When you decompile large chunks of data cant be "decompiled" back to their "original" code completely. Im definitly NO expert, but learning the R3000 assembly language is important in your hardware modification quest. In my position I want to learn by experimenting the Higher language first. just making some games (Hopefully ++points my programming experience for the PS1) then move to do some Assembly parts (Ill keep it simple, to get the basics) and look at My own "c" games in IDA for example. I then try to understand and "see" the Higher language I used in assembly. When Ive done that Ill take a small peek at the bios for example and try to reconize parts of code. Inportant lesson learned from Gameboy Rom hacking, some parts are data and some code. code can break and checks are at "reconizeble" places. A bios file is even more complicated at first sight. Done small bits of PC bios "editing" and there are bit of "setup code" done, NOT from a language like C, it was done directly in Assembly. So, i would try to understand those and try to let the bios set some registers different and then Detect them with my own apps. Set the bios in debug mode or change a region code... add a menu if the bios has a menu. Many bugs, failures and in the end understood that the Bios is important, fragile and can break the system. :thumbsup: lotts of babeling of a n00b who priority should be at making a PS1 mem card. My english isnt very good but what I tried to say was "Ãts not inposible, its just damm hard to do". And that makes it so interesting. Use google to search, Hitmen has so much info on nice things, and there are EPROM emulators out there. http://www.piclist.com/images/boards/EPROMemuMk2/index.htm is one I want to try building. :crying: I have so many things to learn and try. ;-) Ill keep it simple all the time, and have fun with the small things. this was more than my 2 cents but maybe someone gets my feeling and understand that Learning with a Lott of patience is a MUST. <end of line>:cur_sonic:
Not a smart move fella, just sayin...lol...Unless you're looking to troll on purpose (by performing the ol' reverse troll ). BTW I admire your enthusiasm, but as has been mentioned previously on this thread - it's misplaced here (I think).
I was simply making people aware that the thread is actually open. You kinda shot yourself in the foot declaring it closed. What if someone with some good links/advice came a long and took your statement as fact and carried on with their day? Just saying.
And here I thought they got pissed for no reason... (pissed meaning drunk for the benefit of those without any knowlege of aussies, or british idioms...lol)
-_- argh, nevermind... If you do have useful info like I said, post it. If not, please dont reply like all of the above comments so far. I QUOTE: "Post useful info or GTFO..."
Indeed we are and I believe I've chimed in a few times here and there but you do seem to be asking an awful lot of questions when google would clearly suffice. Not in all cases but some.
Yea, but Google finds links that are dead. I mean, its not like I can track down Loser2000 and these forums were started to revive all this information. Hence, why I am asking you members for some help.
Another good one, check out the psxdev mailing list.. http://groups.yahoo.com/list/psxdev/ the archives go right back about 13 years or so.
For dead sites (or sites which have been updated and you want to take a look at the old version), you have this excellent site: http://web.archive.org You enter the URL of the site you're looking for and it'll give you a list of all available "snapshots" in a chronological order. Choose the one you want to see and enjoy! Keep in mind it doesn't always have the site you're looking for, and even sometimes the snapshot won't work, but most of the times it's just fine. Also, some files may have been ignored when creating the snapshot, mostly big files. Hope this helps