@everyoneFirstly, apologies for the double post - I have also posted the following information
here. This information clearly belongs in the MiniXP thread as well.
Thanks for the suggestions and a special thanks to
cdob who put me on to DcomLaunch being the problem. The following registry entries are working in MiniXP with SP2 and SP3 source files -
RegWrite,HKLM,0x7,"_XPCLI_SOFTWARE\Microsoft\Windows NT\CurrentVersion\SvcHost","DComLaunch","DComLaunch"
RegWrite,HKLM,0x4,"_XPCLI_SOFTWARE\Microsoft\Windows NT\CurrentVersion\SvcHost\DComLaunch","CoInitializeSecurityParam",0x1
RegWrite,HKLM,0x4,"_XPCLI_SOFTWARE\Microsoft\Windows NT\CurrentVersion\SvcHost\DComLaunch","DefaultRpcStackSize",0x8
RegWrite,HKLM,0x4,"_XPCLI_SYSTEM\ControlSet001\Enum\Root\LEGACY_DCOMLAUNCH","NextInstance",0x1
RegWrite,HKLM,0x1,"_XPCLI_SYSTEM\ControlSet001\Enum\Root\LEGACY_DCOMLAUNCH\0000","Class","LegacyDriver"
RegWrite,HKLM,0x1,"_XPCLI_SYSTEM\ControlSet001\Enum\Root\LEGACY_DCOMLAUNCH\0000","ClassGUID","{8ECC055D-047F-11D1-A537-0000F8753ED1}"
RegWrite,HKLM,0x4,"_XPCLI_SYSTEM\ControlSet001\Enum\Root\LEGACY_DCOMLAUNCH\0000","ConfigFlags",0x20
RegWrite,HKLM,0x1,"_XPCLI_SYSTEM\ControlSet001\Enum\Root\LEGACY_DCOMLAUNCH\0000","DeviceDesc","DCOM Server Process Launcher"
RegWrite,HKLM,0x4,"_XPCLI_SYSTEM\ControlSet001\Enum\Root\LEGACY_DCOMLAUNCH\0000","Legacy",0x1
RegWrite,HKLM,0x1,"_XPCLI_SYSTEM\ControlSet001\Enum\Root\LEGACY_DCOMLAUNCH\0000","Service","DcomLaunch"
RegWrite,HKLM,0x1,"_XPCLI_SYSTEM\ControlSet001\Enum\Root\LEGACY_DCOMLAUNCH\0000\Control","ActiveService","DcomLaunch"
RegWrite,HKLM,0x1,"_XPCLI_SYSTEM\ControlSet001\Services\DcomLaunch","Description","Provides launch functionality for DCOM services."
RegWrite,HKLM,0x1,"_XPCLI_SYSTEM\ControlSet001\Services\DcomLaunch","DisplayName","DCOM Server Process Launcher"
RegWrite,HKLM,0x4,"_XPCLI_SYSTEM\ControlSet001\Services\DcomLaunch","ErrorControl",0x1
RegWrite,HKLM,0x1,"_XPCLI_SYSTEM\ControlSet001\Services\DcomLaunch","Group","Event Log"
RegWrite,HKLM,0x2,"_XPCLI_SYSTEM\ControlSet001\Services\DcomLaunch","ImagePath","%SystemRoot%\system32\svchost -k DcomLaunch"
RegWrite,HKLM,0x1,"_XPCLI_SYSTEM\ControlSet001\Services\DcomLaunch","ObjectName","LocalSystem"
RegWrite,HKLM,0x4,"_XPCLI_SYSTEM\ControlSet001\Services\DcomLaunch","Start",0x2
RegWrite,HKLM,0x4,"_XPCLI_SYSTEM\ControlSet001\Services\DcomLaunch","Type",0x20
RegWrite,HKLM,0x3,"_XPCLI_SYSTEM\ControlSet001\Services\DcomLaunch","FailureActions",00,00,00,00,00,00,00,00,00,00,00,00,01,00,00,00,00,00,00,00,02,00,00,00,60,ea,00,00
RegWrite,HKLM,0x1,"_XPCLI_SYSTEM\ControlSet001\Services\DcomLaunch\Enum","0","Root\LEGACY_DCOMLAUNCH\0000"
RegWrite,HKLM,0x4,"_XPCLI_SYSTEM\ControlSet001\Services\DcomLaunch\Enum","Count",0x1
RegWrite,HKLM,0x4,"_XPCLI_SYSTEM\ControlSet001\Services\DcomLaunch\Enum","NextInstance",0x1
RegWrite,HKLM,0x2,"_XPCLI_SYSTEM\ControlSet001\Services\DcomLaunch\Parameters","ServiceDll","system32\rpcss.dll"
There are also two file dependencies -
xpsp2res.dll - does not appear to be essential.
With xpsp2res.dll -
without -
Other than not displaying the diskpart version information, xpsp2res.dll does not appear to effect diskpart.
Unfortunately I cannot fully test Diskpart at the moment as I don't have a system I can risk using it on. I'll test in a VM when I get some spare time.
Diskpart starts and appears to list disks and partitions without error. Please test and feedback.
Regards,
Misty