Project MICA

 MICA was the codename of the operating system developed for the DEC PRISM architecture.[1] MICA was designed by a team at Digital Equipment Corporation led by Dave Cutler.[2] MICA's design was driven by Digital's need to provide a migration path to PRISM for Digital's VAX/VMS customers, as well as allowing PRISM systems to compete in the increasingly important Unix market.[3] MICA attempted to address these requirements by implementing VMS and ULTRIX user interfaces on top of a common kernel that could support the system calls (or "system services" in VMS parlance), libraries and utilities needed for both environments.[4]

MICA was cancelled in 1988 along with the PRISM architecture, before either project was complete. MICA is most notable for inspiring the design of Windows NT.[2] When the PRISM architecture evolved into the DEC Alpha architecture, Digital opted to port OSF/1 and VMS to Alpha instead of reusing MICA.[5]

Design goals

The original goal for MICA was that all applications would have full and interchangeable access to both the VMS and ULTRIX interfaces, and that a user could choose to log in to an ULTRIX or VMS environment, and run any MICA application from either environment.[6] However, it proved to be impossible to provide both full ULTRIX and full VMS compatibility to the same application at the same time, and Digital scrapped this plan in favour of having a separate Unix operating system based on OSF/1 (this was variously referred to as PRISM ULTRIX or OZIX).[7] As a result, MICA would have served as a portable implementation of a VMS-like operating system, with compatible implementations of DCL, RMS, Files-11, VAXclusters, and the VAX/VMS RTLs and system services. Proposals were made for reinstating Unix compatibility in MICA on a per-application basis so that a MICA application could be compiled and linked against the VMS interfaces, or the ULTRIX interfaces, but not both simultaneously.[8]

Due to scheduling concerns, the first PRISM systems would have been delivered with restricted subsets of the full MICA operating system. This included systems such as Cheyenne and Glacier which were dedicated to running specific applications, and where direct interaction with the operating system by customers would be limited.[9]

DEC MICA 

Posted by at

Digital Equipment Corporation

 


"Digital Equipment Corporation (DEC /dɛk/), using the trademark Digital, was a major American company in the computer industry from the 1960s to the 1990s. The company was co-founded by Ken Olsen and Harlan Anderson in 1957. Olsen was president until he was forced to resign in 1992, after the company had gone into precipitous decline.

The company produced many different product lines over its history. It is best known for the work in the minicomputer market starting in the mid-1960s. The company produced a series of machines known as the PDP line, with the PDP-8 and PDP-11 being among the most successful minis in history. Their success was only surpassed by another DEC product, the late-1970s VAX "supermini" systems that were designed to replace the PDP-11. Although a number of competitors had successfully competed with Digital through the 1970s, the VAX cemented the company's place as a leading vendor in the computer space.

As microcomputers improved in the late 1980s, especially with the introduction of RISC-based workstation machines, the performance niche of the minicomputer was rapidly eroded. By the early 1990s, the company was in turmoil as their mini sales collapsed and their attempts to address this by entering the high-end market with machines like the VAX 9000 were market failures. After several attempts to enter the workstation and file server market, the DEC Alpha product line began to make successful inroads in the mid-1990s, but was too late to save the company.

DEC was acquired in June 1998 by Compaq in what was at that time the largest merger in the history of the computer industry. During the purchase, some parts of DEC were sold to other companies; the compiler business and the Hudson Fab were sold to Intel. At the time, Compaq was focused on the enterprise market and had recently purchased several other large vendors. DEC was a major player overseas where Compaq had less presence. However, Compaq had little idea what to do with its acquisitions,[1][2] and soon found itself in financial difficulty of its own. Compaq subsequently merged with Hewlett-Packard (HP) in May 2002"--Taken from Wikipedia

Posted by at
Labels:

Windows Embedded


I started with Platform Builder 3.0 17 CD Disc Set. I made a Windows CE phone in Tennessee. in 1999. I bought Windows XP Embedded in 2004 a MSDN Subscription.and used my system integrator contract to build XP and .NET Server from source and generate project 'mantis' the SDL files in project 'mantis' could be used in Windows Embedded 2009 which is the same revision 6000 as the contract.

Posted by at
Labels:

Jazz Computer

"The Jazz computer architecture is a motherboard and chipset design originally developed by Microsoft for use in developing Windows NT. The design was eventually used as the basis for most MIPS-based Windows NT systems.

In part because Microsoft intended NT to be portable between various microprocessor architectures, the MIPS RISC architecture was chosen for one of the first development platforms for the NT project in the late 1980s/early 1990s. However, around 1990, the existing MIPS-based systems (such as the Turbo channel-equipped DECstation or the SGI Indigo) varied drastically from standard Intel personal computers such as the IBM AT—for example, neither used the ISA bus so common in Intel 386-class machines.

For those and other reasons, Microsoft decided to design their own MIPS-based hardware platform on which to develop NT, which resulted in the Jazz architecture. Later, Microsoft sold this architecture design to the MIPS Computer Systems, Inc. where it became the MIPS Magnum.

The Jazz architecture includes:

This design was simple enough and powerful enough that a majority of Windows NT-capable MIPS systems were based on modified versions of the Jazz architecture. A list of systems which more or less were based on Jazz includes:

The Jazz systems were designed to partially comply with the Advanced RISC Computing (ARC) standard, and each used the ARC firmware to boot Windows NT. Other operating systems were also ported to various Jazz implementations, such as RISC/os to the MIPS Magnum.

There were also some MIPS systems designed to run Windows NT and comply with the ARC standard, but nevertheless were not based on the Jazz platform:

DEC (Digital Equipment Corporation) Manuals 

Berkeley UNIX moves to Walnut Creek  

Walnut Creek Collection 

I had a MIPS SGI Octane with 3dLabs graphics card in 1998 running NetBSD, FreeBSD and Windows NT. I also had a IBM Aptiva. In 2000 I worked on SELinux on the NSA mailing list.

 

Posted by at
Labels:

Hewlwett Packard Operating Environment.


Possibly the Windows Team starts in the Hewlett Packard operating environment for OpenVMS or Digital's Gatekeeper from New Zealand's ftp.zx.net.nz World-Wide Web Server FTP Server, but who are you going to call? 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

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 minimum 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 directory.

Posted by at
Labels:

Global Sustainability

 In 1998 I bought the album 'Yield' By Pearl Jam, the book 'The Road Ahead' By Bill Gates and the book Ishmael by Danial Quinn. In the books including the Story of B and Beyond Civilization. Quinn talks about Population Law and in the Road Ahead Gates talks about finance. In 2003 I wrote congress about a population law to quit fighting wars. In Beyond Civilization Quinn talks about the analogy of living without celebrity.  I'm leaving the autographed 'Ishmael' to Jonathan Shulman in my will for my cousin Anne Hathaway the hollywood actress 5th removed. Proven by Family Tree DNA. Or National Geographic. My uncle Curtis Hathaway went to Robert's funeral. Since 2024 I talk to Anne Hathaway on a weekly basis.

It is money and cash we need to defeater ate about. not all money are liquid assets. I met Quinn in 1999 at UVa my future Alma mater and he signed the book. Which I transferred in straight A's computer literacy and a 3.5 GPA in computer science and 2007 scholar award. Cash and money market are the best liquidity you will ever find as of now. I called the IRS in 2005 and a 1040 is the most you will ever get out of the IRS with schedules in 2018. I became a Royal Society of the Arts Fellow. I was also ACM vice president of the Wise, Va Chapter in college I tested as a INTJ or mastermind at the University of California. There has been a misdiagnoses at the local csb according to Hollins Communications. Which we're are seeking at Microsoft legal with a normal MRI with contrast. Still in review, may take five more years to review. My INTJ profile would receive a take down notice if it were online. With the help of the local Community Service Board.  I pushed for an award to Forbes magazine for how many electronic devices per household about 21. According to China we will never run out of resources how ever it is climate change and we have prolonged the next ice age 100K years according to CNN. Also according to foreign affairs 1984 our society is zero sum. However there is the positive sum strategy and new social rank.theory. "This helps to achieve social cohesion. According to social rank theory, anxiety and depression are natural experiences that are common to all mammalian species. It is the pathological exaggeration of anxiety and depression that contributes to psychological disorders" In sociology.

COCOMO II was approved by the US Dept. of Defense to make source code capital in the 70's My grandfather fought in WWII. In the navy. I was approved for the system integrator program in 2002 under then Microsoft CEO Steve Ballmer. Later Microsoft Bizspark in 2009 and a Academic Grant in 2023. With letters of recommendation from Ballmer and Gates. I've paid Microsoft $30K including internet service over the years and would like Code Center Premium. I've had problems with east coast computer treat actors. I was taught that the top down approach is best; bottom up is more practical, but I don't believe in Linux just FreeBSD as a product. Linus Tervolds can keep Git.

Posted by at
Labels:

Building MS-DOS


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 here 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!

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

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

Posted by at
Labels:

Building Windows 2003

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

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

certmgr -add D:\NT\tools\testpca.cer -r localMachine -s ca
Run tools\checktestroot.cmd and checktestca.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 it copy ntos, and the sdktools 
directory into a private directory. Bring in the sdk and ddk soureces 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
\\%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.
	
    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
    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

    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.

    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.0 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 Vista IDW SDK, IDW DDK and Classic Samples. Join USEINIX, 
and the ACM and try and find Vista Microsoft Research Papers.

    Here is a VAD Tree acedemic paper

Posted by at
Labels: , , ,

Building Windows NT 4.0

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
Posted by at
Labels:

Adding Annunciators to the Taskbar Windows CE 4.2

Adding Annunciators to the Taskbar

If the fill H/PC-like shell is included, Windows CE supports the use of annunciators, icons placed onto the taskbar to indicate user notifications are active. Applications can add, change, and delete an annunciator using the Shell_NotifyIcon function. The following code example shows the prototype for this function.

BOOL Shell_NotifyIcon (DWORD dwMessage, PNOTIFYICONDATA pnid);

The first parameter, dwMessage, specifies the task the function should perform. This parameter can be one of the following three values:

NIM_ADD
This function adds an annunciator to the taskbar.
NIM_DELETE
This function deletes an annunciator from the taskbar.
NIM_MODIFY
This function modifies an existing annunciator on the taskbar.

The other parameter, pnid, points to the NOTIFYICONDATA structure. The following code example shows the structure definition.

typedef struct _NOTIFYICONDATA { 
   DWORD cbSize;
   HWND hWnd; 
   UINT uID; 
   UINT uFlags; 
   UINT uCallbackMessage; 
   HICON hIcon; 
   WCHAR szTip[64]; 
} NOTIFYICONDATA;

The first member, cbSize, contains the structure size, in bytes. The hWnd member specifies the window handle that owns the icon. This window receives messages notifying the window that a user has tapped, double-tapped, or moved a pen on the icon. The uID member identifies the icon being added, deleted, or modified. Assigning a uID to an icon enables an application to have more than one icon on the taskbar. The uFlags member contains flags that identify which of the remaining structure fields contain valid data.

The uCallbackMessage member contains an application-defined message identifier. Windows CE uses the identifier to notify the window specified in hWnd of any user actions on the icon. This value is based on WM_USER so that the message value does not conflict with other messages the window receives. The taskbar looks at uCallbackMessage only if uFlags contains the NIF_MESSAGE flag.

The hIcon member contains a handle to the icon to be displayed on the taskbar. Notification icons must be 16 x 16 pixels. Call the LoadImage function instead of the LoadIcon function to load the icon because LoadIcon does not return a small format icon. The taskbar looks at hIcon only if the NIF_ICON flag is set in uFlags. The last member, szTip, contains ToolTip text to display for the icon.

To effectively manage an annuciator, your application must handle any notification messages the taskbar sends to it. The wParam parameter of the message contains the identifier value of the taskbar icon that the message references. This identifier value is the same identifier defined in the call to the Shell_NotifyIcon function. The lParam parameter contains a code indicating the reason for the message. These values are actually the message codes for various mouse events. For example, if a user taps on a taskbar icon, the lParam value in the notification message will be WM_LBUTTONDOWN, followed by another message containing WM_LBUTTONUP.

 

Posted by at

GDI Support in Windows CE 4.2

 GDI Support

The GDI is the GWES subsystem that controls the display of text and graphics. Use GDI to draw lines, curves, closed figures, text, and bitmap images.

GDI uses a device context to store data that it requires to display text and graphics on a specified device. The graphics objects stored in a device context include a pen for line drawing, a brush for painting and filling, a font for text output, a bitmap for copying or scrolling, a palette for defining the available colors, and a clipping region. Windows CE supports printer device contexts for drawing on printers, display device contexts for drawing on video displays, and memory device contexts for drawing into memory.

The following table shows GDI features supported by Windows CE.

GDI feature
Description
Raster and TrueType fonts TrueType fonts are scalable and rotatable. Seven rasterized system fonts are available in several sizes in ROM. You can also add your own raster fonts. Windows CE supports only one category of font, either raster or TrueType, on a specified system.
Custom color palettes and both palletized and nonpalletized color display devices Supports color bit depths of 1, 2, 4, 8, 16, 24, and 32 bits per pixel (bpp). A bpp depth of 2 is unique to Windows CE.
Bit block transfer functions and raster operation codes Enables you to transform and combine bitmaps
Pens and brushes Supports dashed, wide, and solid pens, patterned brushes
Printing Supports graphics printing
Cursors Supports full use of cursors, including user-defined cursors, or the wait cursor
Shape drawing functions Supports the ellipse, polygon, rectangle, and round rectangle shapes

Windows CE GDI does not support the following features:

  • Transformation functions of coordinate space, such as SetMapMode, GetMapMode, SetViewportExt, and SetWindowExt. Coordinate space is equivalent to device space.
  • World Transform API
  • MoveTo and LineTo functions
  • Color cursors
  • Animated cursors
Posted by at

Application development in Windows CE Toolkit

Application Development

Microsoft provides several toolkits to assist you in developing Windows CE–based applications. These toolkits include the Microsoft® Windows® CE Toolkit for Visual C++® 6.0 and the Microsoft® Windows® CE Toolkit for Visual Basic® 6.0. The toolkits are add-ins to the Microsoft® Visual C++® and Microsoft® Visual Basic® development systems, which means that they use the IDE used to develop desktop applications. Microsoft packages the toolkits along with emulators to enable you to develop applications on a desktop computer.

Windows CE–based devices run different versions of the Windows CE OS and therefore support different toolkits. For example, if you want to use Visual Basic to create an application for an H/PC running Handheld PC Pro Edition software, you need the following products:

  • Microsoft Visual Basic 6.0 development system
  • Microsoft Windows CE Toolkit for Visual Basic 6.0
  • Microsoft Windows CE Platform SDK, Handheld PC Edition, version 2.0

Both the development system and the toolkit are available through standard retail channels; the SDK is distributed on the Windows CE Web site.

The following table shows the toolkits that are available for each platform.

Windows CE–based devices span the home entertainment, vertical device, and PC companion markets. In the home entertainment market, products that run Windows CE include the Sega Dreamcast system, Internet set-top boxes, and Web telephones. In the vertical device market, embedded systems developers provide custom-built computers designed for special tasks, such as package and mail tracking devices, point-of-sale terminals, and navigation devices. In the PC companion market, products that run Windows CE include the H/PC, the Palm-size PC, and the Auto PC.

Each device category supports a different set of APIs. Within each device category, what is supported depends on the version of the OS that the device is built on and what modules and components are included. In addition, each device category contains a unique shell with its supporting APIs. Therefore, a Windows CE–based platform can contain APIs that are not included in the core Windows CE OS.

Additionally, Windows CE differs based on how it is ported to a device. While all H/PCs of a particular version may have the same set of functions, the functions available on a Palm-size PC differ from those on an H/PC. In addition, OEMs have the option of removing optional sections of the OS, so configuration of the OS running on a specific device can vary significantly.

Posted by at

Creating and Terminating a Thread in Windows CE 4.2

 Creating and Terminating a Thread

To create a thread, call the CreateThread function. The following code example shows the CreateThread function prototype.

HANDLE CreateThread(LPSECURITY_ATTRIBUTES lpThreadAttributes,
DWORD dwStackSize, LPTHREAD_START_ROUTINE lpStartAddress,
LPVOID lpParameter, DWORD dwCreationFlags, LPDWORD lpThreadId );

Because Windows CE does not support the lpThreadAttributes and dwStackSize parameters, you must set them to NULL or 0. The following table describes the remaining CreateThread parameters.

Parameter
Description
lpStartAddress Points to the start of the thread routine
lpParameter Specifies an application-defined value that is passed to the thread routine
dwCreationFlags Set to 0 or CREATE_SUSPENDED
lpThreadId Points to a DWORD that receives the new thread's identifier

If CreateThread is successful, it returns the handle to the new thread and the thread identifier. You can also retrieve the thread identifier by calling the GetCurrentThreadId function from within the thread. In Windows CE, the value returned in GetCurrentThreadId is the actual thread handle. You can also retrieve a handle to the thread by calling the GetCurrentThread function. This function returns a pseudo-handle to the thread that is valid only while in the thread. If you specify CREATE_SUSPENDED in the dwCreationFlags parameter, the thread is created in a suspended state and must be resumed with a call to the ResumeThread function.

You can terminate a thread by calling ExitThread, which frees the resources that are used by a thread when they are no longer needed. Calling ExitThread for an application's primary thread causes the application to terminate.

Posted by at

Creating a Process in Windows CE 4.2

 Creating a Process

To start a process from within another process, call the CreateProcess function, which loads a new application into memory and creates a new process with at least one new thread.

The following code example shows the CreateProcess function prototype.

BOOL CreateProcess(LPCTSTR lpApplicationName,
LPTSTR lpCommandLine,
LPSECURITY_ATTRIBUTES lpProcessAttributes,
LPSECURITY_ATTRIBUTES lpThreadAttributes,
BOOL bInheritHandles, DWORD dwCreationFlags, LPVOID lpEnvironment,
LPCTSTR lpCurrentDirectory, LPSTARTUPINFO lpStartupInfo,
LPPROCESS_INFORMATION lpProcessInformation );

Because Windows CE does not support security or current directories and does not handle inheritance, the majority of the parameters must be set to NULL or 0. The following code example shows how the function prototype would look when all nonsupported features are taken into consideration.

BOOL CreateProcess(LPCTSTR lpApplicationName,
LPTSTR lpCommandLine, NULL, NULL, FALSE,
DWORD dwCreationFlags, NULL, NULL, NULL,
LPPROCESS_INFORMATION lpProcessInformation );

The first parameter, lpApplicationName, must contain a pointer to the name of the application to start. Windows CE does not support passing NULL for lpApplicationName and looks for the application in the following directories, in the following order:

  1. The path specified in lpApplicationName, if one is listed.
  2. An OEM-specified search path.
  3. The Windows directory (\Windows).
  4. The root directory in the object store (\).

The lpCommandLine parameter specifies the command line to pass to the new process. The command line must be passed as a Unicode string. The dwCreationFlags parameter specifies the initial state of the process after loading. The following table describes all of the supported flags.

Flag
Description
0 Creates a standard process.
CREATE_SUSPENDED Creates a process with a suspended primary thread.
DEBUG_PROCESS Creates a process to be debugged by the calling process.
DEBUG_ONLY_THIS_PROCESS Creates a process to be debugged by the calling process, but doesn't debug any child processes that are launched by the process being debugged. This flag must be used in conjunction with DEBUG_PROCESS.
CREATE_NEW_CONSOLE Creates a new console.

The last parameter used by CreateProcess is lpProcessInformation. This parameter points to the PROCESS_INFORMATION structure, which contains data about the new process. The parameter can also be set to NULL.

If the process cannot run, CreateProcess returns FALSE. For more information about the failure, call the GetLastError function

Posted by at

Building the F# Compiler Nov 2013 from Microsoft Open Technologies

F# 3.1 Compiler matching Visual Studio 2013  RTM binary release

This directory contains a drop of the source code for an F# 3.1 compiler and core library. The code has been cleaned up "a little" to try to help ensure better stability as more development is done on the codebase.

The compiler is normally compiled as a set of .NET 4.0 components.

Before we start, are sure you're in the right place?

To emphasize, this distribution should not be seen as a way to "get" an F# compiler for immediate use. For that you're better going to fsharp.org.

License: subject to terms and conditions of the Apache License, Version 2.0. A copy of the license can be found in the License.html file at the root of this distribution. By using this source code in any fashion, you are agreeing to be bound by the terms of the Apache License, Version 2.0. You must not remove this notice, or any other, from this software.

Questions? If you have questions about the source code, please ask at the F# Open Source Google Group. Please do not ask the F# team at Microsoft for help with this source code: they like to be friendly, but they are very busy working on improving F# and need to focus on that.

Updates? The F# team do not do active development in open repositories, though some changes such as cleanup or additional tools may be submitted. They aspire to update the code drop when future versions of F# compilers are released from Microsoft, usually at or around the RTM stage.

Copyright: Copyright 2002-2012 (c) Microsoft Corporation.

What do I get when I compile?

When you build the compiler using the standard instructions below, you get fsc.exe, fsi.exe, FSharp.Core.dll, FSharp.Compiler.dll and some related DLLs.

The compiler binaries produced are "private" and strong-named signed with a test key (src\fsharp\test.snk). They use CLI assembly version nunmber 2.9.9.999. You can place these components in the GAC but they will not replace the components used by normal Visual Studio or normal F# programs.

Steps - Building a Proto Compiler 

  cd src 
  gacutil /i ..\lkg\FSharp-2.0.50726.900\bin\FSharp.Core.dll
  msbuild fsharp-proto-build.proj

Note: Make sure you run the .NET 4.0 msbuild.exe, e.g. C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe.

Optional: NGEN the Proto Compiler for faster future startup (optional)

ngen install ..\Proto\net40\bin\fsc-proto.exe

Steps - Building the F# Core Library

This uses the proto compiler to build the FSharp.Core library, for Mono/.NET 4.0.

msbuild fsharp-library-build.proj /p:TargetFramework=net40
msbuild fsharp-library-build.proj /p:TargetFramework=net20

Note: Make sure you run the .NET 4.0 msbuild.exe, e.g. C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe.

Steps - Building the F# Compiler

This uses the proto compiler to build the FSharp.Compiler.dll and fsc.exe to run on for Mono/.NET 4.0.

msbuild fsharp-compiler-build.proj /p:TargetFramework=net40

Note: Make sure you run the .NET 4.0 msbuild.exe, e.g. C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe.

Notes on the build

The prerequisites and build command line for compiling the source (on Windows) are shown later in this README. Here's the logic of the build:

  • We first need an existing F# compiler, using the one in the 'lkg' directory. Let's assume this compiler has an FSharp.Core.dll with version X.
  • We use this compiler to compile the source in this distribution, to produce a "proto" compiler, in the Proto directory. When run, this compiler still relies on the FSharp.Core.dll with version X.
  • We use the proto compiler to compile the source for FSharp.Core.dll in this distribution, producing an FSharp.Core.dll with the version identified in src\source-build-version, usually 1.9.999.
  • We use the proto compiler to compile the source for FSharp.Compiler.dll, fsc.exe, fsi.exe and other binaries found in this distribution. When run, these binaries will rely on the FSharp.Core.dll with version 1.9.999. This is good, since it means the 1.9.999 binaries now form a consistent, bootstrapped compiler. If you like you should now be able to throw away the compiler with version X.

Some additional tools are required to build the compiler, notably fslex.exe, fsyacc.exe, FSharp.PowerPack.Build.Tasks.dll, FsSrGen.exe, FSharp.SRGen.Build.Tasks.dll and the other tools found in the lkg directory. These are "Last Known Good" binaries created from a version of the F# Power Pack on CodePlex. If you like you can throw away these binaries and use your own compiled versions of these. tools.

Use

Here are some simple tests to validate what you have built by checking fsi.exe (F# Interactive) starts up:

ngen install ..\Debug\net40\bin\fsi.exe
..\Debug\net40\bin\fsi.exe
1 + 1;;
#q;;
..\Debug\net40\bin\fsi.exe /help
..\Debug\net40\bin\fsc.exe /help
echo printfn "hello world" > hello.fs
..\Debug\net40\bin\fsc.exe hello.fs
copy ..\Debug\net40\bin\FSharp.Core.dll .
hello.exe
del /q FSharp.Core.dll

Some alternative Steps - Building an optimized (Release) compiler for .NET 4.0 profile

msbuild fsharp-compiler-build.proj /p:TargetFramework=net40 /p:Configuration=Release

ngen install ..\Release\net40\bin\fsi.exe
..\Release\net40\bin\fsi.exe
1 + 1;;
#q;;
..\Release\net40\bin\fsi.exe /help
..\Release\net40\bin\fsc.exe /help
echo printfn "hello world" > hello.fs
..\Release\net40\bin\fsc.exe hello.fs
copy ..\Release\net40\bin\FSharp.Core.dll .
hello.exe
del /q FSharp.Core.dll

 

Posted by at

SCO UNIXWare in a Virtual Machine


 

Posted by at

Building a Windows NT Virtual Machine with a 10 GB Virtual Hard Disk or VHD.

Installing Windows NT into a Virtual Machine

Windows NT 4.0 can be installed in a virtual machine using the standard Windows NT CD.

Note: Some Microsoft Windows NT OEM disks included with new computers are customized for those computers and include device drivers and other utilities specific to the hardware system. Even if you can install this Windows NT operating system on your actual computer, you may not be able to install it in a virtual machine. You may need to purchase a new copy of Windows to install in a virtual machine.

Note: If you are going to run a Windows NT virtual machine with IDE virtual disks on a multiprocessor host computer, you may notice slower than expected disk input/output performance. For more information, see Disk Performance in Windows NT Guests on Multiprocessor Hosts on page 361.

Before installing the operating system, be sure that you have already created a new virtual machine and configured it using the VMware ESX Server Virtual Machine Wizard.

Windows NT Installation Steps

Note: Windows NT 4.0 virtual machines must have Service Pack 4 or higher installed. If your initial installation is from an installation disc that has a lower service pack level, you must first create the virtual machine with less than 3.5GB of RAM. After applying Service Pack 4 or higher, you may use the VMware Management Interface to increase the memory setting to as much as 3.6GB.

To install Windows NT into a virtual machine:

  1. Use the VMware Management Interface to verify the virtual machine’s devices are set up as you expect before starting the installation. For example, if you would like networking software to be installed during the Windows NT installation, be sure the virtual machine’s Ethernet adapter is configured and enabled.

    If you plan to install the guest operating system from a physical CD-ROM disc, be sure the CD-ROM drive is connected to the virtual machine.

  2. Insert the Windows NT CD in the CD-ROM drive on your VMware ESX Server host.
  3. Power on the virtual machine to start installing Windows NT.
  4. If you have enabled the virtual machine’s Ethernet Adapter, a VMware PCI Ethernet Adapter is detected and set up automatically. The default settings should work fine and do not need to be changed.
  5. Finish the Windows NT installation.

VMware Tools

Be sure to install VMware Tools in your in your guest operating system.

Setting up a Windows NT 4.0 Guest with Multiple Disks

To set up a virtual machine running Windows NT 4.0 and using multiple disks, you must first create a virtual machine with only one disk. Install Windows NT on that disk. Then use the Configuration Editor (Settings > Configuration Editor) to add the additional disks.

In addition, note that if you have a Windows NT 4.0 guest with a SCSI virtual disk, you cannot add both an additional SCSI disk and an IDE disk to the configuration.

Enabling Sound After Installing Windows NT

The VMware ESX Server sound device is disabled by default and must be enabled with the Configuration Editor (Settings > Configuration Editor) after the operating system has been installed.

Enabling Networking After Installing Windows NT

If networking was disabled at the time you installed Windows NT, you can enable it after the operating system has been installed.

  1. Shut down Windows NT and power off the virtual machine.
  2. Enable networking for the virtual machine.
  3. Power on the virtual machine.
  4. While Windows NT is booting, insert the Windows NT 4.0 CD in the CD-ROM drive on your VMware ESX Server host.
  5. Log in to Windows NT and open the Network properties page by double-clicking the Network icon in the Control Panel.
  6. Change to the Network Adapters screen by clicking the Adapters tab.
  7. Click the Add button and select AMD PCNET Family Ethernet Adapter from the list.
  8. A message pops up prompting you to enter a path for the Windows NT files. Specify the \I386 directory on the CD in the path you enter (for example, type D:\i386 if the CD is in drive D) and click Continue.
  9. Windows NT setup prompts you for the Windows NT files again. Click Continue.
  10. Use the default adapter settings; they do not need to be changed. Windows NT setup prompts you again for a path to the Windows NT files. Click Continue to finish installing the driver.

Known Issues

On a Linux host with an XFree86 3.x X server, it is best not to run a screen saver in the guest operating system. Guest screen savers that demand a lot of processing power can cause the X server on the host to freeze.         `                                                                        Back to top

© 2001-2002 VMware, Inc. All rights reserved. 

Install or Copy the following

1. Install Windows 4.0 with Inside Windows NT with Helen Custer

2. Install Windows NT 4.0 Embedded

3. Install Windows NT 4.0 Source (From UVa professor with Deans permission because I had straight A's from prep school).

4. Install the Windows NT 4.0 DDK and SDK

5. Install Visual Studio 4.0 

7. Install Office 1997 Professional

12. Install OpenNT

13. Install the MSDN Magazine Archive CDROM.

Only use CDROM capacity 700mb on Windows NT 4.0 because DVD wasn't supported.

https://stuff.mit.edu/afs/sipb/project/vmdialup/archive/i386_linux24.old/lib/vmware-console/help/esx/guestos-winnt.htm 

Posted by at
Labels:

Building a Jazz Computer

The Jazz computer architecture is a motherboard and chipset design originally developed by Microsoft for use in developing Windows NT. The design was eventually used as the basis for most MIPS-based Windows NT systems.

In part because Microsoft intended NT to be portable between various microprocessor architectures, the MIPS RISC architecture was chosen for one of the first development platforms for the NT project in the late 1980s/early 1990s. However, around 1990, the existing MIPS-based systems (such as the TURBOchannel-equipped DECstation or the SGI Indigo) varied drastically from standard Intel personal computers such as the IBM AT—for example, neither used the ISA bus so common in Intel 386-class machines.

For those and other reasons, Microsoft decided to design their own MIPS-based hardware platform on which to develop NT, which resulted in the Jazz architecture. Later, Microsoft sold this architecture design to the MIPS Computer Systems, Inc. where it became the MIPS Magnum.

The Jazz architecture includes:

This design was simple enough and powerful enough that a majority of Windows NT-capable MIPS systems were based on modified versions of the Jazz architecture. A list of systems which more or less were based on Jazz includes:

The Jazz systems were designed to partially comply with the Advanced RISC Computing (ARC) standard, and each used the ARC firmware to boot Windows NT. Other operating systems were also ported to various Jazz implementations, such as RISC/os to the MIPS Magnum.

There were also some MIPS systems designed to run Windows NT and comply with the ARC standard, but nevertheless were not based on the Jazz platform:

https://en.wikipedia.org/wiki/Jazz_(computer) 
Posted by at
Labels:

Making a Windows XP Virtual Machine Using 400GB as the Virtual Hard Disk or VHD.

 Windows XP Home Edition or Professional can be installed in a virtual machine using the corresponding Windows XP distribution CD. If you wish to use sound in the virtual machine, be sure to read Using Sound in a Windows XP Guest Operating System below.

Note: Some Microsoft Windows XP OEM disks included with new computers are customized for those computers and include device drivers and other utilities specific to the hardware system. Even if you can install this Windows XP operating system on your actual computer, you may not be able to install it in a VMware ESX Server virtual machine. You may need to purchase a new copy of Windows to install in a virtual machine.

Note: To use SCSI disks in a Windows XP virtual machine, you need a special SCSI driver available from the download section of the VMware Web site at http://www.vmware.com/download. Follow the instructions on the Web site to use the driver with a fresh installation of Windows XP. If you have a virtual machine with a SCSI virtual disk and a Windows 9x, Windows Me, Windows NT or Windows 2000 guest operating system and want to upgrade it to Windows XP, install the new SCSI driver before upgrading the operating system.

To install Windows XP into a virtual machine:

Note: If you want to run Windows XP Home Edition or Professional in a VMware ESX Server virtual machine, be sure you have a full installation CD for the operating system.

Before installing the operating system, be sure that you have already created a new virtual machine and configured it using the Virtual Machine Wizard.

Follow these steps to install Windows XP into a virtual machine:

  1. Use the Configuration Editor to verify the virtual machine's devices are set up as you expect before starting the installation. For example, if you would like networking software to be installed during the Windows XP installation, be sure the virtual machine's Ethernet adapter is configured and enabled. VMware also recommends that you disable the screen saver on the host system before starting the installation process.
  2. Insert the installation CD in the CD-ROM drive on your VMware ESX Server host.
  3. Power on the virtual machine to start installing the guest operating system.
  4. Follow the installation steps as you would for a physical machine, except as noted in the following steps.
  5. After the system reboots, a message box asks if you want Windows to automatically correct your screen resolution and color depth setting. Do not make the change at this time. You cannot change resolution and color depth until you have installed the VMware SVGA driver - part of the VMware Tools package.
  6. Run the VMware Tools installer. For details, see Using VMware Tools.
  7. When the guest operating system reboots, allow it to change the screen resolution and color depth setting.

Using Sound in a Windows XP Guest Operating System

The VMware ESX Server sound device is disabled by default and must be enabled with the Configuration Editor (Settings > Configuration Editor) after the operating system has been installed.

Note: Your sound card must be working in your host operating system in order to use sound in the virtual machine.

In addition, Windows XP does not automatically detect and install drivers for ISA sound cards, such as the Creative Sound Blaster emulated in a virtual machine. Follow these steps to configure sound in a Windows XP guest operating system.

Known Issues

The Microsoft Windows XP product activation feature creates a numerical key based on the virtual hardware in the virtual machine where it is installed. Changes in the configuration of the virtual machine may require you to reactivate the operating system. There are some steps you can take to minimize the number of significant changes.

  • Set the final memory size for your virtual machine before you activate Windows XP. When you cross certain thresholds — approximately 32MB, 64MB, 128MB, 256MB, 512MB and 1GB — the product activation feature sees the changes as significant.
    Note: The size reported to the Windows product activation feature is slightly less than the actual amount configured for the virtual machine. For example, 128MB is interpreted as falling in the 64MB–127MB range.
  • Install VMware Tools before you activate Windows XP. When the SVGA driver in the VMware Tools package is installed, it activates features in the virtual graphics adapter that make it appear to Windows XP as a new graphics adapter.
  • If you want to experiment with any other aspects of the virtual machine configuration, do so before activating Windows XP. Keep in mind that you have 30 days for experimentation before you have to activate the operating system.

For more details on Windows XP product activation, see the Microsoft Web site.

On a Linux host with an XFree86 3.x X server, it is best not to run a screen saver in the guest operating system. Guest screen savers that demand a lot of processing power can cause the X server on the host to freeze.

The hibernation feature is not supported in this release. Instead of using the guest operating system’s hibernate feature, suspend the virtual machine by clicking Suspend on the VMware ESX Server toolbar.

Back to top

© 2001-2002 VMware, Inc. All rights reserved. 

Install or Copy the following

1. Install Windows XP with Windows Internals 4th ebook

2. Install Windows XP Embedded

3. Install Windows XP/2003 Source (due to incomplete contract it's on the internet archive,       but complete source).

4. Install the Windows 2003 DDK and SDK

5. Install Visual Studio 2003 Academic

6. Install Visual Studio 2005 Professional  

7. Install Office XP Professional

8. Install the Windows Research Kernel Source. With Curriculum Toolkit (from 2009 UVa Wise Sysdmin)

9. Install the Shared Source Common Language Infustructure v 2.0 with ebook (from Shared Source contract 2006)

10. Install SCO OpenServer 5 Source 

11. Install MinWin (from Beta Archive)

12. Install Windows Services for UNIX v 3.0

13. Install the MSDN Magazine Archive CDROM.

14. Make a Longhorn Virtual Machine from the PDC 2003 Discs and remove the time bomb and crack the activation then mount it in the Windows XP VM.

https://stuff.mit.edu/afs/sipb/project/vmdialup/archive/i386_linux24.old/lib/vmware-console/help/esx/guestos-winXP.htm

Posted by at
Labels:

Building Windows XP Datacenter Edition

 


Posted by at

Building SCO on Windows XP

For my latest project I am building Open Server 5 Source on Windows Xp with Windows Services for UNIX 3.0.then finding the Microsoft Partners like Terilk RAD Controls to fill in the gaps.to production in my MSDN Magazine Archive. the Partners are in 'New Stuff' in every month.








Posted by at

Installing OpenStep in a Virtual Machine

 


Posted by at

Building the Longhorn LDK

 


Posted by at

Using Source Depot

 



The above screenshot from my computer shows the NT Codebase ready to ready to be enlisted into source depot you need you International MAP file changed to SD.MAP

Posted by at

Building DOS 1.25


 
 
 
Building MS-DOS 1.25 Beta Archive 

After your done building DOS make a 6.22 Virtual Machine and install Microsoft Fortran and the MKS Toolkit for MS-DOS.
 
 

 

Posted by at
Labels:
Subscribe to: Posts (Atom)