Kullenen_Ask

Member
  • Content count

    315
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Kullenen_Ask

Profile Information

  • OS
    XP Pro x86
  • Country
  1. 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 remove them. %70 control panel works. Supports x86 programs. You can delete dism folder to save space. Smaller then nanoserver. It is x64 10586 Windows 10 PE with 296Mb boot.wim size. File_List.txt
  2. 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
  3. For info: http://forums.mydigitallife.info/threads/52374-Windows-8-1-Build-9600-16610-DISM-Now-Can-Work-On-ESD
  4. 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
  5. 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.
  6. Thanks for such nice tool.
  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 the exact problem. Can you summarise http://theoven.org/index.php?PHPSESSID=2c760e845415c6ed46b9f88119754c10&topic=847.msg11060;topicseen#msg11060
  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 windows to think first run customizations done for that feature (I prefer) Third is to add all files and let windows do the all customizations. But will need the all the files (space consuming), will make windows to consume more time (registering dll's) (As you do)
  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 necessery to change all permissions on all over the hives. I do not know where that necessity comes from. I only had problems on "Classes", "Network List" about premissions. Other problematic keys already exist in the corrupted part (i call it corruption maybe it is not. we can call it undesired changes). I do not know If your premission changes solves all problems about "Access denied" because maybe trusted installer or system or any other program does not let changes after boot. There is a mistake (i think) that you are trying to go on your past experiences about winpe. This is not a winpe and winpeshell is not used so things that help and works on winpe does not works in here always. That should be kept in mind. Forexample because of somebody says "this registry key does not let this one to work" and you remove it. But that key can be needed for some other things to work. If you remove one service any other service depends on it can not start, any other, any other one and this will let a feature lost in the future. Without changing premissions of "tcpip" or removing "qos" winpe can works ok. This behaviours will let the corruption of the pure hivs in the future because everybody will say something and scripts will change. Everybody can make his changes with heir own scripts. I do not want to say nobody can do changes, they can but prefer out of the main shell script because we need some/have to changes sometimes. http://www.datafilehost.com/d/d52a0ce8
  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 users wishes. I want to make a very long comment. All are just ADVICES and you developers will go on your ways as always so please keep calm and do not blame me as a winbuilder enemy. (If it is, it could be because of diffiulties to get lost in scripts for to make little changes and maybe because of it keeps users does not give it is deserved value and in winbuilder forums we mostly see just developers create and answer their topics) Hope to see it get populer from now and deserve it's value. After i see it builds errorless last two builds (very surprising as a novice like me). I decided that it can at least get easy my winpe works with little changes. As i am writing comments same time i will try to modify scripts as my needs. Line numbers maybe change because i am modifiying it. Shell&Config Script 1-)DelOpenWithProgIds.reg can be removed and let the user overrite the values with his own desired associations later with other app scripts. Maybe users want to use windows defaults. (keep untouched) 2-)Why removed PintoStartScreen? not works? (keep untouched line 244-251) 3-)After resetting ownerships on all the hivs, why need to change ownerships again on some places. (Line 280) I do not know if ownership can be taken with registry. In there ownership means to change some keys or to change really the ownership? What is the advantage of "appinfo" and "profsvc" registry changes? In (Line 282) there is a tcpip service registry change also. It comments the reason 4-)It is better to keep unwanted service start 4 and not to delete. No harm with 4 some of them can get work for extreme modding. Line (311-339) RegDelete,HKLM,Tmp_System\ControlSet001\Services\hwpolicy -> RegWrite,HKLM,0x4,Tmp_System\ControlSet001\Services\hwpolicy,Start,4 5-)Comment outed lines //RegDelete,HKLM,Tmp_System\ControlSet001\Control\WMI\Autologger\PEAuthLog can be made start 4 without deleting with other unwanted keys. (keep keys) RegWrite,HKLM,0x4,Tmp_System\ControlSet001\Control\WMI\Autologger\PEAuthLog,Start,4 Middle note: Keep registry changes minimum and make another script and comment and code we changed this key values. Also users can see what changed over untouched registry. On main script only do C:->X: conversion, 6-)There is "RegWrite,HKLM,0x4,Tmp_System\ControlSet001\Services\i8042prt\Parameters,EnableWheelDetection,2" line 2 times in the script. (Line 418 and 284) 7-)What changes made over SAM hiv? Enable Administrator account and ? Did you give a password to it also?
  15. Batch file works ok. I am tested. Also with %PROGRAMFILES% Environment Variable @FOR %%A IN ("%ProgramFiles%\RegImport\*.reg") DO @REGEDIT /S "%%~A"