SRL Archive - MSI Bugs

I have installed simba into a my documents so that i dont need to run it as admin. I have also ran simba as admin, and restarted it numerous times (atleast 15 ) and i still get this error. Im using windows 7 and its a 64bit i believe, any suggestions? I have also completly deleted simba and re-installed it. All other scripts work, the MSI form and everything works great, as soon as the script starts up and has logged in i get the error.

Can you post the whole error?

Acces violation in ??? or something.

SPS, it says to run as admin but i am :S

We're having major issues with 64-bit Windows and SPS. My desktop (32-bit) works perfectly without error, but my laptop (64-bit) errors every time no matter what. We've been aware of this for a while and working to get it resolved. Sorry for the inconvenience.

For now, you'd have to run MSI with a script that doesn't walk (Any powerscript would work). I am working on a walker that's could act as a failsafe in-case SPS doesn't work

Having this same problem. Somewhat glad to see others are facing the same problem as well.

I mostly run MSI with my army anyways, so it's not really a matter of life and death for me. :)

From: Coh3n
We're having major issues with 64-bit Windows and SPS. My desktop (32-bit) works perfectly without error, but my laptop (64-bit) errors every time no matter what. We've been aware of this for a while and working to get it resolved. Sorry for the inconvenience.

That's weird, cause my 64 Bit Windows laptop runs MSI with SPS just fine. Never got the "Access Violation" error. Could it be the actual version on Windows? Like XP/Vista/7?

From: Camo Developer
That's weird, cause my 64 Bit Windows laptop runs MSI with SPS just fine. Never got the "Access Violation" error. Could it be the actual version on Windows? Like XP/Vista/7?

Could be, what version of Windows are you running?

Anyone who's getting the error please post your version of Windows. I get it on my Win7 64-bit laptop.

I'm running Windows 7 Home Premium 64 bit.

From: Camo Developer
I'm running Windows 7 Home Premium 64 bit.

Well, there goes that idea. I'm running the same on my laptop.

Regardless, we've found a temporary solution. More details can be found here.

I'm running Windows XP SP3, and getting the Access Violation even though I have the current version of SPS.

From: shstiger2009
I'm running Windows XP SP3, and getting the Access Violation even though I have the current version of SPS.

Are you running Simba as an admin?

From: shstiger2009
I'm running Windows XP SP3, and getting the Access Violation even though I have the current version of SPS.

Same, running on the only windows xp account on the installation. Everything works fine until about 5 secs after you login into a runescape server. At one point it put my cash stack in the bank and withdrew vials but, then the error just popped up again and I haven't been able to get anywhere near that one time.

I'm pretty sure I'm 32-bit btw.

http://villavu.com/forum/showthread.php?p=842063#post842063

From: Coh3n
We're having major issues with 64-bit Windows and SPS. My desktop (32-bit) works perfectly without error, but my laptop (64-bit) errors every time no matter what. We've been aware of this for a while and working to get it resolved. Sorry for the inconvenience.

add 64bit linux in there too, not sure why it doesn't work well =[

I'm sure running in wine isn't much different than 64bit windows though

From: Coh3n
Well, there goes that idea. I'm running the same on my laptop.

Regardless, we've found a temporary solution. More details can be found here.

hate to destroy your idea even more (I figured it would be a good one to figure which OS's specifically.).. but……
one of my VM's with xp sp3 has no probs, one does.. I just went to test, they're clones of a different VM so basically identical lol -.-

makes me wonder what really even can cause this

Use {.libload sps}

I'm on 64bit Win 7 and I haven't had an issue since I did that.

From: Bam Bam
Use {.libload sps}

I'm on 64bit Win 7 and I haven't had an issue since I did that.

Don't you need this?

{$loadlib libname}