The Matrix NOT Reloaded

There has been much dispute over wether or not The Matrix is reloaded/rebooted/recompiled whatever when The One enters the source. I have mentioned before the need for a 'hot' recompile, meaning that only the objects that were upgraded are reloaded, as opposed to the whole system. I do concede that this is impossible with todays computers, and I have no idea on how it works, I have just realized that it HAS to work. The Vampires, Ware wolves, and Ghosts(Twins) were all from the first version of The Matrix, however they are in the current version that Neo is in as well. This proves that a so called 'hot' recompile must be necessary.

I thought that the Merovingian programmed the twins.

Maybe he did...

I wonder what their code looks like!!!

The matrix has simply been reloaded (multiple times as the second part reveals) as the title states!:)

Looks like the matrix has been 5 times reloaded, but, was this time meant to reaload the matrix? What the arquitect says to Neo tries to see if Neo is really in love with Trinity, he needs to see if this time is the one in which the machines and the humans can live together in armony. The revolution is up to start, the very war is not between humans and machines, is between machines, machines with free will and love and machines with free will and hate. Machines have to learn how to live with humans and viceversa.

Ya, that was the Councillor's point..

No points! :D

However the Matrix was NOT reloaded in this movie.

Neo (the One) did NOT enter the source.

Mayhaps the twins, Merovingian etc are like ROM within the Matrix..

Permanence: The values stored in ROM are always there, whether the power is on or not. A ROM can be removed from the PC, stored for an indefinite period of time, and then replaced, and the data it contains will still be there. For this reason, it is called non-volatile storage.
Security: The fact that ROM cannot easily be modified provides a measure of security against accidental (or malicious) changes to its contents.

just a guess...

Hot swapping code is possible with out rebooting a system in today's modern computer systems.....

An example is Java 1.4 which allows hot swapping of new compiled code (classes) into a running Virtual Machine (MWAM ?)

:-)

Chasolab, yes, but first all instanciated objects using the code must first be unloaded from memory. This is also dependant on each object code is in it's own seporate document. And any object oriented language can do that, the JVM has nothing to do with this. The JVM only enables code to be cross platform compatable.

And the Merovingian may have programed the twins; however Persephony described the ware wolves as "comming from a much older version of the matrix", and her husband kept them around.

She stated, because they are notoriously difficult to liquidate. They can't be ROM because they *can* be liquidated. And if they truly were immortal, they wouldn't run from Neo or fight him, what would the point be?

And as for the hot swapping part, what is the problem with their execution being interrupted for a split second, then resumed? You cannot replace the execution code unless you actually replace it, which means the execution must be interrupted, the code replaced, then resume execution. Who even says the entire Matrix doesn't just come to a halt while everything gets 'reloaded', and the entities inside wouldn't even know until they noticed changes in their being or other beings around them afterwards?

sigh I guess I have to be more specific for ppl.

Erasable Programmable ROM (EPROM)
Electrically Erasable Programmable ROM (EEPROM)

Not that this would be the case but its just a reminder that there is more then just ROM.

:)

Originally posted by phase
She stated, because they are notoriously difficult to liquidate. They can't be ROM because they *can* be liquidated. And if they truly were immortal, they wouldn't run from Neo or fight him, what would the point be?

And as for the hot swapping part, what is the problem with their execution being interrupted for a split second, then resumed? You cannot replace the execution code unless you actually replace it, which means the execution must be interrupted, the code replaced, then resume execution. Who even says the entire Matrix doesn't just come to a halt while everything gets 'reloaded', and the entities inside wouldn't even know until they noticed changes in their being or other beings around them afterwards?

Who said that they were ROM??? Also I'm not saying that 'hot' swap not possible. I am saying that it has to be possible. It's just not feasable in todays computer systems. Let me try and explain how it works.

Lets say you have the code that makes up an agent. Well call it agent.dll You can create an infinite number of agents from that code. This is called instantation. Each instantitation can be minipulated and changed from it's initial construction. The code would look somewhat like this

Include Agent.dll

Create AgentSmith = Agent.dll
Set AgentSmith As New Agent.dll
Create AgentBrown = Agent.dll
Set AgentBrown As New Agent.dll
Create AgentJones = Agent.dll
Set AgentJones As New Agent.dll

if you were to make a change to Agent.dll, those changes would not effect AgentSmith, AgentBrown, or AgentJones because there code is already instantiated. Inbetween M1 and M2 the agent code WAS upgraded and now we have Agents Johnson, Jackson, and Thompson. The changes in the code were not passed on to Agent Smith (even though he received other changes from Neo).

So far we have no problem with that. But remember objects are made up of objects are made up of objects are made..... you get the point. Say they wanted to change how a peice of hair flows in the wind. They could change that code, but it would only be effected in new objects that are created.

Again I'm not saying that it's not possible. If fact it has to be possible. I'm just stating that I don't know how it's possible.