254 replies to this topic

[TheHive]

No, it is supposed to build a small HD image.

ok! Thanks!

In "Task Manager" .script:


Try NOT checking the Task Manager .script. (at first sight there is a missing space after the -o in the 7z command ).


Wonko

Some files from the
ROOT
do not want to be deleted.


When you run WInbuilder again.
DirDelete - Failed to delete directory [%BaseDir%ROOT]: Unknown error

[misty]

test result Windows XP Pro SP0

FileCopy - Failed to copy [%BaseDir%\ROOT\WINDOWS\system32\wzcsvc.dll] to: [%BaseDir%\ROOT\INSTALLERS\TASKMGR\SystemRoot\system32\wzcsvc.dll]: The system cannot find the file specified.

@TheHive
This is working on my system - I've only tested the new scripts on x86 Windows 7 (SP1) host though. Please check to see if the wzcsvc.dll file is in the ROOT/WINDOWS/system32/ directory - if it has been expanded successfully in the earlier part of the Task Manager script then perhaps there is a delay in the file being extracted and it does not appear to be there when the FileCopy command is carried out.


Will look into using the the Winbuilder internal Expand command instead of 7-zip - I have only just found out that single files can be extracted. What can I say - I'm a Winbuilder n00b!

@Misty
Sure .
The point is only that we can make a "diff" allright between Dietmar's first set and second set.
If you prefer you started from "step 2" whilst I am advocating to start from "step 1", not that big a difference, but I would like to have the "finest granularity" possible.

Just as an example (and please don't take it as a critic ) even in the small build you already have a "logical fallacy" , you get the fastfat.sys in "Core":

BUT you add the Registry entry in "Recommended":

@Wonko
I'm not sure if the fastfat script is actually required at all. There are a lot of, in my opinion, unnecessary registry entires in Dietmar's files - I need to retest whether his FastFat entries work without adding the edits you use in the first file set.

I am kind of starting from step 2 as you have put it for the previously stated reason that I simply don't have the skills and knowledge to get to step 2 from step 1 using your modular approach - there are simply too many registry changes that I don't understand.

There's still a lot of work to do! Thanks for the link to Extract - will explore this if the internel Winbuilder Expand command is not working.

Regards,

Misty

[misty]

Some files from the
ROOT\
do not want to be deleted.


When you run WInbuilder again.
DirDelete - Failed to delete directory [%BaseDir%\ROOT]: Unknown error

Did the registry hives unmount properly in the previous build? If the last build was not completed successfully then the hives may still be mounted. Look under HKLM/ key for entries similiar to _XPCLI_SYSTEM and manually unload them.

Regards,

Misty

[Wonko the Sane]

@Wonko
I'm not sure if the fastfat script is actually required at all. There are a lot of, in my opinion, unnecessary registry entires in Dietmar's files - I need to retest whether his FastFat entries work without adding the edits you use in the first file set.

I agree , that's why I'm working on it, trying to "sync" them also to the PicoXP Registry (it seems like there is more than one way to skin a cat, i.e. same problem is solved in XPCLI and PicoXP in two different ways, I hope by comparing and testing to find both ways).

I am kind of starting from step 2 as you have put it for the previously stated reason that I simply don't have the skills and knowledge to get to step 2 from step 1 using your modular approach - there are simply too many registry changes that I don't understand.

Yep , you are cheating , I hope to find the info to "fill the gaps".


Wonko

[misty]

I agree , that's why I'm working on it, trying to "sync" them also to the PicoXP Registry (it seems like there is more than one way to skin a cat, i.e. same problem is solved in XPCLI and PicoXP in two different ways, I hope by comparing and testing to find both ways).

I'm having enough difficulty trying to make sense of the differences between the registry entries in Dietmar's two file sets - introducing registry hives from an altogether different project is IMO a recipe for a big headache. I wish you the best of luck.

Yep , you are cheating , I hope to find the info to "fill the gaps".

I know I'm cheating, and I will continue to do so - until you hopefully manage to fill in those gaps for me. If nothing else I have a much better understanding of Winbuilder - my time at the moment is being spent improving my little project. I know this is going off on a bit of a tangent, however I'm enjoying the game - we are here to have some fun after all.

Playing with the first file set was starting to feel a little like - I'm happy with the diversion at the moment.



Regards,

Misty

[misty]

Having learned a bit more about Winbuilder scripting I have updated the scripts for my project which will build a XPCLI based on Dietmar's second file set.

The new scripts (attached to this post - see below) do not require 7-zip and use a better logic to ensure that any registry hives left mounted (e.g. due to a previous build having aborted prematurely) will be unmounted before the %TargetDir% is removed.

I have also removed the core script that mounted all registry hives. Individual scripts that require access to the registry will check if the hive is mounted (e.g. by another script executed earlier) and will mount the necessary hive(s) as required.

I have removed the FastFat script as it wasn't required - cheers Wonko .

After running the build with all scripts selected, the build files (excluding the INSTALLERS that were generated) were 38.5 MB in size (XP Gold source). This includes Dietmar's core files + the following (and their dependencies - this includes the massive (at 7.93 MB) shell32.dll) -

• Regedit
  
• Task Manager
  
• xcopy
  
• Format
  
• Notepad
  
• Calculator
  
• Mouse support
  
• CDFS support
  
• marlett.ttf and tahoma.ttf fonts (used for some symbols in GUI based applications)

Regards,

Misty

Attached Files

•  XPCLI_v3.zip   1.37MB   78 downloads

[TheHive]

Tested XPCLI_v3 ran build from Desktop and not from C:
Better results.

Test1
Built using default Core scripts
No errors reported and build seemed ok. I see a ROOT folder.
23.5 MB

What Can you do with this?


Test2
Built using Core scripts + all Recommended scripts
No errors reported and build seemed ok. I see a ROOT folder.
75.7MB

What Can you do with this?
Im guessing more UI supported apps.

No, it is supposed to build a small HD image.


Wonko

In this test there is no Small HD image created. Only a ROO folder is in the XPCLI_v3 Directory .

[misty]

@TheHive
Thanks for testing. Please read the README.HTM file included in the download for more details about the project.

What you can now do with either build is MANUALLY copy the files to the disk image included in /Projects/Files/empty.zip - the instructions are in the README.HTM file. With the disk image manually created you can now test in QEMU.

I have purposefully not tried to create the disk image as part of the Winbuilder project as it introduced too many variables - I'm a WInbuilder n00b remember.

IMO, the is a risk of too many errors being introduced to the project by automating the disk building process in Winbuilder.

Regards,

Misty

p.s. In your test 2 you do not need files contained in the /ROOT/INSTALLERS folder - these are custom installers to add the necessary apps to an already installed and running XPCLI built with the project - e.g. the file from your test 1.

[TheHive]

@TheHive
Thanks for testing. Please read the README.HTM file included in the download for more details about the project.
What you can now do with either build is MANUALLY copy the files to the disk image included in /Projects/Files/empty.zip - the instructions are in the README.HTM file. With the disk image manually created you can now test in QEMU.

Before reading the rest of the readme. I tried to Manually copy all files in Root to a empty vhd file to test in Virtual PC. But It doesnt seem to want to boot up.
Here is a pic of the files booted in LiveXP 2012 PE.

I have purposefully not tried to create the disk image as part of the Winbuilder project as it introduced too many variables - I'm a WInbuilder n00b remember.

IMO, the is a risk of too many errors being introduced to the project by automating the disk building process in Winbuilder.

Regards,

Misty

Maybe Psc can help in creating or adapting the script to make it work with this project.

p.s. In your test 2 you do not need files contained in the /ROOT/INSTALLERS folder - these are custom installers to add the necessary apps to an already installed and running XPCLI built with the project - e.g. the file from your test 1.

So when we have a booted Root
We have to manually use each Install.cmd for each app in order to install it. And then we can delete that Installers folder.

[misty]

So when we have a booted Root
We have to manually use each Install.cmd for each app in order to install it. And then we can delete that Installers folder.

@TheHive
No. If you are using the files from your Test 2 then the \ROOT\INSTALLERS\ folder is not required at all. Simply delete it and save approximately 40 MB disk space. All of the apps in \ROOT\INSTALLERS\ will also be in the \ROOT\WINDOWS\ directory - they are duplicates.

The \ROOT\INSTALLERS\ folder is only required to add specific applications to another already installed XPCLI. If for example the files from your Test 1 (just the core files) had been copied to a disk image and you wanted to install just \ROOT\INSTALLERS\REGEDIT, you would copy the REGEDIT directory from \ROOT\INSTALLERS to your disk image, boot it in QEMU and then run REGEDIT\install.cmd. At least this is what you would do in an ideal world - xcopy will already need to be in you booted XPCLI for the installer to work.

If XCOPY is missing from your core files and you want to try the installers you will need to install it (XCOPY) manually first. E.g. -

copy C:\INSTALLERS\XCOPY\SystemRoot\System32\*.* C:\WINDOWS\System32

Sorry if adding the \ROOT\INSTALLERS\ has overcomplicated matters - this was more a proof of concept idea.

Regards,

Misty

[Wonko the Sane]

we are here to have some fun after all.

Actually that is the ONLY important thing .


Wonko

[TheHive]

That explanation makes more sense. Much clearer for the use of the Installers folder.
ROOT down to 36.3 MB

Qemu Manager 7 Portable doesnt know what empty.ima is. It wont let me use it as a drive
It only seems to allow
.qcow
.qcow2
.raw
.vmdk

[misty]

Qemu Manager 7 Portable doesnt know what empty.ima is.

Sorry. Rename the file with .raw file extension.

Regards,

Misty

[Wonko the Sane]

@The HIve
No need to rename.
Simply type *.* in the "name file" box of the Specify Hard Disk 0 open dialog.
You will see all files, and you can choose the .ima (or whatever)

@Misty
As a general Rule, the common convention is:

• .ima is a floppy or super-floppy (UNpartitioned, NO MBR) image
  
• .img is a HD-like (with MBR) image

Wonko

[TheHive]

Finally success with renaming to .raw file extension.




I wonder why when I copy the files to the fat32 Empty vhd file it wont boot in Virtual PC.



In the readme it better to recommend the Portable Qemu Manager = qman70.zip

Zip File Edition (Unzip and run! can be used with USB Pen sticks/Drives

Open qemumanager.exe.manifest with a text editor and delete the tag <trustInfo xmlns="urn:schemas-microsoft-com:asm.v2"> along with its content (this way Qemu Manager doesn't request elevation when launched under Windows Vista/7)

So in other word delete

<trustInfo xmlns="urn:schemas-microsoft-com:asm.v2">

   <security>

	  <requestedPrivileges>

		 <requestedExecutionLevel

			level="requireAdministrator"

			uiAccess="False"/>

	  </requestedPrivileges>

   </security>

</trustInfo>

Any Shutdown command available.


So did you get miniexplorer to work Wonko?
http://reboot.pro/37...dpost__p__27253

Maybe a simple mini launcher. This seem to work.
http://app.etizer.org/download
Appetizer 1.4 (ZIP Package)

Gave it a short name folder and renamed app name to app
so I put in in system32 folder as app and launched it as app. Maybe can default to system 32 folder with its subfolder in there.

[Wonko the Sane]

I wonder why when I copy the files to the fat32 Empty vhd file it wont boot in Virtual PC.

Because it is empty?
Why don't you simply use Clonedisk to convert the .ima/.raw to "static" .vhd?

So did you get miniexplorer to work Wonko?
http://reboot.pro/37...dpost__p__27253

Sure it works .
Just try it.
The issue (more graphical than anything else) is for some "default" places (and their icons), like "Desktop" and "My Computer" that simply do not exist in XPCLI.


Wonko

[TheHive]

Because it is empty?
Why don't you simply use Clonedisk to convert the .ima/.raw to "static" .vhd?

Lol! Maybe because I forgot about it. That works. Thanks for the reminder.



Used the DiskImage to VHD option.

CloneDisk 1.9.6
http://reboot.pro/fi...e/24-clonedisk/

[TheHive]

Can you make a script for Appetizer App Launcher so it will automatically launch
It used around 7 MB memory to run. Unless their is a smaller alternative.
Something like this




XPCLI_v3 Booting in Virtual PC running
Appetizer App Launcher with shortcuts to the other scripted apps.BAM!

[Wonko the Sane]

Can you make a script for Appetizer App Launcher so it will automatically launch
It used around 7 MB memory to run. Unless their is a smaller alternative.

I wonder what is the use of that launcher

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


Wonko

[misty]

@TheHive
Hope you are having fun with this project. Hopefully it will entice you into experimenting with Dietmar's first file set.

Can you make a script for Appetizer App Launcher so it will automatically launch
It used around 7 MB memory to run. Unless their is a smaller alternative.

At the moment I'm (re)working the core functions. This includes -

• Caching of core files to improve build speed - saves approximately 30 seconds on rerun.
  
• Installers folder moved to %BaseDir% (e.g. %BaseDir\INSTALLERS)
  
• Script to automatically copy files to a mounted disk Image

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.

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

[misty]

I wonder what is the use of that launcher

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

@Wonko
bblean is a fantastic shell application - I've been using it for several years with WinPE 2.*/3.* and highly recommend it. There are still issues around adding menu entries to it though.

Regards,

Misty

[Wonko the Sane]

@Wonko
bblean is a fantastic shell application - I've been using it for several years with WinPE 2.*/3.* and highly recommend it. There are still issues around adding menu entries to it though.

Which issues?
The "base" set of config files I posted:
http://reboot.pro/3717/page__st__47
work very well here, and adding items to the menu is seemingly very easy (example of the menu.rc I am currently using):

[exec] (miniexplorer) {%SystemRoot%\Apps\miniexplorer\miniexplorer.exe}

[exec] (WinExplorer) {%SystemRoot%\Apps\WinExplorer\Winexplorer.exe}

[exec] (Cmd Prompt) {cmd.exe}

[exec] (Edxor) {%SystemRoot%\Apps\Edxor\Edxor.exe}

[exec] (Dos Navigator) {%SystemRoot%\Apps\dn\dn.exe}

[exec] (SwissKnife) {%SystemRoot%\Apps\SwissKnife\SWISKNFE.exe}

[exec] (NTRegEdit) {%SystemRoot%\Apps\NTregedit\NTRegEdit.exe}

i.e.:
[exec] (<name of the app visible in menu>) {<full path to the executable>}


Wonko

[misty]

Which issues?
...[exec] (<name of the app visible in menu>) {<full path to the executable>}

@Wonko
Sorry for not being clearer. I should have said that there are issues with scripting the menu entries if using winbuilder. It's not that difficult to actually do as the entries are merely text based, however it adds another layer of complexity. I'd prefer not to impose a shell on the user at this time - the end user is free to choose their own.

Regards,

Misty

p.s. and actually do a bit of work themselves

[Wonko the Sane]

p.s. and actually do a bit of work themselves

Sure , if you check I adviced TheHive to add blackbox, and never suggested you to "force it upon" the end user, since I already produced and posted the needed files it should not be a problem.


Wonko

[misty]

... I adviced TheHive to add blackbox, and never suggested you to "force it upon" the end user...

@Wonko
Sorry, I didn't mean to imply that you had suggested this. Although I stated that "I'd prefer not to impose a shell on the user at this time", at some point I may well add this as an option.

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!

Regards,

Misty