Skip to content

Commit

Permalink
First commit of actual content
Browse files Browse the repository at this point in the history
  • Loading branch information
jeffpar committed Oct 18, 2017
1 parent 35043bf commit 9d07a0f
Show file tree
Hide file tree
Showing 56,985 changed files with 5,433,662 additions and 1 deletion.
The diff you're trying to view is too large. We only load the first 3000 changed files.
4 changes: 4 additions & 0 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
.idea/
.DS_Store
node_modules/
kbtxt/
14 changes: 13 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
@@ -1 +1,13 @@
# kbarchive
# Microsoft KnowledgeBase Archive (circa 2002)

This repository contains all the KB content from Microsoft's FTP archive, circa 2002.

It started with a collection of 56,989 TXT files, which were then [converted](scripts/genmd.js) to Markdown files
in anticipation of publishing the content using GitHub Pages. The original TXT files have not been stored in the
repository, since they can be obtained from snapshots of Microsoft's FTP archive elsewhere, and since the Markdown
files are virtually identical, with only minor reformatting of the headers (to make them consistent with the way KB
articles were formatted in the Microsoft Programmer's Library CD-ROMs) and removal of the boilerplate legal notices
(which will be restored prior to publishing, via a page template).

A [log file](scripts/genmd.log) recorded the use of any non-ASCII characters. These haven't been examined yet,
so it's unclear if the files used CP-437, CP-1252, UTF-8, or some other character set.
69 changes: 69 additions & 0 deletions kb/010/Q10022/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,69 @@
---
layout: page
title: "Q10022: OFF97: EPS File Is Not Printed or Is Printed Incorrectly in NT"
permalink: kb/010/Q10022/
---

## Q10022: OFF97: EPS File Is Not Printed or Is Printed Incorrectly in NT

Article: Q10022
Product(s): Word 97 for Windows
Version(s): WINDOWS:97; winnt:4.0
Operating System(s):
Keyword(s): kbprint kbPrinting
Last Modified: 07-SEP-2001

-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft Word 97 for Windows
- Microsoft Excel 97 for Windows
- Microsoft PowerPoint 97 for Windows
- the operating system: Microsoft Windows NT 4.0
-------------------------------------------------------------------------------


SYMPTOMS
========

When you print an Encapsulated PostScript (EPS) file, the file may fail to print
or may be printed incorrectly.

CAUSE
=====

This problem may occur when you print an EPS file under Microsoft Windows NT
version 4.0.

RESOLUTION
==========

To correct this problem, obtain Microsoft Office 97 Service Release 2 (SR-2).

STATUS
======

Microsoft has confirmed this to be a problem in the Microsoft products listed at
the beginning of this article. This problem was corrected in Microsoft Office 97
Service Release 2 (SR-2).

MORE INFORMATION
================

For additional information about SR-2, please see the following article in the
Microsoft Knowledge Base:

Q151261 OFF97: How to Obtain and Install MS Office 97 SR-2


Additional query words: EPS filter print garbled does not is printed

======================================================================
Keywords : kbprint kbPrinting
Technology : kbWordSearch kbExcelSearch kbOSWinSearch kbPowerPtSearch kbWord97 kbWord97Search kbOSWinNT400 kbPowerPt97 kbZNotKeyword2 kbExcel97Search kbPowerPt97Search kbZNotKeyword3 kbOSWinNTSearch kbExcelWinSearch
Version : WINDOWS:97; winnt:4.0
Issue type : kbbug
Solution Type : kbfix

=============================================================================

72 changes: 72 additions & 0 deletions kb/010/Q10212/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,72 @@
---
layout: page
title: "Q10212: INFO: Definition of a Region"
permalink: kb/010/Q10212/
---

## Q10212: INFO: Definition of a Region

Article: Q10212
Product(s): Microsoft Windows Software Development Kit
Version(s): WINDOWS:3.1
Operating System(s):
Keyword(s): kbSDKWin32 kbSDKWin16
Last Modified: 19-JUN-1999

3.00 3.10
WINDOWS
kbprg kbref kbdocerr

-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft Windows Software Development Kit (SDK) 3.1
-------------------------------------------------------------------------------

SUMMARY
=======

The term "region" is used throughout the Windows documentation; however, the
term is not defined. This article explains regions, how they are used, and how a
region is defined or specified.

MORE INFORMATION
================

Unlike most graphics packages that can manipulate only simple geometric
structures (usually rectilinear), The Windows Graphics Device Interface (GDI)
has the unique ability to gather an arbitrary set of spatially coherent points
into a structure called a region, and perform complex yet rapid manipulations
and calculations on such structures. This feature not only makes standard
programs simpler and faster, it also allows operations to be performed that
would otherwise be nearly impossible (for example, it is fundamental to the
implementation of the Windows user interface).

Although most GDI function parameters are given in logical units and then are
converted to device units, region function parameters are given in device
units.

A region is defined by defining lines, shapes (such as rectangles and ellipses),
or other regions. The outline of a region should be one or more closed loops. A
region can be concave or convex, can consist of one area or many disjoint areas,
and can have "holes" in the middle.

Many calculations can be performed on regions. For example, given any two
regions, GDI can find their union, intersection, difference, and exclusive.
There is a set of graphic operations on regions to draw them on the screen.

When a region is selected into a Device Context (DC), a new clipping area is
created. Any graphics sent to that DC will be clipped to the region created.
Regions are defined using CreateRectRgn(), CreateEllipticRgn(), and
CreatePolygonRgn().

Additional query words: 3.00 3.10

======================================================================
Keywords : kbSDKWin32 kbSDKWin16
Technology : kbAudDeveloper kbWin3xSearch kbSDKSearch kbWinSDKSearch kbWinSDK310
Version : WINDOWS:3.1
Issue type : kbinfo

=============================================================================

44 changes: 44 additions & 0 deletions kb/010/Q10213/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,44 @@
---
layout: page
title: "Q10213: INFO: Window Handles of Global Objects"
permalink: kb/010/Q10213/
---

## Q10213: INFO: Window Handles of Global Objects

Article: Q10213
Product(s): Microsoft Windows Software Development Kit
Version(s): WINDOWS:3.0,3.1
Operating System(s):
Keyword(s): kb16bitonly kbSDKPlatform kbGrpDSUser kbWndw
Last Modified: 06-NOV-1999

-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft Windows Software Development Kit (SDK) versions 3.0, 3.1
-------------------------------------------------------------------------------

SUMMARY
=======

A handle is a unique, fixed identifier for a global object. Handles exist to
allow easy, indirect access to an object that may move in memory.

Handles are unique only among the objects to which they refer. A handle to a
window will always be different from all other handles to windows, but it could
have the same value as a handle to a brush (or to any other object).

It is safe to hold onto a window handle (or any handle) of a global object. As
long as that object exists, its handle will not change.

Additional query words:

======================================================================
Keywords : kb16bitonly kbSDKPlatform kbGrpDSUser kbWndw
Technology : kbAudDeveloper kbWin3xSearch kbSDKSearch kbWinSDKSearch kbWinSDK300 kbWinSDK310
Version : WINDOWS:3.0,3.1
Issue type : kbinfo

=============================================================================

50 changes: 50 additions & 0 deletions kb/010/Q10216/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,50 @@
---
layout: page
title: "Q10216: Using EndPaint() and BeginPaint()"
permalink: kb/010/Q10216/
---

## Q10216: Using EndPaint() and BeginPaint()

Article: Q10216
Product(s): Microsoft Windows Software Development Kit
Version(s): WINDOWS:3.0,3.1
Operating System(s):
Keyword(s): kb16bitonly
Last Modified: 06-NOV-1999

-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft Windows Software Development Kit (SDK) versions 3.0, 3.1
-------------------------------------------------------------------------------

SUMMARY
=======

The PAINTSTRUCT structure contains information for an application that can be
used to paint the client area of a window owned by that application.

The PAINTSTRUCT data structure is automatically updated by the BeginPaint()
function; if a window has been restored, BeginPaint() will update the
PAINTSTRUCT fields (for example, fRestore). The application would be duplicating
effort if it also updated the fields of the PAINTSTRUCT after a window is
restored. The EndPaint() procedure is required after BeginPaint(). The
application only needs to be concerned about its own paint procedure that comes
between BeginPaint() and EndPaint().

For additional information on the PAINTSTRUCT data structure, see page 7-55 in
the "Microsoft Windows Software Development Kit Reference Volume 2" for version
3.0 of the Windows SDK, and page 384 in the "Microsoft Windows Software
Development Kit Programmer's Reference, Volume 3: Messages, Structures, and
Macros" for version 3.1 of the Windows SDK.

Additional query words: 3.00 3.10

======================================================================
Keywords : kb16bitonly
Technology : kbAudDeveloper kbWin3xSearch kbSDKSearch kbWinSDKSearch kbWinSDK300 kbWinSDK310
Version : WINDOWS:3.0,3.1

=============================================================================

39 changes: 39 additions & 0 deletions kb/010/Q10220/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,39 @@
---
layout: page
title: "Q10220: Locking Discardable Objects"
permalink: kb/010/Q10220/
---

## Q10220: Locking Discardable Objects

Article: Q10220
Product(s): Microsoft Windows Software Development Kit
Version(s): WINDOWS:3.0,3.1
Operating System(s):
Keyword(s): kb16bitonly
Last Modified: 06-NOV-1999

-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft Windows Software Development Kit (SDK) versions 3.0, 3.1
-------------------------------------------------------------------------------

SUMMARY
=======

It is not possible to put in a call to determine whether an object is discarded.
GlobalLock() returns NULL if the object is discarded. There is no such thing as
a swapped object. Locking a discarded object does not affect its lock count.
Discarded objects always have a lock count of zero. Objects with a nonzero lock
count are never discarded.

Additional query words: 3.00 no32bit 3.10

======================================================================
Keywords : kb16bitonly
Technology : kbAudDeveloper kbWin3xSearch kbSDKSearch kbWinSDKSearch kbWinSDK300 kbWinSDK310
Version : WINDOWS:3.0,3.1

=============================================================================

36 changes: 36 additions & 0 deletions kb/010/Q10462/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
---
layout: page
title: "Q10462: The MASM ASSUME Directive Does Not Generate Code"
permalink: kb/010/Q10462/
---

## Q10462: The MASM ASSUME Directive Does Not Generate Code

Article: Q10462
Product(s): Microsoft Macro Assembler
Version(s): 5.0,5.1,6.0,6.0a,6.0b
Operating System(s):
Keyword(s):
Last Modified: 06-MAY-2001

-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft Macro Assembler (MASM), versions 5.0, 5.1, 6.0, 6.0a, 6.0b
-------------------------------------------------------------------------------

SUMMARY
=======

The ASSUME directive does not generate code, therefore you will not see it
expanded in the listing file, only echoed.

Additional query words: 5.00 5.10 6.00 6.00a 6.00b

======================================================================
Keywords :
Technology : kbMASMsearch kbAudDeveloper kbMASM510 kbMASM600 kbMASM500 kbMASM600a kbMASM600b
Version : :5.0,5.1,6.0,6.0a,6.0b

=============================================================================

Loading

0 comments on commit 9d07a0f

Please sign in to comment.