I'm working on some solutions for the shell problem but in the meantime have a go at instead using the process.start command which is apparently a lot more uac friendly, it should work the exact same, an example being Process.Start("ReadMe.txt").
As for the users with the problem, have a go at trying some compatibility related settings on both the editor and Mojos exe.
Heres some extra stuff to help figuring this crap out.
I'll also look into more 'safety checks' to lower the complexity of it all.Code:process.StartInfo.FileName = "C:\Windows\system32\cmd.exe" process.StartInfo.Arguments = " /k ""c:\windows\system32\nbtstat.exe -a " + clientIP + """"









I am currently installing win7 on my notebook.
Update 5.1 should work for everyone.
What i have shown you is reality. What you remember... that is the illusion.
Is it a 64 bit version?
I tried the editor myself in one of my x86 win 7 virtuals and it worked fine.
If the users with problems are running on x64 then its a UAC issue and theres a number of ways to fix that.









What i have shown you is reality. What you remember... that is the illusion.
Im having a problem everytime i open my save it says oops i could not decrypt your save please try again ? but no luck whats up with it








