The Mini XP project scripts can currently be divided into six distinct sections -
This section contains only one script - Core Files. This will build Dietmar Stoelting's core files. This script cannot be disabled. Dietmar's registry hives will be extracted from the script on first run. If Minlogon.exe is not found, the build process will be aborted.
I have tried not to add anything to Dietmar's build, however the following additions have been made if Service Pack 2 or 3 files are used as source -
Several files are missing as they are not included in the source CD, however they do not appear to be required anyway? The missing files are -
- DcomLaunch service
The following are all Recommended scripts. They add what I consider to be core features that were not included by Dietmar in his second file set. These scripts can be enabled or disabled as required -
- CDFS - add support for CD file system to access CD/DVD-ROMs. Thanks to ilko - see here.
- CMD in Window - the project uses CMD.exe as the shell (the user interface). The command line interface will run in full screen mode by default. To run in a window, select this script.
- File Associations - Register basic EXECUTABLE file associations (.bat, .com, .cmd, .exe) - recommended if using a file manager or other shells (e.g. bblean). Based on fileass.bat by Wonko the Sane. These are added directly to the registry.
- Fonts - add marlett.ttf and tahoma.ttf fonts to the build. Thanks to Wonko the Sane for pointing out that the marlett and tahoma fonts are used for some symbols in GUI based applications.
- Mouse - add mouse support to the build.
- Regional Settings - Dietmar's registry settings include Daylight Saving Time changes. When booting on a real PC the BIOS clock might be changed - enabling this script will change regional time settings to GMT without Daylight Saving Time changes!
- Resolution - Set the screen resolution as either 1024x768, 800x600 or 640x480.
The following section is reserved for Application scripts for third party applications - those that cannot be extracted from Windows XP source files. I hope to add to this over time, however I need to clarify whether it is possible to distribute the relevant files.
- a43 - File Manager and lightweight replacement for Explorer (see here). This script will attempt to download the application so you will need to be connected to the internet - nothing is installed locally. The files will be cached when this script is first executed, so you should only need to download the files once (unless you delete the cache). If you have any issues with the build process due to this script then please disable it.
- WinVBlock - Virtual Disk Driver. Boot MiniXP from a hard disk image file - RAM disk and file backed disks are supported. The disk image will need to be "mapped" using the Grub4dos boot loader. Please refer to the WinVBlock thread(s) on reboot.pro for further information -
WinVBlock and Win7Block.
The following Applications are not included but have been tested and appear to work in Mini XP -
Refer to reboot.pro forum post here for the file dependencies of these applications.
- Agent Ransack (search tool)
- beeblebrox (Partition Table Editor)
- dd for Windows
- DriveImageXML (Partition Backup)
- Eraser (Secure File Erase)
- Everest (Diagnostics)
- ImDisk (Virtual Disk manager)
- NT Password Edit
- Opera (Web Browser)
- PTEdit32 (Partition Table Editor)
- Recuva (File recovery tool)
- TinyHexer (Hex editor)
- Wincontig (File defragmentor)
The following are Application scripts. This section is for applications that can be extracted from Windows XP source files. These scripts can be enabled or disabled as required -
- Calculator - add calc.exe to the build. This has been tested successfully with XP Gold, SP1, SP2 and SP3 sources - despite using possibly incorrect WinSxS paths/dependences.
- Format - add Format.com to the build. Supports formatting partitions with NTFS/FAT/FAT32 file systems.
- Notepad - add notepad.exe to the build. This has been tested successfully with XP Gold, SP1, SP2 and SP3 sources - despite using possibly incorrect WinSxS paths/dependences.
- Regedit - This script will add Regedit to the build. This has been tested successfully with XP Gold, SP1, SP2 and SP3 sources - despite using possibly incorrect WinSxS paths/dependences. Thanks to Wonko the Sane - see here.
- Task Manager - This script will add Task Manager to the build. This has been tested successfully with XP Gold, SP1, SP2 and SP3 sources - despite using possibly incorrect WinSxS paths/dependences. Thanks to Wonko the Sane - see here.
- xcopy - add xcopy.exe to the build.
A Shell is another term for the operating systems user interface (or UI). The default MiniXP shell is the Windows Command Shell - a command line user interface. At present I have not been able to boot directly to an alternative shell, however it is possible to use the default Command Shell to launch an alternative.
- BlackBox Lean - (bblean Version 1.17.1). This provides a menu driven UI - to start it simply type shell at the command prompt when MiniXP has finished booting. All of the required files are included in the script and will be extracted and cached on first run. There are two options included in the script, these being lite or full versions - refer to the script for further details.
All of the options in this script require ImDisk (see here for the ImDisk homepage) to be installed on the Host Operating System, or the script will abort. The ImDisk (version 1.5.7) installer is included in the script and can be installed by using the relevent check box (see screenshot below) -
The Finish script will be executed after all other scripts have been processed - alternatively it can be executed independently (by pressing the script play button - the small green play icon to the right of the logo). There are currently three seperate options, only one of which can be selected -
- 1 - Create Disk Image - This script will copy the current build to a disk image. A 100 MB hard disk image will be extracted (using 7z.exe) and mounted (using Imdisk).
- 2 - Test standard build in QEMU - this will copy the build files to a hard disk image. It will run the same tasks as option 1 (see above), but will additionally test it using QEMU.
- 3 - Test RAM loading build - This will execute the same tasks as option 2. Additionally the WinVBlock driver will be added (if it wasn't already included) before the disk image is created, and the disk image will be tested in QEMU to ensure that it boots from RAM.