GitHub

Building Windows XP/2003

Jonathan Moore Bio

The founder is Irish, Spanish, Native American and Mediterranean I'm a Moore, Chapman, Little, Vaughn, Turner, Spencer, Lyon, Hathaway, and McCaulley. Jonathan tested as a INTJ-T top 1% personality of the population and Royal Society of the Arts Fellow. Went to Sullins Academy and St Annes Catholic School starting in 1984. Went to Hollins Communications in 1989 in Roanoake Va, right next door the a entertainment law firm. Now Anglican, Computer Science

In compliance with shared source law whe are are taking Microsoft to court at thier own Microsoft Legal with 15 years of customer reciepts. In the following excert of shared source law. "In response to the demands of its customers for access to source code, Microsoft created its shared source licensing program. This program allows Microsoft customers to read and examine certain of the company’s source code."

In High School took AP English and AP Biology and obtained Mosaic the Web Browser. Company Founder made straight A's in College, Made Flash and Ideaworks Vecta 3D active desktop templates and folder views for Windows XP in 2001. A Ivy League College Graduate. and an 3.5 GPA at UVa in 2013 with as Virginia Scholar Award. Was ACM Vice President of the UVa Wise chapter from 2011-2013. And met Harvard's author Steven Pinker at UVa-Wise. He took Geology and Art in Abingdon, Va at VHCC and the credits were never transered to UVa-Wise. He invested in Knuth at a early age and scored low on mathmatical college placement tests, but took High School AP courses. Why? because Knuth is not standerized testing. A letter from President Obama. Since 2015 With intracompany Email from Microsoft Co-Founder Bill Gates and Steve Ballmer and a 20 year Microsoft partner with official Windows 8 Storyboards and fixed variable revenue. Which was featured in MSDN Magazine. And have MFC, COM COM+ Win32 and .NET Framework Projects. And Working on UNIX and OpenVMS Win32 ports. Our business is UX, Virtualization, and Operating System Theory The founder is Windows 7 Internals and Network+ Certified. He was given a referal to St. Paul for hyperacusis in 2018 by Abingdon, Va Ear and throat. He is being discrimminated against by the local community. Even his own family won't take him for the referal. His IQ is 90 tested by Mensa.

Jonathan lives in historic Abingdon, Va. He was given a trust fund by the government. After working and using a few of his fathers work credits to retire. He is a local dissident because he grew up in the 90's and on classified and R-and NC-17 rated hollywood and political material. He is Askanazi Jewish and in Southwest Virginia where there are no synagogues to worship only baptists and catholic churches. He is leaning toward the algelican or orthodox christinaity because of Charles Darwin. He has lost faith in hollywood and Microsoft after 2012. Until their Quantuam Kernel is replaced by the Zenith Kernel in 2035. He is in UK nobility and has seven family UK hereidity titles. Also is American and UK upper class by linage. Working on family trust by putting property and certainty of invention in the trust as shares to have income as dividends. His Working Capital or Net Worth is high and there are lawsuits for unpaid startup salaries dating back to 2011 pending at Microsoft Legal. Our Working Capital Includes Prepaid Expenses: All of the value for expenses paid in advance. Though it may be difficult to liquidate these in the event of needing cash, they still carry short-term value and are included. Cashing out shares converted into the right to receive the Cash Merger Consideration pursuant to this Section 2.02. He wrote his thesis in 2004 on Stanfords webbase and since has become a SEP friend of Stanford and Washington University. Nsquared solutions and SQL server sales 2006-2011. He recieved a Microsoft tender offer in 2006 extended for 75 years an is eligible for company merger.

In 2001 Intel Sponsored my kernel Jonathan wrote for IA-64 its now x86 and being developed for NetBSD and MINIX first. Jonathan is at version 3.2 with redendent OVA backups.

Jonathan's first open source operating system was OpenBSD 2.3 and had a net worth of $500K or over at the age of 24 at Edward Jones Investments. At the time the most secure operating system according the NSA maybe still is.

We are a S corporation with Dunn and Bradstreet. With a Macromedia Patent and Microsoft Tender offer funds with a $28.3 million net worth and working capital $28.3 million. Good for salaries. When my father wants to cut me a small check. I have a net operating income of $800K to buy a second home from family and business expenses on a income statement. We have a extended Microsoft tender offer from 2006. We will use a 1040 Schedule E to report. He also used COCOMO II To value Debian Linux at $5 billion, which is open source. He has been a diagnosed lisp and am a moderate. Through a psychologist used to be right brain dominant now a moderate. We use the Microsoft Loopback Test connector for Microsoft Research's Singularity communication. I have a complete Microsoft research proposal. And benefits from Microsoft's Midori Lawler. And my apply for the payroll protection program.

Jonathan is 45 and has been helping Microsoft with a Dev Drive for Windows 11 through Microsoft Collaborate and Virtual Box he can build Windows XP and 2003 from source as well as SCO's Open Server in XP's Services for UNIX. Microsoft uses UNIX System 7 and BCPL. Microsoft Windows XP is in support in Visual Studio 2019 until 2029 so is the .NET Framework 3.5. There is a difference between .NET and the .NET Framework. We are with Merrill Lynch. We gave a financial gift to the University of Washington in the memory of his parents and for future work with AT&T on UWIN. The AT&T UNIX Subsystem for Windows or MKS Toolkit. We were contracted by VMS Software to port VMS to x86 in their early adopters program. We almost have every version of the Windows SDK's and DDK's with Reference Source from 2009 with the .NET Framework 8.0 with true type source. Windows Research Kernel, Curriculum Kit, Walnut Creek Collection. and Windows Code Pack API. and Spec#

We want to run a PDP-11, the MITS Altair, Macintosh G4, for Visual C++ 4.0 MIPS, and RISC editions and a Jazz Computer. We need MIPS emulation for NetBSD MIPS architecture for symbols. We have TRS-80's with XENIX and Microsot LISP. and HP's We also want to run DEC UNIX. and Intel UNIX. We have the OpenVMS archive which is David Cutler's OpenVMS to NT work. We are IEEE, ACM and USENIX Members. Apple has a rivalry between System V Unix and BSD Unix. We are studying Complex Adaptive Systems at Udemy in a MOOC and want to do business with Redmond's XKL for a TOAD-2. And AVT for VAX emulation. The Founder has submitted his application to Bell Labs as a distinguished academic partner status pending. We have all the software just need the hardware or virtualization. We also have a technical Microsoft case open for Bizspark retail and access to Code Center Premium because of Windows CE access in Bizspark. We have System V source but no current contract with AT&T at the moment.

We've sued the Linux trademark for false open source advertising and poor refactoring at Microsoft Legal. We support Microsoft's One Core Engineering team. In the Windows 10 Driver kit's. In the past we've used Mac's and Windows PC's just with the same userland applications for 25 years Jonathan's family started with a TRS-80 running TRS-DOS and XEINX in 1984 and bought Jonathan a IBM Aptiva with home director in 1995 for high school graduation. We make head nodes that utilize Microsoft's HPC Pack and connect to Microsoft Azure Data Centers for home owners. We are also learning how to use Matlab and VHDL. We may specialize in CapEx and OpEx eventually. Jonathan still invests in nonvolatile stock like bonds and mutual funds with a lot of shares in the funds. And has one M&A shareholders equity exit. We are understanding intangible assets and real estate.

The founder Jonathan has a famous technical case at Microsoft with https://referencesource.microsoft.com/

He has Open Group Sources 1995-present, GNU, Apache and Perl, Micosoft UNIX Licenced Source 1974-2012, SUSE Source Cache, Microsoft Samples 1974-present, And MSDN Magazine Partner Source from Component Source. Microsoft Code Center Priemium, Every Windows SDK and DDK And Visual Sudio 2003, 2005, 2017 Source. Plus Microsoft Research and Code Plex Archive. Macromedia Flash 4 Source now in the Computer History Museum. Adobe Source Libraies Etc, Sauerbraten Cube 2 Source. IRCAM Sources. His Northrup Grumann Mars Rover which he was lead Software Engineer on in college. Was featured in MSDN Magazine for Javascript Essentials which was taken over by Mads. My Company is doing well in with Windows 2000, XP/2003, and 7/2008 R2 HPC. However we do not see a future at Microsoft past Windows 2012 R2 with MKS Toolkit. We did research in Microsoft Research's Barrelfish at UVa in 2011. We are investing in Ubuntu 16.04 LTS until 2026. Windows Server 2003 was released on his birthday. He contributed to the Shared Source Common Langauge Infustructure 1.0 in 2002. The common type system and the PAL. Through several serverity A technical cases. And Finally Thank You to the Royal Society of the Arts for bringing to justice the medical field. 'The Intervening State'.

Sauerbraten: Cube 2

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!

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

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.

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

You might want to download the Single UNIX Specification, and put AT&T System V Source in SFU or SUA and Ultrix from the UNIX Heritage Society Source in DEC FTP Cache. Which maybe VAX or Alpha.

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

Internal Developer Server or Workstation for Windows NT 3.5.

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

Internal Developer Server or Workstation for Windows NT 4.0

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

Internal Developer Server or Workstation for Windows 2000.

As of this writing 2000 Source is only 33%.

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

Whistler and pre-reset Longhorn

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.

Since Longhorn reset

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.

Internal Developer Server or Workstation for Windows Server 2003

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

run buildnum.exe in sdktools you may have to build it, to get the machine name and build numer 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 SDKTool 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. And Active State Perl ActivePerl-5.16.3.1603-MSWin32-x86-296746.msi
 or 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.

<pre>build -cz</pre>
<pre>delobj.cmd to clean the source tree</pre>

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

If you want to wait 6 to 12 hours for a new clean build you'll type this:

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.

The Boot Process for XP/2003 is:

Use Bootsect to write MBR and boot sector.

bootsect /nt52. e:

NTLDR, Ntdetect.com, Ntbootdd.sys, Ntoskrnl.exe, hal.dll, smss.exe, winlogon.exe, Service Contol Manager SCM

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.

Release branch prefixes

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

VFS for Git: Git at Enterprise Scale

Download the Windows API Code Pack extract it.

Download it from my Sharepoint drive

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.

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

Name		Name	Last commit message	Last commit date
Latest commit History 1,122 Commits
app		app
brand		brand
docs		docs
images		images
Computer History.docx		Computer History.docx
Jonathan Chapman Moore FRSA.docx		Jonathan Chapman Moore FRSA.docx
LICENSE		LICENSE
README.md		README.md

License

jonathanlyonmoore/jonathanlyonmoore

Folders and files

Latest commit

History

Repository files navigation

Building Windows XP/2003

Moore's Law

Jonathan Lyon Moore

My Blogs

Websites Hosted on Azure and Github

Infinity

Channel 9

Code Project

Jonathan Moore Bio

Internal Developer Server or Workstation for Windows NT 3.5.

Internal Developer Server or Workstation for Windows NT 4.0

Internal Developer Server or Workstation for Windows 2000.

Whistler and pre-reset Longhorn

Since Longhorn reset

Internal Developer Server or Workstation for Windows Server 2003

Release branch prefixes

Views

About

Topics

Resources

License

Stars

Watchers

Forks

Languages