How to Build MS-DOS and Windows

MS-DOS Source

MS-DOS 1.25 was published on GitHub MS-DOS 1.25 was completely written in 8086 assembly so it needs to be assembled using an assembler (MASM and SCP 8086 Assembler). The object file(s) produced by MASM will then be linked to produce an executable which will then be converted to a raw binary executable (.COM). The .HEX files produced by SCP 8086 Assembler will be converted directly to raw .COM files using the HEX2BIN utility.

2. How to Make DOS?

This is as hard as the source code for the DOS BIOS (IO.SYS) was designed for Virtual Box and is not PC-compatible. Theoretically, the compiled binaries should work on Virtual Box but using the source code release by Microsoft alone will not produce a valid bootable disk as no source code for the boot sector is given. I do have access to the source code of the boot sector but as a result of Microsoft not releasing it publicly, I will not share it. This basically means with only the source code published by Microsoft, it is impossible to produce a working copy of MS-DOS 1.25.

3. What is Required

The following is required for compiling MS-DOS 1.25:

• Microsoft Macro Assembler (MASM)
• Microsoft 8086 Object Linker (LINK)
• EXE to Binary Conversion Utility (EXE2BIN)
• Seattle Computer Products 8086 Assembler (ASM)
• HEX to Binary Conversion Utility (HEX2BIN)
• A copy of the MS-DOS 1.25 source code

4. Details

The files STDDOS.ASM and MSDOS.ASM can be assembled to produce the DOS kernel and they are MASM compatible. All switches are set in the file STDDOS.ASM. MSVER generates binaries for MS-DOS with Microsoft copyright strings, IBM produces IBM PC-DOS binaries with IBM copyright strings. There is no need to change HIMEM and DSKTEST unless you want to experiment more with it.

COMMAND.ASM can be assembled using MASM to produce the command interpreter for MS-DOS. Just like the DOS kernel, you may use switches to produce both MS-DOS and IBM PC-DOS binaries. The HIMEM switch is also present.

ASM.ASM, HEX2BIN.ASM, IO.ASM and TRANS.ASM were written by SCP and must be assembled using their own assembler. IO.ASM have switches to configure the floppy disk controller and the Cromemco 4FDC is currently supported by The SIMH Altair 8800 Z80 simulator.

5. Compile It

Now, we are ready to compile MS-DOS 1.25 for the first time! If you are experienced in assembly, used those assemblers and tools listed above, then you should be able to get everything done by yourself. For those unable to assemble it on their own, my build disk will save your time.

Here is how to build MS-DOS 1.25 with the build disk: Download the build disk. Create a new virtual machine using your favorite emulator or hypervisor. Add a floppy drive, load the build disk. Start the virtual machine (it should boot from the build disk). Check the filenames using the DIR command and it should return: Type in MK to assemble that particular component or MK ALL to assemble everything. Once you have everything assembled, type in DIR *.COM and DIR *.SYS to see the executable produced, it should be similar to: You have done it! You can now copy those executables to another disk or extract them or run them!

• MINX 3
• MIT Open Courseware Mirror Site Program
• My Google Scholar

YOU NEED A 600 GIGABYTE VIRTUAL MACHINE TO COMPLETE THIS TUTORIAL

HERE IS WHERE YOU CAN OBTAIN WINDOWS SOURCE CODE FROM THE SHARED SOURCE INITIATIVE HERE.

• Licencing Documents
• Create a Enterprise Agreement Subscription.
• Plan for Enterprise Agreement enrollment
• Get started with your Enterprise Agreement billing account
• Enterprise Source Licensing Program
• Windows 10 Enterprise LTSC 2019
• You must own a Enterprise Product to have a Enterprise Agreement with a EULA and at least 5 PC's

Microsoft's Open Source Program

• Open Source Program
• Patent Promises and Patents

Adobe Contibutor Licence Agreement

• Adobe Open Source

Microsoft Legal

• Tutorial: Microsoft Entra integration with Convercent

Liquity Value

• Liquidity Value definition

I'm American and UK upper class according to lineage and graduated to Ivy League college with scholar awards in computer science. I'm enrolled in MITx. And I've finished my UVa coursework at MITx and Stanford online. I'm waiting on a offical MIT affiliation because I'm not fond or their partner universities to graduate. I've given $1k to the University of Washington and have access to materials. I was UVa-Wise ACM Vice President am a current IEEE and USENIX member. I'm writing congress to enforce Max Weber thories of police and education polices. I hold a .NET Foundation seat and or Windows seat at the .NET Foundation and pay my dues. I own Windows 10 Enterprise LTSC 2019. I sold my Microsoft and Adobe stock in 2013 and left college after I sent a gift to the Actress Anne Hathaway in 2011. Microsoft's Jonathan Chang called my Wise, Va apartment with my Microsoft MVP Award in 2011. I'm still trying to collect my Code Center Priemium Benifits. I'm a Royal Society of the Arts Fellow. I'm paternal and materal egyptian ashkanazi jewish and is now Anglican because of Charles Darwin a local dissident. As tradition royality keeps it in the family. I'm a Hathaway and Mculley too. I have seven hereidty titles in my family from the UK. Pluto and Venus are soulmates if you believe in that if not you have no soul and read Sean Carrol I'm not.

Worked on Made with Macromedia enhanced Cd's from 1999-2006. I used to work for Macromedia from 1998-2006. In San Fransisco, Ca. Which gave me a nice $8 million dollar patent portfolio and a 2006 Microsoft $28 million dollar tender offer funds. After reading the tender offer. I'm eligible for a book transfer of funds to Microsoft. I've printed my 25 years of career paperwork into one perfect folder. Me and Ms. Hathaway keep in touch to this day. I do not support Virginia V. Loving nor do I support country accents. I never have owned one country music album and was born in Johnson City, TN. and lived in Atlanta, Ga for 10 years. I have fond memories of the Swan House it the historical distric. Me and my family support Bristol TN/Va in the 50's before country music moved in and my father office refects it. I grew up on C.S. Lewis, Jane Austin, and Thomas More, classical music, opera, the ballet and rock n' roll. And have fond memories of the United Coal Ballet when I was younger. I do not support homosexuality. I'm gay not queer. I do not support the Linux operating system because it is false advertsing and is really just a hack and support Intel MINIX for acedemia and NetBSD for Microsoft Intrerix. Windows XP is in support until 2029 in Visual Studio 2019. We will move forward with Windows Vista source and beyond after 2029. I use Redmond, Wa's Living Computer Museum and connect to a XKL Toad-2. I'm working with XKL to buy a TOAD-2 running CTSS for my home like Pual Allen before me.

Microsoft has one mailing list for the Microsoft Research introductory project 'Detours'

I have my System Integrator ID and NDA which you can find in the Partner Center. You can access Microsoft Collaborate here I'm retired from Microsoft until the faternity leaves and Computer Science teaches Opertaing System Theory again. Or until Microsoft is a Computer Science Company not a IT Company.

You may want to try DR-DOS 7.03 from Caldera Licensing or Novell DR-DOS 7.0 from 1999 a updated from MS-DOS as the operating system stayed up to date until 2011 at Novell. and fetch the latest Perl distribution from the NT Sources Perl distribution and start DOS Globbing. I'm working on a Alpha, VAX or MIPS server and I hope I can boot something from the

• Does the Soul Exist? Evidence Says ‘Yes’
• DECUS
• MIPS/NT allied at birth
• Windows NT and VMS: The Rest of the Story
• SCO confirms Microsoft has licensed its Unix technology
• Microsoft and Novell Announce Broad Collaboration on Windows and Linux Interoperability and Support
• Visual Studio 2019 Compatibility
• The history of change-packing tools at Microsoft (so far)
• Random internal Windows terminology: IDW, Razzle, and their forgotten partners IDS and Dazzle
• It's Only A Hacker If It's Linus Himself
• MINIX: ​Intel's hidden in-chip operating system

Cache the Hewlett Packard operating environment for OpenVMS from the ftp.zx.net.nz World-Wide Web Server FTP Server and start updating to x86. Start with the 95 Win32 SDK. Find the MAPI Sample. Install Azure DevOps which comes with the Education Hub on Azure. For Computer Science Majors or Alumni. With the default collection and a OS project. Named OS the path should be _git/OS

In Cygwin use:

wget -r --no-parent to cache a directory

• Single UNIX Specification, and put AT&T System V and Source in SFU or SUA and Ultrix, Source in DEC.
• The ECMA 335 336 Standard started in 2002 and 2006 and worked on FreeBSD before Linux The .NET Framework work begain in 1998 with the COM SDK and the Next Generation Web Services SDK.
• Here is the documentation for it. The archive can be found on Github
• Advanced Computer Science Teaching with the SSCLI is a SSCLI Powerpoint.
• The Common Language Infrastructure Annotated Standard
• The .NET Framework 3.5 is in support until 2029.

• .NET vs. .NET Framework for server apps

Launch a CMD prompt and type pwd to execute UNIX Commands in the Win32 shell. With SFU or SUA.

• Aslo cache the University of Washington and Digital Corp from the same server. You should have your freeware 8.0 for XP from the HP FTP cache. Become a USENIX Member and download all the Login Jounals and put it in your HP's paper's directory.
• You can start updtaing the XP HP cache to x86 32-bit for Services for UNIX in XP/2003. 64-bit for SUA and Windows Server 2003 R2. I started with my Oracle Contract and netbeans 8.1 source and apache ant 1.7 from apache. I might have Visual Studio Webcasts or courses from my 2000, 2004 and 2008 MSDN Enterprise Subscriptions.
• You can buy Visual Studio Source from Code Jock Suite Pro a Microsoft Partner at Component Source. You also may want to install Bridgeworks from the HP Cache on XP to help port J2EE to .NET Framework from OpenVMS.
• Intsall GitFVFS from GitHub to speed up the cloning and pushing of repositories.
• You can read about the Windows Repo here: VFS for Git: Git at Enterprise Scale
• Windows 10 Enterprise and Education You may want 10 2019 LTSC like me so you'll have until 2029.
• Install Cygwin, the minimium Delev category and the latest JDK from Oracle.
• Clone the Java JDK from Github and install at least the Visual Studio 2019 Build Tools. All Devops projects should be in the _git/OS directory.
• The future GIT structure can be found in the 2005 or 2008 MSDN Library Samples.
• Azure Linux released at Build where Microsoft revealed why it did not fork Fedora

Install on Windows 3.5 Advanced Server, Windows NT 4.0, Back Office Suite or 2003 in a Virtual Machine.

Download the Win32SDK Extract the MDX Microsoft Access 97 file with 7-Zip or open it with Microsoft Access. 
I use Microsoft Access 97.

Install the Windows NT 3.5 DDK. setupddk.bat C:\ddk mips, alpha or i386.

Install the Windows NT 3.5 SDK. setupsdk.bat C:\

Copy the SDK, DDK, MSTOOLS, and MSDEV directory's to the build drive.

run razzle.cmd

set the _NTDRIVE and the apporiate paths

D:\NT-782\NT\private\bldtools\buildall.cmd B1

If you want to build a IDW release execute the following

D:\NT-782\NT\private\bldtools\idwrelease.cmd built;nonbuilt

Install on Windows NT 4.0, Back Office Suite or 2003 in a Virtual Machine.

Install the Windows NT 4.0 DDK. You may have to look for a IDW DDK RC Release.

Install the Windows NT 4.0 SDK.

Install Visual C++ 4.0 w/ MFC Migration Kit.,

Copy the DDK, MSTOOLS, and MSDEV directory's to the build drive.

Use the CAB SDK to make a cabinet file of the Leaked ZIP to make a CD+R of the Cabinet. 
If you are using NT 4.0 use expand.exe to extract the NT source to its location.

Extract the NT.CAB or cabinet file containing full Windows NT 4.0 source in it.

Place the NT Root in the root SDK Directory.

Install the Windows NT 4.0 DDK.

Install the Windows NT 4.0 SDK.

Install Visual C++ 4.0 w/ MFC MIgration Kit.

Copy the MSDEV, DDK, And PlatformSDK directory's to the Build drive and rename the DDK to 'IDWNT4' 

set Path=D:\NT40\MSDEV\bin;D:\NT40\IDWNT4\bin;%path%

set Lib=D:\NT40\MSDEV\lib;D:\NT40\MSTOOLS\lib;%lib%

set Include=D:\NT40\MSDEV\include;D:\NT40\NT\public\sdk\inc;D:\NT40\NT\private\inc;%include%

cd D:\NT40\MSTOOLS\

edit VCVARS32 to set MSDevDir=D:\NT40\MSDEV set vcsource=D:\NT40\MSDEV

run SETENV D:\NT40\MSTOOLS D:\NT40\MSDEV\BIN

cd D:\NT40\IDWNT4\bin

run D:\NT40\IDWNT4\bin\setenv.bat D:\NT40\IDWNT4

build -cz to build the DDK

run razzle.cmd with the 'main' 'hotfix_checked' or 'hotfix_free' argument

In razzle set the _NTDRIVE and the apporiate paths

You can build just a section of NT using B1, B2 or B3 on the command line.
B1 builds from NT\Private.  B2 builds SDKTools and Utils.B3 builds
Setup, Posix, MVDM, WinDbg, and OS2. 

D:\NT40\NT\private\bldtools\buildall.cmd B1

As of this writing 2000 Source is only 33%.

I dont play Black Ops Cold War I'm just not that kind of person.

The top-most branch was called main, which integrated changes from all labs. Under it were several numbered labs, each of which was working on a separate part of Windows, such as:

These labs also had a "_N" branch, which served as a buffer between main and the actual branch. For example, changes from the main branch would first get integrated into Lab06_N before later being integrated into Lab06 in a process called forward integration. The same applied for reverse integration, where the lab would first integrate changes into its N-branch before integrating them into the main branch.

There were also idx (internal development workstation/server) branches, builds from which are usually recompilations intended for TAP/OEM partners. However, they were also occasionally released for public testing, e.g. Windows Longhorn build 4074 or Windows XP build 2257.

Before the release of Windows XP, the main branch was forked into the xpclient branch while the main branch moved on to track Windows Server 2003 development.After the final version was shipped, new branches were created for updates, hotfixes and Service Pack development. Similarly, the dnsrv branch (short for Dot NET Server, i.e. Windows .NET Server) was forked from the main branch before the release of Windows Server 2003.

The lab hierarchy was overhauled after the development reset of Longhorn to address the flaws that plagued most of the pre-reset period. Instead of having a small amount of general virtual build labs each focusing on a different general scope of Windows functionality, a new hierarchical model with considerably more feature branches was introduced, which helped reduce the amount of code to reverse integrate for branch. Microsoft also set stricter criteria for reverse integrating changes from the labs into the main branch, which was now renamed to winmain.

The main branch was later renamed to rsmain at some point after the release of Windows 10, and then to rsmaster after the Windows source repository's conversion to Git, likely to comply with the Git convention of calling the top-most branch the master branch. At some point after February 2021, [2] the branch was renamed back to main. This was likely done in order to follow suit with other Microsoft projects after the master/slave terminology became a subject of controversy in 2020 due to slavery connotations. [3] [4]

Historically, the build lab was a physical room populated with machines that periodically produced mainline builds of Windows NT. At first, there was a single build lab for the entire project that all developers submitted their changes to. As the number of developers grew, the concept of virtual build labs was introduced, where each team developing a subset of the feature set works on its own separate branch and has one or more machines compiling periodic builds of that branch. Each developer submits their changes first to their team's branch, and they are merged to the mainline only after they meet its acceptance criteria. Other teams can then pull the changes from the mainline into their branches.

Builds that were not built by the build lab machines, but are rather compiled by individual Microsoft employees, are called private builds. They are identified by having the VS_FF_PRIVATEBUILD file flag set in the executable's version information and by including the account name of the individual or service that initiated the build in the branch part of the build tag.

Microsoft has used several branching systems since the start of Windows XP development, which differ in the hierarchy of labs as well as in the naming scheme. However, there are some specifics common to most schemes, such as the presence of a top-most main branch, or the use of special branches for important development milestones.

Microsoft Acedemic Program

The Official Build Number of the XP/2003 source is 5.1.2600.6000 is revision 6000 the same as the XP Embedded RTM.

Make a Windows 2000 Advanced Server or Server 2003 or 2003 R2 Virtual Machine with SFU for 2003 and SUA for 2003 R2. Your UNIX source should go in SFU or SUA usr->src directory AT&T System V or SCO V5 or V6 is fine.

If you need to use 'expand /r' to X:\ENGLISH\WIN2003\ENT\I386\* D:\binaries.x86fre from a retail DVD.

1. Set the Signing Certificate

buildnum.exe in sdktools you may have to build it, to get the machine name and build number of the operating system.

certmgr -add D:\NT\tools\testpca.cer -r localMachine -s ca

cd D:\NT

tools\checktestroot.cmd and tools\checktestpca.cmd 

2. Setting Razzle

tools\razzle free offline or tools\razzle win64 amd64 free offline    
or for checked
tools\razzle offline or tools\razzle win64 amd64 offline 

Make a PROJECT_ROOT and a private directory and make one NT project tools\ntnewver.cmd is 
incomplete to complete in production in the NT directory use the Windows Research Kernel in college 
ask the Computer Science Dept. System Administrator. For access.

and a sdktools and make the apporoite directories into a private directory. 
Bring in the sdk and ddk sources into your private directory if you want and start with the 'Begin' project 
Any maybe the VS directory in the sdktools debuggers directory and make a new enlistment or NT Project. 
Next use the source depot templates to set up source depot.

Rename 'projects.map' in the tools directory to 'sd.map' and place in the root of the NT directory.

3. Build or find xcopy and findstr from the RTM DVD and place on path

4. Setting the Path:

path %path%;D:\NT\tools\perl\bin;D:\binaries.x86fre;D:\NT\tools\sp;D:\NT\tools\x86

set sdxroot=D:\NT

enlist projects ex: sdx enlist NT master com -c 
tools\ntnewver.cmd

\\PATSTYLESVS.main.x86.fre

\\%COMPUTERNAME%.main.x86.fre in BuildMachine.txt

We look in BuildMachines.txt for the machine name, branch, architecture,and build type. If we find a match, then we set OFFICIAL_BUILD_MACHINE to the appropriate value ("primary" or "secondary") look for the the offical build machine client in sdktools->debuggers->vs->enlistment->sd.ini.txt.

tools\verifybuildmachine.cmd

perl xcopy2binplace.pl

You can compile the Lab 01 down to about 8 errors the rest of the Labs and Operating System shouldn't have any errors. You should have the research kernel to muck around with also from college, needing to comment out the Longhorn additions in revision 6000, files beginning with 'dp' are Longhorn files. The 'dp' files are not in the 'Longhorn' beta LDK they maybe in a IDW or internal developer workstation release if I can find one. Maybe look in Embedded 2009 for supported hardware and maybe learning what PCI hardware and coding the plug n' play to support in the NT Kernel. The PCI codes you can use now a days in 2024 is Linux and you might want to remove some of the cheap hardware.

Lab01: Kernel

Copy the base\ntos directory and all of it's files to Lab01 it might be a virtual lab 
in source depot and it is a physical lab.

CD to base\busdrv\isapnp and use the message compiler to generate 'message.h'

Make pcicodes.h using the message compiler too. This file goes in base\busdrv\pci

build -cz 

delobj.cmd to clean the source tree

Lab02: Networking

Copy the NT\net directory to Lab02. The Network Stack or Lab will build without error in the Vitrual Lab. 
 You might have issues in the Pysical Lab

build -cz

delobj.cmd to clean the source tree

Lab03: Server[c]

Copy the Entire Server folder from nt5src.7z to Lab03

The entire Server build should build with about 20 shipping errors and take about 6 hrs for a free build and 12 hrs for a checked.

build -cz

delobj.cmd to clean the source tree

Lab04: Terminal Services[1]

Copy NT\termsrv directory to Lab04. The Terminal Services Stack should build without error in the Virtual Lab.
You might have issues in the Physical Lab.

build -cz

delobj.cmd to clean the source tree

Lab05: Shared Source Common Language infustructure

However the Beta Wiki doesn't list a Lab 05 I believe it's either the SSCLI or the COM Stack. 
With the .NET Framework. To build the SSCLI you need Visual Studio 2005 Professional 
or higher in a 2000 or 2003 Virtual Machine. 
Active State Perl ActivePerl-5.16.3.1603-MSWin32-x86-296746.msi ActivePerl-5.16.3.1603-MSWin32-x64-296746.msi

ActivePerl-5.16.3.1603-MSWin32-x64-296746.msi for 64-Bit extract the sscli20_20060311.tgz 
for 2.0 or 1.0 sscli_20021101.tgz sscli_ref_20021101.tgz and and Gyro Genetrics with 1.0 
and execute env.bat at the root of the directory. To set the free or checked 
environment then execute buildall.cmd To build the COM stack run build -cz 
in the root of the COM directory or lab.

Lab06: User interface

Copy NT\shell directory to Lab06. The UI Stack should build without error in the Virtual Lab.
 You might have issues in the Physical Lab. With the GNUmakfile

build -cz

delobj.cmd to clean the source tree

Lab07: Internet Information Services/COM+

Copy NT\inetsrv directory to Lab07. The IIS Stack should build without error in the Virtual Lab.
You might have issues in the Physical Lab.
build -cz

delobj.cmd to clean the source tree

build individual projects

in the directory of a makefile with build -cz

or

build the whole operating system

perl tools\timebuild.pl -NOCLEANBUILD -NOSYNC -NOSCORCH 

perl tools\timebuild.pl -!NOCLEANBUILD -NOSYNC -NOSCORCH  -NOPOSTBUILD

build -cz

make a 'symbol' share with symbol and build subdirectories.

symsrv.cmd

POSTBUILD:

We only create boot floppy images on fre compressed i386 builds.

tools\postbuildscripts\sanitycheckunicodefiles.cmd

Generate the winnt32.msi for different SKUs

tools\postbuildscripts\winnt32msi.cmd

tools\postbuildscripts\makebuildname.cmd

tools\postbuildscripts\cdimage.cmd -d Release

move delobj.cmd the the tools directory to the NT Root and clean the source tree by deleting all the object files. After the build

Close Razzle Window run the VC7 vcvars32.bat from the VCBuilt share and set _NTTREE environment variable. Which is the binaries directory.

path %path%;D:\binaries.x86fre\bldtools

Copy the 'copyddkfiles.cmd' the the NT\base\ddk directory for the tools directory run:

copyddkfiles.cmd ddk_base.ini ddk D:\NT\base

It should begin to copy the ddk files you will need to edit the ddk, hal, IFS INI files to fit your kit needs.

You might want to learn how to make a service pack.

cd to D:\NT\tools\postbuildscripts\svcpack\ and open spcab.cmd and set the FILELIST CABNAME and EVENTNAME using the gold directory
text files as a FILENAME

After the build run the post build batch file in the tools directory and read the error log you shouldn't get any errors in Windows XP/2003 Professional Edition.

certmgr.msc, go to Trusted Root Certification Authorities\Certificates and remove the Microsoft Test Root Authority certificate,
Sign out and Sign in again. The 'For Testing Purposes' Watermark should now be removed.

It takes 6 hours to build a Free Build and 12 hrs a Checked.

Themes

To test the defualt Visual Styles build and execute UXBUD.EXE in the shell->themes directory

Build packthem, cd to the themedir and build 'mallard' read the Powerpoints use Office XP, And Adobe CS2.

Here's is a Mallard Screenshot

After the build the Active Directory Migration Tools and Debugging Tools should be built. After the post build very edition and every supported language should be built. In the binaries directory the usa default build should be revision 6000 leading up to Windows Embedded 2009. After the Windows 6000 revision source build you might want to use the SLD files in the 'mantis' folder with XP embedded and make a Embedded Windows repository and engineer 2003 revision 6000 which was released in Embedded 2009. You can compile the Operating System down to about 16 errors needing to remove the Longhorn additions in revision 6000 maybe look in Embedded 2009 for supported hardware and maybe learning what PCI hardware and coding the plug n' play to support in the NT Kernel. The PCI codes you can use now a days in 2024 is Linux and you might want to remove some of the cheap hardware.

Use the Target Analyzer probes to create a comprehensive list of all hardware devices installed on the device. You can choose from either of the Target Analyzer probes, Ta.exe or Tap.exe. Ta.exe is a real-mode 16-bit application that can be run using Microsoft MS-DOS. Tap.exe is a protected Microsoft Win32-based application that runs on Microsoft Windows XP or Microsoft Windows 2000 Service Pack (SP) 2 OS that supports Plug and Play. Tap.exe produces a more complete and refined hardware list than Ta.exe.

The following list shows the hardware requirements for the Microsoft Windows Preinstallation Environment that is included on the Windows XP Embedded CD 1.

A computer that can boot from an El Torito CD. A Pentium, preferably Pentium II or later, CPU. 128 MB RAM. It is possible that 64 MB will work but it may cause a low memory error if networking is initialized. A display adapter that supports VESA mode video. After you have booted the device, run either Target Analyzer probe program, based on your needs. The Target Analyzer probe creates a file that contains the Plug and Play identifiers for each device installed on the target device. The default name for the .pmq file is Devices.pmq. Copy the device list to your development system

You create a configuration using one of the following two methods:

Using the Target Designer import function. Using Target Designer to manually create a configuration. To import the device list

To create a configuration based on the device list, run Target Designer. The device list is imported as a configuration into the configuration editor.

1. From the File menu, choose Import.
2. In the Choose File for Import dialog box, type the name of the device list, or browse to search for the file.
3. Choose Import.

There are four ways to add a component to a configuration in Target Designer:

From the Configuration menu, choose Add Component. Drag the component from the component browser, and then drop it into the configuration editor. Right-click the component, and then choose Add. Choose the component in the component browser, and then choose Add on the toolbar.

A dependency is a functional relationship between two or more components. Before building your configuration into a run-time image, you should run a dependency check to ensure that all the component dependencies have been resolved.

To check your dependencies, choose the Configuration menu in Target Designer, and then choose Check Dependencies.

If the dependency check encounters components with unresolved dependencies, a task describing the requirement is automatically added to the Tasks list for each unresolved dependency.

You can locate a resolution by opening a task. The database shows only the component or components that can resolve the task. You simply select the check box for a component, and then choose OK.

For example, the following task may appear in the Tasks list:

COM Base [Version 1.0, R1] is dependent upon at least one of component 'RPCSS [Version 1.0, R4]'.

For this example, you would open the task. The task becomes a filter that searches the database for all components that contain the name RPCSS [Version 1.0, R4]. The Resolve Dependency dialog box then displays only the components containing RPCSS in the name.

Continue resolving tasks, closing each task as it is resolved. When all tasks have been resolved, run the dependency check again, because a new component added as a resolution may have other dependencies. Ensure that all dependencies are resolved.

The build process uses the information in a configuration to construct a complete run-time image.

To build the run-time image

1. From the Configuration menu in Target Designer, choose Build Target Image.
2. In the Build type box, select Release. Note Select Release even during development and when you are debugging an application. Select Debug if you are performing a low-level OS debug, such as debugging a device driver.
3. In the Destination box, type the full path where you want to store the new run-time image.
4. In the Log file box, type the full path and file name for the log file.
5. Choose Build.

After you have built your run-time image, you need to prepare your device for image deployment.

The BootPrep tool prepares your device for booting a Windows embedded system. The device must have an active partition that has been formatted and made bootable with a FAT16, FAT 16, or FAT32. The BootPrep tool replaces the partition boot sector code that would typically boot into MS-DOS by loading Io.sys and Msdos.sys with the code that loads the Windows NT loader, called NTLDR.

Note NTFS file systems are not supported by this utility. If you wish to use NTFS file system, you must create your initial file system using one of the FAT file systems and then use the Convert tool provided with Windows XP to convert your file system to the NTFS file system.

After you have prepared your device for deployment, you are ready to deploy the run-time image from your development system to your device.

You can transfer the image using traditional methods such as disk, or bootable CD-ROM. You can also swap a storage device such as a hard disk drive or persistent storage module, such as ROM or flash memory or disk. You can also transfer the image electronically over a communications line.

You can use the deployment tools to transfer, install, and configure the run-time image to your device.

To create an ISO image of the Pre-FBA run-time image Open a command prompt window. For example, from the Start menu, choose Run. In the Run Window, type: cmd

Change to the Windows Embedded\utilities directory. For example:

cd "\Program Files\Windows Embedded\utilities"

Run the hd2iso utility.

Select 1. Create an ISO-9660/El Torito bootable image file. The ISO image menu appears.

Select 2. Select physical drive. The Select physical drive menu appears.

Select the deployment hard disk. For example, select PhysicalDrive1.

Select 3. Select partition(s). The Set partition(s) menu appears.

Select the 650 MB FAT16 partition where the run-time image is located. For example, select Partition 1. Return to the Main menu by typing P.

Select 4. Set image File path. The Image file path menu appears.

Type the full path of where the ISO image file should be created. For example, C:\PreFBA.iso

Select 5. Advanced Options.

Choose 5. Select partition to boot. Select the first bootable partition. Return to the menu by typing P.

Select 6. Create image. The hd2iso utility creates an ISO image based on the contents of the selected partition.

After you have created the ISO image, create a CD-ROM from the ISO image by using CD creation software that supports ISO images. The CD-ROM that you create is the Pre-FBA run-time image CD-ROM.

After you create your CD-ROM, you are ready to boot your run-time image and run the FBA process.

To run FBA, enable EWF, and run ETPrep on your run-time image Copy the run-time image to the deployment hard disk. For example, use Windows Explorer, select the run-time image files in the Windows Embedded Images directory and drag and drop them to the deployment hard disk.

Shut down your system and remove the power cable.

Remove the development hard disk from the system.

Attach the deployment disk to the primary IDE channel as master.

Attach the CD-ROM drive to the secondary IDE channel as master.

Reattach the power cable and power on the system. Insert the Pre-FBA CD-ROM into the CD-ROM drive.

Configure your BIOS to boot from the hard disk.

Boot your run-time image from the deployment hard disk and allow the FBA phase to finish.

During the FBA phase, the system will reboot twice.

To verify that EWF is configured, open a command prompt and run EWF manager. For example, type the following at a command prompt:

ewfmgr

The following sample output is displayed.

Ewf Volume Configuration Volume Size 64512 Segments 0 Segment Size 20 Free segments 0 Max Levels 1 Max Protected Volumes 1 Protected Volumes 1 Overlay volume percent full 0.00 Protected volumes Arc Path "\Device\HarddiskVolume1" [C:]

Verify that EWF is configured to protect the C: drive by typing the following command:

ewfmgr c:

The following sample output is displayed:

Protected Volume Configuration Type RAM State DISABLED Boot Command NO_CMD Param1 0 Param2 0 Persistent Data "" Volume ID D2 02 96 49 00 0E 59 96 02 00 00 00 00 00 00 00 Device Name "\Device\HarddiskVolume1" [C:] Max Levels 1 Clump Size 512 Current Level 1 Disk space used for data 0 bytes Disk space used for mapping 0 bytes Memory used for mapping 0 bytes

If EWF is reporting errors, verify that EWF is configured properly by opening the C:\Windows\FBA\FBALOG.txt file. For more information, see Troubleshooting Enhanced Write Filter.

After you have verified that EWF is properly configured, use the etprep /all command from a command line. This command will delete the EWF volume and configure the run-time image to boot from the CD-ROM drive. For example:

etprep /all

The system will immediately reboot. Do not reboot your post-FBA run-time image. Shut down the system and remove the power cable.

Reattach the Windows Embedded Studio development disk to the system as a master disk on the primary IDE channel.

Reattach the deployment disk to the system as the target disk on the primary IDE channel.

Reattach the power cable and configure the BIOS to boot from the hard disk.

Remove the Pre-FBA CD-ROM from the CD-ROM drive.

Boot the development hard disk.

After your run-time image is properly configured, you are ready to burn it to a bootable CD-ROM.

To create an ISO image of the post-FBA run-time image Open a command line.

Navigate to the Windows Embedded\utilities directory. For example, by typing the following command:

cd "\Program Files\Windows Embedded\utilities"

Run the hd2iso utility by typing:

hd2iso

Select 1. Create an ISO-9660/El Torito bootable image file. The ISO image menu appears.

Select 2. Select physical drive. The Set physical drive menu appears.

Select the deployment hard disk. For example, select PhysicalDrive1.

Select 3. Select partition(s). The Set partition(s) menu appears.

Select the 650 MB FAT16 partition where the run-time image is located. For example, select Partition 1. Return to the Main menu by typing P.

Select 4. Image File path. The Image file path menu appears.

Type the full path of where the ISO image file should be created. For example, C:\PostFBA.iso.

Select 6. Create image. The hd2iso utility creates an ISO image based on the contents of the selected partition.

After create the ISO image, you must create a CD-ROM from the ISO image by using CD creation software that supports ISO images. Simply copying the ISO image to the CD-ROM will not enable it to boot. You should use a third-party CD-ROM burning utility to create a CD-ROM from the ISO image.

The CD-ROM that you create is the Post-FBA run-time image CD-ROM.

Note:
The CD-ROM may appear empty if it is viewed in Windows Explorer. This is because the contents of the bootable CD-ROM are written in a low-level language that Windows Explorer does not recognize.

Your post-FBA CD-ROM is your bootable CD-ROM. You can immediately deploy this CD-ROM on your system.

If the target directory is not empty, Target Designer prompts you to confirm the deletion of the directory.

In a free build the kernel may not build you may have to to use the Windows Research Kernel. Microsoft does not give you the source to WinLogon even in the SSLIP. It's named Winlogon.exe.lc

A build lab (or simply a lab) commonly refers to a Microsoft Windows source code branch. By extension, it can also refer to the team that works on this branch.

Microsoft has used multiple prefixes to refer to feature branches over time:

Setting up a Public Symbol Server

You can use the Symchk tool to check to see if the Symbol file is public or private.

Mono is acedemic .NET Framework

Here are the Windows Build Instructions.

Similarly to the previous system, the main branch is forked off before release to contain update development. The following is the list of known prefixes:

You might want to install the Longhorn Driver Kit or LDK and SDK the Samples from the SDK or in the PDC 2003 Whideby DVD and the SDK Help. Here is a link to the 2003 PDCand PDC 2003 Whideby DVD

In the LDK Samples you might want to start a GIT Repo in the OS directory. Per kind of the Offical Windows Repo here:Microsoft.UI.Xaml v2.1.190405004.2in the Windows Porting Directory and here: You need a login.

git clone https://microsoft.visualstudio.com/os/_git/os 

On Windows 10 you might was to install Scalar

Download the Windows API Code Pack extract it.

You can read about the Windows API Code Pack from the Code Project here

Please refactor with Visual Studio 2017, 2019 on 10 or 2005 in the XP VM,
the namespace 'Microsoft.WindowsAPICodePack' to 'Microsoft.Windows'

Set up a Lab03_N a buffer lab with a "N' NOT A FINAL LAB. with the 7 IDW SDK, IDW DDK, .NET Framework 3.5 Reference Source, 
Symbols and Classic Samples. And it wont be a Final lab until we get more source from the KGB in Russia.

Or Install the 2008 SDK and WDK copy the 6.1 and sdk files to a Lab03_n and take note the the 7 samples directory is really your 'NT' 
directory

and compare both sdk and wdk with directories with windiff and carefully go through the samples and src directories and 
compare and recreate Lab03 save both setenv.bat files and name the apporiate files setenv.sdk and setenv.ddk.

After your done and you set the ddk environment. You can set up the VS Directory with SharpDevelop,  
The Common Compiler Infustructure, Dafney, .NET Framework 3.0 Reference Source,Symbols Windows API Code Pack, 
The Visual Studio Project System and Spec#.

Set up a Lab03_N with the Longhorn LDK, SDK, Longhorn Samples, and the MSDN Library Samples. and Classic Samples.
Use Visual Studio 2008 	MSDN Library Samples to begin a 'Source' Layout. 
For Future Git Version Control. Join USEINIX,and the ACM and try and 
find Vista Microsoft Research Papers.

Acedemia Papers

Here is a VAD Tree acedemic paper

• fbl (feature branch level) - A little story about feature build labs
• vista, longhorn, lh - Windows Vista, Windows Server 2008
• Longhorn requires .NET Framework 1.2 found the redistributable found in the PDC 2003 Discs. Which can be found on the internet archive.
• The Best Operating System Microsoft Never Released (Longhorn Overview)
• You might want to start with the Login Screen demo in the Longhorn SDK Samples.
• win7 - Windows 7, Windows Server 2008 R2
• win8 - Windows 8, Windows Server 2012
• winblue - Windows 8.1, Windows Server 2012 R2

Installing the WDK 8.1 Build Environment in a Lab

I know there were alot of Windows 10 versions but the only dev version that is complete is version 10.0.18362.1

• 19h1 - Windows 10 May 2019 Update, Windows 10 November 2019 Update
• fe (Iron) - Windows Server 2022

Download you Windows Server 2022 SDK & WDK Supscription Only

download the latest perl sources by running lwp-download.bat it he tools/perl directory and build perl.

The future of this paper with cover Windows NT 3.5, NT 4,0 and 2000 with some UNIX Ports.

After all your hard work hope you enjoy this HP Z8 Workstation