|
Audio Asylum Thread Printer Get a view of an entire thread on one page |
For Sale Ads |
183.179.34.77
In Reply to: RE: It is only an assumption posted by steppe on February 16, 2012 at 02:27:21
other Privilege Rights in one of the Security Configuration Templates, named DEFLTP.INF, in the XP PRO SP2 installation disc. It reads "SeLockMemoryPrivilege = "
Adding *S-1-5-32-544, or *SID, to it will result in AWE being enabled for the named SID, after installation.
All other privileges written in the same Template for different SIDs will appear in Local Computer Policy\....\User Rights Assignment in the exact manner as it is written in the Template. And they will be stored in the Security hive. One can see the changes in value each and every time the user rights assignment is changed. To view one's own Sam and Security hives in real time, one needs to logon as the System Account. In this connection, Psexec.exe from the System Internal can be put to good use.
However, the situation is different in XP Home SP0, SP1 and some earlier Beta versions, where there is no mention of LockMemoryPrivilege amongst a few Privilege Rights present in the Template. Nonetheless, Administrators will be assigned AWE privilege automatically. This is not the same case for XP Home SP2 though. The relevant entries for Privilege Rights can be found in dpup.inf in SP0 and SP1 etc.
I know too little about AWE and privilege assignment, and have no answer to all the questions. But what's presented, is solid.
You may aware that I've only 4 entries inside Winlogon and the UserNames/DomainNames were gone. I did so because the Administrator account was removed and there was no point logging on as such SID. I successfully logged as no one! And still got AWE. Perhaps, I've logged on using the Everyone account, i.e. S-1-1-0, which is the only account left behind after the deletion.
Back to the question of AWE in cMP. Although it says AWE successful, it also Ram Load each and every time, even when told not to do so.
And to echo Rick's comments, the effects of AWE is diminishing as we move on. I guess our Windows have become so efficient and quiet that it now closely resembles loading music files in Ram or alike. Just a guess though.
By the way, Rick, if you put NiMh batteries in, there will be no voltage regulation. The voltage will slowly drop from 1.35V to the lowest working voltage of your memory.
Follow Ups:
Using minlogon is one not always logged on as the system account?
.
.
.
It should be used in conjunction with shlwapi.dll.
Shlwapi.dll also caused a no boot. I was able to use this substitution with mini XP previously but not here. What I haven't tried yet is putting in both your shell32 and shlwapi at the same time. I will report back if that happens to work.
Quoted from MS "How the System account is used in Windows."
"The system account and the administrator account (Administrators group) have the same file privileges, but they have different functions. The system account is used by the operating system and by services that run under Windows. There are many services and processes within Windows that need the capability to log on internally (for example during a Windows installation). The system account was designed for that purpose; it is an internal account, does not show up in User Manager, cannot be added to any groups, and cannot have user rights assigned to it. On the other hand, the system account does show up on an NTFS volume in File Manager in the Permissions portion of the Security menu. By default, the system account is granted full control to all files on an NTFS volume. Here the system account has the same functional privileges as the administrator account."
Some up until now have said minlogon puts one as the default user, others more lately have said it is the system account, now you--who seems to know what you are talking about--say it is "an" administrator account. Is it "the" (real, fundamental) administrator account? Is there such a thing?
More importantly, how DOES one logon to the system account?
download a set of very useful Pstools from Windows Sysinternals.http://download.sysinternals.com/Files/PsTools.zip
Unzip and copy Psexec.exe to your system32.
In CMD, type "psexec -i -d c:\windows\regedit.exe" and enter.
A powerful Regedit will then pop up under your service.
You can also load and view other Sam and Security hives without using any 3rd party software.
How the System account is used in Windows:http://support.microsoft.com/kb/120929
"Some up until now have said minlogon puts one as the default user"It depends on what account is logged on. E.g. in SP1, after minlogon, one logon as Owner, this one is logged on as Default user, and the Default User folder will be created in C:\Documents and Settings. If logged on as Administrator, then the Administrator account.
Edit: after minlogon, one would use the Default folder in C:\Documents and Settings, as a computer users, perhaps a super one.
Edits: 02/16/12 02/16/12 02/17/12
WOW, you are speeding ahead and flying high - I cannot wait to see/hear what you come up with.
Thanks for your efforts and your generosity.
if excluding cPlay, cMP files, 1 Chinese font and C_950.nls, The config folder is now 164kb.
I want to do more file substitution before letting you know. I now use a micro-shell32. It sound so much better!
I might have found a way, as my registry slimming went exceptionally easy and smooth.
.
with .dll substitutions and registry mods you still end up in the same place (if you want to).
config at 164? Incredible!
I have not been trying much lately because I thought when I got below 300 I was just about done AND NOW you post this.
I get the feeling there must a combination aspect to further deletions since I have tried numerous "single" items with no success.
Will TRY to wait patiently for the micro-shell32 but it is NOT going to be easy.
Congratulations and thanks again.
.
Post a Followup:
FAQ |
Post a Message! |
Forgot Password? |
|
||||||||||||||
|
This post is made possible by the generous support of people like you and our sponsors: