Home
last modified time | relevance | path

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

12345678910>>...17

/freebsd-12-stable/sbin/pfctl/
Dpf.os122 # OS - OS genre (Linux, Solaris, Windows)
135 # you don't have a precise match, but can tell it's Windows or FreeBSD
382 # ----------------- Windows -----------------
384 # Windows TCP/IP stack is a mess. For most recent XP, 2000 and
387 # seem. Luckily for us, almost all Windows 9x boxes have an
391 8192:32:1:44:M*: Windows:3.11::Windows 3.11 (Tucows)
392 S44:64:1:64:M*,N,W0,N,N,T0,N,N,S: Windows:95::Windows 95
393 8192:128:1:64:M*,N,W0,N,N,T0,N,N,S: Windows:95:b:Windows 95b
396 # Windows 98 it is no longer possible to tell them from each other
400 S44:32:1:48:M*,N,N,S: Windows:98:lowTTL:Windows 98 (low TTL)
[all …]
/freebsd-12-stable/crypto/heimdal/doc/
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 …]
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-12-stable/tools/tools/tinybsd/conf/wireless/etc/
Dpf.os120 # OS - OS genre (Linux, Solaris, Windows)
133 # you don't have a precise match, but can tell it's Windows or FreeBSD
334 # ----------------- Windows -----------------
336 # Windows 95 - need more:
338 8192:32:1:44:M*: Windows:95::Windows 95 (low TTL)
340 # Windows 98 - plenty of silly signatures:
341 S44:32:1:48:M*,N,N,S: Windows:98::Windows 98 (low TTL)
342 8192:32:1:48:M*,N,N,S: Windows:98::Windows 98 (low TTL)
344 %8192:64:1:48:M*,N,N,S: Windows:98::Windows 98 (or newer XP/2000 with tweaked TTL)
345 S4:64:1:48:M*,N,N,S: Windows:98::Windows 98
[all …]
/freebsd-12-stable/tools/tools/tinybsd/conf/firewall/etc/
Dpf.os120 # OS - OS genre (Linux, Solaris, Windows)
133 # you don't have a precise match, but can tell it's Windows or FreeBSD
334 # ----------------- Windows -----------------
336 # Windows 95 - need more:
338 8192:32:1:44:M*: Windows:95::Windows 95 (low TTL)
340 # Windows 98 - plenty of silly signatures:
341 S44:32:1:48:M*,N,N,S: Windows:98::Windows 98 (low TTL)
342 8192:32:1:48:M*,N,N,S: Windows:98::Windows 98 (low TTL)
344 %8192:64:1:48:M*,N,N,S: Windows:98::Windows 98 (or newer XP/2000 with tweaked TTL)
345 S4:64:1:48:M*,N,N,S: Windows:98::Windows 98
[all …]
/freebsd-12-stable/contrib/file/magic/Magdir/
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
103 >4 string DUMP MS Windows 32bit crash dump
110 >4 string DU64 MS Windows 64bit crash dump
121 0 string ElfFile\0 MS Windows Vista Event Log
129 # Summary: Windows System Deployment Image
192 # Summary: Windows boot status log BOOTSTAT.DAT
[all …]
Dmsdos35 #0 leshort 0x14c MS Windows COFF Intel 80386 object file
37 0 leshort 0x166 MS Windows COFF MIPS R4000 object file
39 0 leshort 0x184 MS Windows COFF Alpha object file
41 0 leshort 0x268 MS Windows COFF Motorola 68000 object file
43 0 leshort 0x1f0 MS Windows COFF PowerPC object file
45 0 leshort 0x290 MS Windows COFF PA-RISC object file
56 # Windows and later versions of DOS will allow .EXEs to be named with a .COM
77 # drivers in Windows/System32/drivers/*.sys.
104 >>(0x3c.l+92) leshort 9 (Windows CE)
110 >>(0x3c.l+92) leshort 15 (Windows boot application)
[all …]
/freebsd-12-stable/contrib/llvm-project/llvm/lib/Support/Windows/
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
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.
DThreading.inc1 //===- Windows/Threading.inc - Win32 Threading Implementation - -*- C++ -*-===//
16 #include "llvm/Support/Windows/WindowsSupport.h"
21 // Windows will at times define MemoryFence.
106 // "Name" is not an inherent property of a thread on Windows. In fact, when
202 // current process to only a single CPU group. On Windows, it is not
208 // We don't expect more that 4 CPU groups on Windows (256 processors).
/freebsd-12-stable/contrib/ncurses/
DREADME.MinGW33 works at least on the Windows Console.
39 To build ncurses for native Windows, you need the MinGW toolchain. The
40 original MinGW toolchain from the above site is only for 32-Bit Windows. As
41 Windows Server - and also regular workstations - are moving to 64-Bit, it
46 of the gcc toolchain that can compile for native 32- and 64-Bit Windows
53 heavily UNIX based sourcebase to native Windows. The goal is of course
55 common traditional development environments on Windows, mainly with
58 The TERM environment variable must be set specially to active the Windows
63 your MinGW toolchain. For TDM this is usually C:\MinGW64. In your Windows
68 Windows) to create the junction point.
[all …]
/freebsd-12-stable/contrib/apr/
DREADME.cmake1 Experimental cmake-based build support for APR on Microsoft Windows
6 This build support is currently intended only for Microsoft Windows.
7 Only Windows NT-based systems can be targeted. (The traditional
8 Windows build support for APR can target Windows 9x as well.)
14 compatible with the previous Windows build support.
72 MIN_WINDOWS_VER Minimum Windows version supported by this build
108 * Developers need to examine the existing Windows build in great detail and see
/freebsd-12-stable/contrib/llvm-project/lld/docs/
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-12-stable/contrib/apr-util/
DREADME.cmake1 Experimental cmake-based build support for APR-Util on Microsoft Windows
6 This build support is currently intended only for Microsoft Windows.
7 Only Windows NT-based systems can be targeted. (The traditional
8 Windows build support for APR can target Windows 9x as well.)
14 compatible with the previous Windows build support.
135 * Developers need to examine the existing Windows build in great detail and see
/freebsd-12-stable/contrib/wpa/wpa_supplicant/
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-12-stable/contrib/sqlite3/
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-12-stable/contrib/bc/
DREADME.md33 1. Windows 10 or later, or
51 In addition, there is compatibility code to make this `bc` work on Windows.
58 This `bc` should build unmodified on any POSIX-compliant system or on Windows
59 starting with Windows 10 (though earlier versions may work).
64 ### Windows subsection
66 There is no guarantee that this `bc` will work on any version of Windows earlier
67 than Windows 10 (I cannot test on earlier versions), but it is guaranteed to
68 work on Windows 10 at least.
74 supported on Windows: extra math and prompt enabled, history and NLS (locale
106 `bin/dc` by default. On Windows, they are built as `Release/bc/bc.exe` and
[all …]
/freebsd-12-stable/contrib/llvm-project/llvm/include/llvm/BinaryFormat/
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-12-stable/contrib/apr-util/include/private/
Dapu_config.hw18 * Note: This is a Windows specific version of apu_config.hw. It is copied
19 * as apu_config.h at the start of a Windows build.
41 * Windows does not have GDBM, and we always use the bundled (new) Expat
/freebsd-12-stable/contrib/expat/
DChanges56 #597 #599 Windows|CMake: Add missing -DXML_STATIC to test runners
58 #512 #621 Windows|CMake: Render .def file from a template to fix
83 #597 #598 CI: Windows: Start covering MSVC 2022
130 #555 #570 #581 CMake|Windows: Store Expat version in the DLL
237 #554 Windows: Add missing files to the installer to fix
435 #422 #426 #447 Windows: Drop support for Visual Studio <=14.0/2015
436 #434 Windows: CMake: Detect unsupported Visual Studio at
474 #396 Windows: Drop support for Visual Studio <=8.0/2005
475 #409 Windows: Add missing file "Changes" to the installer
497 Windows
[all …]
/freebsd-12-stable/contrib/lua/src/
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 */
77 ** C89 ('long' and 'double'); Windows always has '__int64', so it does
166 ** LUA_EXEC_DIR in a Windows path is replaced by the executable's
186 ** In Windows, any exclamation mark ('!') in the path is replaced by the
219 ** and is not Windows. (On Windows Lua automatically uses "\".)
241 ** For instance, if you want to create one Windows DLL with the core and
572 /* in Windows, can use specific Windows types */
/freebsd-12-stable/contrib/llvm-project/libcxx/include/
D__undef_macros15 "before any Windows header. #undefing min")
27 "before any Windows header. #undefing max")
/freebsd-12-stable/contrib/googletest/
DREADME.md52 * Windows
55 * Windows Mobile
73 …ated test-runner and Graphical User Interface with powerful features for Windows and Linux platfor…
94 Linux, Windows, Mac OS X, and Cygwin. We will also make our best
112 ### Windows Requirements ###
/freebsd-12-stable/contrib/serf/
DCHANGES59 Fix Windows build: Also export functions with capital letters in .def file
61 Ensure less TCP package fragmentation on Windows (r2145)
71 Checksum generation in Windows shared libraries for release builds (2162)
105 Windows: add support for NTLM authentication
116 Fix issue 100: building against an old Windows Platform SDK (r1881)
123 Windows build: dereference INTDIR in serf.mak (r1882)
154 Windows: Fix https connection aborts (r1628..-30,-33,-34,-37)
182 Fixed issue 71: handle ECONNREFUSED on Windows
189 Work around broken WSAPoll() impl on Windows introduced in APR 1.4.0 (r1506)
212 Remove the SERF_DECLARE macros, preferring a .DEF file for Windows
[all …]
/freebsd-12-stable/crypto/openssl/
DINSTALL6 and Windows).
23 * NOTES.WIN (any supported Windows)
94 on Windows (only pick one of the targets for configuration):
110 Windows: C:\Program Files\OpenSSL or C:\Program Files (x86)\OpenSSL
140 the build (note that for Windows, the defaults for --prefix and
141 --openssldir depend in what configuration is used and what Windows
183 be installed. By default this is "lib". Note that on Windows
192 Windows: C:\Program Files\Common Files\SSL
200 Windows: C:\Program Files\OpenSSL
223 On Windows: this is the filename of the zlib library (with or
[all …]

12345678910>>...17