Home
last modified time | relevance | path

Searched refs:Windows (Results 1 – 25 of 377) sorted by relevance

12345678910>>...16

/freebsd/sbin/pfctl/
H A Dpf.os121 # OS - OS genre (Linux, Solaris, Windows)
134 # you don't have a precise match, but can tell it's Windows or FreeBSD
381 # ----------------- Windows -----------------
383 # Windows TCP/IP stack is a mess. For most recent XP, 2000 and
386 # seem. Luckily for us, almost all Windows 9x boxes have an
390 8192:32:1:44:M*: Windows:3.11::Windows 3.11 (Tucows)
391 S44:64:1:64:M*,N,W0,N,N,T0,N,N,S: Windows:95::Windows 95
392 8192:128:1:64:M*,N,W0,N,N,T0,N,N,S: Windows:95:b:Windows 95b
395 # Windows 98 it is no longer possible to tell them from each other
399 S44:32:1:48:M*,N,N,S: Windows:98:lowTTL:Windows 98 (low TTL)
[all …]
/freebsd/crypto/heimdal/doc/
H A Dwin2k.texi4 @node Windows compatibility, Programming with Kerberos, Kerberos 4 issues, Top
6 @chapter Windows compatibility
8 Microsoft Windows, starting from version 2000 (formerly known as Windows NT 5), implements Kerberos…
10 issues between Heimdal and various Windows versions.
12 The big problem with the Kerberos implementation in Windows
20 * Configuring Windows to use a Heimdal KDC::
21 * Inter-Realm keys (trust) between Windows and a Heimdal KDC::
25 * Quirks of Windows 2000 KDC::
26 * Useful links when reading about the Windows::
29 …ode Configuring Windows to use a Heimdal KDC, Inter-Realm keys (trust) between Windows and a Heimd…
[all …]
H A Dheimdal.texi72 * Windows compatibility::
116 Windows compatibility
118 * Configuring Windows to use a Heimdal KDC::
119 * Inter-Realm keys (trust) between Windows and a Heimdal KDC::
123 * Quirks of Windows 2000 KDC::
124 * Useful links when reading about the Windows::
/freebsd/contrib/file/magic/Magdir/
H A Dwindows4 # windows: file(1) magic for Microsoft Windows
7 # using them are run almost always on MS Windows 3.x or
8 # above, or files only used exclusively in Windows OS,
10 # For example, even though WinZIP almost run on Windows
97 # Summary: Windows crash dump
104 # Note: called "Windows memory dump" by TrID
105 # and verified by like Windows Kit `Dumpchk.exe 043022-18703-01.dmp`
110 >4 string DUMP MS Windows 32bit crash dump
172 # Note: called "Windows 64bit Memory Dump" by TrID
174 >4 string DU64 MS Windows 64bit crash dump
[all …]
H A Dmsdos45 # MEXW32:MATLAB Windows 32bit compiled function https://en.wikipedia.org/wiki/MATLAB
46 # MEXW64:MATLAB Windows 64bit compiled function https://en.wikipedia.org/wiki/MATLAB
104 >>>(0x3c.l+0x36) byte 2 for MS Windows
182 # 1~IMAGE_SUBSYSTEM_NATIVE device drivers and native Windows processes
187 >>>0 default x for MS Windows
193 # - NT kernel drivers: Windows/System32/drivers/*.sys
203 # 2~IMAGE_SUBSYSTEM_WINDOWS_GUI The Windows graphical user interface (GUI) subsystem
208 >>>0 default x for MS Windows
226 # 3~IMAGE_SUBSYSTEM_WINDOWS_CUI The Windows character subsystem
231 >>>0 default x for MS Windows
[all …]
H A Dsylk22 # MP~Multiplan, XL~Excel WXL~Excel Windows
28 # Excel, version probably running on Windows
/freebsd/contrib/ncurses/
H A DREADME.MinGW34 works at least on the Windows Console.
48 To build ncurses for native Windows with support for the new Windows 10 Virtual
51 required Windows SDK level. Please note that some of the Linux distributions
53 not be able to properly build the libraries for current Windows 10 using these
54 toolchains. Although it is a bit slow, MSYS2 on Windows 10 64-Bit is the
58 heavily UNIX based sourcebase to native Windows. The goal is of course
60 common traditional development environments on Windows, mainly with
63 The TERM environment variable must be set especially to activate the Windows
67 Beginning with build 17763 (Fall 2018 update), Windows 10 supports ANSI escape
69 Windows 10 version, the interpretation of the implicit TERM setting (which
[all …]
/freebsd/contrib/llvm-project/llvm/lib/Support/Windows/
H A DWatchdog.inc1 //===--- Windows/Watchdog.inc - Windows Watchdog Implementation -*- C++ -*-===//
9 // This file provides the generic Windows implementation of the Watchdog class.
15 // on Windows. Roughly, a Windows implementation would use CreateWaitableTimer
H A DCOM.inc1 //==- llvm/Support/Windows/COM.inc - Windows COM Implementation -*- C++ -*-===//
9 // This file implements the Windows portion of COM support.
14 //=== WARNING: Implementation here must contain only Windows code.
H A DThreading.inc1 //===- Windows/Threading.inc - Win32 Threading Implementation - -*- C++ -*-===//
16 #include "llvm/Support/Windows/WindowsSupport.h"
21 // Windows will at times define MemoryFence.
99 // "Name" is not an inherent property of a thread on Windows. In fact, when
217 // current process to only a single CPU group. On Windows, it is not
298 // After Windows 11 and Windows Server 2022, let the OS do the scheduling,
H A DMemory.inc19 // The Windows.h header must be the last one included.
20 #include "llvm/Support/Windows/WindowsSupport.h"
24 // Contrary to what you might expect, the Windows page protection flags
47 // While we'd be happy to allocate single pages, the Windows allocation
/freebsd/contrib/llvm-project/lld/docs/
H A Dwindows_support.rst14 Windows support
17 LLD supports Windows operating system. When invoked as ``lld-link.exe`` or with
18 ``-flavor link``, the driver for Windows operating system is used to parse
38 :good:`Done`. The format of static library (.lib) on Windows is actually the
47 Windows resource files support
66 The Windows version of LLD is included in the `pre-built binaries of LLVM's
/freebsd/contrib/wpa/wpa_supplicant/
H A DREADME-Windows.txt1 wpa_supplicant for Windows
12 Supplicant on Windows. The current port requires that WinPcap
17 mainly on Windows XP (SP2) with limited set of NDIS drivers. In
18 addition, the current version has been reported to work with Windows
37 cross-compiling from Linux to MinGW/Windows. It should also be
38 possible to build this under Windows using the MinGW tools, but that
124 Using wpa_supplicant for Windows
130 version of wpa_supplicant, wpasvc.exe, which can be used as a Windows
137 Windows NDIS/WinPcap uses quite long interface names, so some care
194 the native build for Windows uses named pipes and the contents of the
[all …]
/freebsd/contrib/libpcap/doc/
H A DREADME.windows.md1 Building libpcap on Windows with Visual Studio
4 Unlike the UN*Xes on which libpcap can capture network traffic, Windows
26 such as a requirement to support versions of Windows earlier than
27 Windows Vista, which is the earliest version supported by Npcap.
50 Building libpcap on Windows requires Visual Studio 2015 or later. The
56 Windows with which those tools, and other tools, can be installed; it
80 runs on UN*Xes and on Windows and that can generate project files for
104 Windows" is installed.
110 expressions. Windows versions of Flex and Bison can be downloaded from
124 provided as an optional installation component, "Git for Windows", with
/freebsd/crypto/openssl/Configurations/platform/Windows/
H A Dcppbuilder.pm1 package platform::Windows::cppbuilder;
5 require platform::Windows::MSVC;
H A DMSVC.pm1 package platform::Windows::MSVC;
9 require platform::Windows;
/freebsd/contrib/sqlite3/
H A DREADME.txt10 Visual C++ on Windows
16 Windows: nmake /f Makefile.msc
48 To compile for Windows using Microsoft Visual C++:
52 Using Microsoft Visual C++ 2005 (or later) is recommended. Several Windows
91 Building for the Windows 10 SDK
/freebsd/contrib/libfido2/
H A DNEWS12 ** Support for linking against OpenSSL on Windows; gh#668.
86 ** Fixed detection of Windows's native webauthn API; gh#382.
91 ** Support for Windows's native webauthn API.
153 ** Hardened Windows build.
217 ** Command-line tools for Windows.
223 ** Windows: fix contents of release file.
229 ** Native HID support on Linux, MacOS, and Windows.
/freebsd/contrib/llvm-project/llvm/include/llvm/BinaryFormat/
H A DMinidumpConstants.def105 HANDLE_MDMP_PLATFORM(0x0000, Win32S) // Win32 on Windows 3.1
106 HANDLE_MDMP_PLATFORM(0x0001, Win32Windows) // Windows 95-98-Me
107 HANDLE_MDMP_PLATFORM(0x0002, Win32NT) // Windows NT, 2000+
108 HANDLE_MDMP_PLATFORM(0x0003, Win32CE) // Windows CE, Windows Mobile, "Handheld"
/freebsd/contrib/unifdef/
H A DINSTALL24 Unlike the Unix Makefile, the Windows builds do not automatically
28 part of GitHub for Windows - http://windows.github.com/
34 as Windows that don't have them built in.
/freebsd/contrib/expat/
H A DChanges23 !! - the Windows binaries topic (needs requirements engineering first), !!
97 #741 Windows: Drop support for Visual Studio <=15.0/2017
207 against static libexpat using pkg-config on Windows
215 #785 CMake|Windows: Fix generation of DLL file version info
331 #597 #599 Windows|CMake: Add missing -DXML_STATIC to test runners
333 #512 #621 Windows|CMake: Render .def file from a template to fix
358 #597 #598 CI: Windows: Start covering MSVC 2022
405 #555 #570 #581 CMake|Windows: Store Expat version in the DLL
512 #554 Windows: Add missing files to the installer to fix
710 #422 #426 #447 Windows
[all...]
/freebsd/crypto/openssl/
H A DNOTES-WINDOWS.md1 Notes for Windows platforms
11 There are various options to build and run OpenSSL on the Windows platforms.
13 "Native" OpenSSL uses the Windows APIs directly at run time.
78 - `perl Configure VC-WIN64-ARM` if you want Windows on Arm (win-arm64)
120 Special notes for Universal Windows Platform builds, aka `VC-*-UWP`
160 * Usually the build is done on Windows in a GNU-like environment called MSYS2.
227 relying on `USER32.DLL`. E.g., on Windows Vista and later you could:
247 Windows subsystem and provides a Bash shell and GNU tools environment.
/freebsd/contrib/lua/src/
H A Dluaconf.h.dist42 ** or Windows-specific features on Windows.
48 ** By default, Lua on Windows use (some) specific Windows features
51 #define LUA_USE_WINDOWS /* enable goodies for regular Windows */
57 #define LUA_USE_C89 /* broadly, Windows is C89 */
125 ** C89 ('long' and 'double'); Windows always has '__int64', so it does
176 ** LUA_EXEC_DIR in a Windows path is replaced by the executable's
197 ** In Windows, any exclamation mark ('!') in the path is replaced by the
243 ** and is not Windows. (On Windows Lua automatically uses "\".)
269 ** For instance, if you want to create one Windows DLL with the core and
546 /* in Windows, can use specific Windows types */
/freebsd/contrib/bc/
H A DREADME.md38 1. Windows 10 or later, or
56 In addition, there is compatibility code to make this `bc` work on Windows.
63 This `bc` should build unmodified on any POSIX-compliant system or on Windows
64 starting with Windows 10 (though earlier versions may work).
69 ### Windows subsection
71 There is no guarantee that this `bc` will work on any version of Windows earlier
72 than Windows 10 (I cannot test on earlier versions), but it is guaranteed to
73 work on Windows 10 at least.
79 supported on Windows: extra math and history enabled, NLS (locale support)
95 On Windows, th
82 `bc``bc`""Build""Windows global() argument
102 `bcl` (Library)`bc`""Build""Windows global() argument
[all...]
/freebsd/share/i18n/csmapper/JIS/
H A DUCS@SIP%JISX0213-1.src26 ## Windows Windows (CP932) mapping

12345678910>>...16