okto

I had to resort to a batch file which is executed at first boot Assuming reg.exe is present inside system32 folder REG ADD HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\StuckRects2 /v Settings /t REG_BINARY /d 28000000FFFFFFFF06000000030000007A0000001E000000FEFFFFFFE40300000205000002040000 /f ...06.. is the "Small" icons setting. Thank's to everyone who've spent their time resolving current issue.

From what I gather it is not enough just to keep taskkill.exe I've checked against these threads: http://www.tech-archive.net/Archive/WinXP/...9/msg00336.html http://groups.google.com/group/microsoft.p...%85d794eab22066 If I interpret it correctly taskkill.exe does have dependencies, WMI inclusively. (re)registering 'framedyn.dll' does not resolve an issue on it's own, as there are other dependencies present. ADVAPI32.DLL GDI32.DLL DBGHELP.DLL NTDLL.DLL KERNEL32.DLL MSVCRT.DLL SECUR32.DLL RPCRT4.DLL USER32.DLL MPR.DLL OLE32.DLL OLEAUT32.DLL WS2HELP.DLL WS2_32.DLL FRAMEDYN.DLL NETAPI32.DLL VERSION.DLL IMM32.DLL MSCTF.DLL COMRES.DLL CLBCATQ.DLL WINSTA.DLL XPSP2RES.DLL WBEMCOMN.DLL WBEMPROX.DLL Last two in particular are WMI components. I did a test build where I droped all the dependancies into a keep box, and still recieved an "ERROR: Class not registered". The issue is resolved by enabling WMI services.

Certainly. Last_Session.ini Similar issue has been raised and unresolved http://www.msfn.org/board/index.php?showto...mp;#entry803608 Alternative solution. http://www.911cd.net/forums//index.php?showtopic=14421 Although this is a solution I still fail to find out what affects taskkill.exe

Hi Windows XP Professional Service Pack 3 v. 5.1.2600.5512 nLite v. 1.4.9.1 I've kept taskkill.exe as one of the batch files I use during runonce rely on it When batch file is executed I recieve: "ERROR: Class not registered" DOS message and deployment is interrupted. The file is present and is located at Windows\system32 an OS which I haven't passed through nLite has taskkill.exe and it doesn't output any errors. Any thoughts as to why taskkill.exe is affected?

johnhc, strel. thank you for your prompt response. I've started a new build using: Windows XP Professional Service Pack 3 v. 5.1.2600.5512 nLite v. 1.4.9.1 VMware Workstation v. 6.5.1 build-126130 Preset Last_Session.ini Result Start Panel Classic Start Panel under Unattended>Desktop themes [unchecked] Start Menu Classic Start Menu under Unattended>Desktop themes [checked] @strel note that the pink highlight issue is gone using Visual Effects-Menu style-Normal I'm trying to achieve this effect. Which I haven't so far. And I still don't know what's ignoring the Start Menu-Use small icons in Start Panel

Hi I'm trying to achieve a Small Icons Classic Start Menu look using nLite v. 1.4.9.1 and get unsatisfactory results. Here is the line that deal with a Start menu from the "Last session.ini" file Start Menu-Use small icons in Start Panel Visual Effects-Menu style-Flat I also [check] Classic Start Menu under Unattended>Desktop themes What I get as an end result is this If "Use small icons in Start Panel" is selected what makes the Start menu remain using large icons? In addition to that a black side banner appear. As far as my knowledge goes there should be "Windows XP Professional" image on the side. Other reports have been made on that matter. http://www.msfn.org/board/black-classic-st...bar-t54835.html But that's to do with XPize, which isn't the application of my inquiry. The Side banner issue can be resolved manually by selecting "Small Icons in start menu" from Taskbar settings, but then it defeats the purpose of using the same tweak inside nLite. I've also found a thread that explains how to runOnce registry entries which would force windows Classic Style Start Menu http://www.msfn.org/board/change-start-men...ry-t123053.html No mentioning of small icons inside the menu however. Am I missing something? Could, The fact that the "Start Menu-Use small icons in Start Panel" is ignored, be a bug with nLite? Any response is appreciated

In order to avoid this error will placing hhctrl.ocx as an exception into a "keep box" prevent this error from occuring? Or is it also an option to place hhctrl.ocx into it's native folder once OS is installed?