Messages - mraeryceos [ switch to compact view ]

Pages: prev1 2 3 [4] 5 6 7 8 9next
16
Finished Programs / Re: SOLVED: GUI for DISM
« on: June 02, 2013, 02:13 AM »
Thanks Shades.  I edited my original post to better explain what I want.

I used nLite back in the day.  I think the current popular one is RT7 Lite http://www.rt7lite.com/rt-se7en-lite.html.  I thought I would go with the Microsoft version, and have been using Windows Embedded Standard 7 instead.  However, WES7 does not include ""Turn Windows features on or off", because they figure that isn't needed by professionals, as professionals would use the command line version called DISM instead.  Right after I get to a good stopping point on WES7, I will switch to WES8, oops, I mean WE8S (man, why did they have to keep switching their naming conventions???)

There are other forums more closely related to this topic, but there isn't a place to ask people to work on something for a donation.  I could and do go to other places to pay for "coding snacks", but here I hope to find someone that likes the idea, and wants to do it even if money isn't a motivation.  That's the best!

17
I don't know if disabling ACL is possible.  It may be, but I don't have a clue how to do it.  I have thought of a work-around, that doesn't disable ACL, but makes everyone a ROOT user, sort of.

The best way I can think to do this, is to follow the path of WinPE, where the only account that is functional is SYSTEM.  So in the installer for Windows (the DVD or the USB key), you would change all references of TrustedInstaller (and it's SID), to that of SYSTEM.

I don't know how you would keep the ability to have multiple users, since I think there can only be one SYSTEM account (unlike the Administrator's "group").  Maybe by changing all references to TrustedInstaller and SYSTEM to a unique member of the administrator's group?  I don't know if this would work though... it would have to be very thorough.

I don't think you could change all users to TrustedInstaller, because I'm not sure that TrustedInstaller is an actual user.  It is a "security principal", whatever that means, and I don't think it has a user profile (SYSTEM has registry hives in system32\config, and I don't know if TrustedInstaller does).

ps.  IMO, FAT32 is a more elegant (because of it's simplicity), and faster file-system than ntfs for smaller partitions (8GB and less).  I wish to state this, and not argue this with dictator mentalities, that are unwilling to look up info for themselves, and would likely refute hard data if put in their hands.

18
Finished Programs / SOLVED: GUI for DISM
« on: May 30, 2013, 12:16 AM »
Looking for a GUI for DISM

Basically, I want it to look like "Turn Windows features on or off", only working off cab files in a DS (distribution share).  Also, as a bonus, would be nice to be able to use this booted from a flash drive, on a system that is offline.

There are some existing GUI's for DISM, but they don't list and explain the different packages, with checkboxes next to them (the checkboxes to add/remove the packages).  Package dependencies could show up highlighted on the list.  Hovering over a highlighted package could show which currently installed, or about to be installed package(s) require it.

I guess this isn't exactly a "coding snack", but it should be easy if the underlying foundation is already there, and you just need a GUI for it.

The original title for this was "GUI for pckmgr".  I found out pckmgr was deprecated, and replaced with DISM.  I got the idea that maybe pckmgr had the ability to work on both online and offline systems.  The "offline" part is a little confusing: it only works on WIM files (for making custom Windows installers).  DISM is the same.  The semantic difference is the "installer" versus the "installation".  They call the WIM file an "offline" system.  I think of an offline system as a windows installation that isn't running.  I am pretty sure that both pckmgr and DISM don't work on a windows installation, only on a mounted WIM file.

19
Yes, there are programs that do this.  I could even do it myself by having SetACL in the right-click context menu for all files.  I suppose I could even find some registry editing program that would have a command in the context menu to takeown+grant.  However, disabling ACL lookups by the system would be better.

20
I am trying to figure out what you are trying to do is it so you can delete files or are you sick of the annoying popups.

depends on what you are trying to do you may not need to disable acl.
-dreamfuture

Ideally, the system efficiency would be improved because ACL does not exist in the registry or file system.  However, I would be willing to accept something that automatically does takeown and grants permission anytime you are denied access.  For the file system, Unlocker works most of the time... I keep it in the send-to context menu.  Perhaps something for the registry as well?

Pages: prev1 2 3 [4] 5 6 7 8 9next
Go to full version