96 replies to this topic

[wimb]

We are now now in the unfortunate position where diskpart is only working with Gold and SP1 sources, and USB Mass Storage is only working with SP2 and SP3.

For me Diskpart is working together with USB-support for XP SP3 Source and by using the registry of Installed XP
as you can see here http://reboot.pro/16765/#entry153226 (Remark the Hello World in the cmd Window)

[Wonko the Sane]

Would also love to get this working with Gold and SP1 sources - suggestions are welcome.

We are now now in the unfortunate position where diskpart is only working with Gold and SP1 sources, and USB Mass Storage is only working with SP2 and SP3.

You could cheat and try using :
http://support.micro...kb/822603/en-us
http://download.micr...603-x86-ENU.exe


Wonko

[misty]

@wimb

For me Diskpart is working together with USB-support with XP SP3 Source and by using the registry of Installed XP
as you can see here http://reboot.pro/16765/#entry153226

That's great news. Are you volunteering to find the necessary dependencies to get diskpart working in MiniXP and/or your original 40MB XPCMD?

BTW, the XPCMD project (40 MB and 100 MB flavors) looks good. Unfortunately I can't test them at the moment until I find a spare USB drive. I look forward to doing so.

Thanks for all the help and suggestions.

Regards,

Misty

[misty]

@Wonko

You could cheat and try using :
http://support.micro...kb/822603/en-us
http://download.micr...603-x86-ENU.exe

If all else fails then I'm more than happy to cheat - that's why I ended up using Dietmar's second file set after all!

Will check your links out later, as I'm logging off for the evening.

Thanks.

Regards,

Misty

[cdob]

diskpart is only working with Gold and SP1 sources

This rings a old bell: Bart added DComLaunch Service to enable diskpart at SP2 and up.
LiveXP adds DComLaunch at Register Factory API http://livexp.boot-l...gFactory.Script

[misty]

diskpart is only working with Gold and SP1 sources

This rings a old bell: Bart added DComLaunch Service to enable diskpart at SP2 and up.
LiveXP adds DComLaunch at Register Factory API http://livexp.boot-l...gFactory.Script

@cdob
Thanks for the hints. I feel like I'm making some progress, however I can't get the DcomLaunch service working. I tried adding the following registry keys via a winbuilder script -

RegWrite,HKLM,0x7,"_XPCLI_SYSTEM\ControlSet001\Services\RpcSs","DependOnService","DcomLaunch",""

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",0x0

RegWrite,HKLM,0x1,"_XPCLI_SYSTEM\ControlSet001\Enum\Root\LEGACY_DCOMLAUNCH\0000","DeviceDesc","DCOM Services"

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","DCOM Services"

RegWrite,HKLM,0x1,"_XPCLI_SYSTEM\ControlSet001\Services\DcomLaunch","DisplayName","DCOM Services"

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","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","rpcss.dll"

Sadly diskpart is still not working. I used the sc command to check whether dcomlaunch and rpcss services were working, and received the following errors -




RpcSs starts fine if the DependOnService DcomLaunch entry is removed.

Does anyone know of any DcomLaunch dependencies that might be missing in MiniXP?

Regards,

Misty

[TheHive]

ImDisk is only a requirement of the Finish script, which is why I added the option in that script. Whilst your suggestion would definitely make the option to install ImDisk more visible, it adds yet another script for the user to wade through. I'll have more of a think about the suggestions, but I want to keep the scripts (at least the one's visible to the end user) to a minimum if possible.

Lets say im seeing it from a more of beginners point of using the project.
1. Its 5 to 10 years from now and I download MiniXP.zip from an archive of some kind. I dont have a heads up that I need Imdisk or minlogon.exe [Minlogon might no be necessay as you mentioned earlier in a future build]
2. launch Winbuilder. ok. You dont get any instructions on the front page. Say and easy 1,2,3 steps.

Not sure how to do this. Will add it to the project if anyone can tell me how. I would prefer to be able to automatically launch bblean if possible, but again I don't actually know how.

Suggest Posting the bblean and asking in the Developers section of the forum how to do do the auto launch and or the adding of the text to the cmd prompt. That way there could be some help in the scripts development.

[misty]

@TheHive

Lets say im seeing it from a more of beginners point of using the project.
1. Its 5 to 10 years from now and I download MiniXP.zip from an archive of some kind. I dont have a heads up that I need Imdisk or minlogon.exe [Minlogon might no be necessay as you mentioned earlier in a future build]
2. launch Winbuilder. ok. You dont get any instructions on the front page. Say and easy 1,2,3 steps......

The reason I've spent almost as long writing the documentation as coding the project is to address these issues. The next release will link to the documentation in the download, the MiniXP site, and this forum thread - from within WinBuilder (as suggested by yourself).

The above is already IMO covered in the documentation. It would fall under the remit of RTFM - something I know most of us (myself at times included) can't be bothered to do. The instructions in the documentation do however provide a detailed walkthrough.

Suggest Posting the bblean and asking in the Developers section of the forum how to do do the auto launch and or the adding of the text to the cmd prompt. That way there could be some help in the scripts development.

I'm a bit preoccupied at the moment with improving the docs, Diskpart and USB Mass Storage Issues - but will follow this advice soon. Thanks.

Regard,

Misty

[misty]

@Wonko

You could cheat and try using :
http://support.micro...kb/822603/en-us
http://download.micr...603-x86-ENU.exe

Looks like cheats never prosper. This was a great suggestion but proved not to work. The driver version of the included files in KB822603 is 5.1.2600.1243.

Carrying on the cheating theme however, I managed to get USB Mass Storage support working in XP Gold and SP1 by playing around with SP2 source files.

I've now isolated it to just one file - the SP2 version of usbehci.sys (version 5.1.2600.2180). The other files listed below are still required, but can be extracted from the source being used -

• usbohci.sys
• usbuhci.sys
• usbport.sys
• usbhub.sys
• usbd.sys
• usbstor.sys

cdob's registry settings are also required (see here and here)

usbehci.sys from SP3 sources may also work - I've not tested it yet.

This is not an ideal situation, as I don't like mixing source files.

Regards,

Misty

[Wonko the Sane]

This is not an ideal situation, as I don't like mixing source files.

It's strange.
I am afraid you (or cdob or wimb or myself ) are mixing together something.
We did have XP actually booting from XP with SP1 files since 2006:
http://www.911cd.net...topic=14181&hl=
While "Gold" may obviously have issues, SP1should work (and though never tested the mentioned SP, those files should work as well ).


Wonko

[misty]

@everyone
The good news is that there is a legal way to obtain the Service Pack 2 version of usbehci.sys - currently required for USB Mass Storage Support when XP Gold and SP1 source files are used in the MiniXP project.

The bad news is that this will require the downloading of Windows XP service Pack 2 - a 266 MB download for a 26 KB file.

@Wonko

I am afraid you (or cdob or wimb or myself ) are mixing together something....While "Gold" may obviously have issues, SP1 should work ....

I suspect that SP1 will work with different registry entries. Not sure which ones though - cdob is the expert in this area.

If we can find the correct registry entries then possibly the KB822603 files you linked to in a previous post will work - a mere 341 KB download.

Fingers crossed someone will come up with the answers. Yet another area in which I am at a loss for answers.

Regards,

Misty

[Vortex]

Hi misty,

Please feel free to add my tool ExitPE to your project :

http://reboot.pro/15339/

[cdob]

The good news is that there is a legal way to obtain the Service Pack 2 version of usbehci.sys - currently required for USB Mass Storage Support when XP Gold and SP1 source files are used in the MiniXP project.

The bad news is that this will require the downloading of Windows XP service Pack 2 - a 266 MB download for a 26 KB file.

There are XP floppy installation files. http://support.microsoft.com/kb/310994
SP2 floppy files are available still and cdboot4.img contains usbehci.sy_

As for SP1 source files:
Adding KB331958 atapi.sys is a nice precaution.
http://support.micro....com/kb/331958/

No solution about Domlaunch, scratching memory from 2004.
There can be more dependencies.

@Wonko
Mixing different questions:
XP1 source files with USB and diskpart
XP2 source files with USB and diskpart

[Wonko the Sane]

Yep, what I am missing is if the issue is:

• XP "Gold" USB 2.0 Support (but NOT booting from USB)
• XP "SP1" USB 2.0 Support (but NOT booting from USB)
• XP "SP2" USB 2.0 Support (but NOT booting from USB)
• XP "SP3" USB 2.0 Support (but NOT booting from USB)
• XP "Gold" USB 2.0 Support (AND booting from USB)
• XP "SP1" USB 2.0 Support (AND booting from USB)
• XP "SP2" USB 2.0 Support (AND booting from USB)
• XP "SP3" USB 2.0 Support (AND booting from USB)

IMHO one should solve first 4 before attempting solcing the last 4.
For diskpart I presume that you have the "right" approach, let's "predate" from BartPE's experience .
http://www.nu2.nu/pebuilder/faq/#14

When I boot BartPE from harddisk, diskpart does not work. I get the following message: The disk management services could not complete the operation.
This is normal, when booting bartPE/winPE from harddisk diskpart will not work, when booting from CD-Rom/DVD it should work fine.
When I boot BartPE build from WinXP/Sp2 from CD-Rom, diskpart does not work. When I try to execute diskpart, I get the following message: The disk management services could not complete the operation.
You must enable the dcomlaunch plugin "RpcSS needs to launch DComLaunch Service first - SP2 only".

@Misty
Can you post a .reg file with the export of keys:
ControlSet001\Services\RpcSs
ControlSet001\Services\DcomLaunch
ControlSet001\Enum\Root\LEGACY_DCOMLAUNCH\0000
(I mean the resulting keys) maybe there is something in there that is not "kosher" .

Or some other entry (that is in a "Full" install, and that is not needed in a PE, is needed in the MiniXP), like :
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\SafeBoot\Minimal\DcomLaunch
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\SafeBoot\Network\DcomLaunch
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{8ECC055D-047F-11D1-A537-0000F8753ED1}


Wonko

[Wonko the Sane]

A couple of tools that may come (VERY ) handy:
http://fstaal01.home...gsearch-us.html
http://fstaal01.home...s/regsearch.zip
http://fstaal01.home...s/reghexenc.exe

The very good thing about Regsearch is that it provides output:

• in a text file
• with a format comaptible with .reg files
• adds to hex(2) and hex(7) the plain text contents

Example of output:

[HKEY_LOCAL_MACHINESYSTEMControlSet001ServicesEventlogSystemdmio]
; Contents of value:
; %SystemRoot%System32IoLogMsg.dll;%SystemRoot%System32Driversdmio.sys
"EventMessageFile"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,
00,6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,
5c,00,49,00,6f,00,4c,00,6f,00,67,00,4d,00,73,00,67,00,2e,00,64,00,6c,00,6c,
00,3b,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,
25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,72,
00,69,00,76,00,65,00,72,00,73,00,5c,00,64,00,6d,00,69,00,6f,00,2e,00,73,00,
79,00,73,00,00,00

The hexenc comes handy as you can modify the "plain text" and get the hex(2) or hex(7), already formatted as usual with the "," line breaks.



Wonko

[misty]

@Vortex

Please feel free to add my tool ExitPE to your project :

http://reboot.pro/15339/

Thanks, I'll check this out when I get a bit of free time - hopefully next week.

@cdob

There are XP floppy installation files. http://support.microsoft.com/kb/310994
SP2 floppy files are available still and cdboot4.img contains usbehci.sy_

Good find. Thank you.

No solution about Domlaunch, scratching memory from 2004.
There can be more dependencies.

I think I have resolved this problem - you were right about Diskpart requiring DcomLaunch. More on this later, as I have a few more tests to run.

@Wonko the Sane

A couple of tools that may come (VERY ) handy:
http://fstaal01.home...gsearch-us.html
http://fstaal01.home...s/regsearch.zip
http://fstaal01.home...s/reghexenc.exe

Yet another great find - I'm very much looking forward to checking these tools out. Thanks.

@Everyone
It looks like my reports of USB mass storage working (see here) was premature. I managed to get file backed disk support working with USB Mass storage support, however when a USB mouse was connected the system failed to boot. Another case of one step forward and two steps back.

Regards,

Misty

[misty]

@everyone
Firstly, 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 -

• iphlpapi.dll
• xpsp2res.dll

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

[misty]

A new version of the MiniXP project has been uploaded to the MiniXP website (click on the link in my signature for the homepage).

The documentation has been updated (added Testing on a Real (Non-Virtual) System and Acknowledgements and Links) and a number of minor edits have been made to various scripts - too many for me to have actually kept an accurate record of.

I have added diskpart support if Service Pack 2 or 3 source files are used - the fix has the added bonus of xcopy now working too!

I have also included an experimental USB Mass Storage script - use this at your own risk. The script is in the Tests folder. As I stated in a previous post, this appeared to be working until a USB mouse was added to the system. With a USB mouse attached, MiniXP would not boot - the splash screen started to appear before stalling. Any suggestions regarding this issue are welcome. I tried adding the additional files that wimb recommended here + his registry settings, however this has not solved the problem.

As usual, please test and feedback.

Regards,

Misty

[Wonko the Sane]

@Misty, JFYI:
http://reboot.pro/98...600#entry153588


Wonko

[cdob]

With a USB mouse attached, MiniXP would not boot

Local notes refers files:
usbccgp.sys HidUsb.sys mouhid.sys kbdhid.sys hidclass.sys hidparse.sys

And offline registry loaded to loaded_SYSTEM

Spoiler

[HKEY_LOCAL_MACHINEloaded_SYSTEMControlSet001ControlCriticalDeviceDatabaseUSB#COMPOSITE]
"ClassGUID"="{36FC9E60-C465-11CF-8056-444553540000}"
"Service"="usbccgp"

[HKEY_LOCAL_MACHINEloaded_SYSTEMControlSet001Servicesusbccgp]
"DisplayName"="Microsoft USB Generic Parent Driver"
"Group"="Base"
"ImagePath"="system32driversusbccgp.sys"
"ErrorControl"=dword:00000001
"Start"=dword:00000003
"Type"=dword:00000001

;USB Keyboard and Mouse

[HKEY_LOCAL_MACHINEloaded_SYSTEMControlSet001ControlCriticalDeviceDatabaseUSB#Class_03]
"ClassGUID"="{745a17a0-74d3-11d0-b6fe-00a0c90f57da}"
"Service"="HidUsb"
[HKEY_LOCAL_MACHINEloaded_SYSTEMControlSet001ControlCriticalDeviceDatabaseGENERIC_HID_DEVICE]
"ClassGUID"="{745a17a0-74d3-11d0-b6fe-00a0c90f57da}"
"Service"="HidUsb"

[HKEY_LOCAL_MACHINEloaded_SYSTEMControlSet001ServicesHidUsb]
"DisplayName"="Microsoft HID Class Driver"
"Group"="extended base"
"ImagePath"="system32driversHidUsb.sys"
"ErrorControl"=dword:00000000
"Start"=dword:00000003
"Type"=dword:00000001


[HKEY_LOCAL_MACHINEloaded_SYSTEMControlSet001ControlCriticalDeviceDatabaseHID_DEVICE_SYSTEM_MOUSE]
"ClassGUID"="{4D36E96F-E325-11CE-BFC1-08002BE10318}"
"Service"="mouhid"

[HKEY_LOCAL_MACHINEloaded_SYSTEMControlSet001Servicesmouhid]
"DisplayName"="Mouse HID Driver"
"Group"="Pointer Port"
"ImagePath"="system32driversmouhid.sys"
"ErrorControl"=dword:00000000
"Start"=dword:00000003
"Type"=dword:00000001

[HKEY_LOCAL_MACHINEloaded_SYSTEMControlSet001ServicesmouhidParameters]
"UseOnlyMice"=dword:00000000
"TreatAbsoluteAsRelative"=dword:00000000
"TreatAbsolutePointerAsAbsolute"=dword:00000000


[HKEY_LOCAL_MACHINEloaded_SYSTEMControlSet001ControlCriticalDeviceDatabaseHID_DEVICE_SYSTEM_KEYBOARD]
"ClassGUID"="{4D36E96B-E325-11CE-BFC1-08002BE10318}"
"Service"="kbdhid"

[HKEY_LOCAL_MACHINEloaded_SYSTEMControlSet001Serviceskbdhid]
"DisplayName"="Keyboard HID Driver"
"Group"="Keyboard Port"
"ImagePath"="system32driverskbdhid.sys"
"ErrorControl"=dword:00000000
"Start"=dword:00000003
"Type"=dword:00000001

[HKEY_LOCAL_MACHINEloaded_SYSTEMControlSet001ServiceskbdhidParameters]
"WorkNicely"=dword:00000000

[TheHive]

When you select and deselect an option on either one. They both trigger the action. Can they be made into a push button to launch the action.


I was thinking it was going to be more like.



Online doc need mini update on release date.



Wonko the desktoplitethingy_v1.0.1
For it to work in MiniXP the file " psapi.dll " is needed

To download desktoplitethingy_v1.0.1 select the little NYM|TEC button


When you select to use it as the shell it asks to logoff, When you say yes it shutsdown the PC. So, I couldnt run and test the Mini Explorer Shell. Seems like a lite alternative.

[VV2006]

For Far manager to work in MiniXP the file " psapi.dll " is needed too.
And need to add National Fonts Support...

[Wonko the Sane]

@TheHive
The idea was NOT "Hey peeps, try this in MiniXP".
It was a JFYI to Misty, that thingy or "Michelle" should be tested on a more complete system, and then decide whether it is worth the effort to provide it in MiniXP, though I suspect that a more "complete" build such as wimb's one might be needed.


Wonko

[misty]

@Wonko the Sane

@Misty, JFYI:
http://reboot.pro/98...600#entry153588

Thanks for the heads up. These apps do start in MiniXP - psapi.dll is required as highlighted by TheHive. Start them from the command-line and click No when prompted to use as desktop manager (or when prompted to logoff - I can't remember the exact prompts) - this will avoid a reboot. Neither is working properly. The settings cannot be edited and they seem to rely on shell folders, which are not supported. To be honest, I don't think it's worth the effort integrating them into MiniXP at this time. I really need to play around with them in a full WIndows XP environment to test them properly, however this is low on my priority list as bblean meets all of my needs at the moment.

@TheHive

When you select and deselect an option on either one. They both trigger the action. Can they be made into a push button to launch the action.....Online doc need mini update on release date.

Thanks as always for the suggestions. Will implement buttons on the next release. Will change the release date information later tonight. I'm not ready to add MiniXP to the download centre yet, and will look into your other suggestions when I am.

@cdob

Local notes refers files:
usbccgp.sys HidUsb.sys mouhid.sys kbdhid.sys hidclass.sys hidparse.sys

And offline registry .......

Thanks for the suggestions. Sadly, when the registry settings and files you mentioned were added to the build, MiniXP still failed to boot. I'll keep investigating - please keep the suggestions coming.

Regards,

Misty

[Marietto]

I would like to try it,but I'm on a mac. I can only use a virtual machine,like vmware player or virtualbox. And I need to create an img/iso file from the mini xp source files. How to do it ?