How can i add Windows XP style ( blue taskbar, green start butoon, etc. )
to MS Windows PE? Which files i need and what i have to place i registry?
Full Version: Windows Xp Style
Here's the real answer: you can't (as of yet) enable the official themes servie on PE, But you can enable windowblinds to do a similar thing.
May I ask why you can't, a friend and I are thinking about trying to get it working and wondering if someone could give us a heads up or tip as to why it has problems.
@this is me, do you use a plug in or a registry key?
If you don't now, that WindowBlinds is a third party utility to change the look of Windows ( ANY!!! Even 98! ). But i dont know how can i add this to Pe and where it stores it registraton data. Where does it stores??? How can i add a service by adding some registry keys, because it is avialable to enable oficial styles by adding the sevice "Themes" to MS WinPE...
@remyservices,
Sorry, I was off for a while. When you run a regular XP system, winlogon tells the themes service at the right time when to enable themeing. The themeing only takes place after the windows default logon screen (logonui). With BartPE, because you set the shell using the cmdline in the registry, winlogon never tells the themes service to start themeing. Yes, you can get the themes service started and running in PE, but it never themes, because PE never tells the service that it is able to.
@betaluva,
When you use windowblinds you use plugins and reg keys that the plugin adds.
@StirolXXX
On windowblinds you get from object desktop, the reg info is stored in an ini file in the system32 directory. Here is my plugin that works fine for me:
All you do is copy all the files from the windowblinds dir to a "files" folder in the same directory as this plugin. You will also need to copy wbsys.dll and wb.ini from your system32 dir to the plugin folder. Then start wbload.exe after starting PE.
Sorry, I was off for a while. When you run a regular XP system, winlogon tells the themes service at the right time when to enable themeing. The themeing only takes place after the windows default logon screen (logonui). With BartPE, because you set the shell using the cmdline in the registry, winlogon never tells the themes service to start themeing. Yes, you can get the themes service started and running in PE, but it never themes, because PE never tells the service that it is able to.
@betaluva,
When you use windowblinds you use plugins and reg keys that the plugin adds.
@StirolXXX
On windowblinds you get from object desktop, the reg info is stored in an ini file in the system32 directory. Here is my plugin that works fine for me:
CODE
; PE Builder v3 plug-in INF file
[Version]
Signature= "$Windows NT$"
[PEBuilder]
Name="Window Blinds"
Enable=1
[WinntDirectories]
a="Programs\WindowBlinds",2
[SourceDisksFolders]
files=a,,1
[SourceDisksFiles]
wb.ini=2
wbsys.dll=2
[Default.AddReg]
0x0,"Software\Stardock\WindowBlinds\WB5.ini\Installed"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\Installed","Path","\Programs\WindowBlinds"
0x0,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","DoMenuBorders","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","UseChecks","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","UseButtons","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","UseColours","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","TaskBar","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","bitBmp","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","OptionNum","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","ShowConfig","0"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","AllowCol","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","noDiaBitmaps","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","transTxt","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","SubSkin","0"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","TOOLON","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","noExpBitmaps","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","stretchBitmaps","0"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","noFlatTool","0"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","Wallpaper","0"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","Icons","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","SysTray","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","UnloadWarn","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","Prompt","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","Fade","0"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","Over2","0"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","UserMode","0"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","SORTMODE","0"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","DoExplorerColour","0"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","FastExplorer","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","ExpTrans","0"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","Skinset","\Programs\WindowBlinds\LunaXP\LunaXP.UIS"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","Skinset2","Windows XP Style"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","LastSub","0"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","InstantOn","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","OverrideXP","0"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","InclusionList","0"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","OverrideShell","0"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","FlattenTools","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","FontResize","0"
0x0,"Software\Stardock\WindowBlinds\wb.ini\0"
0x1,"Software\Stardock\WindowBlinds\wb.ini\0","COL","65280"
0x0,"Software\Stardock\WindowBlinds\wb.ini\1"
0x1,"Software\Stardock\WindowBlinds\wb.ini\1","COL","15326093"
0x0,"Software\Stardock\WindowBlinds\wb.ini\10"
0x1,"Software\Stardock\WindowBlinds\wb.ini\10","COL","8453888"
0x0,"Software\Stardock\WindowBlinds\wb.ini\11"
0x1,"Software\Stardock\WindowBlinds\wb.ini\11","COL","8421440"
0x0,"Software\Stardock\WindowBlinds\wb.ini\2"
0x1,"Software\Stardock\WindowBlinds\wb.ini\2","COL","9982701"
0x0,"Software\Stardock\WindowBlinds\wb.ini\3"
0x1,"Software\Stardock\WindowBlinds\wb.ini\3","COL","4975603"
0x0,"Software\Stardock\WindowBlinds\wb.ini\4"
0x1,"Software\Stardock\WindowBlinds\wb.ini\4","COL","4227072"
0x0,"Software\Stardock\WindowBlinds\wb.ini\5"
0x1,"Software\Stardock\WindowBlinds\wb.ini\5","COL","8404992"
0x0,"Software\Stardock\WindowBlinds\wb.ini\6"
0x1,"Software\Stardock\WindowBlinds\wb.ini\6","COL","4227327"
0x0,"Software\Stardock\WindowBlinds\wb.ini\7"
0x1,"Software\Stardock\WindowBlinds\wb.ini\7","COL","128"
0x0,"Software\Stardock\WindowBlinds\wb.ini\8"
0x1,"Software\Stardock\WindowBlinds\wb.ini\8","COL","16777088"
0x0,"Software\Stardock\WindowBlinds\wb.ini\9"
0x1,"Software\Stardock\WindowBlinds\wb.ini\9","COL","8388863"
0x0,"Software\Stardock\WindowBlinds\wb.ini\MAP"
0x1,"Software\Stardock\WindowBlinds\wb.ini\MAP","FORCE2","255"
0x1,"Software\Stardock\WindowBlinds\wb.ini\MAP","Red","141"
0x1,"Software\Stardock\WindowBlinds\wb.ini\MAP","Green","219"
0x1,"Software\Stardock\WindowBlinds\wb.ini\MAP","Blue","233"
0x1,"Software\Stardock\WindowBlinds\wb.ini\MAP","LCOL","4"
0x0,"Software\Stardock\WindowBlinds\wb.ini\MAP2"
0x1,"Software\Stardock\WindowBlinds\wb.ini\MAP2","Enabled","0"
0x0,"Software\Stardock\WindowBlinds\wb.ini\global"
0x1,"Software\Stardock\WindowBlinds\wb.ini\global","noMenu","0"
0x1,"Software\Stardock\WindowBlinds\wb.ini\global","noStatus","0"
[Software.AddReg]
0x0,"Classes\.wba"
0x1,"Classes\.wba","Content Type","application/wbload"
0x1,"Classes\.wba","","wbload.Document"
0x0,"Classes\.wba\AlternateApps"
0x0,"Classes\CLSID\{2F5AC606-70CF-461C-BFE1-734234536262}"
0x1,"Classes\CLSID\{2F5AC606-70CF-461C-BFE1-734234536262}","","DisplayCplExt Class"
0x0,"Classes\CLSID\{2F5AC606-70CF-461C-BFE1-734234536262}\InprocServer32"
0x1,"Classes\CLSID\{2F5AC606-70CF-461C-BFE1-734234536262}\InprocServer32","ThreadingModel","Apartment"
0x1,"Classes\CLSID\{2F5AC606-70CF-461C-BFE1-734234536262}\InprocServer32","","\Programs\WindowBlinds\wbui.dll"
0x0,"Classes\CLSID\{2F5AC606-70CF-461C-BFE1-734234536262}\ProgID"
0x1,"Classes\CLSID\{2F5AC606-70CF-461C-BFE1-734234536262}\ProgID","","DisplayPage.DisplayCplExt.1"
0x0,"Classes\CLSID\{2F5AC606-70CF-461C-BFE1-734234536262}\Programmable"
0x0,"Classes\CLSID\{2F5AC606-70CF-461C-BFE1-734234536262}\TypeLib"
0x1,"Classes\CLSID\{2F5AC606-70CF-461C-BFE1-734234536262}\TypeLib","","{EAB5A27C-D97B-47F2-96E3-678D66676876}"
0x0,"Classes\CLSID\{2F5AC606-70CF-461C-BFE1-734234536262}\VersionIndependentProgID"
0x1,"Classes\CLSID\{2F5AC606-70CF-461C-BFE1-734234536262}\VersionIndependentProgID","","DisplayPage.DisplayCplExt"
0x0,"Classes\DisplayPage.DisplayCplExt"
0x1,"Classes\DisplayPage.DisplayCplExt","","DisplayCplExt Class"
0x0,"Classes\DisplayPage.DisplayCplExt.1"
0x1,"Classes\DisplayPage.DisplayCplExt.1","","DisplayCplExt Class"
0x0,"Classes\DisplayPage.DisplayCplExt.1\CLSID"
0x1,"Classes\DisplayPage.DisplayCplExt.1\CLSID","","{2F5AC606-70CF-461C-BFE1-734234536262}"
0x0,"Classes\DisplayPage.DisplayCplExt\CLSID"
0x1,"Classes\DisplayPage.DisplayCplExt\CLSID","","{2F5AC606-70CF-461C-BFE1-734234536262}"
0x0,"Classes\DisplayPage.DisplayCplExt\CurVer"
0x1,"Classes\DisplayPage.DisplayCplExt\CurVer","","DisplayPage.DisplayCplExt.1"
0x0,"Classes\Interface\{D35EA4CA-6CB8-451E-B3A0-943BC18E9439}"
0x1,"Classes\Interface\{D35EA4CA-6CB8-451E-B3A0-943BC18E9439}","","IDisplayCplExt"
0x0,"Classes\Interface\{D35EA4CA-6CB8-451E-B3A0-943BC18E9439}\ProxyStubClsid"
0x1,"Classes\Interface\{D35EA4CA-6CB8-451E-B3A0-943BC18E9439}\ProxyStubClsid","","{00020424-0000-0000-C000-000000000046}"
0x0,"Classes\Interface\{D35EA4CA-6CB8-451E-B3A0-943BC18E9439}\ProxyStubClsid32"
0x1,"Classes\Interface\{D35EA4CA-6CB8-451E-B3A0-943BC18E9439}\ProxyStubClsid32","","{00020424-0000-0000-C000-000000000046}"
0x0,"Classes\Interface\{D35EA4CA-6CB8-451E-B3A0-943BC18E9439}\TypeLib"
0x1,"Classes\Interface\{D35EA4CA-6CB8-451E-B3A0-943BC18E9439}\TypeLib","Version","1.0"
0x1,"Classes\Interface\{D35EA4CA-6CB8-451E-B3A0-943BC18E9439}\TypeLib","","{EAB5A27C-D97B-47F2-96E3-678D66676876}"
0x0,"Classes\TypeLib\{EAB5A27C-D97B-47F2-96E3-678D66676876}\1.0"
0x1,"Classes\TypeLib\{EAB5A27C-D97B-47F2-96E3-678D66676876}\1.0","","DisplayPage 1.0 Type Library"
0x0,"Classes\TypeLib\{EAB5A27C-D97B-47F2-96E3-678D66676876}\1.0\0\win32"
0x1,"Classes\TypeLib\{EAB5A27C-D97B-47F2-96E3-678D66676876}\1.0\0\win32","","\Programs\WindowBlinds\wbui.dll"
0x0,"Classes\TypeLib\{EAB5A27C-D97B-47F2-96E3-678D66676876}\1.0\FLAGS"
0x1,"Classes\TypeLib\{EAB5A27C-D97B-47F2-96E3-678D66676876}\1.0\FLAGS","","0"
0x0,"Classes\TypeLib\{EAB5A27C-D97B-47F2-96E3-678D66676876}\1.0\HELPDIR"
0x1,"Classes\TypeLib\{EAB5A27C-D97B-47F2-96E3-678D66676876}\1.0\HELPDIR","","\Programs\WindowBlinds\"
0x0,"Classes\wbload.Document"
0x3,"Classes\wbload.Document","EditFlags",00,00,01,00
0x1,"Classes\wbload.Document","","wbload Document"
0x0,"Classes\wbload.Document\DefaultIcon"
0x1,"Classes\wbload.Document\DefaultIcon","",""
0x0,"Classes\wbload.Document\shell\open\command"
0x2,"Classes\wbload.Document\shell\open\command","","\"\Programs\WindowBlinds\wbload.exe\" \"%1\""
0x0,"Microsoft\Windows NT\CurrentVersion\Windows"
0x1,"Microsoft\Windows NT\CurrentVersion\Windows","AppInit_DLLs","wbsys.dll"
0x0,"Microsoft\Windows NT\CurrentVersion\Winlogon\Notify\WB"
0x1,"Microsoft\Windows NT\CurrentVersion\Winlogon\Notify\WB","Logon","StartWB"
0x4,"Microsoft\Windows NT\CurrentVersion\Winlogon\Notify\WB","Asynchronous",0x0
0x1,"Microsoft\Windows NT\CurrentVersion\Winlogon\Notify\WB","DllName","\Programs\WindowBlinds\fastload.dll"
0x1,"Microsoft\Windows NT\CurrentVersion\Winlogon\Notify\WB","Startup","StartSys"
0x0,"Microsoft\Windows\CurrentVersion\Controls Folder\Desk\shellex\PropertySheetHandlers\WindowBlinds"
0x1,"Microsoft\Windows\CurrentVersion\Controls Folder\Desk\shellex\PropertySheetHandlers\WindowBlinds","","{2F5AC606-70CF-461C-BFE1-734234536262}"
0x0,"Microsoft\Windows\CurrentVersion\Shell Extensions\Approved"
0x1,"Microsoft\Windows\CurrentVersion\Shell Extensions\Approved","{2F5AC606-70CF-461C-BFE1-734234536262}","WindowBlinds CPL Extension"
0x0,"Stardock\ObjectDesktop\WindowBlinds"
0x1,"Stardock\ObjectDesktop\WindowBlinds","Tooltip",""
0x1,"Stardock\ObjectDesktop\WindowBlinds","CanUpgrade","1"
0x1,"Stardock\ObjectDesktop\WindowBlinds","Path","\Programs\WindowBlinds"
0x1,"Stardock\ObjectDesktop\WindowBlinds","EXE","wbload.exe"
0x1,"Stardock\ObjectDesktop\WindowBlinds","Revision","107"
0x1,"Stardock\ObjectDesktop\WindowBlinds","NeedsReboot","1"
0x1,"Stardock\ObjectDesktop\WindowBlinds","Startup","1"
0x1,"Stardock\ObjectDesktop\WindowBlinds","Disable","wbload.exe UNLOAD"
0x1,"Stardock\ObjectDesktop\WindowBlinds","Updated","03/15/2004 23:46:13"
0x0,"Stardock\WindowBlinds\WB5.ini\INSTALLED"
0x1,"Stardock\WindowBlinds\WB5.ini\INSTALLED","ver",""
0x1,"Stardock\WindowBlinds\WB5.ini\INSTALLED","RealPath","\Programs\WindowBlinds"
0x1,"Stardock\WindowBlinds\WB5.ini\INSTALLED","Path","Object Desktop"
0x1,"Stardock\WindowBlinds\WB5.ini\INSTALLED","Path2","WB-g1de774"
0x1,"Stardock\WindowBlinds\WB5.ini\INSTALLED","Path3","107"
0x0,"Stardock\WindowBlinds\WB5.ini\WBLiteFX"
0x1,"Stardock\WindowBlinds\WB5.ini\WBLiteFX","INET","O"
[Version]
Signature= "$Windows NT$"
[PEBuilder]
Name="Window Blinds"
Enable=1
[WinntDirectories]
a="Programs\WindowBlinds",2
[SourceDisksFolders]
files=a,,1
[SourceDisksFiles]
wb.ini=2
wbsys.dll=2
[Default.AddReg]
0x0,"Software\Stardock\WindowBlinds\WB5.ini\Installed"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\Installed","Path","\Programs\WindowBlinds"
0x0,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","DoMenuBorders","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","UseChecks","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","UseButtons","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","UseColours","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","TaskBar","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","bitBmp","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","OptionNum","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","ShowConfig","0"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","AllowCol","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","noDiaBitmaps","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","transTxt","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","SubSkin","0"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","TOOLON","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","noExpBitmaps","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","stretchBitmaps","0"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","noFlatTool","0"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","Wallpaper","0"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","Icons","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","SysTray","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","UnloadWarn","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","Prompt","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","Fade","0"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","Over2","0"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","UserMode","0"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","SORTMODE","0"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","DoExplorerColour","0"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","FastExplorer","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","ExpTrans","0"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","Skinset","\Programs\WindowBlinds\LunaXP\LunaXP.UIS"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","Skinset2","Windows XP Style"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","LastSub","0"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","InstantOn","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","OverrideXP","0"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","InclusionList","0"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","OverrideShell","0"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","FlattenTools","1"
0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","FontResize","0"
0x0,"Software\Stardock\WindowBlinds\wb.ini\0"
0x1,"Software\Stardock\WindowBlinds\wb.ini\0","COL","65280"
0x0,"Software\Stardock\WindowBlinds\wb.ini\1"
0x1,"Software\Stardock\WindowBlinds\wb.ini\1","COL","15326093"
0x0,"Software\Stardock\WindowBlinds\wb.ini\10"
0x1,"Software\Stardock\WindowBlinds\wb.ini\10","COL","8453888"
0x0,"Software\Stardock\WindowBlinds\wb.ini\11"
0x1,"Software\Stardock\WindowBlinds\wb.ini\11","COL","8421440"
0x0,"Software\Stardock\WindowBlinds\wb.ini\2"
0x1,"Software\Stardock\WindowBlinds\wb.ini\2","COL","9982701"
0x0,"Software\Stardock\WindowBlinds\wb.ini\3"
0x1,"Software\Stardock\WindowBlinds\wb.ini\3","COL","4975603"
0x0,"Software\Stardock\WindowBlinds\wb.ini\4"
0x1,"Software\Stardock\WindowBlinds\wb.ini\4","COL","4227072"
0x0,"Software\Stardock\WindowBlinds\wb.ini\5"
0x1,"Software\Stardock\WindowBlinds\wb.ini\5","COL","8404992"
0x0,"Software\Stardock\WindowBlinds\wb.ini\6"
0x1,"Software\Stardock\WindowBlinds\wb.ini\6","COL","4227327"
0x0,"Software\Stardock\WindowBlinds\wb.ini\7"
0x1,"Software\Stardock\WindowBlinds\wb.ini\7","COL","128"
0x0,"Software\Stardock\WindowBlinds\wb.ini\8"
0x1,"Software\Stardock\WindowBlinds\wb.ini\8","COL","16777088"
0x0,"Software\Stardock\WindowBlinds\wb.ini\9"
0x1,"Software\Stardock\WindowBlinds\wb.ini\9","COL","8388863"
0x0,"Software\Stardock\WindowBlinds\wb.ini\MAP"
0x1,"Software\Stardock\WindowBlinds\wb.ini\MAP","FORCE2","255"
0x1,"Software\Stardock\WindowBlinds\wb.ini\MAP","Red","141"
0x1,"Software\Stardock\WindowBlinds\wb.ini\MAP","Green","219"
0x1,"Software\Stardock\WindowBlinds\wb.ini\MAP","Blue","233"
0x1,"Software\Stardock\WindowBlinds\wb.ini\MAP","LCOL","4"
0x0,"Software\Stardock\WindowBlinds\wb.ini\MAP2"
0x1,"Software\Stardock\WindowBlinds\wb.ini\MAP2","Enabled","0"
0x0,"Software\Stardock\WindowBlinds\wb.ini\global"
0x1,"Software\Stardock\WindowBlinds\wb.ini\global","noMenu","0"
0x1,"Software\Stardock\WindowBlinds\wb.ini\global","noStatus","0"
[Software.AddReg]
0x0,"Classes\.wba"
0x1,"Classes\.wba","Content Type","application/wbload"
0x1,"Classes\.wba","","wbload.Document"
0x0,"Classes\.wba\AlternateApps"
0x0,"Classes\CLSID\{2F5AC606-70CF-461C-BFE1-734234536262}"
0x1,"Classes\CLSID\{2F5AC606-70CF-461C-BFE1-734234536262}","","DisplayCplExt Class"
0x0,"Classes\CLSID\{2F5AC606-70CF-461C-BFE1-734234536262}\InprocServer32"
0x1,"Classes\CLSID\{2F5AC606-70CF-461C-BFE1-734234536262}\InprocServer32","ThreadingModel","Apartment"
0x1,"Classes\CLSID\{2F5AC606-70CF-461C-BFE1-734234536262}\InprocServer32","","\Programs\WindowBlinds\wbui.dll"
0x0,"Classes\CLSID\{2F5AC606-70CF-461C-BFE1-734234536262}\ProgID"
0x1,"Classes\CLSID\{2F5AC606-70CF-461C-BFE1-734234536262}\ProgID","","DisplayPage.DisplayCplExt.1"
0x0,"Classes\CLSID\{2F5AC606-70CF-461C-BFE1-734234536262}\Programmable"
0x0,"Classes\CLSID\{2F5AC606-70CF-461C-BFE1-734234536262}\TypeLib"
0x1,"Classes\CLSID\{2F5AC606-70CF-461C-BFE1-734234536262}\TypeLib","","{EAB5A27C-D97B-47F2-96E3-678D66676876}"
0x0,"Classes\CLSID\{2F5AC606-70CF-461C-BFE1-734234536262}\VersionIndependentProgID"
0x1,"Classes\CLSID\{2F5AC606-70CF-461C-BFE1-734234536262}\VersionIndependentProgID","","DisplayPage.DisplayCplExt"
0x0,"Classes\DisplayPage.DisplayCplExt"
0x1,"Classes\DisplayPage.DisplayCplExt","","DisplayCplExt Class"
0x0,"Classes\DisplayPage.DisplayCplExt.1"
0x1,"Classes\DisplayPage.DisplayCplExt.1","","DisplayCplExt Class"
0x0,"Classes\DisplayPage.DisplayCplExt.1\CLSID"
0x1,"Classes\DisplayPage.DisplayCplExt.1\CLSID","","{2F5AC606-70CF-461C-BFE1-734234536262}"
0x0,"Classes\DisplayPage.DisplayCplExt\CLSID"
0x1,"Classes\DisplayPage.DisplayCplExt\CLSID","","{2F5AC606-70CF-461C-BFE1-734234536262}"
0x0,"Classes\DisplayPage.DisplayCplExt\CurVer"
0x1,"Classes\DisplayPage.DisplayCplExt\CurVer","","DisplayPage.DisplayCplExt.1"
0x0,"Classes\Interface\{D35EA4CA-6CB8-451E-B3A0-943BC18E9439}"
0x1,"Classes\Interface\{D35EA4CA-6CB8-451E-B3A0-943BC18E9439}","","IDisplayCplExt"
0x0,"Classes\Interface\{D35EA4CA-6CB8-451E-B3A0-943BC18E9439}\ProxyStubClsid"
0x1,"Classes\Interface\{D35EA4CA-6CB8-451E-B3A0-943BC18E9439}\ProxyStubClsid","","{00020424-0000-0000-C000-000000000046}"
0x0,"Classes\Interface\{D35EA4CA-6CB8-451E-B3A0-943BC18E9439}\ProxyStubClsid32"
0x1,"Classes\Interface\{D35EA4CA-6CB8-451E-B3A0-943BC18E9439}\ProxyStubClsid32","","{00020424-0000-0000-C000-000000000046}"
0x0,"Classes\Interface\{D35EA4CA-6CB8-451E-B3A0-943BC18E9439}\TypeLib"
0x1,"Classes\Interface\{D35EA4CA-6CB8-451E-B3A0-943BC18E9439}\TypeLib","Version","1.0"
0x1,"Classes\Interface\{D35EA4CA-6CB8-451E-B3A0-943BC18E9439}\TypeLib","","{EAB5A27C-D97B-47F2-96E3-678D66676876}"
0x0,"Classes\TypeLib\{EAB5A27C-D97B-47F2-96E3-678D66676876}\1.0"
0x1,"Classes\TypeLib\{EAB5A27C-D97B-47F2-96E3-678D66676876}\1.0","","DisplayPage 1.0 Type Library"
0x0,"Classes\TypeLib\{EAB5A27C-D97B-47F2-96E3-678D66676876}\1.0\0\win32"
0x1,"Classes\TypeLib\{EAB5A27C-D97B-47F2-96E3-678D66676876}\1.0\0\win32","","\Programs\WindowBlinds\wbui.dll"
0x0,"Classes\TypeLib\{EAB5A27C-D97B-47F2-96E3-678D66676876}\1.0\FLAGS"
0x1,"Classes\TypeLib\{EAB5A27C-D97B-47F2-96E3-678D66676876}\1.0\FLAGS","","0"
0x0,"Classes\TypeLib\{EAB5A27C-D97B-47F2-96E3-678D66676876}\1.0\HELPDIR"
0x1,"Classes\TypeLib\{EAB5A27C-D97B-47F2-96E3-678D66676876}\1.0\HELPDIR","","\Programs\WindowBlinds\"
0x0,"Classes\wbload.Document"
0x3,"Classes\wbload.Document","EditFlags",00,00,01,00
0x1,"Classes\wbload.Document","","wbload Document"
0x0,"Classes\wbload.Document\DefaultIcon"
0x1,"Classes\wbload.Document\DefaultIcon","",""
0x0,"Classes\wbload.Document\shell\open\command"
0x2,"Classes\wbload.Document\shell\open\command","","\"\Programs\WindowBlinds\wbload.exe\" \"%1\""
0x0,"Microsoft\Windows NT\CurrentVersion\Windows"
0x1,"Microsoft\Windows NT\CurrentVersion\Windows","AppInit_DLLs","wbsys.dll"
0x0,"Microsoft\Windows NT\CurrentVersion\Winlogon\Notify\WB"
0x1,"Microsoft\Windows NT\CurrentVersion\Winlogon\Notify\WB","Logon","StartWB"
0x4,"Microsoft\Windows NT\CurrentVersion\Winlogon\Notify\WB","Asynchronous",0x0
0x1,"Microsoft\Windows NT\CurrentVersion\Winlogon\Notify\WB","DllName","\Programs\WindowBlinds\fastload.dll"
0x1,"Microsoft\Windows NT\CurrentVersion\Winlogon\Notify\WB","Startup","StartSys"
0x0,"Microsoft\Windows\CurrentVersion\Controls Folder\Desk\shellex\PropertySheetHandlers\WindowBlinds"
0x1,"Microsoft\Windows\CurrentVersion\Controls Folder\Desk\shellex\PropertySheetHandlers\WindowBlinds","","{2F5AC606-70CF-461C-BFE1-734234536262}"
0x0,"Microsoft\Windows\CurrentVersion\Shell Extensions\Approved"
0x1,"Microsoft\Windows\CurrentVersion\Shell Extensions\Approved","{2F5AC606-70CF-461C-BFE1-734234536262}","WindowBlinds CPL Extension"
0x0,"Stardock\ObjectDesktop\WindowBlinds"
0x1,"Stardock\ObjectDesktop\WindowBlinds","Tooltip",""
0x1,"Stardock\ObjectDesktop\WindowBlinds","CanUpgrade","1"
0x1,"Stardock\ObjectDesktop\WindowBlinds","Path","\Programs\WindowBlinds"
0x1,"Stardock\ObjectDesktop\WindowBlinds","EXE","wbload.exe"
0x1,"Stardock\ObjectDesktop\WindowBlinds","Revision","107"
0x1,"Stardock\ObjectDesktop\WindowBlinds","NeedsReboot","1"
0x1,"Stardock\ObjectDesktop\WindowBlinds","Startup","1"
0x1,"Stardock\ObjectDesktop\WindowBlinds","Disable","wbload.exe UNLOAD"
0x1,"Stardock\ObjectDesktop\WindowBlinds","Updated","03/15/2004 23:46:13"
0x0,"Stardock\WindowBlinds\WB5.ini\INSTALLED"
0x1,"Stardock\WindowBlinds\WB5.ini\INSTALLED","ver",""
0x1,"Stardock\WindowBlinds\WB5.ini\INSTALLED","RealPath","\Programs\WindowBlinds"
0x1,"Stardock\WindowBlinds\WB5.ini\INSTALLED","Path","Object Desktop"
0x1,"Stardock\WindowBlinds\WB5.ini\INSTALLED","Path2","WB-g1de774"
0x1,"Stardock\WindowBlinds\WB5.ini\INSTALLED","Path3","107"
0x0,"Stardock\WindowBlinds\WB5.ini\WBLiteFX"
0x1,"Stardock\WindowBlinds\WB5.ini\WBLiteFX","INET","O"
All you do is copy all the files from the windowblinds dir to a "files" folder in the same directory as this plugin. You will also need to copy wbsys.dll and wb.ini from your system32 dir to the plugin folder. Then start wbload.exe after starting PE.
Here is a screenshot of PE with themes enabled and some other things I am proud of:
Answers to questions ahead of time:
Yes, this is really PE and not XP full.
Yes, that is really M$ Virtual PC running from inside of PE
Yes, I do have my NVidia 128MB Video Card, AOpen 5.1 Surround Sound Card, and v.92 Modem correctly seen and installed (although no dialup yet).
If anyone would like my plugin for VPC or any of the programs you see here, just let me know.
Answers to questions ahead of time:
Yes, this is really PE and not XP full.
Yes, that is really M$ Virtual PC running from inside of PE
Yes, I do have my NVidia 128MB Video Card, AOpen 5.1 Surround Sound Card, and v.92 Modem correctly seen and installed (although no dialup yet).
If anyone would like my plugin for VPC or any of the programs you see here, just let me know.
I want this plugin, but how did you done this PE?
Do you use WindowBlinds or M$ WinXP temes???
If M$ WinXP, how did you added the support for them???
What must i place in registry to hide from WinXP style Eplorer.exe command Logoff? I can't understand how you added drivers for sound, and is it avialable to add all dirvers form Windows XP Professional to M$ WinXP??? Because i like your WinPE!!! Did you used some plugins to add drivers or you have added them manualy? And what happens with your WinXP when you press shutdown? If it shows standart windows shutdown dialog, so where i can set command which to execute when i press shutdown??? Can i use the TGSoft StyleXP v2.0 <Cracked>
to do such skin???
Do you use WindowBlinds or M$ WinXP temes???
If M$ WinXP, how did you added the support for them???
What must i place in registry to hide from WinXP style Eplorer.exe command Logoff? I can't understand how you added drivers for sound, and is it avialable to add all dirvers form Windows XP Professional to M$ WinXP??? Because i like your WinPE!!! Did you used some plugins to add drivers or you have added them manualy? And what happens with your WinXP when you press shutdown? If it shows standart windows shutdown dialog, so where i can set command which to execute when i press shutdown??? Can i use the TGSoft StyleXP v2.0 <Cracked>
to do such skin???
Look for the enable_shutdown plugin at http://popup3.tok2.com/home2/waaaamc/plug/...le_shutdown.zip. You can't logoff from PE because you don't ever log on.
So this may be a stupid question but how do you get WindowBlinds running?
Did you not see the instructions in this thread.
@this-is-me
Yes, pretty please, post your VPC plugin !
Yes, pretty please, post your VPC plugin !
Sorry I missed th elines where it said to copy the files.
I tried doing this but got and error when I tried to add the plugin in PE Builder:
Error: SetupIterateCabinet failed
System error code: 0xD
System error message: The data is invalid
I am new to making plugins and am completely lost.
I tried doing this but got and error when I tried to add the plugin in PE Builder:
Error: SetupIterateCabinet failed
System error code: 0xD
System error message: The data is invalid
I am new to making plugins and am completely lost.
Due to popular demand, the main plugins featured here are now here.
If you have questions, please post here instead of PM'ing me.
DOWNLOAD AND READ INSTRUCTIONS BEFORE ASKING QUESTIONS!!!
Answers to questions ahead of time:
The WindowBlinds plugin will work best if the explorer plugin is also enabled.
Yes, you may need winlogon... (don't ask)
Explorer is not the default shell when these are enabled.
To do that, copy this code to a plugin:
This may not be all that is needed for these plugins, because I have many more plugins, and they all interrelate with each other to provide functionality. If anyone has problems, ask me. Also, Check this link for my answers to questions on my explorer plugin:
http://www.911cd.net/forums/index.php?showtopic=5135
If you have questions, please post here instead of PM'ing me.
DOWNLOAD AND READ INSTRUCTIONS BEFORE ASKING QUESTIONS!!!
Answers to questions ahead of time:
The WindowBlinds plugin will work best if the explorer plugin is also enabled.
Yes, you may need winlogon... (don't ask)
Explorer is not the default shell when these are enabled.
To do that, copy this code to a plugin:
CODE
[SetupReg.AddReg]
0x1, "Setup", "CmdLine", "explorer.exe"
0x1, "Setup", "CmdLine", "explorer.exe"
This may not be all that is needed for these plugins, because I have many more plugins, and they all interrelate with each other to provide functionality. If anyone has problems, ask me. Also, Check this link for my answers to questions on my explorer plugin:
http://www.911cd.net/forums/index.php?showtopic=5135
this-is-me:
Thanks for sharing your plugins! I would like to see your plugins for Foobar and IZarc.... ?
Thanks for sharing your plugins! I would like to see your plugins for Foobar and IZarc.... ?
Actually, for foobar2000, all you have to do is copy the whole foobar2000 folder to a plugin. No regedits are needed. You can get foobar2000 from foobar2000.org If you want wma support, also copy wmasf.dll and wmvcore.dll to the system32 folder on your CD.
The plugin for IZArc is now in the plugins pack above.
The plugin for IZArc is now in the plugins pack above.
Hi, I'm a newbie. A teacher told me 'bout this PE and I'm really interested. But now I want to have a XP style. I read the posts before. But when I choose WindowBlinds as plugin, it has an error when it's copying. "Cannot find "files"."
what did I do wrong?
what did I do wrong?
Did you follow the instructions:
All you do is copy all the files from the windowblinds dir to a "files" folder in the same directory as this plugin. You will also need to copy wbsys.dll and wb.ini from your system32 dir to the plugin folder. Then start wbload.exe after starting PE.
All you do is copy all the files from the windowblinds dir to a "files" folder in the same directory as this plugin. You will also need to copy wbsys.dll and wb.ini from your system32 dir to the plugin folder. Then start wbload.exe after starting PE.
Thanx 'this-is-me' for the VPC plugin. Saved me a lot of work.
QUOTE (this-is-me @ Mar 17 2004, 02:12 PM)
Here is a screenshot of PE with themes enabled and some other things I am proud of:
...Yes, this is really PE and not XP full.
...Yes, this is really PE and not XP full.
@this-is-me,
How did you manage to get your start-menu to look the way you have? I have used the WindowsBlinds plugin to create the XP 'look'... and that has worked perfectly, but I can still only get the 'classic' start menu? (I have the Explorer plugin enabled).
How can I get an XP style start menu?
Have been playing around with the Themes service and various registry settings but still have had no luck. Am I missing something obvious?
Or do I need to do something that cannot be discussed on this forum?
Cheers m8
it works here,
did you read the info.txt and follow it???
did you read the info.txt and follow it???
Hey all,
I've been playing around with the BartPE stuff for a couple of weeks. I've just built from a freshly installed PEBuilder 3031 an ISO with this-is-me's "explorernew" plugin working with just the bare minimum (thank you this-is-me!). The only plugins running are:
I'm having a problem with the AutoRamResizer plugin. If I build an ISO with Nu2Menu as the default explorer, AutoRamResizer works perfectly. However, if explorernew is set at the default, AUTORUN.CMD does not run at all. Then if I navigate to %systemdrive%\i386\system32 and manually execute AUTORUN.CMD, I get an AutoRamResizer error:
I've been playing around with the BartPE stuff for a couple of weeks. I've just built from a freshly installed PEBuilder 3031 an ISO with this-is-me's "explorernew" plugin working with just the bare minimum (thank you this-is-me!). The only plugins running are:
- ramdisk
Nu2Menu
explorernew
AutoRamResizer
I'm having a problem with the AutoRamResizer plugin. If I build an ISO with Nu2Menu as the default explorer, AutoRamResizer works perfectly. However, if explorernew is set at the default, AUTORUN.CMD does not run at all. Then if I navigate to %systemdrive%\i386\system32 and manually execute AUTORUN.CMD, I get an AutoRamResizer error:
- "Error cleaning ramdrive (code 32)"
- 1) AUTORUN.CMD is not getting executed with the explorernew plugin, but does run with Nu2Menu. I have no clue of how to fix this one or even where to start.
2) Running AUTORUN.CMD manually results in the AutoRamResizer error. With the explorernew plugin, 3 directories get copied into the ramdrive:
- Cookies
History
Temporary Internet Files
QUOTE (vette3619 @ Mar 21 2004, 01:17 AM)
it works here,
did you read the info.txt and follow it???
did you read the info.txt and follow it???
@vette3619
Yeah, read the info.txt and followed it... put the mfc42loc.dll file in the right place and everything..... still no luck
@Jimanny
I'm having the same problem here using the Explorer&IE plugin (Created by 2ch.332, Translated by Gordon8452). Besides the folders you mention i've some extra folders on the ramdrive like my profiles and startmenu. Further my eventviewer files are located here.
In my case, Autorun.cmd is being executed which results in the infamous error, so i've disabled the specific Autorun.cmd for now and changed the size of my ram-drive to a static size of 32MB, until i can find a work-around.
Like you've said, the problem seems to be caused by Windows taking control of the ramdrive which prevents AutoRamResizer from resizing the drive resulting in this error. I've been trying to execute Autorun.cmd before Windows grabs control, but could not realize it.
I think it should be possible using GroupPolicy StartupScript but i could not find the correct registry keys to realize it. Maybe that you can have a glance at it.
Right now, i'm looking at the possibility to detect the registry keys which are responsible for locking the ramdrive (the folders mentioned) and if it is possible to unregister them just before the moment the ramdrive is being resized (with the use of regedit.exe). After the ramdrive is being resized, the registry keys will have to be registered again.
I don't now if it is possible, i don't now when i will have the time for it, because i'm working at my interface settings right now. Maybe i will change priorities, because the Ramdrive is, from my point of view, one of the most important plug-ins and i want to have it dynamic.
Pce
I'm having the same problem here using the Explorer&IE plugin (Created by 2ch.332, Translated by Gordon8452). Besides the folders you mention i've some extra folders on the ramdrive like my profiles and startmenu. Further my eventviewer files are located here.
In my case, Autorun.cmd is being executed which results in the infamous error, so i've disabled the specific Autorun.cmd for now and changed the size of my ram-drive to a static size of 32MB, until i can find a work-around.
Like you've said, the problem seems to be caused by Windows taking control of the ramdrive which prevents AutoRamResizer from resizing the drive resulting in this error. I've been trying to execute Autorun.cmd before Windows grabs control, but could not realize it.
I think it should be possible using GroupPolicy StartupScript but i could not find the correct registry keys to realize it. Maybe that you can have a glance at it.
Right now, i'm looking at the possibility to detect the registry keys which are responsible for locking the ramdrive (the folders mentioned) and if it is possible to unregister them just before the moment the ramdrive is being resized (with the use of regedit.exe). After the ramdrive is being resized, the registry keys will have to be registered again.
I don't now if it is possible, i don't now when i will have the time for it, because i'm working at my interface settings right now. Maybe i will change priorities, because the Ramdrive is, from my point of view, one of the most important plug-ins and i want to have it dynamic.
Pce
QUOTE (nlphillips @ Mar 21 2004, 10:38 AM)
Yeah, read the info.txt and followed it... put the mfc42loc.dll file in the right place and everything..... still no luck
Sorted my problem now.... works like a treat. Still don't know what I did to make it work... all I know is that now it does work!
Cheers everyone....
People i haven't any mfc42loc.dll in any directory on my HDD!!!
What a hell is this???
What a hell is this???
@StirolXXX, I had the same problem. I believe, correct me if I am wrong, that if you are working on an english system mfc42.dll should work. You will need to change the INF file so that any refernces to mfc42loc.dll say mfc42.dll. I did this and it worked great.
@murbano, I would like to have all point i which are written what have you done ( copied, regedited, etc. )
@all, sorry folks, I was out for a couple of days.
@nlphillips, (1) So far as themes, If you download the plugins pack I have, it has a link to the XP theme in the info.txt (2) I am getting mixed results as to whether or not that file is needed. If you want, just comment that line out in the plugin.
@jimanny, @pce, The autoramresizer does not work with explorer and plug&play both enabled at the same time. If you disable plug&play, it will start working.
@murbano, the dll you refernence is not the same file, so by renaming the mfc42.dll to mfc42loc.dll you are in effect commenting that file out.
@nlphillips, (1) So far as themes, If you download the plugins pack I have, it has a link to the XP theme in the info.txt (2) I am getting mixed results as to whether or not that file is needed. If you want, just comment that line out in the plugin.
@jimanny, @pce, The autoramresizer does not work with explorer and plug&play both enabled at the same time. If you disable plug&play, it will start working.
@murbano, the dll you refernence is not the same file, so by renaming the mfc42.dll to mfc42loc.dll you are in effect commenting that file out.
QUOTE (nlphillips @ Mar 21 2004, 11:04 AM)
QUOTE (nlphillips @ Mar 21 2004, 10:38 AM)
Yeah, read the info.txt and followed it... put the mfc42loc.dll file in the right place and everything..... still no luck
Sorted my problem now.... works like a treat. Still don't know what I did to make it work... all I know is that now it does work!
Cheers everyone....
Glad to hear it works for you
@this-is-me
As far as i know, I'm not using plug and play at this time.
At least not Frodo's plug-in!! maybe that bartpe is in the way??
Greetz.
Pce
As far as i know, I'm not using plug and play at this time.
At least not Frodo's plug-in!! maybe that bartpe is in the way??
Greetz.
Pce
No... the BartPE plugin is not the problem. You haven't by chance hex edited any files, have you?
No, i do not have the knowledge to hex edit the files (e.a. changing the location of the sytem event files), so i'm still guessing the problem could be resolved the way i mentioned earlier.
unfortunately , i do not have the time to deal with it now, so i'm hoping someone else is making some progress in this matter.
Greetz,
Pce
unfortunately
, i do not have the time to deal with it now, so i'm hoping someone else is making some progress in this matter.Greetz,
Pce
Are you using autorun.cmd as your shell?
If not, try this:
have autorun.cmd as the shell.
start explorer with "start /wait" at the end of your autorun commands.
See if that works.
If not, try this:
have autorun.cmd as the shell.
start explorer with "start /wait" at the end of your autorun commands.
See if that works.
@this-is-me
I'm not currently using autorun as a plugin for Explorer&IE 'cause it giving some problems with the display of the desktop (it's giving errors about the location of the desktop which can not be found. At the same time, you can see all the icons on the desktop are not present reappearing straight afterwards).
Instead of using the autorun plugin, Explorer&IE starts 'startsrv.cmd' which is being used for initiating all the autorun commands.
This being the case, following your advice, i've used startsrv.cmd as the shell with "start /wait explorer.exe" at the end of the startsrv.cmd file.
During the booting process, after the Windows XP logo dissapears, you will see that the explorer system tray appears before the startsrv.cmd is being started.
At the time that the autoramresizer is being started, the same error appears (error cleaning ramdrive: code 32) . After verifying, the size of the ram-drive hasn't changed.
It seems like the problem can't be resolved using your suggestion, instead i still believe the problem could be resolved by detaching the registry from the desktop and several other folders (and the eventlog files), resizing the memory and detaching the files and directories afterwards.
At this time, i'm not convinced i will find a resolution for the problem at short notice, due to lack of time and knowledge of the registry (i'm also having a hard time changing some simple interface settings using the registry), so i'm hoping there will be someone who will find a resolution for it.
All help and suggestions will be appreciated, i'm even willing to try and test out all the given suggestions, if i have the time for it.
Greetz,
Pce
I'm not currently using autorun as a plugin for Explorer&IE 'cause it giving some problems with the display of the desktop (it's giving errors about the location of the desktop which can not be found. At the same time, you can see all the icons on the desktop are not present reappearing straight afterwards).
Instead of using the autorun plugin, Explorer&IE starts 'startsrv.cmd' which is being used for initiating all the autorun commands.
This being the case, following your advice, i've used startsrv.cmd as the shell with "start /wait explorer.exe" at the end of the startsrv.cmd file.
During the booting process, after the Windows XP logo dissapears, you will see that the explorer system tray appears before the startsrv.cmd is being started.
At the time that the autoramresizer is being started, the same error appears (error cleaning ramdrive: code 32) . After verifying, the size of the ram-drive hasn't changed.It seems like the problem can't be resolved using your suggestion, instead i still believe the problem could be resolved by detaching the registry from the desktop and several other folders (and the eventlog files), resizing the memory and detaching the files and directories afterwards.
At this time, i'm not convinced i will find a resolution for the problem at short notice, due to lack of time and knowledge of the registry (i'm also having a hard time changing some simple interface settings using the registry), so i'm hoping there will be someone who will find a resolution for it.
All help and suggestions will be appreciated, i'm even willing to try and test out all the given suggestions, if i have the time for it.
Greetz,
Pce
no no no... The startsrv.cmd starts after the explorer has been started, so it will not work. Explorer starts startsrv.cmd and hides itself until startsrv.cmd is finished instead of startsrv.cmd starting explorer. If you do it that way, then explorer is already locking the ramdrive. The key here is to have a command prompt as your shell, and not explorer. You will have a command prompt hanging around till you shut down PE, but it is a necessary evil. Use this as the shell plugin:
CODE
[SetupReg.AddReg]
0x1, "Setup", "CmdLine", "cmd.exe /k your.cmd"
0x1, "Setup", "CmdLine", "cmd.exe /k your.cmd"
Shortly I will have on my website a version of my ShellExecute program that can run as the shell. It can be configured to run hidden so you will not need to have a command prompt visible all the time.
Its now available at http://www.freewebs.com/paraglider
Details about how to set it up as the shell are in the htm file.
Its now available at http://www.freewebs.com/paraglider
Details about how to set it up as the shell are in the htm file.
To be able to run things before explorer starts, all you need to do is utilitze the infamous RunOnceEx. Works like a charm, as once it is in the registry, it'll launch every time before explorer creates any files on the ramdrive.
For those of you confused, the format as is follows:
the first line sets the title of the window. nothing more.
the second line sets the text the user will see, eg. "Resizing RAM Drive"
the third line tells windows what to execute, eg. "AutoRamResizer.exe"
the fourth and fifth lines are the same as the second and third, but execute a different command.
the sixth line shows the user what is happening
the seventh through fourteenth lines all execute under the name "Starting Network" before moving on to the next set.
All in all, the 001, 002, 003, are your big areas which the user see and each 00# subset can contain many commands too, eg - 003 has 8 commands.
NOTE: In PE (for some reason) you CANNOT use paths in the actual command area, so everything you launch MUST be in System32. Also, built in dos commands such as COPY, MOVE, START, etc cannot be used either - so they must be put in a .cmd (or .bat) file.
I hope this is clear, as it is early early (3:30AM) in the morning here,
-jbenhm
Works like a charm, as once it is in the registry, it'll launch every time before explorer creates any files on the ramdrive.CODE
[Software.AddReg]
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx","TITLE","Preparing Windows Preinstallation Environment..."
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\001","","Resizing RAM Drive"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\001","1","AutoRamResizer.exe"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\002","","Detecting PNP Devices"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\002","1","bartpe -pnp"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\003","","Starting Network"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\003","1","regsvr32 /s netcfgx.dll"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\003","2","bartpe -cn PENV -wg PE"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\003","3","bartpe -c p -i ms_tcpip"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\003","4","bartpe -c p -i ms_ipx"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\003","5","bartpe -c c -i ms_msclient"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\003","6","net start tcpip"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\003","7","net start dhcp"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\003","8","net start nla"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\004","","Preparing RAM Drive"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\004","1","MkDirProfiles.exe"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\005","","Copying Start Menu Items"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\005","1","copy.cmd"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\006","","Background Information"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\006","1","autorun_bginfo.cmd"
should get you started. I use this to launch ramdisk resizer, detect any pnp devices, launch the network manually, change windows environment settings, copy startmenu and desktop items, and lastly run bginfo. Like I said, works like a charm every time.0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx","TITLE","Preparing Windows Preinstallation Environment..."
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\001","","Resizing RAM Drive"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\001","1","AutoRamResizer.exe"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\002","","Detecting PNP Devices"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\002","1","bartpe -pnp"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\003","","Starting Network"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\003","1","regsvr32 /s netcfgx.dll"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\003","2","bartpe -cn PENV -wg PE"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\003","3","bartpe -c p -i ms_tcpip"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\003","4","bartpe -c p -i ms_ipx"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\003","5","bartpe -c c -i ms_msclient"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\003","6","net start tcpip"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\003","7","net start dhcp"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\003","8","net start nla"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\004","","Preparing RAM Drive"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\004","1","MkDirProfiles.exe"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\005","","Copying Start Menu Items"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\005","1","copy.cmd"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\006","","Background Information"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\006","1","autorun_bginfo.cmd"
For those of you confused, the format as is follows:
the first line sets the title of the window. nothing more.
the second line sets the text the user will see, eg. "Resizing RAM Drive"
the third line tells windows what to execute, eg. "AutoRamResizer.exe"
the fourth and fifth lines are the same as the second and third, but execute a different command.
the sixth line shows the user what is happening
the seventh through fourteenth lines all execute under the name "Starting Network" before moving on to the next set.
All in all, the 001, 002, 003, are your big areas which the user see and each 00# subset can contain many commands too, eg - 003 has 8 commands.
NOTE: In PE (for some reason) you CANNOT use paths in the actual command area, so everything you launch MUST be in System32. Also, built in dos commands such as COPY, MOVE, START, etc cannot be used either - so they must be put in a .cmd (or .bat) file.
I hope this is clear, as it is early early (3:30AM) in the morning here,
-jbenhm
DAM FINALLY LOL
I KNEW IT
well been a very long time since i havent touch to winpe ... however i'm comming back now that i have a little free time ... the fact we cannot use xp theme in pe really suprised me, in fact i was sure to had read a post done by someone with some credibility with 3 huge .inf post containing xp theme... so i start searching ... i was about to stop when i remember i have made a post about that on another forum
here it is
http://www.911cd.net/forums/index.php?showtopic=1032
i'm pretty sure it works ... can anyone confirm the information ?
I KNEW IT
well been a very long time since i havent touch to winpe ... however i'm comming back now that i have a little free time ... the fact we cannot use xp theme in pe really suprised me, in fact i was sure to had read a post done by someone with some credibility with 3 huge .inf post containing xp theme... so i start searching ... i was about to stop when i remember i have made a post about that on another forum
here it is
http://www.911cd.net/forums/index.php?showtopic=1032
i'm pretty sure it works ... can anyone confirm the information ?
CODE
i'm pretty sure it works ... can anyone confirm the information ?
That code appears to be for changing normal color appearances i.e. classic style.... it has nothing to do with the theme service or msstyles.
QUOTE
i'm pretty sure it works ... can anyone confirm the information ?
QUOTE
That code appears to be for changing normal color appearances i.e. classic style.... it has nothing to do with the theme service or msstyles.
Yes it does work but it is not the xp visual styles just the colour scheme you see if you go to display properties > Appearance > Advanced.
That was an old post of mine and I later converted it to bartpe inf type but seem to have lost the blue and silver and only have the green at the moment. Here's that anyway in case anyone wants it:
CODE
; --- XP LUNA GREEN ---
0x1,"Control Panel\Colors","ActiveBorder","212 208 200"
0x1,"Control Panel\Colors","ActiveTitle","139 161 105"
0x1,"Control Panel\Colors","AppWorkSpace","128 128 128"
0x1,"Control Panel\Colors","Background","64 64 64"
0x1,"Control Panel\Colors","ButtonAlternateFace","181 181 181"
0x1,"Control Panel\Colors","ButtonDkShadow","113 111 100"
0x1,"Control Panel\Colors","ButtonFace","236 233 216"
0x1,"Control Panel\Colors","ButtonHilight","255 255 255"
0x1,"Control Panel\Colors","ButtonLight","241 239 226"
0x1,"Control Panel\Colors","ButtonShadow","172 168 153"
0x1,"Control Panel\Colors","ButtonText","0 0 0"
0x1,"Control Panel\Colors","GradientActiveTitle","198 210 162"
0x1,"Control Panel\Colors","GradientInactiveTitle","212 214 186"
0x1,"Control Panel\Colors","GrayText","172 168 153"
0x1,"Control Panel\Colors","Hilight","147 160 112"
0x1,"Control Panel\Colors","HilightText","255 255 255"
0x1,"Control Panel\Colors","HotTrackingColor","0 0 128"
0x1,"Control Panel\Colors","InactiveBorder","212 208 200"
0x1,"Control Panel\Colors","InactiveTitle","212 214 186"
0x1,"Control Panel\Colors","InactiveTitleText","255 255 255"
0x1,"Control Panel\Colors","InfoText","0 0 0"
0x1,"Control Panel\Colors","InfoWindow","255 255 225"
0x1,"Control Panel\Colors","Menu","255 255 255"
0x1,"Control Panel\Colors","MenuText","0 0 0"
0x1,"Control Panel\Colors","Scrollbar","212 208 200"
0x1,"Control Panel\Colors","TitleText","255 255 255"
0x1,"Control Panel\Colors","Window","255 255 255"
0x1,"Control Panel\Colors","WindowFrame","0 0 0"
0x1,"Control Panel\Colors","WindowText","0 0 0"
0x1,"Control Panel\Colors","MenuHilight","147 160 112"
0x1,"Control Panel\Colors","MenuBar","236 233 216"
0x1,"Control Panel\Colors","ButtonShadowFill","147 159 255"
0x1,"Control Panel\Desktop\WindowMetrics","BorderWidth","0"
0x3,"Control Panel\Desktop\WindowMetrics","CaptionFont", \
f3,ff,ff,ff,00,00,00,00,00,00,00,00,00,00,00,00,bc,02,00,00,\
00,00,00,01,00,00,00,00,54,00,72,00,65,00,62,00,75,00,63,00,68,00,65,00,74,\
00,20,00,4d,00,53,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00
0x1,"Control Panel\Desktop\WindowMetrics","CaptionHeight","-375"
0x1,"Control Panel\Desktop\WindowMetrics","CaptionWidth","-270"
0x3,"Control Panel\Desktop\WindowMetrics","IconFont", \
f5,ff,ff,ff,00,00,00,00,00,00,00,00,00,00,00,00,90,01,00,00,00,\
00,00,01,00,00,00,00,54,00,61,00,68,00,6f,00,6d,00,61,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,28,c5,06,00,00,00,00,00,cb,44,f9,77,e8,36,0b,\
00,cd,8b,f5,77,a8,16,08,00,37,90,f5,77,00,00,00,00,f0,36,0b,00
0x1,"Control Panel\Desktop\WindowMetrics","IconSpacing","-1125"
0x1,"Control Panel\Desktop\WindowMetrics","IconTitleWrap","1"
0x1,"Control Panel\Desktop\WindowMetrics","IconVerticalspacing","-1125"
0x3,"Control Panel\Desktop\WindowMetrics","MenuFont", \
f5,ff,ff,ff,00,00,00,00,00,00,00,00,00,00,00,00,90,01,00,00,00,\
00,00,01,00,00,00,00,54,00,61,00,68,00,6f,00,6d,00,61,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00
0x1,"Control Panel\Desktop\WindowMetrics","MenuHeight","-285"
0x1,"Control Panel\Desktop\WindowMetrics","MenuWidth","-270"
0x3,"Control Panel\Desktop\WindowMetrics","MessageFont", \
f5,ff,ff,ff,00,00,00,00,00,00,00,00,00,00,00,00,90,01,00,00,\
00,00,00,01,00,00,00,00,54,00,61,00,68,00,6f,00,6d,00,61,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00
0x1,"Control Panel\Desktop\WindowMetrics","ScrollHeight","-255"
0x1,"Control Panel\Desktop\WindowMetrics","ScrollWidth","-255"
0x1,"Control Panel\Desktop\WindowMetrics","Shell Icon BPP","16"
0x3,"Control Panel\Desktop\WindowMetrics","SmCaptionFont", \
f5,ff,ff,ff,00,00,00,00,00,00,00,00,00,00,00,00,bc,02,00,\
00,00,00,00,01,00,00,00,00,54,00,61,00,68,00,6f,00,6d,00,61,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00
0x1,"Control Panel\Desktop\WindowMetrics","SmCaptionHeight","-255"
0x1,"Control Panel\Desktop\WindowMetrics","SmCaptionWidth","-255"
0x3,"Control Panel\Desktop\WindowMetrics","StatusFont", \
f5,ff,ff,ff,00,00,00,00,00,00,00,00,00,00,00,00,90,01,00,00,\
00,00,00,01,00,00,00,00,54,00,61,00,68,00,6f,00,6d,00,61,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00
0x1,"Control Panel\Colors","ActiveBorder","212 208 200"
0x1,"Control Panel\Colors","ActiveTitle","139 161 105"
0x1,"Control Panel\Colors","AppWorkSpace","128 128 128"
0x1,"Control Panel\Colors","Background","64 64 64"
0x1,"Control Panel\Colors","ButtonAlternateFace","181 181 181"
0x1,"Control Panel\Colors","ButtonDkShadow","113 111 100"
0x1,"Control Panel\Colors","ButtonFace","236 233 216"
0x1,"Control Panel\Colors","ButtonHilight","255 255 255"
0x1,"Control Panel\Colors","ButtonLight","241 239 226"
0x1,"Control Panel\Colors","ButtonShadow","172 168 153"
0x1,"Control Panel\Colors","ButtonText","0 0 0"
0x1,"Control Panel\Colors","GradientActiveTitle","198 210 162"
0x1,"Control Panel\Colors","GradientInactiveTitle","212 214 186"
0x1,"Control Panel\Colors","GrayText","172 168 153"
0x1,"Control Panel\Colors","Hilight","147 160 112"
0x1,"Control Panel\Colors","HilightText","255 255 255"
0x1,"Control Panel\Colors","HotTrackingColor","0 0 128"
0x1,"Control Panel\Colors","InactiveBorder","212 208 200"
0x1,"Control Panel\Colors","InactiveTitle","212 214 186"
0x1,"Control Panel\Colors","InactiveTitleText","255 255 255"
0x1,"Control Panel\Colors","InfoText","0 0 0"
0x1,"Control Panel\Colors","InfoWindow","255 255 225"
0x1,"Control Panel\Colors","Menu","255 255 255"
0x1,"Control Panel\Colors","MenuText","0 0 0"
0x1,"Control Panel\Colors","Scrollbar","212 208 200"
0x1,"Control Panel\Colors","TitleText","255 255 255"
0x1,"Control Panel\Colors","Window","255 255 255"
0x1,"Control Panel\Colors","WindowFrame","0 0 0"
0x1,"Control Panel\Colors","WindowText","0 0 0"
0x1,"Control Panel\Colors","MenuHilight","147 160 112"
0x1,"Control Panel\Colors","MenuBar","236 233 216"
0x1,"Control Panel\Colors","ButtonShadowFill","147 159 255"
0x1,"Control Panel\Desktop\WindowMetrics","BorderWidth","0"
0x3,"Control Panel\Desktop\WindowMetrics","CaptionFont", \
f3,ff,ff,ff,00,00,00,00,00,00,00,00,00,00,00,00,bc,02,00,00,\
00,00,00,01,00,00,00,00,54,00,72,00,65,00,62,00,75,00,63,00,68,00,65,00,74,\
00,20,00,4d,00,53,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00
0x1,"Control Panel\Desktop\WindowMetrics","CaptionHeight","-375"
0x1,"Control Panel\Desktop\WindowMetrics","CaptionWidth","-270"
0x3,"Control Panel\Desktop\WindowMetrics","IconFont", \
f5,ff,ff,ff,00,00,00,00,00,00,00,00,00,00,00,00,90,01,00,00,00,\
00,00,01,00,00,00,00,54,00,61,00,68,00,6f,00,6d,00,61,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,28,c5,06,00,00,00,00,00,cb,44,f9,77,e8,36,0b,\
00,cd,8b,f5,77,a8,16,08,00,37,90,f5,77,00,00,00,00,f0,36,0b,00
0x1,"Control Panel\Desktop\WindowMetrics","IconSpacing","-1125"
0x1,"Control Panel\Desktop\WindowMetrics","IconTitleWrap","1"
0x1,"Control Panel\Desktop\WindowMetrics","IconVerticalspacing","-1125"
0x3,"Control Panel\Desktop\WindowMetrics","MenuFont", \
f5,ff,ff,ff,00,00,00,00,00,00,00,00,00,00,00,00,90,01,00,00,00,\
00,00,01,00,00,00,00,54,00,61,00,68,00,6f,00,6d,00,61,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00
0x1,"Control Panel\Desktop\WindowMetrics","MenuHeight","-285"
0x1,"Control Panel\Desktop\WindowMetrics","MenuWidth","-270"
0x3,"Control Panel\Desktop\WindowMetrics","MessageFont", \
f5,ff,ff,ff,00,00,00,00,00,00,00,00,00,00,00,00,90,01,00,00,\
00,00,00,01,00,00,00,00,54,00,61,00,68,00,6f,00,6d,00,61,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00
0x1,"Control Panel\Desktop\WindowMetrics","ScrollHeight","-255"
0x1,"Control Panel\Desktop\WindowMetrics","ScrollWidth","-255"
0x1,"Control Panel\Desktop\WindowMetrics","Shell Icon BPP","16"
0x3,"Control Panel\Desktop\WindowMetrics","SmCaptionFont", \
f5,ff,ff,ff,00,00,00,00,00,00,00,00,00,00,00,00,bc,02,00,\
00,00,00,00,01,00,00,00,00,54,00,61,00,68,00,6f,00,6d,00,61,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00
0x1,"Control Panel\Desktop\WindowMetrics","SmCaptionHeight","-255"
0x1,"Control Panel\Desktop\WindowMetrics","SmCaptionWidth","-255"
0x3,"Control Panel\Desktop\WindowMetrics","StatusFont", \
f5,ff,ff,ff,00,00,00,00,00,00,00,00,00,00,00,00,90,01,00,00,\
00,00,00,01,00,00,00,00,54,00,61,00,68,00,6f,00,6d,00,61,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00
So, let's think what we have to do to make it work!
@jbenhm
It took a long time before i could go further with my personal project, due to other obligations, but here i am.
First, i would like to thank you for the suggestion using RunOnceEx for starting AutoRamDiskResizer before explorer loads. The initial test made clear that this was the thing I was looking for.
Even though I was still having the same error:
code 32: error cleaning ramdrive
, I knew this would mean a big breakthrough.
As I pointed out before, I believed the problem could be associated with the profiles directories being placed at the ramdrive (meaning hard-coded through the registry) and the eventlog files which had been placed there.
After seeing the first result trying your suggestion I located the exact position in my own registry of the three infamous files, being:
1) secevent.evt
2) sysevent.evt
3) appevent.evt
I changed the location of the specifice files 'on the fly' to the locations used by WinPE and exported the keys to three separate registry files.
Then, I removed all the unnessecary information from the three registry files only leeving the "file" information (hex-value).
Using regedit from within a .cmd-file I've imported the mentioned .evt-files during boot-up of WinPE after the ram-drive size was being changed, and behold.
The Ram-drive is now being resized and all my profiles-files and the three mentioned files are in the right location. No more errors.
Once again, thanks for the navigition to the solution of my problem
Greetz,
Pce
It took a long time before i could go further with my personal project, due to other obligations, but here i am.
First, i would like to thank you for the suggestion using RunOnceEx for starting AutoRamDiskResizer before explorer loads. The initial test made clear that this was the thing I was looking for.
Even though I was still having the same error:
code 32: error cleaning ramdrive
, I knew this would mean a big breakthrough.
As I pointed out before, I believed the problem could be associated with the profiles directories being placed at the ramdrive (meaning hard-coded through the registry) and the eventlog files which had been placed there.
After seeing the first result trying your suggestion I located the exact position in my own registry of the three infamous files, being:
1) secevent.evt
2) sysevent.evt
3) appevent.evt
I changed the location of the specifice files 'on the fly' to the locations used by WinPE and exported the keys to three separate registry files.
Then, I removed all the unnessecary information from the three registry files only leeving the "file" information (hex-value).
Using regedit from within a .cmd-file I've imported the mentioned .evt-files during boot-up of WinPE after the ram-drive size was being changed, and behold.
The Ram-drive is now being resized and all my profiles-files and the three mentioned files are in the right location. No more errors.
Once again, thanks for the navigition to the solution of my problem
Greetz,
Pce
@Pce
Could you elaborate a little more on this as I'm having the same problem.
Where to place the evt files and how to change the registry entries ?
Thanks...
Could you elaborate a little more on this as I'm having the same problem.
Where to place the evt files and how to change the registry entries ?
Thanks...
@Intrax
I've added the following files to the root of the True Explorer Plugin directory:
1) appevent_evt.reg
2) secevent_evt.reg
3) sysevent_evt.reg
4) imp_reg.cmd
These files will be used to import the correct settings for the eventlog files after the ramdrive has been resized.
Furthermore, you will have to make the following adjustments to "Explorer.inf".
Simply add the SourceDiskFiles section and the Software.addreg section and comment out the lines mentioned at the SetupReg.Addreg section. Change titles to your own preferences.
Greetz,
Pce
18-04-2004
Added some extra lines to [Software.AddReg] to display my current usage.
I've added the following files to the root of the True Explorer Plugin directory:
1) appevent_evt.reg
CODE
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application]
"File"=hex(2):25,00,74,00,65,00,6d,00,70,00,25,00,5c,00,41,00,70,00,70,00,45,\
00,76,00,65,00,6e,00,74,00,2e,00,45,00,76,00,74,00,00,00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application]
"File"=hex(2):25,00,74,00,65,00,6d,00,70,00,25,00,5c,00,41,00,70,00,70,00,45,\
00,76,00,65,00,6e,00,74,00,2e,00,45,00,76,00,74,00,00,00
2) secevent_evt.reg
CODE
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Security]
"File"=hex(2):25,00,74,00,65,00,6d,00,70,00,25,00,5c,00,53,00,65,00,63,00,45,\
00,76,00,65,00,6e,00,74,00,2e,00,45,00,76,00,74,00,00,00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Security]
"File"=hex(2):25,00,74,00,65,00,6d,00,70,00,25,00,5c,00,53,00,65,00,63,00,45,\
00,76,00,65,00,6e,00,74,00,2e,00,45,00,76,00,74,00,00,00
3) sysevent_evt.reg
CODE
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\System]
"File"=hex(2):25,00,74,00,65,00,6d,00,70,00,25,00,5c,00,53,00,79,00,73,00,45,\
00,76,00,65,00,6e,00,74,00,2e,00,45,00,76,00,74,00,00,00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\System]
"File"=hex(2):25,00,74,00,65,00,6d,00,70,00,25,00,5c,00,53,00,79,00,73,00,45,\
00,76,00,65,00,6e,00,74,00,2e,00,45,00,76,00,74,00,00,00
4) imp_reg.cmd
CODE
@echo off
regedit /s secevent_evt.reg
regedit /s sysevent_evt.reg
regedit /s appevent_evt.reg
regedit /s secevent_evt.reg
regedit /s sysevent_evt.reg
regedit /s appevent_evt.reg
These files will be used to import the correct settings for the eventlog files after the ramdrive has been resized.
Furthermore, you will have to make the following adjustments to "Explorer.inf".
CODE
[SourceDisksFiles]
imp_reg.cmd=2,,1
secevent_evt.reg=2,,1
sysevent_evt.reg=2,,1
appevent_evt.reg=2,,1
[Software.AddReg]
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx","TITLE","Preparing PCE Preinstallation Environment..."
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\001","","Resizing RAM Drive"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\001","1","AutoRamResizer.exe"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\002","","Importing registry settings"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\002","1","imp_reg.cmd"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\003","","Starting Network Support"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\003","1","autorun0bartpe.cmd"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\004","","Copying Profiles Settings"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\004","1","explorer.cmd"
;0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\005","","Registering DirectX"
;0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\005","1","autorun0dx9.cmd"
[SetupReg.AddReg]
;0x2,"ControlSet001\Services\Eventlog\Application","File","%temp%\AppEvent.Evt"
;0x2,"ControlSet001\Services\Eventlog\Security","File","%temp%\SecEvent.Evt"
;0x2,"ControlSet001\Services\Eventlog\System","File","%temp%\SysEvent.Evt"
imp_reg.cmd=2,,1
secevent_evt.reg=2,,1
sysevent_evt.reg=2,,1
appevent_evt.reg=2,,1
[Software.AddReg]
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx","TITLE","Preparing PCE Preinstallation Environment..."
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\001","","Resizing RAM Drive"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\001","1","AutoRamResizer.exe"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\002","","Importing registry settings"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\002","1","imp_reg.cmd"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\003","","Starting Network Support"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\003","1","autorun0bartpe.cmd"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\004","","Copying Profiles Settings"
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\004","1","explorer.cmd"
;0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\005","","Registering DirectX"
;0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\005","1","autorun0dx9.cmd"
[SetupReg.AddReg]
;0x2,"ControlSet001\Services\Eventlog\Application","File","%temp%\AppEvent.Evt"
;0x2,"ControlSet001\Services\Eventlog\Security","File","%temp%\SecEvent.Evt"
;0x2,"ControlSet001\Services\Eventlog\System","File","%temp%\SysEvent.Evt"
Simply add the SourceDiskFiles section and the Software.addreg section and comment out the lines mentioned at the SetupReg.Addreg section. Change titles to your own preferences.
Greetz,
Pce
18-04-2004
Added some extra lines to [Software.AddReg] to display my current usage.
Excellent! That did it. I guess I was messing up cause I was adding the runonce commands to the Zexplorer.
Glad that there are intelligent people like you to help us less talented wanna be's.
Just one cmd runs that I have to kill off, but it's not anything that keeps anything from working correctly. Thanks again.
Glad that there are intelligent people like you to help us less talented wanna be's.
Just one cmd runs that I have to kill off, but it's not anything that keeps anything from working correctly. Thanks again.
Thanx Pce. It's great!
better solution here --> http://www.911cd.net/forums/index.php?show...l=runonce&st=15
for now solved in the 0.40 zie_plug explorer must intregation !
thx for all paraglider and adminz
---all around there !
for now solved in the 0.40 zie_plug explorer must intregation !
thx for all paraglider and adminz
---all around there !
Hi I tried the explorer pluggin,
but I get the following error,
When it starts to load, a message comes up stating that,
Services.exe is unable to locate or load Msacm32.dll
So I added the file into the Explorer.inf file as a required file
Rebooted to test but now my PC gets only about half way through the boot process and then just reboots.
Any help would be appreciated.
but I get the following error,
When it starts to load, a message comes up stating that,
Services.exe is unable to locate or load Msacm32.dll
So I added the file into the Explorer.inf file as a required file
Rebooted to test but now my PC gets only about half way through the boot process and then just reboots.
Any help would be appreciated.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.