is xor a n64cpu code or is it a rdp/rcp command?

[n64warrior]

i know it's CPC2 code but where do i put in the source code of an emulator?:confused:

[n64warrior]

i now it has to be decrypt!!but how do i do this?? and how do i put it in my source code??

[Badaro]

XOR is a basic logic operation (Exclusive OR). Here's the truth table:

I1 I2 O
0  0  0
0  1  1
1  0  1
1  1  0

I1, I2 - Inputs
O - Output

[]s Badaro

Edit: Learning how to use "CODE" tags.

[n64warrior]

ok.thanks now how do i implent this into say an n64 emulator??i alreadey know how to do the opcodes from the emu book.

[n64warrior]

i was thinking of useing banjo to decrypt tooie!by compare where the encyption is in tooie.and where it is not in banjo! like they did in sf2 here http://cps2shock.retrogames.com/encript.html

that is the key to emulateing tooie!!

[Badaro]

:dots:

I give up.

[]s Badaro

[Prafull]

<b>"All geniuses are first considered to be an idiot by most people or infact all geniuses are idiots (until they discover something)". </b>

Quoted by Prafull in " Remember that day "

Coming back to topic,
wow, what a great idea to decript tooie using banjo.I hope it works.:music:

[n64warrior]

well like i said they did it with sf on this website http://cps2shock.retrogames.com/encript.html
so it should or might work the same way..

[cooliscool]

come on prafull.. he cant spell (no offense) he keeps saying a bunch of bull****, and banjo kazzoie and banjo tooie are two SEPERATE games, and the enryption isnt THE SAME AS CPS2, this is REALLY getting on my nerves, and he hasn't shown a thing, meaning that he loves his "emulatores" and wants to be a "next gen emul programer" and wants "recognition" and just in case you didnt know next gen emul programer, cps2 is arcade hardware; based on different EVERYTHING! PLEASE STFU!! a few examples; he posted shots on his DAD's pc. "emulateing", no puctuation. run on sentences. what kind of genius is that?? PUHLEEZE!!!!

:dots::dots::shout: :stupid: :stupid:

[Zephon]

cooliscool, calm down.

I don't know where n64warrior is from, but probably English is not his first language. Everybody can make spelling mistakes. What do you want to do with him? Ban him for spelling mistakes, or for asking stuff that you don't believe? You may think that everythink he asks is a lie, but who knows? If you don't like his posts, just ignore them.

[n64warrior]

so my spellings alittle off! it's been say about 8years when i got my out of high school.and about over 5years liveing on my own! working on and off jobs.while studying 3 years html java and now i am learning c,c++..besides i think my family is very thing to me.

[cooliscool]

well, i dont care what he does. its just seeing this same crap about tooie isn old, and all of his "projects" :dots:

[Kellicros]

Got to agree with Zephon. Don't like him? Just put him into your ignore list, that's what the ignore list is for.

[cooliscool]

Nah, i think its funny. so funny it pisses me off at times lol

[M.I.K.e7]

Christ!
If you really want to program a N64 emulator as you claim then get the "fine" official MIPS64 documentation from MIPS (http://www.mips.com/publications/pro...hitecture.html)!
There it says on page 331 of the MIPS64™ Architecture For Programmers Volume II, Revision 0.95:

Format: XOR rd, rs, rt

Purpose:
To do a bitwise logical Exclusive OR

Description: rd <= rs XOR rt
Combine the contents of GPR rs and GPR rt in a bitwise logical Exclusive OR operation and place the result into
GPR rd.

Restrictions:
None

Operation:
GPR[rd] <= GPR[rs] xor GPR[rt]

Exceptions:
None

At the top of the page is even the whole instruction encoding layout which I cannot reproduce here.

So get this document and read it and don't ask any more silly questions claiming you'll be coding a N64 emulator before you've done so! Because if you really want to code a N64 emulator you have to read these documentations and you have to understand it - it's essential!

The last time you asked me about something about N64 emulation in a thread with a totally different topic, I gave you the links of several open source N64 emulators to take a look at how they do it, but from you continuing silly questions I bet you didn't even take the slightest peek at these sources!

Here are the links to the open source N64 emulators again:
http://www.1964emu.com/
http://daedalus.boob.co.uk/
http://mupen64.emulation64.com/
http://www.pj64.net/code/mainiframe_downloads.htm

If you are really interested in doing N64 emulation then you will take a look at the sources and the MIPS documentation.
If you don't do it then you are only someone who wants to annoy people with stupid questions - in that case shut the hell up!

If you just want a special game to run then it would be better to team up with one of the emulation teams (eg. 1964), but I guess you'd probably only slow down progression of that emulator with your questions...

And another advice I gave you last time:
If the specs in your profile are correct, get a faster machine, because a Pentium 2 with 350MHz is too slow for any emulator but UltraHLE, and that only achieves the speed because of lots of dirty tricks, which results in the bad compatibility you're experiencing.

@Administrators:
Sorry for the long rant, but this had to be said and I hope you'll understand it when you take a look at some of the other postings by n64warrior.

[DominaTor]

Hrm ... Unless you consider High Level Emulaion as a dirty method, UltraHLE is not using any "dirty" trick. And those tricks are not responsible for the "low" compatibility.
The main reason is : UltraHLE has only had a single release.
Please pick up any n64 emulator released prior to february 1999 and compare its compatiblity with UltraHLE's one ...

[cooliscool]

i think i'd have to agree with dom. nemu wont play all the cpu demos, the first version, but uhle plays commercial games, on the FIRST release. i think you may want to check your answer mike.

[cooliscool]

Originally posted by M.I.K.e7
Christ!
If you really want to program a N64 emulator as you claim then get the "fine" official MIPS64 documentation from MIPS (http://www.mips.com/publications/pro...hitecture.html)!
There it says on page 331 of the MIPS64™ Architecture For Programmers Volume II, Revision 0.95:



At the top of the page is even the whole instruction encoding layout which I cannot reproduce here.

So get this document and read it and don't ask any more silly questions claiming you'll be coding a N64 emulator before you've done so! Because if you really want to code a N64 emulator you have to read these documentations and you have to understand it - it's essential!

The last time you asked me about something about N64 emulation in a thread with a totally different topic, I gave you the links of several open source N64 emulators to take a look at how they do it, but from you continuing silly questions I bet you didn't even take the slightest peek at these sources!

Here are the links to the open source N64 emulators again:
http://www.1964emu.com/
http://daedalus.boob.co.uk/
http://mupen64.emulation64.com/
http://www.pj64.net/code/mainiframe_downloads.htm

If you are really interested in doing N64 emulation then you will take a look at the sources and the MIPS documentation.
If you don't do it then you are only someone who wants to annoy people with stupid questions - in that case shut the hell up!

If you just want a special game to run then it would be better to team up with one of the emulation teams (eg. 1964), but I guess you'd probably only slow down progression of that emulator with your questions...

And another advice I gave you last time:
If the specs in your profile are correct, get a faster machine, because a Pentium 2 with 350MHz is too slow for any emulator but UltraHLE, and that only achieves the speed because of lots of dirty tricks, which results in the bad compatibility you're experiencing.

@Administrators:
Sorry for the long rant, but this had to be said and I hope you'll understand it when you take a look at some of the other postings by n64warrior.

BUT! i whole heartedly agree with you on n64warrior being a dumbass. you might want to tell him what MIPS stands for lol.. Million Instructions Per Second, to save you the time

[n64warrior]

"there is copy protection beyond the usual type
that does a check for the presence
of an actual 6105 boot chip after booting.
If the game fails to find the chip,
it refuses to run. Beyond needing an actual 6105 boot chip,
Banjo-Tooie also requires a 16kbit EEPROM
or it will refuse to detect a controller.
There is no crack available yet for this game,
so an actual CIC-NUS-6105 host card with 16Kbit EEPROM
is necessary to enjoy this game.!"

so i know by simulating the CIC-NUS-6105 host card with 16Kbit EEPROM, will make banjo-tooie will run"

taken from

http://www.icequake.net/n64/mirror/w...ve_faq.html#b7

this 1 way i found out how to make tooie run.in pj641.4. no lie..

[M.I.K.e7]

Originally posted by cooliscool

you might want to tell him what MIPS stands for lol.. Million Instructions Per Second, to save you the time

Erm, that's true for the most often use of MIPS, but in the case of the microprocessors it actually stands for:
"Microprocessor without Interlocking Pipeline Stages"

That means, if you have an instruction loading a register with a value from memory then you shouldn't use that register directly after the load. You could do that of course, but due to the pipelining the registers isn't filled with the correct value when the following instruction is executed, so it will lead to unpredictable results.
But that is only true for the MIPS I processors. All processors of MIPS II and up introduced interlocking, ie. when you access a register after a load the execution of the pipeline is stalled until the register contains the correct value.

But even with an interlocking pipeline it's always a good idea not to access a register directly after the load instruction, because the resulting pipeline stall will slow down the execution of the program.

MIPS I didn't have an interlocking pipeline because it makes the processor much easier, and that's why I like it. Later processors processors bacame much more complicated, so my favourite MIPS is the R3000.