Инструменты и утилиты для windows

Follow on X!

Some of my programs listed here are written many years ago and some
are new, but most of them are now recompiled with MSVC++ compiler.
Source code repositories for most of the things are available at
Github.

Most of the programs here are compressed into ZIP files. ZIP files
can be uncompressed in Windows XP and Windows Server 2003 but
earlier versions of Windows require a third-party ZIP tool, like the
freeware
7-zip.

Each WorkerNode in a Kubernetes cluster can have a limited number of Pods running, and this limit is determined by three parameters:

• CPU: the total number of requests.cpu cannot be more than the number of CPUs on the Node
• Memory: the total number of requests.memory cannot be more than the Memory on the Node
• IP: the total number of Pods cannot be more than the number of IP addresses in the node

And if the first two are kind of “soft limits” – because we can just do not set requests at all – then the limit by the number of IP addresses on a Node is more a “hard limit”, because each Pod that runs on a Node needs to be given its own address from the Secondary IP pool of its Node.

And the problem here is that these addresses are often used much before the Node runs out of CPU or Memory, and in this case, we find ourselves in a situation where our Node is underutilized, that is, we still could run Pods on it, but we can’t, because there are no free IPs for them.

For example, one of our t3.medium Nodes looks like this:

It has free CPUs, not all memory is requested, but Pods Allocation is already 100% – because only 17 Secondary IPs for Pods can be added to the t3.medium instance type, and they are all already used.

To set the maximum number of Pods on WorkerNodes created by Karpenter, use the maxPods option for NodePool:

...
        - key: karpenter.sh/capacity-type
          operator: In 
          values: ["spot", "on-demand"]
      kubelet:
        maxPods: 110
...

I’m testing that on a test EKS cluster where there is currently only one node for CiritcalAddons, that’s it that regular Pods will not scheduled on it:

$ kk get node
NAME                          STATUS   ROLES    AGE   VERSION
ip-10-0-61-176.ec2.internal   Ready    <none>   2d    v1.28.5-eks-5e0fdde

To check it, let’s create a Deployment with 3 Pods:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: nginx-deployment
  labels:
    app: nginx
spec:
  replicas: 3
  selector:
    matchLabels:
      app: nginx
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - name: nginx
        image: nginx:latest
        ports:
        - containerPort: 80

Deploy it, and Karpenter creates a single NodeClaim with a t3.small instance:

$ kk get nodeclaim
NAME            TYPE       ZONE         NODE   READY   AGE
default-w7g9l   t3.small   us-east-1a          False   3s

A couple of minutes, the Pods are up and running:

Now let’s scale Deployment up to 50 Pods:

$ kk scale deployment nginx-deployment --replicas=50
deployment.apps/nginx-deployment scaled

And we still have one NodeClaim with the same t3.small, but now it has 50 Pods running on it:

Of course, with this approach you should always set Pod requests so that each Pod will have enough CPU and Memory – the requests will now be the limits for the number of Pods on Nodes.

Что такое команда ipcalc в Linux?

Здесь мы определим, как использовать команду ipcalc в Linux и как с ее помощью получить желаемую информацию об IP. Во-первых, давайте отобразим, какую опцию предоставляет нам команда ipcal в Linux с помощью команды –help, а затем мы будем использовать эти опции для получения желаемого вывода. Давайте отобразим параметры команды ipcalc в Linux:

Нажмите Enter, чтобы запустить команду –help. Когда вы попытаетесь выполнить эту команду, вы можете получить следующий вывод:

Поскольку команда ipcalc еще не установлена, ее необходимо установить перед использованием любой связанной с ней команды. Команда «sudo apt install ipcalc» используется для установки команды ipcalc в Linux. Используйте следующую команду:

Если у вас есть система с включенным паролем, она может попросить вас ввести пароль администратора:

Введите пароль администратора, чтобы система могла установить команду ipcalc в Linux. После ввода пароля начнется установка, и система автоматически установит команду ipcalc в Linux. Смотрите результат ниже:

Как видите, команда ipcalc успешно установлена, и теперь система готова выполнять команды, связанные с командой ipcalc. Итак, снова запустите команду –help:

Это отобразит все параметры, доступные для команды ipcal. См. список ниже:

Давайте посмотрим, что мы получим, когда выполним эту команду:

Вот результат подсетей:

Это очень просто, верно?

Давайте посмотрим, какую информацию предоставляют параметры ipcalc. Первый параметр, который мы рассмотрим, — это флаг -s. Флаг -s используется для получения 10 хостов в одной подсети. Давайте используем флаг -s с командой ipcalc:

Нажмите Enter, чтобы запустить эту команду и увидеть результат, аналогичный приведенному ниже:

Как вы можете заметить, запрошенный размер хоста был равен 10, а команда ipcal вычислила подсеть с 10 хостами. Это гораздо больше информации, которую нужно потреблять сразу. Если бы мы могли подавить двоичный вывод, это было бы полезно. Команда ipcalc предоставляет параметр a -b для подавления двоичного вывода. Вот как вы можете этого добиться:

Это должно подавлять двоичный адрес и возвращать только десятичный адрес. Подтвердите результат ниже:

Параметр -r с командой ipcalc обеспечивает следующий вывод:

Теперь давайте отобразим версию команды ipcalc, которую мы использовали до сих пор:

Чтобы узнать версию команды ipcalc, у нас есть опция -v. Просто запустите команду ipcal -v, чтобы отобразить версию команды ipcalc. Вот версия нашей команды ipcalc:

Есть много дополнительных опций, доступных с функциями ipcalc. Все можно перечислить с помощью флага –help. Каждый параметр следует тому же формату, который использовался выше.

Small .NET command line utilities (cross platform)

check which versions and download other frameworks here

can be downloaded here

On this page

• Update history for this page (last update 26 June 2024)
• ImDisk Virtual Disk Driver and Arsenal Image Mounter
• Zero and Random Device Driver
• Small native Windows command line utilities
• 
  
  Small native Windows utilities with graphical user
  interface
  
  
• Small .NET cross-platform command line utilities
• Small .NET Windows utilities with graphical user interface

Amazon VPC Prefix Assignment Mode

For example, we can create a new ENI and assign it a CIDR (Classless Inter-Domain Routing) prefix:

$ aws --profile work ec2 create-network-interface --subnet-id subnet-01de26778bea10395 --ipv4-prefix-count 1

Let’s check this ENI:

The only thing to keep in mind is that VPC Prefix Assignment Mode is only available for instances on the AWS Nitro System – the latest generation of AWS hypervisors that run T3, M5, C5, R5, etc. – See Instances built on the Nitro System.

Small native Windows utilities with
graphical user interface (or with no user interface at all)

32 bit versions are compiled with Microsoft Visual C++ 7 (2003) compiler. They are not linked with the standard C or C++
libraries that comes with this compiler. Instead, most of them are linked
with a dynamic library I call minwcrt (Minimal Windows C Run-Time
Library) linking them to crtdll.dll instead of msvcrt.dll. This
makes them run in all versions of Win32 without additional dll
files. This is also the reason why the exe files are very small.
Source for this library is available as part of the source archive
mentioned in the top of this document. Some other tools are linked to msvcrt.dll to support formatting 64-bit integers and similar features not available in crtdll.dll. This means that some such tools may require updated MS VC++ runtime dll files on Windows NT 3.51, Windows 95 or Win32s.

64 bit versions are compiled with Microsoft Visual C++ 8 (2005) compiler. They are linked to msvcrt.dll and are compatible with all 64 bit Windows versions from Windows XP/Server 2003 and onwards.

ARM versions are compiled with Microsoft Visual C++ 12 (2013) compiler. They are linked to msvcr120.dll which is installed on both Windows RT and Windows 10 IoT editions by default.

ARM64 versions are compiled with Microsoft Visual C++ 14.1 (2017) compiler. They are linked to vcruntime140.dll and related libraries, which are installed with Windows 10 ARM64 editions by default.

• enumwinw.zip – 15,6 KB (32 bit, compiled 2016-02-21)
  Like the utilities in killwin.zip above,
  but this one is a graphical interface tool to view information
  about windows and other graphical objects on the current desktop
  and possibly show, hide, minimize or close them if you want.
  This tool requires Windows NT 4.0 Service Pack 3 or later or
  Windows 95 or later. It is written in Visual Basic 6 so if it
  does not work you probably don’t have the VB run-time
  environment installed. You can get it here.
• fsplitw.zip – 12,8 KB (32 bit, compiled 2018-12-18)
  fsplitw64.zip – 13,8 KB (64 bit, compiled 2018-11-26)
  fsplitw.zip – 14,9 KB (ARM64, compiled 2018-11-26)
  Splits a big file into smaller part files
  of specified size. Useful to split a large file to many floppies
  or CD:s. The file parts can be restored to the large file again
  using the copy /b command at the command line, like copy /b
  part1+part2+part3 bigfile. This is an old tool originally developed around 1998. Please be aware that there might be certain limitations in functionality, particularly when used on modern Windows versions.
• gethostw.zip – 10,1 KB (32 bit, compiled 2024-06-26)
  gethostw64.zip – 10,6 KB (64 bit, compiled 2024-06-16)
  gethostw.zip – 13,0 KB (ARM64, compiled 2024-06-16)
  Like gethost.zip above, but displays the
  information in a dialog box instead, making it compatible with
  Win32s on Windows 3.x (or good if you don’t like the console
  anyway…).
• logonwrap.zip – 10,0 KB (32 bit, compiled 2024-06-26)
  logonwrap64.zip – 10,5 KB (64 bit, compiled 2024-06-16)
  logonwrap.zip – 12,6 KB (ARM64, compiled 2024-06-16)
  Runs the application specified on command
  line and waits for it to terminate and then logs out the user
  session. Particularly useful on Terminal Servers in cases where
  you want only one single application to run when user logs on
  and make sure the session is closed properly when that
  application is terminated.
• logout.zip – 10,5 KB (32 bit, compiled 2024-06-26)
  logout64.zip – 10,9 KB (64 bit, compiled 2024-06-16)
  logout.zip – 13,2 KB (ARM64, compiled 2024-06-16)
  Command line interface for the
  ExitWindowsEx() API function. Useful to log out the current user
  or shutdown or restart the system in the way you want.
• regrepl.zip – 11,7 KB (32 bit, compiled 2016-02-21)
  regrepl64.zip – 13,3 KB (64 bit, compiled 2016-02-21)
  regrepl.zip – 15,2 KB (ARM64, compiled 2018-11-26)
  Registry Replace Tool. This program is useful
  if you have missed a “replace all”-function in the Registry
  Editor. The new version also supports remote operation on other
  computers on the network and selecting subkey where the search
  and replace should start. It supports replacing Ansi and Unicode
  texts in REG_SZ, REG_MULTI_SZ, REG_EXPAND_SZ and REG_BINARY type
  registry values. Download screenshot here (9,4 KB). This is an old tool originally developed around 1998. Please be aware that there might be certain limitations in functionality, particularly when used on modern Windows versions.
• tickcntw.zip – 9,9 KB (32 bit, compiled 2024-06-26)
  tickcntw64.zip – 9,9 KB (64 bit, compiled 2024-06-16)
  tickcntw.zip – 12,5 KB (ARM64, compiled 2024-06-16)
  Displays a dialog box with information
  about how long the system has been up. (Weeks, days, hours,
  minutes, seconds and milliseconds.)
• w32ver.zip – 18,8 KB (32 bit, compiled 2021-08-28)
  w32ver64.zip – 19,6 KB (64 bit, compiled 2021-08-28)
  w32ver.zip – 11,5 KB (ARM32, compiled 2021-08-28)
  w32ver.zip – 12,7 KB (ARM64, compiled 2021-06-28)
  Displays the current version number, build
  number and service pack level for the current Win32 environment.
  w32verc.exe displays the information in the console window and
  w32ver.exe displays it in a dialog box making it compatible with
  Win32s on Windows 3.x. Displays correct version numbers up to Windows 10.
• winlogoncfg.zip – 23,3 KB (32 bit, compiled 2016-02-21)
  winlogoncfg64.zip – 25,3 KB (64 bit, compiled 2016-02-21)
  winlogoncfg.zip – 16,1 KB (ARM64, compiled 2018-11-26)
  A small utility
  to view and change settings for the Winlogon process. This
  includes settings up
  auto
  logon
  feature,
  logon
  dialog
  options and settings for Windows File Protection.
  Operates on local and remote computers. Tested on Windows NT 3.51/4.0,
  2000, XP or Server 2003. A help file with some how-to
  instructions is included.
  Download screenshot
  here (21,3 KB)
  . Limited functionality on later versions of Windows.

Activating VPC CNI Prefix Assignment Mode in AWS EKS

Documentation – Increase the number of available IP addresses for your Amazon EC2 nodes.

All you need to do is to change the value of the ENABLE_PREFIX_DELEGATION variable in the aws-node DaemonSet:

$ kubectl set env daemonset aws-node -n kube-system ENABLE_PREFIX_DELEGATION=true

When using the terraform-aws-modules/eks/aws Terraform module, this can be done through configuration_values for the vpc-cni AddOn:

...
module "eks" {
  ...
  cluster_addons = {
    coredns = {
      most_recent = true
    }
    kube-proxy = {
      most_recent = true
    }
    vpc-cni = {
      most_recent    = true
      before_compute = true
      configuration_values = jsonencode({
        env = {
          ENABLE_PREFIX_DELEGATION = "true"
          WARM_PREFIX_TARGET       = "1"
        }
      })
    }
  }
...

$ kubectl describe daemonset aws-node -n kube-system
...
    Environment:
      ...
      VPC_ID:                                 vpc-0fbaffe234c0d81ea
      WARM_ENI_TARGET:                        1
      WARM_PREFIX_TARGET:                     1
...

When using AWS Managed NodeGroups, the new limit will be set automatically.

In general, the maximum number of Pods will depend on the type of instance and the number of vCPUs on it – 110 pods for every 10 cores (see Kubernetes scalability thresholds). But there are also limits that are set by AWS itself.

For example, for a t3.nano with 2 vCPUs, this will be 34 Pods – let’s check it with the max-pod-calculator.sh script:

$ ./max-pods-calculator.sh --instance-type t3.nano --cni-version 1.9.0 --cni-prefix-delegation-enabled
34

On a c5.4xlarge with 16 vCPUs, it took 110 Pods:

$ ./max-pods-calculator.sh --instance-type c5.4xlarge --cni-version 1.9.0 --cni-prefix-delegation-enabled 
110

And on the c5.24xlarge with 96 cores it will be 250 Pods, because this is already a limit from AWS:

$ ./max-pods-calculator.sh --instance-type c5.24xlarge --cni-version 1.9.0 --cni-prefix-delegation-enabled
250

Small native Windows command line utilities

32 bit versions are compiled with Microsoft Visual C++ 7 (2003) compiler. They are not linked with the standard C or C++
libraries that comes with this compiler. Instead, most of them are linked
with a dynamic library I call minwcrt (Minimal Windows C Run-Time
Library) linking them to crtdll.dll instead of msvcrt.dll. This
makes them run in all versions of Win32 without additional dll
files. This is also the reason why the exe files are very small.
Source for this library is available as part of the source archive
mentioned in the top of this document. Some other tools are linked to msvcrt.dll to support formatting 64-bit integers and similar features not available in crtdll.dll. This means that some such tools may require updated MS VC++ runtime dll files on Windows NT 3.51, Windows 95 or Win32s.

64 bit versions are compiled with Microsoft Visual C++ 8 (2005) compiler. They are linked to msvcrt.dll and are compatible with all x86-64 (previously known as AMD64) Windows versions from Windows XP/Server 2003 and onwards.

ARM versions are compiled with Microsoft Visual C++ 12 (2013) compiler. They are linked to msvcr120.dll which is installed on both Windows RT and Windows 10 IoT editions by default.

ARM64 versions are compiled with Microsoft Visual C++ 14.1 (2017) compiler. You need Visual C++ Redistributable package to run these versions. It is available
here.

Big ZIP files with compiled stand-alone exe-files for most of the utilities
listed here and some more:

Zip archive with 32 bit exe files (1,8 MB)

7-zip archive with 32 bit exe files (520,5 KB)

Zip archive with 64 bit exe files (1,9 MB)

7-zip archive with 64 bit exe files (526,9 KB)

Zip archive with ARM exe files (2,1 MB)

7-zip archive with ARM exe files (517,6 KB)

Zip archive with ARM64 exe files (2,2 MB)

7-zip archive with ARM64 exe files (482,6 KB)

Subnet CIDR reservations

Documentation – Subnet CIDR reservations.

$ ipcalc 10.0.24.0/21 /28
...
Subnets:   128
Hosts:     1792

CIDR /28

Each IPv4 address consists of 32 bits divided into 4 octets (groups of 8 bits). These bits can be represented in binary (0 or 1) or in decimal (values between 0 and 255 for each octet). We will use 0 and 1 here.

The subnet mask /28 indicates that the first 28 bits of the IP address are reserved for the network identification – then 4 bits (32 total minus 28 reserved) remain to identify individual hosts in the network:

Knowing that we have 4 free bits, and each bit can have a value of 0 or 1, we can calculate the total number of combinations: 2 to the power of 4, or 16 – that is, there can be a total of 16 addresses in the /28 network, including both the network address (the first IP) and the broadcast address (the last IP), so there will be 14 addresses available for hosts.

So instead of connecting one Secondary IP to ENI, we connect 16 at once.

Here it is easier to use utilities like ipcalc.

$ ipcalc 10.0.16.0/20 /28
...
Subnets:   256
Hosts:     3584

Or you can use an online calculator – ipcalc.

Voluntary payments for use of downloaded software

Programs listed here are free to
download and use. To make it possible to continue with this and
pay for web site, software signing certificates and other costs you are more than welcome to
pay a voluntary usage “fee”. For information about
possible ways to pay, please follow this link.

Ads from Google. Not
about my products, but might be of interest:

Small .NET tools with graphical user interface (Windows only)

check which versions and download other frameworks here

• Dataviewer.zip – 43,6 KB (.NET Framework 2.0, compiled 2024-05-15)
  Dataviewer.zip – 43,7 KB (.NET Framework 4.0, compiled 2024-05-15)
  Dataviewer.zip – 1,5 MB (.NET 6.0-windows, compiled 2024-05-15)
  Dataviewer.zip – 1,0 MB (.NET 8.0-windows, compiled 2024-05-15)
  A small utility to make ODBC connections and send
  SQL queries. It shows the returned data in an updateable
  DataGridView so it can be used to edit data through any
  ODBC-compatible database connection.
• GraphViewer.zip – 201,9 KB (.NET Framework 3.5, compiled 2024-05-15)
  GraphViewer.zip – 220,1 KB (.NET Framework 4.0, compiled 2024-05-15)
  GraphViewer.zip – 622,7 KB (.NET 6.0-windows, compiled 2024-05-15)
  A math application to view graphs of functions. It
  can also calculate and draw derivative and anti-derivative
  graphs. The graphs can also be saved to a file or printed on
  paper.
  Download
  screenshot here (22,6 KB)
  . This is an updated version that
  uses .NET compiler instead of ScriptControl object which should
  gain performance. There is also an online web version of this application here.
• PictureOnMap.zip – 369,2 KB (.NET Framework 4.6, compiled 2023-10-19)
  PictureOnMap.zip – 604,3 KB (.NET 6.0-windows, compiled 2023-10-19)
  Adds context menu options to jpeg files to open map apps and show where the photo was taken.
• QuickBrowser.zip – 7,6 KB (.NET Framework 2.0, compiled 2023-10-20)
  QuickBrowser.zip – 7,7 KB (.NET Framework 4.0, compiled 2023-10-20)
  QuickBrowser.zip – 13,3 KB (.NET 6.0-windows, compiled 2023-10-20)
  A small window application that encapsulates Internet Explorer WebBrowser control. It can be used as a very lightweight application for browsing web pages.

Back to LTR Data homepage

This site does not use cookies for providing any features or functions. However, ads from Google and third-party ad networks on this site may use cookies to show personalized ads. More information here.

Maximum Secondary IP on AWS EC2

The number of additional (secondary) IPs on EC2 depends on the number of ENI (Elastic network Interface) and the number of IPs per interface, and these parameters depend on the type of EC2.

For example, t3.medium can have 3 interfaces, and each interface can have up to 6 IPs (see IP addresses per network interface per instance type):

That is, a total of 18 addresses, but minus 1 Private IP of the ENI instance itself, and 17 addresses will be available for Pods on such a Node.

Click here
for update history for this page (last update 26 June 2024)

All file dates are in ISO date format, YYYY-MM-DD.
This makes the list easier to sort.

VPC Prefix та AWS EKS VPC CNI

What’s next? How do we get a separate address for the Pod we are running in Kubernetes from this pool of addresses?

This is done by the VPC Container Networking Interface (CNI) Plugin, which consists of two main components:

• L-IPAM daemon (IPAMD): responsible for creating and connecting ENI to EC2 instances, assigning address blocks to these interfaces, and “warming up” IP prefixes to speed up Pods launch (we’ll talk about this in the WARM_PREFIX_TARGET, WARM_IP_TARGET and MINIMUM_IP_TARGET part)
• CNI plugin: is responsible for configuring network interfaces on the node – both ethernet and virtual, and communicates with IPAMD via RPC (Remote Procedure Call)

How exactly this is implemented is perfectly described in the Amazon VPC CNI plugin increases pods per node limits > How it works blog:

So the process looks like this:

1. Kubernetes Pod at startup makes a request to the IPAMD for an IP allocation
2. IPAMD checks the available addresses, if there are free addresses, it allocates one for the Pod
3. if there are no free addresses in the prefixes connected to ES2, then IPAMD makes a request to connect a new prefix to the ENI
   1. if a new prefix cannot be added to the existing ENI – a request is made to connect a new ENI
      1. if the Node already has the maximum number of ENIs, then the Pod’s request for the new IP is failed
   2. if a new prefix is added (to an existing or new ENI), then the IP for the Pod is selected from it

Please note!

The applications and tools provided at this web site are intended for system administration, backup and recovery operations, research, forensics investigations and similar tasks and for legitimate lawful purposes only. There is no malware, spyware or any similar things spread through the software and the software will not make hidden modifications to user’s operating system or environment without user specifically asking for it using command line options, user interface provided options or similar. There are no hidden features for spying on users such as reporting usage information or any other private information back to any other place.

The applications are not tested in all possible
environments. Neither authors nor distributors should be held responsible for what the
applications actually do when they are used.

This site does not use cookies for providing any features or functions. However, ads from Google on this site may use cookies.
More information here.

ImDisk Virtual Disk Driver

Current version 2.1.1 built 23 December 2022 packaged 07 November 2021

An additional driver, awealloc, in this install package supports memory
allocation beyond 4 GB limit on 32 bit Windows through address window extension,
AWE.

The
ImDisk driver supports forwarding I/O requests to third-party image file format
handlers or to services on other
computers on the network. This makes it possible to boot a machine
with NTFS partitions with a Live-CD and use the included 
tool to let
on another computer
running Windows on the network mount the NTFS partition on the
machine with a faulty NTFS partition. This way you can recover information and
even run chkdsk on drives on machines where Windows does not boot. There are also instructions about how to use
under Windows on
Claus Valca’s blog.

• Download screenshot
  – 43,5 KB
• Download ImDisk install package, current stable version 2.1.1 packaged 07 November 2021 – 640,8 KB, works on both 32-bit and
  64-bit versions of Windows. Security Notice: Always download setup packages to a new empty directory. To run a setup package from a directory with other unrelated files could be dangerous!
• Download ImDisk install files for current stable version as a zip file built 23 December 2022 – 1,1 MB.
• Download ImDisk install package, previous stable version 2.0.10 – 561,3 KB
• Download devio tool for FreeBSD x86 built 22 January 2019 – 9,9 KB.
• Download devio tool for FreeBSD x64 built 22 January 2019 – 14,5 KB.
• Download devio tool for Linux x86 built 22 January 2019 – 11,0 KB.
• Download devio tool for Linux x64 built 22 January 2019 – 10,4 KB.
• Download devio tool for Windows x86 built 19 November 2018 – 10,7 KB.
• Download devio tool for Windows x64 built 18 November 2018 – 21,6 KB.
• Download devio tool for Windows ARM built 18 November 2018 – 19,8 KB.
• Download devio tool for Windows ARM64 built 30 October 2021 – 21,4 KB.

About the install package

Compatibility

ImDisk Virtual Disk Driver is designed to be a small, simple and yet powerful virtual disk driver. It runs on very old versions of Windows NT as well as modern Windows versions. However, because of this compatibility design and because it emulates disk volumes rather than complete disks, it is not always compatible with all applications and drivers. For instance, you cannot manage things like mount points, drive letters and similar for ImDisk drives using mountvol command line tool or in Disk Management in Windows. As another example, you cannot create or access shadow copies on ImDisk drives. So, applications that use similar Windows features as Disk Management dialog to enumerate disks and disk volumes to find disk properties like sector sizes and similar, might possibly not work as expected with ImDisk drives.

Arsenal Image Mounter – If you need full disk emulation support

Questions?

Reboot.pro

Answers to frequently asked questions are

collected in this thread

ImDisk Toolkit

download here

Reviewed by Tekzilla

There is a Tekzilla review of ImDisk Toolkit on Youtube:

5/5 star rating and certified free from virus and malware by several freeware download sites.

CPU architecture compatibility

Driver files are digitally
signed with a certificate trusted by Microsoft.

Special note for Windows NT 3.51

Source code

Source code for all of ImDisk Virtual Disk Driver,
including the devio server-side tool, API libraries etc is available as a Github repository. Different parts of the source tree are built in different environments:

• The Windows drivers, command line tool and Control Panel applet parts of the source code are built with WDK 7.1.0. There is a Makefile in the source tree root that builds imdisk.sys, awealloc.sys, imdisk.cpl, imdisk.exe and imdsksvc.exe when ran with nmake in WDK 7.1.0 command prompts.
• The devio server side tool used with ImDisk clients in proxy mode, can be built with most *nix C++ compilers like gcc and similar. It can also be built in most Visual Studio/C++ command prompts. In all cases the devio binary you get supports listening for a tcp/ip connection and serving either a raw image file or a Microsoft vhd image file and parsing MBR partition tables to find offsets and sizes. When built with Visual Studio/C++ compilers, you will get a devio.exe that also supports listening for shared memory connections, the –dll switch to load custom dlls for accessing custom image file formats and features for auto-finding sizes of a physical devices.
• The .NET library located in ImDiskNet subdirectory can be built using Visual Studio 2017 or higher or any recent version of .NET SDK.
• There is also a Visual Studio solution with some project files for the driver, Control Panel applet, imdisk.exe and devio.exe. It is particularly useful to build for architectures not supported by the old WDK 7.1.0 environment, such as arm and arm64.

API

There is also a .NET application, DiscUtilsDevio, that combines image file format support in DiscUtils libraries with ImDisk.

License

This means that if you modify the code and/or include it in and/or redistribute it along with your own product, all of the modified/integrated/redistributed product that you distribute needs to be redistributed under GPL, including source code. If you wish to avoid GPL requirements, such as the need to redistribute source code, you would therefore need to remove all floppy emulation related code from the driver. I
will be happy to do such modifications for you to make the code comply with your license requirements. Just send me an e-mail!

Zero and Random device driver – updated
10 September 2021

Beginning with version 1.1.0.3 different versions are installed on different versions of Windows. On Vista and later, random numbers are generated by system cryptographic random number generator. On earlier versions random numbers are generated by
RtlRandom or
RtlRandomEx API functions with a time based seed.

The install package installs the driver and loads it into the kernel
and setup for automatic load when Windows starts up. The driver can
be uninstalled using Add/Remove programs applet in the Control
Panel.

• Download the install package
  – 172,9 KB. Works on both 32-bit and 64-bit versions of Windows. Security Notice: Always download setup packages to a new empty directory. To run a setup package from a directory with other unrelated files could be dangerous!

About the install package

Drivers are now digitally signed with a certificate
trusted by Microsoft.

Special note for Windows NT 3.51

Source code

GitHub

, WARM_IP_TARGET and MINIMUM_IP_TARGET

See WARM_PREFIX_TARGET, WARM_IP_TARGET and MINIMUM_IP_TARGET.

To configure the allocation of prefixes to Nodes and IPs of VPCs, CNI has three additional options – WARM_PREFIX_TARGET, WARM_IP_TARGET, and MINIMUM_IP_TARGET:

• WARM_PREFIX_TARGET: how many connected /28 prefixes to keep “in reserve”, i.e. they will be connected to ENI, but the addresses from them are not yet used
• WARM_IP_TARGET: how many minimum IP addresses to connect when creating a Node
• MINIMUM_IP_TARGET: how many minimum IP addresses to keep “in reserve”

When using VPC Prefix Assignment Mode, you cannot set all three parameters to zero – at least either WARM_PREFIX_TARGET or WARM_IP_TARGET must be set to at least 1.

If WARM_IP_TARGET and/or MINIMUM_IP_TARGET are specified, they will take precedence over WARM_PREFIX_TARGET, i.e. the value from WARM_PREFIX_TARGET will be ignored.

Advice and consultation available

Need advice for programming projects or
need a C/C++ or .NET C#/VB programmer? Advice how
to optimize and simplify administration of computers and networks? Migrate old source code to modern development systems?
Have some kind of hard-to-solve problem with computers, networks,
drivers, applications etc? Maybe I can help you. Send me an
e-mail: olof@ltr-data.se or
call me at +46 70 345 89 52 or Skype: live:ol. (I speak Swedish and English.)

Похожее:

Как обновить power shell Как включить защитник Windows 10 если он отключен Powershell найти и добавлять файлы в zip, соответствуя имя файла и имя его родительской папки Ваша лицензия windows поддерживает только один язык интерфейса