byuu's message board

Sure, people have already done that.

If you want to decap some chips then go right ahead. The problem is that it costs a bit of money.

"Computer" is an artifact title. They used to do only that -- crunch numbers. Wasn't long until they outgrew the name "computer". Basically... 'round the time they invented branching.

If that were the case, there would be no if-then statements.

Until you can figure out how to implement an if-then statement in pure math, you have no meaningful argument.

Do you know what an if-then statement is? I'll give you a hand.



In this example, how do you make a computer go down the correct path? You can use math to figure out what X is, sure, but once you get there, how do you enforce what color to turn the screen? Not math. This is called conditional logic. It isn't math, it has never been math, and it will never be math.

When one has an algorithm to emulate the response of the system and perform on a ROM for identical output numbers, is it not possible to skip / adjust steps to be more direct to calculations while maintaining proportion to still be 'accurate' for 100% compatibility and also be more direct in the math on the numbers for the 1:1 output data strings quicker?
i.e. a process of looking at general functions and doing shortcuts while not breaking the proportion for compatibility to compliment emulator capability? This is what would generally allow for making it more efficient.

EDIT:
And for if statement, it is part of the programmed mechanical nature of the calculator - it checks validity of math results in a 0/1 type approach for determining a trace/path to send, and is part of the mechanical layout.
Where the particular math is done, its result can be in line with the 0/1 and the mechanics determine its transmission.

"Mechanical layout" would seem to me that the three options are fixed in hardware. As a part of a program code, they are not. Therefore, you are still wrong.

OT

Yatta!! Whaah? Already 10 pages?
Still, I didn't know how straightforward it was to read assembled code, thanks kawa!
/OT

Asspull Mk.II, ask me in a PM if you want.

Now it's just a broken record:

SoraK05: Math?
Everyone: No.
SoraK05: Math?
Everyone: No.
SoraK05: Math?
Everyone: No.
SoraK05: Math?
Everyone: No.
SoraK05: Math?
Everyone: No.
SoraK05: Math?
Everyone: No.
SoraK05: Please stop trolling.
Kawa: You're a markov chain bot.
SoraK05: Math?
Everyone: It will never be math.
SoraK05: Aw, cmon....MATH!

This thread'd better still be here when I wake up tomorrow. I plan to save it for posteriority.

8 pages later, I have never felt so right.

Math can include if/or statements as part of an algorithm.

There are math steps in general, and the entire function of what the motherboard system will do can be mapped in an algorithm when when performed on a ROM's data will result in the same output strings as the console.

I mention a suited algorithm around mapping the hardware 1:1 to a program to do math (which can include looping where suitable) on the ROM, tweaked where applicable, and result in the same numbers of what output numbers will be.

Like a compression decoder will perform an algorithm of operations/math on a string where applicable and result in numbers, an algorithm using hardware step constraints on a ROM string will result in the same numbers which are in the buffers that are sent to monitor/speaker + temp.


EDIT:
BTW unrelated, higan 0.92 64 bit works on this laptop, and just downloaded 0.94 64 bit yesterday which crashes loading the same ROM.

For an accomplished programmer such as yourself, isn't that setting your goals a bit low? Or is that the key to success in life? I must believe motherboards do math. I must believe motherboards do math.

What you're now attempting to describe is a transistor level emulator, which is insanely slow. Emulating anything at the physical level is way beyond usable with today's CPU speeds. Except for maybe Chip-8. Oh shit, why did I mention that? Now I've given him hope....


But, but....MATH!