Start of the Elster-Saale Canal at Lindenau Harbour
Good day, I made an inspection (with a custom inspection interface) in VBAI. The inspection runs on a CVS-1458RT and the inspection interface has to be visible on a touchscreen connected via VGA to the CVS. But on the screen connected to the CVS is only a part of the inspection interface visible, the last acuired image. But the inspection interface has also controls and part counter,which are. A smart meter is an electronic device that records consumption of electric energy and communicates the information to the electricity supplier for monitoring and billing. Smart meters typically record energy hourly or more frequently, and report at least daily. Smart meters enable two-way communication between the meter and the central system.
The Elster-Saale Canal (German: Elster-Saale-Kanal), renamed in 1999 by the Federal Waterways and Shipping Administration as the Saale-Leipzig Canal (Saale-Leipzig-Kanal) or SLK[1] and on the Halle side also called the Saale-Elster Canal, was a canal project, started in 1933 and aborted in 1943, that was intended to link the White Elster river with the Saale near Leuna and thus enable the city of Leipzig to be joined to Germany's inland waterway network. The 11 kilometre long water-filled channel is one of the so-called special federal waterways.[1]
This link would have given Leipzig access to the Elbe via the Saale and thus to Hamburg and the North Sea. The canal was planned for ships up to 1,000 tonnes in weight (roughly Class IV).
Plans to complete the canal have been revived and an Elster-Saale Canal Society has been formed.
Gallery[edit]
- Start of the canal in Leipzig
- Railway bridge near Rückmarsdorf
- B 181 bridge near Rückmarsdorf
- Even in GDR times the canal was used for rowing
- Safety gate East near Burghausen
- Underpass for the Zschampert below the Elster-Saale Canal
- Relief work for water level regulation
- The canal near Dölzig
- Bridge near Günthersdorf. Background: the A 9 motorway bridge
- End of the canal near Günthersdorf
See also[edit]
Literature[edit]
- Wolfram Sturm, Leipzig und seine Schiffskanäle. Leipzig, 1998.
- Dirk Becker (2009), Der Südflügel des Mittellandkanals: Per Schiff von Magdeburg über Merseburg nach Leipzig (in German) (1. ed.), Halle: Projekte-Verlag, ISBN3866346093
- Denis Achtner (2008), 'Der Elster-Saale-Kanal'(pdf excerpt), Böhlitzer Hefte (in German) (2. ed.), Leipzig: Creativ Werbeagentur Kolb, Band 2
References[edit]
- ^ abVerzeichnis F der ChronikArchived 2016-07-22 at the Wayback Machine, Wasser- und Schifffahrtsverwaltung des Bundes
External links[edit]
Wikimedia Commons has media related to Elster-Saale Canal. |
Coordinates: 51°21′21″N12°13′55″E / 51.35583°N 12.23194°E
Retrieved from 'https://en.wikipedia.org/w/index.php?title=Elster-Saale_Canal&oldid=909700999'
-->Applies To: Windows Server (Semi-Annual Channel), Windows Server 2016
This topic addresses the minimum system requirements to run Windows Server速 2016 or Windows Server, version 1709.
Note
In this release, clean installations are recommended.
Note
If at the time of installation, you choose to install with the Server Core option, you should be aware that no GUI components are installed at all and you will not be able to install or uninstall them with Server Manager. If you need GUI features, be sure to choose the 'Server with Desktop Experience' option when you install Windows Server 2016. For more information, see Install Nano Server
Review system requirements
The following are estimated system requirements Windows Server 2016. If your computer has less than the 'minimum' requirements, you will not be able to install this product correctly. Actual requirements will vary based on your system configuration and the applications and features you install.
Unless otherwise specified, these minimum system requirements apply to all installation options (Server Core, Server with Desktop Experience, and Nano Server) and both Standard and Datacenter editions.
Important
The highly diverse scope of potential deployments makes it unrealistic to state 'recommended' system requirements that would be generally applicable. Consult documentation for each of the server roles you intend to deploy for more details about the resource needs of particular server roles. For the best results, conduct test deployments to determine appropriate system requirements for your particular deployment scenarios.
Processor
Processor performance depends not only on the clock frequency of the processor, but also on the number of processor cores and the size of the processor cache. The following are the processor requirements for this product:
Minimum:
- 1.4 GHz 64-bit processor
- Compatible with x64 instruction set
- Supports NX and DEP
- Supports CMPXCHG16b, LAHF/SAHF, and PrefetchW
- Supports Second Level Address Translation (EPT or NPT)
Coreinfo is a tool you can use to confirm which of these capabilities your CPU has.
RAM
The following are the estimated RAM requirements for this product:
Minimum:
- 512 MB (2 GB for Server with Desktop Experience installation option)
- ECC (Error Correcting Code) type or similar technology
Important
If you create a virtual machine with the minimum supported hardware parameters (1 processor core and 512 MB RAM) and then attempt to install this release on the virtual machine, Setup will fail.
To avoid this, do one of the following:
- Allocate more than 800 MB RAM to the virtual machine you intend to install this release on. Once Setup has completed, you can change the allocation to as little as 512 MB RAM, depending on the actual server configuration.
- Interrupt the boot process of this release on the virtual machine with SHIFT+F10. In the command prompt that opens, use Diskpart.exe to create and format an installation partition. Run Wpeutil createpagefile /path=C:pf.sys (assuming the installation partition you created was C:). Close the command prompt and proceed with Setup.
Storage controller and disk space requirements
Computers that run Windows Server 2016 must include a storage adapter that is compliant with the PCI Express architecture specification. Persistent storage devices on servers classified as hard disk drives must not be PATA. Windows Server 2016 does not allow ATA/PATA/IDE/EIDE for boot, page, or data drives.
The following are the estimated minimum disk space requirements for the system partition.
Minimum: 32 GB
Note
Be aware that 32 GB should be considered an absolute minimum value for successful installation. This minimum should allow you to install Windows Server 2016 in Server Core mode, with the Web Services (IIS) server role. A server in Server Core mode is about 4 GB smaller than the same server in Server with a GUI mode.
The system partition will need extra space for any of the following circumstances:
- If you install the system over a network.
- Computers with more than 16 GB of RAM will require more disk space for paging, hibernation, and dump files.
Network adapter requirements
Network adapters used with this release should include these features:
Minimum:
- An Ethernet adapter capable of at least gigabit throughput
- Compliant with the PCI Express architecture specification.
- Supports Pre-boot Execution Environment (PXE).
A network adapter that supports network debugging (KDNet) is useful, but not a minimum requirement.
Other requirements
Computers running this release also must have the following:
- DVD drive (if you intend to install the operating system from DVD media)
The following items are not strictly required, but are necessary for certain features:
- UEFI 2.3.1c-based system and firmware that supports secure boot
- Trusted Platform Module
- Graphics device and monitor capable of Super VGA (1024 x 768) or higher-resolution
- Keyboard and Microsoft速 mouse (or other compatible pointing device)
- Internet access (fees may apply)
Note
A Trusted Platform Module (TPM) chip is not strictly required to install this release, though it is necessary in order to use certain features such as BitLocker Drive Encryption. If your computer uses TPM, it must meet these requirements:
- Hardware-based TPMs must implement version 2.0 of the TPM specification.
- TPMs that implement version 2.0 must have an EK certificate that is either pre-provisioned to the TPM by the hardware vendor or be capable of being retrieved by the device during the first boot.
- TPMs that implement version 2.0 must ship with SHA-256 PCR banks and implement PCRs 0 through 23 for SHA-256. It is acceptable to ship TPMs with a single switchable PCR bank that can be used for both SHA-1 and SHA-256 measurements.
- A UEFI option to turn off the TPM is not a requirement.
Installation of Nano Server
For detailed steps to install Windows Server 2016 as a Nano Server, see Install Nano Server.