01-07-2009, 07:19 PM
VM allocations errors on startup are random, they appear only when the ram address that the emulator tries to use is already taken up.
The amount of ram you have is irrelevant, if that address is occupied, the emulator will not start.
The only way you can try to fix it is by restarting your pc,and starting up the vm build immedietaly after. That way you have a better chance of having that address still available.
That, and reduce the number of programs you load on startup. There are no other solutions and there is nothing we can do with the current vm implementation.
And it's precisely this kind of problems that made us decide we will remove the Vm version as soon as the vtlb is better implemented.
And about vista, I use vista and it works perfectly. It's all about how many and which programs you have on load on statup.
The amount of ram you have is irrelevant, if that address is occupied, the emulator will not start.
The only way you can try to fix it is by restarting your pc,and starting up the vm build immedietaly after. That way you have a better chance of having that address still available.
That, and reduce the number of programs you load on startup. There are no other solutions and there is nothing we can do with the current vm implementation.
And it's precisely this kind of problems that made us decide we will remove the Vm version as soon as the vtlb is better implemented.
And about vista, I use vista and it works perfectly. It's all about how many and which programs you have on load on statup.