ChrisR Posted December 13, 2013 Author Posted December 13, 2013 Temporary Problem SolvingNew Pintool 1.2.2.1 - Test VersionClassic Shell - Boot - Start Pin - Not Action - SolvedPre-generated Folder.....\AppData\Roaming\ClassicShell\PinnedI just test your last Pintool 1.2.2.1 with the ClassicShell\Pinned folder created.It seems OK, it makes the job By cons I left in Pecmd.iniEXEC =%SystemRoot%\system32\PinTool.exe -debug %SystemDrive%\Windows\System32\Win8.1SE.cfgIf it is done too early, explorer is not pinned to the taskbar.
neon2m Posted December 14, 2013 Posted December 14, 2013 (edited) Build - 1 - Copy FilesIF Not Check - Add boot.wim Fonts - Then- Mdoern UI Up, Down Button Crash --> [] [] []- Solved - Copy Font 'seguisym.ttf' Edited December 14, 2013 by neon2m
ChrisR Posted December 14, 2013 Author Posted December 14, 2013 seguisym.ttf added in the standard fontDone, thanks
ChrisR Posted December 16, 2013 Author Posted December 16, 2013 Does it have NetFramework ?No, not now, not yet
ChrisR Posted December 16, 2013 Author Posted December 16, 2013 Project Updated: Win8.1SE_2013-12-16 Thank you very much for the first comments and feedback and Improvements : Win8.1SE uses ADK for Win8.1, it is unfortunately not compatible with Windows XP, 2003 and Vista HostOS . A check was added. Improvements, changes and additions:Main script: bouton added with the list of Official Windows 8.1 Enterprise Evaluation 32 and 64 bit.Images configuration: Check compatible HostOS.1 - Copy Files: Servicing added for drivers integration.2 - Shell & Config: Pin to StartMenu compatible with StartIsBack and Classicshell now. Thanks neon2m. Instead of deleting service, keep it with start=4 not to be started under any conditions. Thanks Kullenen.Internet Explorer 11: Improvement in the case of different files between boot.wim and Install.wim. Thanks Lancelot & hehe520.Classic Shell: New Classic Shell Start Menu v4.0.2 added. Thanks neon2m for the initial version. There were many more options in ClassicShell for Win7pese to customize. they can be added, if needed. if you feel it fuwi Media Player Classic-HC: windows media Drm SDK, required for win8.1SE logon. Thanks hehe520Driver Integration: New, I expected also B)BootIce Pauly: updated to v1.321 2013.12.10.0, Thanks master pauly Notes:There is a concern between VirtualBox script and Win8.1SE currently. It works by calling the ISO directly in VirtualBox. It is in good hands.Following the addition of 1-Pin.script, compatible with Win7 & Win8pese, you can manually delete the old 1-Pin8.script. Important: Always Check Win8.1SE topic post 1 to get latest updates and informations. Happy holiday season
Kullenen_Ask Posted December 16, 2013 Posted December 16, 2013 Just for information.Media Player Classic-HC: windows media Drm SDK, required for win8.1SE logon. Thanks hehe520There 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 waysFirst 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)
ChrisR Posted December 17, 2013 Author Posted December 17, 2013 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) Thank you for the tip : , successfully tested in x86, I still try in x64 before putting it on server.wmdrmsdk.dll was only 457 Kb, always good to take
neon2m Posted December 18, 2013 Posted December 18, 2013 Build Ver 12/10My PecmdInit.ini EXEC =%SystemRoot%\system32\shortcuts.exe -f %SystemDrive%\Windows\System32\Win8.1SE.cfg...Boot ok! Start Menu and TaskBar all Good! But....Build Ver 12/16My PecmdInit.ini EXEC =%SystemRoot%\system32\shortcuts.exe -f %SystemDrive%\Windows\System32\Win8.1SE.cfg...Boot Error! Registy Error and Shut down!Why?
Kullenen_Ask Posted December 18, 2013 Posted December 18, 2013 Why could not get rid of the shortcuts.exe for years? pecmd.exe creates shortcuts successfully.
ChrisR Posted December 18, 2013 Author Posted December 18, 2013 Hi neon2m, I tried with the same change: shortcuts.exe moved from Pecmd.ini to PecmdInit.ini.It operated here ! I do not know what's wrong ! Is it OK without this change. Do you have any additional scripts, applications ?What is your Win8.1 source DVD?9600.16384.WINBLUE_RTM.130821-1623_X86FRE_ENTERPRISE_EVAL_KO-KR-IRM_CENA_X86FREE_KO-KR_DV5.ISO9600.16384.WINBLUE_RTM.130821-1623_X64FRE_ENTERPRISE_EVAL_KO-KR-IRM_CENA_X64FREE_KO-KR_DV5.ISOor others. You can perhaps share the log.Enable "Create Support Log" in Main Configuration and share log_201...Win8.1SE_Support.7z. For information, All the changes are written in my post above.
ChrisR Posted December 18, 2013 Author Posted December 18, 2013 Hi KullenenWhy could not get rid of the shortcuts.exe for years? pecmd.exe creates shortcuts successfully.I do not really know what's wrong in neon2m's build!. Creating shortcuts is not a complicated thing. Pecmd or shortcuts.exe, both do it well. And both do more than just shortcuts.Shortcuts.exe is compatible with almost All scripts that can be found around The scripts use the function (the macro) Add_Shortcut, It is very easy and useful to write in a script (Add_Shortcut,Desktop,.. Add_Shortcut,StartMenu,..., )Add_Shortcut writes in the configuration file (Win8.1SE.cfg here) which is used by shortcuts.exe at startup. Win8.1SE.cfg example:[shortcut]Accessories|Notepad|%SystemRoot%\system32\notepad.exe||Shortly, shortcuts.exe is fully compatible with Macro Library and scripts around, not Pecmd.Otherwise, of course you can use the great Pecmd, I have nothing against him but you must manually write pecmd.ini
ChrisR Posted December 18, 2013 Author Posted December 18, 2013 (edited) Posted by error, Edited December 18, 2013 by ChrisR
neon2m Posted December 18, 2013 Posted December 18, 2013 (edited) * Test - Add Script (Current Scripts and pecmd Scripts - All Good)--------------------For PECMD script 2014.01.18 --------------------Build - 1 - Files.Scripts [process]....If,Not,ExistFile,%PECfg%,Run,%ScriptFile%,CreatePECfg,%PECfg%If,Not,ExistFile,%PECfgCD%,Run,%ScriptFile%,CreatePECfg,%PECfgCD%If,Not,ExistFile,%target_sys%\winpeshl.ini,FileCreateBlank,%target_sys%\winpeshl.ini....//--For pecmdIf,Not,ExistFile,"%Target_Sys%\PECMDExec.ini",FileCreateBlank,"%Target_Sys%\PECMDExec.ini"If,Not,ExistFile,"%Target_Sys%\PECMDlink.ini",FileCreateBlank,"%Target_Sys%\PECMDlink.ini"If,Not,ExistFile,"%Target_Sys%\PECMDPint.ini",FileCreateBlank,"%Target_Sys%\PECMDPint.ini" //---------------Build - Macro_Library [Add_Auto_Run2]...TXTDelLine,%PE_CFG%,"#4|#1|#2#$s#3"IniWriteTextLine,%PE_CFG%,autorun,"#4|#1|#2#$s#3" //--------------------//Start-autorun4PECMDExecSet,%SC2ExecFile%,"%Target_Sys%\PECMDExec.ini"Set,"%SC2EXECopt%",""If,#4,Equal,wait,Set,%SC2EXECopt%,"="If,#4,Equal,nowait,Set,%SC2EXECopt%,""If,#4,Equal,hidewait,Set,%SC2EXECopt%,"!="If,#4,Equal,hidenowait,Set,%SC2EXECopt%,"!"//IniWrite,%PE_CFG%,"autorun4PECMD","#2#$s#3","#4"TXTDelLine,%SC2ExecFile%,"EXEC %SC2EXECopt%#2#$s#3"TXTAddLine,%SC2ExecFile%,"EXEC %SC2EXECopt%#2#$s#3",Append//End-autorun4PECMDExec//-------------------- --------------[AddShortcut2]...Else,Begin If,#1,Equal,Autorun,Run,%API%,Add_Auto_Run%API_TYPE%,#4,#3,#6,2 //-------------------- //Start-shortcut4PECMDLINK Else,Begin TXTDelLine,%PE_CFG%,"#1|#4|#3|#7|#6" IniWriteTextLine,%PE_CFG%,shortcut,"#1|#4|#3|#7|#6" //-- //Do-shortcut4PECMDLINK Set,%SC2LinkFile%,"%Target_Sys%\PECMDlink.ini" Set,%SC2LnkPath%,"#$pPrograms#$p\#1" Set,%SC2Option%,#6 Set,%LenSC2Option%,0 //-- Set,%SC2IconInfo%,#7 Set,%LenSC2IconInfo%,0 //-- IF,"#1",EQUAL,Desktop,Set,%SC2LnkPath%,"#$pDesktop#$p" IF,"#1",EQUAL,".",Set,%SC2LnkPath%,"#$pPrograms#$p" IF,"#1",EQUAL,QuickLaunch,Set,%SC2LnkPath%,"#$pQuickLaunch#$p" //-- StrFormat,LEN,%SC2Option%,%LenSC2Option% StrFormat,LEN,%SC2IconInfo%,%LenSC2IconInfo% //-- IF,%LenSC2Option%,NotEQUAL,0,Set,%SC2Option%,"#$c#6" IF,%LenSC2IconInfo%,NotEQUAL,0,Begin StrFormat,REPLACE,#7,"#$c","#$s# ",%SC2IconInfo% Set,%SC2IconInfo%,"#$c%SC2IconInfo%" IF,%LenSC2Option%,EQUAL,0,Set,%SC2Option%,"#$c" End //IniWrite,%PE_CFG%,"shortcut4PECMD","%SC2LnkPath%\#4","#3%SC2Option%%SC2IconInfo%" TXTDelLine,%SC2LinkFile%,"Link %SC2LnkPath%\#4#$c#3%SC2Option%%SC2IconInfo%" TXTAddLine,%SC2LinkFile%,"Link %SC2LnkPath%\#4#$c#3%SC2Option%%SC2IconInfo%",Append End //End-shortcut4PECMDLINK //--------------------End ------------------[Add_Pin_Process2]... IniWrite,%PECfg%,PINTOOL,#1#2,#3|#4|#5|#7|#8||#6 If,Not,-#9-,Equal,--,IniWrite,%PECfg%,PINTOOL,#1#2_Description,#9 //-------------------- //Start-pin4PECMDPint Set,%SC2PintFile%,"%Target_Sys%\PECMDPint.ini" If,#1,Equal,StartMenu,Set,%SC2PintType%,StartMenu If,#1,Equal,TaskBar,Set,%SC2PintType%,TaskBand TXTDelLine,%SC2PintFile%,"Pint #3#$c%SC2PintType% //#2" TXTAddLine,%SC2PintFile%,"Pint #3#$c%SC2PintType% //#2",Append //End-pin4PECMDPint //-------------------- --------------------win7/8 pecmd.iniLOAD %SystemRoot%\system32\PECMDExec.iniLOAD %SystemRoot%\system32\PECMDLink.iniLOAD %SystemRoot%\system32\PECMDPint.ini win8.1pecmdinit.iniLOAD %SystemRoot%\system32\PECMDExec.ini pecmd.iniLOAD %SystemRoot%\system32\PECMDLink.iniLOAD %SystemRoot%\system32\PECMDPint.ini Edited January 18, 2014 by neon2m
ChrisR Posted December 18, 2013 Author Posted December 18, 2013 Is it OK for you now ?As you said, it is probably a result of timing.I have done well or I'm lucky to let shortcuts.exe in Pecmd.ini and not to move it in PecmdInit.ini As explained above, for now, shortcuts.exe is retained for compatibility with Macro Library and existing scripts.To fully use Pecmd, it must be done manually as did neon2m.And for information, creating shortcuts takes at most 1 or 2 seconds, displaying is a bit slower.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now