Next Generation Emulation banner
1 - 20 of 37 Posts

xushao

· Registered
Joined
·
4 Posts
Discussion starter · #1 ·
Hi zerofrog,

Please help me to disable the SE_Lock_Memory setting. I am running XP Home SP2. I know I can't do it through control panel. And I have no idea how to disable it through other means. Your source code suggests that you don't record it in registry and that implies it does have affect the XP system, since I don't have that user name window anymore when I star the PCSX2. If the system remebers it, I would like to revese the action to disable it for the safty of my other programs.

Would you kindly let us know how to disable it in XP SP2 Home?

Thanks,
 
it can't be done under XP Home.

sorry.

even adding GPEDIT.MSC does not work,.. it returns a can't open group profile setting
 
It makes me wonder why anyone would buy the Home version. It's like ME with better drivers :spy:

Anyways, I'm assuming that if PCSX2 can set the attribute, it can unset it too? If any devs are reading this, please consider adding the option to unregister this setting.
 
Pro has very little difference to XP, why people get the stupid illusion the word 'pro' makes it all magical and special is beyond me.

Also being a winXP Home (SP2) user, I have no problems using the VM build. Make sure your username has admin level privilages on that machine.
 
@CKEmu

His problem wasn't setting it, it was unsetting it.

Pro is definitely better than Home in my experience. The cost is nearly identical when you buy it bundled, so it really makes no sense at all to buy Home.
 
Pro has very little difference to XP, why people get the stupid illusion the word 'pro' makes it all magical and special is beyond me.

Also being a winXP Home (SP2) user, I have no problems using the VM build. Make sure your username has admin level privilages on that machine.
Pro has a few major differences compared to home.

such as the Global policy and user editor, advanced machine and networking management. etc.

i personally find Home is unusable in a home network situation. i need access to the gpedit to properly share resources.
 
I had same problem when I used XP Home...
You should search on google wich file is needed for this option (can't remember now, sorry) and copy it from an XP Pro or an Media Center and put in your System32 (if I remember good...) and run it (directly from here), after you can change that impostation... :)
Should work.. :D
 
did you not read what i said.

Copying GPEDIT.msc to XP Home will NOT WORK, the required user profile entries aren't there., i've tried. he'll need to find some other way to disable it
 
:p depends when he installed pcsx2
 
Download the source, goto windows/WinMain.c and look up the WinMain function. You should see a

SysLoggedSetLockPagesPrivilege( GetCurrentProcess(), TRUE)

Change the TRUE to FALSE.

Then make sure you compile it and run it. If you can't compile the whole project for some reason, just take out SysLoggedSetLockPagesPrivilege and all the functions it touches and create a new program. If you don't know how to compile, perhaps someone will be nice enough to do it for you.

However, this is a waste of time... having SE_LOCK_MEMORY off doesn't mean your computer is more secure.
 
Sorry Zerofrog, after an hour and a half fixing the b0rked 2005.vcproj settings from the source available at pcsx2.net, I found out that your suggestion doesn't work.

If I change SysLogged...(...,FALSE) and run the resulting .exe it correctly tells me that it cannot register the virtual memory. However, this only lasts for the one run. If I reboot (or not) and then check the 'Lock Pages..' policy setting, my user name is still there, and the stock VM build still works (without asking to set the privilege again).

I went a bit further and put some debug points in to see if there was an error somewhere, but nothing seemed out of the ordinary. It would seem that the process you are using to set the privilege is either 'one-way' or incorrectly configured for removing it.

You're right that leaving the privilege isn't going to harm anything, but I do still think it would be the 'proper' thing to provide a means of undoing anything the emu does to ones' system. Of course, I'm not personally going to complain about it if it doesn't happen until the emu reaches v1.0+ ;)
 
if you'd really like to remove this user right, at the 99% likely risk of losing your ability to log in to windows, try:

- fire up regedit
- add read/write permissions to the HKLM/Security key
- navigate to HKLM/Security/Policy/Accounts/INSERT-YOUR-USER-SID-HERE/Privilgs
- (note that the privilege may be assigned to a group you're a member of, so you'll have to fish around different SIDs until you find one that contains the lockmemorypages privilege as described below)
- edit the only value in the key (default value)
- subtract 1 from the first value (this is the count of privileges)
- after altering that first byte, skip forward 7 bytes (this marks the start of privileges)
- if the byte you're now on is '04', delete that byte and the 11 null bytes ('00') that follow it, hit ok, and after a restart you're done!
- if the byte you're now on is not '04', it's not the 12-byte value we want to delete. skip forward 11 bytes to the next privilege marker (privileges are listed in this value with an 8-byte header indicating the privilege count that follows, and a series of 12-byte privilege markers). if the byte you're now on is not '04' again, continue on 11 more bytes etc.

all information came from www.beginningtoseethelight.org/ntsecurity/ (search for selockmemoryprivilege)

if you actually follow this advice, i doubt you'll ever be able to login to winxp again. but dag nammit that privilege will finally be gone from your account.
 
1 - 20 of 37 Posts