Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×

Kullenen_Ask

Member
  • Content Count

    316
  • Joined

  • Last visited

  • Donations

    $0.00 

Community Reputation

0 Neutral

About Kullenen_Ask

Profile Information

  • OS
    XP Pro x86

Recent Profile Visitors

2,465 profile views
  1. For to make a winpe i have captured some settings thats need to be changed. You can make your winpe easly by your hands without need third party software. I will not explain as easy as novice can understand but expert users can understand and apply easly. First need to take a booting winpe from boot.wim index 1 or 2 Need to take DEFAULT,SOFTWARE,SYSTEM,NTUSER.DAT registry hives from install.wim of install DVD Need to change all C:\ D:\ or etc. values to X:\ values in this hives with 3rd party tools. (I will not give name, The authors of such tools exist around) I prefer to use I
  2. I am sharing my file list for extreme removal. You can add "copy" lines and make a batch file and easly create your own file list to build PE. (Change your language with tr-TR). You can build your WinPE with WinPeSE and extreme remove unneeded files. Wireless icon needs some more files (Shouldn't be more then a few) Search function can be need one or two file (Searches only in start menu and shows wrong result. mssvp.dll or prn001f.dll something like that files maybe need.) There are all files needed to login as Administrator. There are extra 5mb files for my extra programs. You can
  3. Best one is 6.1.7600.16385 (win7_rtm.090713-1255). I have never had problem with it. And it is not same size you wrote B.1 7/Waik3/PE3.x->6.1.7600.16385->14/07/2009->103,312 bytes mine is 6.1.7600.16385->14/07/2009->95,0 KB (97.280 bayt) There should be a mistake between two B.1 7/Waik3/PE3.x->6.1.7600.16385->14/07/2009->103,312 bytes B.2 7SP1/Waik3/PE3.1->6.1.7601.17514->20/11/2010->97,280 bytes
  4. For info: http://forums.mydigitallife.info/threads/52374-Windows-8-1-Build-9600-16610-DISM-Now-Can-Work-On-ESD
  5. Tools on MDL works pretty nice. As i know only new dism 6.3.9600.17031 supports to apply esds and it should be inside WADK for Windows 8.1 Update. If you do not see a reason for to add new adk you managed to get it work with older dism version? Because Winntsetup uses the waik tools
  6. It is very important functionality that the number of esd setups very increased because of small their small sizes. Winntsetup updated for esds? Theese tools will need to be used on it i think.
  7. Hi Chris; I think i solved the problem. Maybe not to trust setacl much. After I used setacl i have not checked permissions are ok. I mounted the wim to a folder under system account. From explorer permissions page i took the ownerships with inheriting child objects. Checked files to be sure. After removed inheriting child objects (It is just my decision maybe not need). After boot it looks like my all users have permissions of everything. Hope permissions stays. I was helpfull to know that it works for you. By the way i think i know the answer of this topic but i could not understand what is t
  8. But it has side effects at program setups in winpe. I have not set up much programs but one is complains about access denied when i try to install it.
  9. Hi. I take ownership of a file under winpe. Right click context menu works ok but it looks like do nothing because when i look to permissions of that file i see that administrator has no rights to do anything again. Trusted installer takes control again? Any idea?
  10. Why could not get rid of the shortcuts.exe for years? pecmd.exe creates shortcuts successfully.
  11. Just for information. There is a key "HKEY_LOCAL_MACHINE\SOFTWARE_00\Microsoft\Active Setup" in software hiv. It tells to run first time customizations to windows. When the first time customizations finishes it creates a key "HKEY_LOCAL_MACHINE\NTUSER\Software\Microsoft\Active Setup" to users "ntuser.dat" hiv. There are 3 ways First is to delete unwanted startup customizations under HKEY_LOCAL_MACHINE\SOFTWARE_00\Microsoft\Active Setup\Installed Components\ (I do not prefer) Second is to add keys under "HKEY_LOCAL_MACHINE\NTUSER\Software\Microsoft\Active Setup\Installed Components" to make wi
  12. %SYSTEMDRIVE%\"Program Files\Apoint2K\Apoint.exe" to %SYSTEMDRIVE%\Program Files\Apoint2K\Apoint.exe or %ProgramFiles%\Apoint2K\Apoint.exe
  13. Hi Chris; I compared the registry with install.wim and winpe.wim. And i see a problem that setupacl makes unwanted changes when it taking ownerships of the hivs. Especially at "Properties" keys thats belongs to system user. Corruption is in the attached files new.reg and deleted.reg. Also there is a hiv that shows what changes made on the original hives. As you can see corruption also exist in the hiv. I tried another tool subinacl and also it made same corruption on the hives Normally you do not make so many changes on the hives but i see it a problem in my side. I also think that it is not
  14. With one word of summarize it is "Awesome" It is good you keep it clean this time. Looks like not many garbage code. Will keep it in my achive in case of it can get its way lost again. It is the new generation and very different from all other winbuilder versions previously created. We see first time full registry hivs get used without much modifications as i was adviced years beforethat. It were be much and much better if it were untouched except some must to touch keys. I always prefer to keep microsoft untouched and if there will be modifications they should be kept out of core with the us
×
×
  • Create New...