254 replies to this topic

[Wonko the Sane]

On to other matters. I was wondering if you could check something - time and resources permitting. I am currently running this project from a physical hard disk and tried loading some registry hives from another system partition using Regedit. Whilst the hives appeared to load ok (I used the File > Load Hive... option - not mounting via a batch file), when I browsed them I noticed that the registry entries appeared to be a mirror of my running XPCLI - Diskpart Build - the entries that should have been present from the other system were not there!

Sorry, cannot understand .
Can you describe EXACTLY what you have been trying?


Wonko

[misty]

@Wonko

• XPCLI installed to (hd0,0)
  
• XP Gold (Full install) installed to (hd0,1)
  
• Booted XPCLI
  
• Started Regedit and loaded (hd0,1)\Windows\System32\config\SYSTEM hive as HKLM\_XP_SYSTEM
  
• Browsed to HKLM\_XP_SYSTEM keys in regedit - all values were the same as those in the current HKLM\SYSTEM (from - (hd0,0)\Windows\System32\config\SYSTEM hive).

The entries that should have been in HKLM\_XP_SYSTEM were not there!

Hope this clarifies the problem. I will test again myself when I get the chance - hopefully later this evening. This may have been a one off or could mean that the hives are not being properly mounted.

Regards,

Misty

[Wonko the Sane]

This may have been a one off or could mean that the hives are not being properly mounted.

It is possible.
Try using REG.EXE to verify, copy this snippet as regcomact.cmd and place a copy of it in the "real Windows" WindowsSystem32config and another copy in the XPCLISystem32Config:

@ECHO OFF

SETLOCAL ENABLEEXTENSIONS

SET /A Known=0

IF "%1"=="DEFAULT" SET /A Known+=1

IF "%1"=="SOFTWARE" SET /A Known+=1

IF "%1"=="SYSTEM" SET /A Known+=1

IF %Known%==0 GOTO :EOF

REG query HKLMRegCompactTemp 2>nul

IF %ErrorLevel%==0 (GOTO :EOF) ELSE (

REG load HKLMRegCompactTemp %~dpnx1

REG save HKLMRegCompactTemp %~dpn1.CPT

REG unload HKLMRegCompactTemp

)

Navigate (from XPCLI) to WindowsSystem32Config and run as "regcompact.cmd System".
You should see three times "the operation completed successfully" (or something to that effect).
If you get something like "RPC server is unavailable", then the REG.EXE (and/or REGEDIT support is INcomplete)

If you don't have errors, make a copy of actual SYSTEM to SYSTEM.CPY
Boot to the "full" windows and try mounting the SYSTEM.CPT and SYSTEM.CPY hives and see if they are the same contents or not.



Wonko

[misty]

@Wonko
Please accept my sincere apologies. I feel like the class dunce right now - or perhaps more accurately the village idiot.

In a previous test (god knows I've done enough of them recently) I replaced my Full XP reg hives (on (hd0,1)) with Dietmar's reg hives in an attempt to see if the real XP winlogon would start successfully when I booted (hd0,1) - the idea was that all file dependencies might be in the right place. Anyway, this didn't work - I think I got an 0x7b error but can't remember for definite.

Guess who then forgot he'd replaced the real XP reg hives with Dietmar's.

It's no surprise that the reg hives on (hd0,1) looked identical to Dietmar's - they actually were.

Hope this makes sense.

In my defense for this really stupid error - I've had a lot of late nights and little sleep due to the fun I've been having with these projects.

Regards (and more apologies),

Misty

[Wonko the Sane]

Please accept my sincere apologies. I feel like the class dunce right now - or perhaps more accurately the village idiot.

No prob, it happens to everyone.

Anyway, this didn't work - I think I got an 0x7b error but can't remember for definite.

... but do not insist , you defintiely had NOT a 0x0000007b error, but eithear a 0xc0000021 or a 0x00000135 .... (this time if I recall correctly )

In my defense for this really stupid error - I've had a lot of late nights and little sleep due to the fun I've been having with these projects.

That's the idea (having fun I mean )

Have you checked size of the registry files after having run the little batch?




Wonko

[misty]

... but do not insist , you defintiely had NOT a 0x0000007b error, but eithear a 0xc0000021 or a 0x00000135 .... (this time if I recall correctly )

Just rechecked -

• Installed XPCLI (second file set) to (hd0,0) with real Winlogon and the dependencies you identified in a previous post. Booted XPCLI on (hd0,0) - Error c000021a.

• Full XP Gold installed on (hd0,1). Replaced the (hd0,1)\Windows\system32\config folder with Dietmar's registry files. Booted Full XP on (hd0,1) - Error 0x0000007B

Interestingly, the XPCLI system appeared to get further into the boot process. Don't know if this has any relevance to trying to get get Winlogon working or not.

Regards,

Misty

[TheHive]

I wonder what is the use of that launcher

For easy launching of multiple apps without having to have a shell or remember an type the name of the app.

Add blackbox and you have a "real" shell :
http://reboot.pro/3717/page__st__26


Wonko

How much ram does it use. I was just asking for a light app to launch a list of apps that also looks good. Not full blown shell at this time yet.

In terms of Appetizer App Launcher - I have concerns about introducing any application launcher at this time due to issues around creating the required menu entries.

Im using its own add shortcut button to point to the apps. It takes a bit to show the drive to choose the programs to make the shortcut. But it works.

It uses an XML file to store the data
Here is a snippet of what i can see in there.

		<FilePath>$(Drive)WINDOWSsystem32notepad.exe</FilePath>

		<Name>Notepad</Name>

		<AutomaticallyAdded>0</AutomaticallyAdded>

		<MultiLaunchGroup>0</MultiLaunchGroup>

		<IsGroup>0</IsGroup>

	</FolderItem>

	<FolderItem>

		<FilePath>$(Drive)WINDOWSsystem32REGEDIT.EXE</FilePath>

		<Name>Registry Editor</Name>

		<AutomaticallyAdded>0</AutomaticallyAdded>

		<MultiLaunchGroup>0</MultiLaunchGroup>

		<IsGroup>0</IsGroup>

	</FolderItem>

	<FolderItem>

		<FilePath>$(Drive)WINDOWSsystem32taskmgr.exe</FilePath>

		<Name>Windows TaskManager</Name>

		<AutomaticallyAdded>0</AutomaticallyAdded>

		<MultiLaunchGroup>0</MultiLaunchGroup>

		<IsGroup>0</IsGroup>

	</FolderItem>

	<FolderItem>

		<FilePath>$(Drive)WINDOWSsystem32clonedisk.exe</FilePath>

		<Name>clonedisk</Name>

		<AutomaticallyAdded>0</AutomaticallyAdded>

		<MultiLaunchGroup>0</MultiLaunchGroup>

		<IsGroup>0</IsGroup>

	</FolderItem>

In terms of a small application launcher - what about nu2menu (from BartPE). I've not attempted using this myself so I have no idea about dependencies.

Regards,

Misty

You can probably use that as a shell. But for a small app launcher Appetizer App Launcher wouldnt be bad.
It can probably be added as choice to add to be run right after the command prompt shows up.

[misty]

@Everyone
I have decided to abandon my Winbuilder "XPCLI - Diskpart Build" project. Rising like a phoenix from the ashes of this project....... comes....... wait for it....... imagine you can hear a drum roll....... MiniXP!

MiniXP

MiniXP is a modular system. Any application compatible with Windows XP can theoretically be added to the MiniXP project - provided the relevant file dependencies and registry settings are added.

Why the name MiniXP? I want to be able to differentiate this project from Dietmar's first file set to avoid confusion. I have chosen this name based upon a comment Dietmar made in this thread - "...But you have to build a Mini XP to make diskpart work...". It was getting a bit tedious refering to my project as the second file set all the time!

Although I do want to differentiate this Winbuilder project from the work Wonko is doing with the first file set, MiniXP is inextricably linked to the first file set and also his work. Without Wonko's input there would be no MiniXP

I have added the following features -

• caching of core files to decrease build time
  
• automatically copy to disk image (script must be enabled)
  
• automatically test in QEMU (script must be enabled)
  
• boot in RAM using WinVBlock (and Grub4dos) - tested on real system
  
• Installers folder moved to %BaseDir% (e.g. %BaseDir\INSTALLERS)

Please refer to the MiniXP site (hosted courtesy of reboot - many thanks Nuno) for documentation and the project download.

Please read the documentation either on the site or included in the download.

I consider this a beta release. Please test and provide feedback.

Have fun!

Regards,

Misty

[TheHive]

This scree disappears to fast.
Is their a way to allow the user to browse to the "minlogon.exe" or the "minlogon.cab". If its the minlogon.cab then it would extract the minlogon.exe to the right place.
Sample image of what it might say on script.



Copy2DiskImage
Needs to let the user know where to download Imdisk if they never heard of it. Or allow for an auto install if so desired by the user. As how Psc does it in this MultiPE project. Maybe include it in the project.

One error during build

FileRename - Failed to rename file: [%BaseDir%\IMG\empty.img] to:[%BaseDir%\IMG\minixp.img] :The system cannot find the file specified

I think its suppose to be [%BaseDir%\Files\empty.img]\

[wimb]

Please refer to the MiniXP site (hosted courtesy of reboot - many thanks Nuno) for documentation and the project download.

I had to add XP_GOLD\I386\ASMS\6000\MSFT\VCRTL\MSVCP60.DLL to WINDOWS\System32
otherwise there was Error - Services.exe has missing file ....MSVCP60.DLL

But then it worked
Booting is OK in qemu and on real hardware as RAMDISK or as FILEDISK using grub4dos menu.

XP SP2 or SP3 have Error in WinBuilder and did not work for me.

XPCLI - Portable Apps like Ghost and FreeCommander can be launched from PStart Menu

= =

[misty]

@TheHive
Thanks for the feedback. I'll add longer warning messages for any missing files as suggested. Will also add information about ImDisk to the docs when I get the chance. I do not plan to add an option to auto install ImDisk as I don't want to make any changes to someone else's Host System. In terms of minlogon.exe - the docs clearly state where this file needs to be copied. Whilst I accept that your suggestion might make life easier, I would discourage anyone who can't follow these simple instructions from using the project.

One error during build

FileRename - Failed to rename file: [%BaseDir%\IMG\empty.img] to:[%BaseDir%\IMG\minixp.img] :The system cannot find the file specified

I think its suppose to be [%BaseDir%\Files\empty.img]\

Actually, no it's not. This is the second time you have had an error relating to files extracted by 7-zip not being found. I wonder if there is a delay in extracting these files on your system. I have uploaded a new version of the Copy2DiskImage script with the following bolded line 23 added (numbers are new line numbers when edited in Winbuilder) -

22 ShellExecute,Hide,"%BaseDir%\Projects\Tools\7za.exe","e -o%BaseDir%\IMG %BaseDir%\Projects\Files\empty.zip"

[b]23 Wait,5[/b]

24 Echo,"Renaming Disk Image as minixp.img..."

I've uploaded the edited 2_copy2disk.script to the new Temporary File Host service Nuno has implemented. Please test and feedback - hopefully the 5 second delay in renaming the disk image will resolve this issue for you.


@Wimb
Thanks for testing.

I had to add XP_GOLD\I386\ASMS\6000\MSFT\VCRTL\MSVCP60.DLL to WINDOWS\System32
otherwise there was Error - Services.exe has missing file ....MSVCP60.DLL

I experienced this error with Service Packs 2 & 3 - not with Gold or SP1 sources. The Core Files script already adds MSVCP60.DLL if SP2 or SP3 sources are detected - I will consider adding it for all builds, however it's definitely not in Dietmar's original file list. I can't replicate this error at the moment when using Gold or SP1 sources. Will try to investigate. Have you added any additional services? Is it possibly due to different language source files?

XP SP2 or SP3 have Error in WinBuilder and did not work for me.

What errors? My English language SP2 and SP3 sources work fine for me but I haven't tested with any other sources. Also what host OS are you using?

@everyone
Could really use some more beta testers!

Regards,

Misty

[wimb]

I first tried to use NL XP-SP3 and then NL XP-SP2 and got error (have to check it )
(SP3 - unable to copy cat file of I386ASMS6000MSFTWINDOWSCOMMONCONTROLS to Manifests).
Then used NL XP Gold as Source.
Could it be that the Cache (containing SP2 files ?) is causing the trouble with MSVCP60.dll

My Host OS is NL XP-SP3 + Integrated Updates (until jan 2012).

[misty]

Could it be that the Cache (containing SP2 files ?) is causing the trouble with MSVCP60.dll

I've had too many late nights recently - something to do with a Winbuilder addiction! When I first read your post about 30 minutes ago I didn't have a clue what you meant by the Cache (containing SP2 files ?). I have only just realised that you meant the Cache I recently introduced to the project. Need sleep.

Anyway, the cache I introduced will cache the core files only for each service pack version used. The SP caches should be independent of each other. E.g. when SP3 source is first used, the core files will be cached to /Projects/Cache/SP3/ - if SP3 source files are used for a rebuild then the /Projects/Cache/SP3/ files will be reused. If source files are replaced with SP2, then these files will be cached to /Projects/Cache/SP2/ to be used if the project is rebuilt and SP2 source is again detected.

Basically the cache should not be causing any issues at all - unless SP#.cab is not present in the source files as this file is used to identify service pack versions.

Regards,

Misty

[TheHive]

Log
log minixp Beta 2012-04-13.zip
http://temp.reboot.p... 2012-04-13.zip

Same error with updated 2_Copy2Disk.Script
FileRename - Failed to rename file: [%BaseDir%IMGempty.img] to:[%BaseDir%IMGminixp.img] :The system cannot find the file specified

[misty]

@TheHive
Just managed to replicate your error. Are you by any chance running the project from a directory with spaces in the path? From project docs (see here)

Important - ensure that there are no spaces in the file path(s) containing this project.

Hope this is the problem and it's not actually something complicated!

If you are actually using a path with spaces, please try the following code (at line 22 in 2_copy2disk.script ) and report back -

ShellExecute,Hide,"%BaseDir%\Projects\Tools\7za.exe","e -o#$q%BaseDir%\IMG#$q #$q%BaseDir%\Projects\Files\empty.zip#$q"

Regards,

Misty

[TheHive]

Much better
As a new user. What is and where can I get Imdisk!

@TheHive
Just managed to replicate your error. Are you by any chance running the project from a directory with spaces in the path? From project docs (see here)

Hope this is the problem and it's not actually something complicated!

If you are actually using a path with spaces, please try the following code (at line 22 in 2_copy2disk.script ) and report back -

ShellExecute,Hide,"%BaseDir%ProjectsTools7za.exe","e -o#$q%BaseDir%IMG#$q #$q%BaseDir%ProjectsFilesempty.zip#$q"

Regards,

Misty

I tested on both with and with no spaces but had the same error.
With the new snippet the script works.

I like that step where it gives you the chance to add youre own files before final completion and test. I hadent tought of that but its good you did.
How about creating a empty Programs folder where the user is asked to put his Program files and folders. That way we can maintain a good flow.

Test in Qemu didnt seem to boot up. Shows command prompt then nothing.

Phew managed to get a screenshot. Went fast.

[misty]

@TheHive

As a new user. What is and where can I get Imdisk!

Will add to the Required Files section of the documentation.

I tested on both with and with no spaces but had the same error.

Really? I have not had any problems at all when there haven't been any spaces in the path. Any chance you can retest without spaces using the old code as this could be a serious problem.

Test in Qemu didnt seem to boot up. Shows command prompt then nothing.

Phew managed to get a screenshot. Went fast.

Please edit the [process] section of the Test in Qemu script and change the ShellExecuteEx line to -

ShellExecuteEx,Open,"%BaseDir%\Projects\Tools\Qemu_0.15.1\qemu.exe","-L #$q%BaseDir%\Projects\Tools\Qemu_0.15.1#$q -m 64 -boot d -hda #$q%BaseDir%\IMG\minixp.img#$q"

Thanks again for testing.

Regards,

Misty

p.s. I'm pleasantly surprised the build process got as far as it did when the path had spaces - Winbuilder is IMHO very fault tolerant.

[misty]

Double Post - Sorry.

[TheHive]

Really? I have not had any problems at all when there haven't been any spaces in the path. Any chance you can retest without spaces using the old code as this could be a serious problem.

Retestest minixp Beta 2012-04-13.zip unzip to C drive in a MiniXP folder and did not get that error. Seems to build fine and boot.


As reported by wimb
Free Commander Explorer is working.

Please edit the [process] section of the Test in Qemu script and change the ShellExecuteEx line to -

ShellExecuteEx,Open,"%BaseDir%ProjectsToolsQemu_0.15.1qemu.exe","-L #$q%BaseDir%ProjectsToolsQemu_0.15.1#$q -m 64 -boot d -hda #$q%BaseDir%IMGminixp.img#$q"

That fix the folders with spaces in qemu script. Seems to build normally and Boots up now.

p.s. I'm pleasantly surprised the build process got as far as it did when the path had spaces - Winbuilder is IMHO very fault tolerant.

Must be good programming.

Thanks for the fixes.


How does RAM Boot option work. How do you go by testing that. Is it also using qemu?

[misty]

@everyone
Project has been updated. Added code to scripts that TheHive identified as not working if there are spaces in file paths. Documentation also improved (I think) - Imdisk has been added to the Required Files section. MiniXP site layout improved and Aims (& Goals) section added.

@TheHive

How does RAM Boot option work. How do you go by testing that. Is it also using qemu?

Please see the docs for testing on a real system. You will need to have grub4dos installed - not exactly n00b friendly at this point as there's not much in the documents to explain RAM booting.

I will add this as a test option at some point via another script, however this will take a few days as I'm away for the weekend.

Regards,

Misty

[TheHive]

@everyone
Project has been updated. Added code to scripts that TheHive identified as not working if there are spaces in file paths. Documentation also improved (I think) - Imdisk has been added to the Required Files section. MiniXP site layout improved and Aims (& Goals) section added.

Looks much better.

@TheHive

Please see the docs for testing on a real system. You will need to have grub4dos installed - not exactly n00b friendly at this point as there's not much in the documents to explain RAM booting.

I will add this as a test option at some point via another script, however this will take a few days as I'm away for the weekend.

Regards,

Misty

I will wait. Have a good weekend.

From Documentation

. Many of the current registry entries are written in a mixture of English and German - which can make tracing problems difficult.

why not post the registry entries and see if some one that understands german can translate them back to english.

[Nuno Brito]

Hello, I tested the project.

Very simple and straightforward, five stars organization!

Very quick feedback:

• The qemu scripts needs Copy2DiskImage enabled by the user. You can solve this matter by editing the qemu script from inside the winbuilder window, choose "Options" and inside the "Dependencies" box add

  %basedir%minixpProjectsMiniXP_scriptsEnd2_Copy2Disk.Script

• Maybe this project is ready for its own discussion topic and presence at the wb projects section? http://reboot.pro/fi...ory/4-projects/

[wimb]

How come that diskpart is NOT working in MiniXP SP3 ?

(it is working with GOLD SP0 but then my SATA disks are not visible due to missing suitable driver)

By adding 1 file to the minixp SP3 version, then two other interesting Apps can be used.

Windows Partition Manager and Handy Recovery are working by adding oledlg.dll to the build.





In case of SP3 source I have compressed files
I386ASMS6000MSFTWINDOWSCOMMONCONTROLSCONTROLS.CA_
I386ASMS6000MSFTWINDOWSCOMMONCONTROLSCOMCTL32.DL_

Then Calculator, Notepad, Regedit and Task_Manager script will give the earlier mentioned Error for FileCopy Statement.

I don't have I386SP3.CAB in my XP SP3 Source, which has UpdatePack integrated with RyanVM Integrator.
There is DRIVER.CAB file in I386. In that case the SP3 Source is identified as Gold so that MSVCP60.dll is not copied.
On next run when I select real Gold Source then wrongly the GOLD Cache is used, which contains SP3 files.
You might use root tagfile WIN51IP.SP3 to identify SP3 Source.

[misty]

@Nuno

Very simple and straightforward, five stars organization!

Thanks. You're too kind.

The qemu scripts needs Copy2DiskImage enabled by the user. You can solve this matter by editing the qemu script from inside the winbuilder window, choose "Options" and inside the "Dependencies" box add...

Thank you. I still have an awful lot to learn - I suspect many of my scripts could be refined now that I've learned a few more commands. This will really help in achieving my aim of "A successful build every time" - a bit optimistic, but definitely something to strive for!

Maybe this project is ready for its own discussion topic and presence at the wb projects section?

Watch this space, It will hopefully be ready within the next week after a few more updates and beta tests.


@TheHive
See here for a .script for testing RAM booting in QEMU. It's only fair that after my hard work in putting it together you test and feedback . Thanks.

Many of the current registry entries are written in a mixture of English and German - which can make tracing problems difficult.

why not post the registry entries and see if some one that understands german can translate them back to english.

A good suggestion, however this is not necessary as all of the required translations can be copied from a full Windows XP installation. This is not a priority at the moment as the build process needs refining first.


@wimb

How come that diskpart is NOT working in MiniXP SP3 ?

It's not working with SP2 source files either. I'm not sure whether it's due to a missing file dependency or registry settings.

In case of SP3 source I have compressed files
\I386\ASMS\6000\MSFT\WINDOWS\COMMON\CONTROLS\CONTROLS.CA_
\I386\ASMS\6000\MSFT\WINDOWS\COMMON\CONTROLS\COMCTL32.DL_

If I understand correctly, then your source files contain .cab compressed CONTROLS.CAT and COMCTL32.DLL. Please test this updated notepad script (here) and report back - I'll update the other scripts if this is confirmed as working.

Regards,

Misty

[TheHive]

Hope to have time to test Ramboot tommorrow.