BASIL_NETWORKS

BANNER_PRODUCT_INFO
BANNER_Interactive_BUS_Protocol_Development_[IBPD]_System_Overview

 

HomeABOUTPRODUCTSSERVICESSUPPORTCONTACTARTICLESNEWSBLOG
SystemsPeripheralsInstrumentsResearchNetworksSoftwareProgrammersOEM
IBPD-SystemIBPD-HardwareIBPD-CLADSIBPD-ProtocolsIBPD-Test Equip
 
 Main MenuInstall ProtocolsOpen ProjectCreate ProjectUser Buttons Encrypt/DecryptIBPD RegistrationSystem SpecificationsIBPD Demo

BANNER_IBPD_SystemSpecifications

The core specifications for all IBPD Systems are common to all systems in the IBPD series family.   The common core supports easy cascading and integration for an unlimited series of protocols and test instrumentation the use of a single USB port.   The standard recommended USB port release is 2.0 or USB 3.0.  USB 1.1 is backwards compatible for the USB 2.0 release only with reduced performance due to the USB 1.1 max bandwidth.  Specifications for protocols and test instrumentation are given with the function web pages.

Banner_System_Requirements

At this time the IBPD System only supports Microsoft Windows operating systems.  We recommend for all 32 bit systems that at least 2Gig be available after graphics and other drivers, recommended 3Gig or 4Gig RAM be installed.  For 64 bit systems 8 Gig RAM minimum is recommended.  For more than four protocols simultaneously 16 Gig RAM or more is recommended.   The IBPD System installs without creating or using any registry keys and is a self contained system.  To uninstall the IBPD system is simple, just delete the directory it is installed in.

The IBPD System has been tested on the following Windows environments:

  • Windows 2000
    Limited functionality due to system memory limitations of 2Gig RAM and max path limits within the OS.
  • Windows XP SP3 full 32 Bit
    Max Memory installed is 4 Gig RAM including Graphics RAM and peripheral drivers.
    Setting the /PAE option in the boot.ini file.allows the use of memory  that is not mapped out greater than 3.0Gig.
    All 32 bit systems are limited to 4 Gig max.  All peripherials reside within the 4 Gig RAM
  • Win7 Win8.xx all 32 Bit Environments
    Max Memory installed is 4 Gig RAM including Graphics RAM and peripheral drivers.
    All 32 bit systems are limited to 4 Gig max.  All peripherials reside within the 4 Gig RAM.
  • Win7, Win8.xx  All 64 Bit Environments
    Max Memory - See below for Windows 32 and 64 bit memory limits.
    The IBPD system will run multiple protocols in a multi-core, Hyperthread environment.
  • Win10.xx  All 32 Bit Environments
    Max Memory installed is 4 Gig RAM including Graphics RAM and peripheral drivers.
    All 32 bit systems are limited to 4 Gig max.  All peripherials reside within the 4 Gig RAM.
  • Win10.xx  All 64 Bit Environments
    Max Memory - See below for Windows 32 and 64 bit memory limits.
    The IBPD system will run multiple protocols in a multi-core, Hyperthread environment.

Banner_Memory_Address_Space_Limits

The IBPD System core software specifications for the Main Dispatch Startup program only requires about 6 Megabytes to load the default and temporary databases, drivers installed on the system and system task links.

Intel Hex Format File Specs:
The original Intel-Hex format allows up to a 255 byte hex block size.  Although this may have been used in the 80's, today's hex default seems to be 16 bytes of hex data after the format heading.  To conserve memory space the IBPD system has limited the Intel Hex file block size to16 bytes plus the header bytes to reduce this overhead.  When reading an Intel-hex data file the IBPD will automatically reduce the size of the block size if it exceeds 16 bytes and maintain the proper addressing.   This will accommodate the IBPD Hex editors incorporated into the system.   

USB Ports
The standard USB port is USB 2.0 and will operate at all speeds and is USB 1.1 backwards compatible.  The speeds are High Speed (480 Mbs), Full Speed (12 Mbs) and Low Speed (1.5 Mbs).   the IBPD System Model-200 is both USB2.0 and USB 3.0 are  included with USB 3.0 Speeds upto 5Gbps.  The USB 2.0  and USB 3.0 ports are certified USB compliant.

Memory Size Per Protocol:
The memory required for each protocol will vary depending on the file size being stored within the protocol dialogs.  A standard rule is to have at least 384MB available per protocol to handle the maximum allowable file size.  The IBPD-System takes special care when ending tasks and freeing up unused memory.  Each IBPD-System protocol uses about 384 Megabytes to handle the dialogs and data storage for data files.  A standard 4Gig 32bit x86 OS would be able to handle up to 2 protocols due to the task switching and OS overhead.  It is recommended that a 64 bit operating system be used with a minimum of 8GB memory, 16GB recommended.  Only the newer motherboards support the 64 bit memory allocation and are recommended for development.  The links below allow the user to optimize their OS for the required development environment.   The development of the IBPD System is performed under a 32 bit environment and tested on both 32 and 64 bit environments.

Since Windows does not allow direct inter task shared memory (which is a good thing) it eliminates memory allocation leaks directly.  The IBPD-System uses a separate file for keeping track of the number of IBPD-System tasks started during a session.  All protocols are called from the MAIN startup menu. Each task started has its own process ID and Name saved in the active tasks file in the IBPD Installs root directory.  This allows the session to be terminated in entirety by terminating the Main startup menu with a single click of the mouse.

Memory Size of Operating Systems:
The IBPD-System has been tested on both x32 and x64 bit windows operating systems.  There are several Windows operating systems that the IBPD-System will operate on.  The list  of Operating Systems and requirements are shown in the table below.  Memory requirements are set to include the maximum allowable data file per protocol.  Windows does not restrict tasks from overwriting other tasks.  If you run out of memory other programs may not work properly.  For more detailed information visit  Memory Limits for Windows and Windows Server Releases

IMAGE_FILE_LARGE_ADDRESS_AWARE:
Limits on memory and address space vary by platform, operating system, and by whether the IMAGE_FILE_LARGE_ADDRESS_AWARE value of the LOADED_IMAGE structure and 4-gigabyte tuning (4GT) are in use.  IMAGE_FILE_LARGE_ADDRESS_AWARE is set or cleared by using the /LARGEADDRESSAWARE linker option.

4-gigabyte tuning (4GT), also known as application memory tuning, or the /3GB switch, is a technology (only applicable to 32 bit systems) that alters the amount of virtual address space available to user mode applications. Enabling this technology reduces the overall size of the system virtual address space and therefore system resource maximums. For more information, see What is 4GT.

Limits on physical memory for 32-bit platforms also depend on the Physical Address Extension (PAE), which allows 32-bit Windows systems to use more than 4 GB of physical memory.  PAE (Physical Address Extension) allows more memory to be allocated (ex: 64Gigabyte on a 32 bit OS).  Older motherboards may limit the memory to 2 or 4 Gigabytes less the display memory as well.  The IBPD-System has been tested on XP with the full 4 Gigabyte RAM with dual XEON 64 EMT Hyperthread enabled. This shows up as 4 processors in the task manager.  The IBPD-System is compiled with the IMAGE_FILE_LARGE_ADDRESS_AWARE set for all protocols.

The following table specifies the limits on memory and address space for supported releases of Windows. Unless otherwise noted, the limits in this table apply to all supported releases.

Memory type Limit in on X86 Limit in 64-bit Windows

User-mode virtual address space for each 32-bit process

2 GB
Up to 3 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE and 4GT

2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared (default)
4 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE set

User-mode virtual address space for each 64-bit process

Not applicable

With IMAGE_FILE_LARGE_ADDRESS_AWARE set (default):
x64:  8 TB
Intel Itanium-based systems:  
7 TB
Windows 8.1 and Windows Server 2012 R2:  128 TB

2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared

Kernel-mode virtual address space

2 GB
From 1 GB to a maximum of 2 GB with 4GT

8 TB
Windows 8.1 and Windows Server 2012 R2:  128 TB

Paged pool

384 GB or system commit limit, whichever is smaller.

Windows 8.1 and Windows Server 2012 R2:  15.5 TB or system commit limit, whichever is smaller.

Windows Server 2008 R2, Windows 7, Windows Server 2008, and Windows Vista:  Limited by available kernel-mode virtual address space. Starting with Windows Vista with Service Pack 1 (SP1), the paged pool can also be limited by the PagedPoolLimit registry key value.

Windows Home Server and Windows Server 2003:  530 MB
Windows XP:  490 MB

384 GB or system commit limit, whichever is smaller

Windows 8.1 and Windows Server 2012 R2:  15.5 TB or system commit limit, whichever is smaller.

Windows Server 2008 R2, Windows 7, Windows Server 2008, and Windows Vista:  128 GB or system commit limit, whichever is smaller

Windows Server 2003 and Windows XP:  Up to 128 GB depending on configuration and RAM.

Nonpaged pool

75% of RAM or 2 GB, whichever is smaller.

Windows 8.1 and Windows Server 2012 R2:  RAM or 16 TB, whichever is smaller (address space is limited to 2 x RAM).

Windows Vista:  Limited only by kernel mode virtual address space and physical memory. Starting with Windows Vista with SP1, the nonpaged pool can also be limited by the NonPagedPoolLimit registry key value.

Windows Home Server, Windows Server 2003, and Windows XP:  256 MB, or 128 MB with 4GT.

RAM or 128 GB, whichever is smaller (address space is limited to 2 x RAM)

Windows 8.1 and Windows Server 2012 R2:  RAM or 16 TB, whichever is smaller (address space is limited to 2 x RAM).

Windows Server 2008 R2, Windows 7, and Windows Server 2008:  75% of RAM up to a maximum of 128 GB

Windows Vista:  40% of RAM up to a maximum of 128 GB.

Windows Server 2003 and Windows XP:  Up to 128 GB depending on configuration and RAM.

System cache virtual address space (physical size limited only by physical memory)

Limited by available kernel-mode virtual address space or the SystemCacheLimit registry key value.

Windows 8.1 and Windows Server 2012 R2:  16 TB.

Windows Vista:  Limited only by kernel mode virtual address space. Starting with Windows Vista with SP1, system cache virtual address space can also be limited by the SystemCacheLimit registry key value.

Windows Home Server, Windows Server 2003, and Windows XP:  860 MB with LargeSystemCache registry key set and without 4GT; up to 448 MB with 4GT.

Always 1 TB regardless of physical RAM

Windows 8.1 and Windows Server 2012 R2:  16 TB.

Windows Server 2003 and Windows XP:  Up to 1 TB depending on configuration and RAM.

Top

BANNER_MAX_OS_MEMORY

Operating System

x86 (32 Bit) Max

x64 (64 Bit) Max

IA64 (64 Bit) Max

 

Windows XP Pro

4 GB

128 GB

not supported

 


Windows Server 2003 Entrpr

64 GB

-

512 GB

16GB with 4GT on x86

Windows Server 2003 Entrpr SP1

64 GB

1 TB

1 TB

16GB with 4GT on x86

Windows Server 2003 Entrpr SP2

4 GB

1 TB

2 TB

16GB with 4GT on x86

Windows Server 2008 Standard

4 GB

32 GB

not supported

 

Windows Server 2008 Enterprise

64 GB

1 TB

not supported

 

Windows Server 2008 Datacenter

64 GB

1 TB

not supported

 

Windows Server 2008 Itanium

-

-

2 TB

 


Windows Vista Ultimate

4 GB

128 GB

not supported

 

Windows Vista Enterprise

4 GB

128 GB

not supported

 

Windows Vista Business

4 GB

128 GB

not supported

 

Windows Vista Premium

4 GB

16 GB

not supported

 


Windows 7 Ultimate

4 GB

192 GB

not supported

 

Windows 7 Enterprise

4 GB

192 GB

not supported

 

Windows 7 Professional

4 GB

192 GB

not supported

 

Windows 7 Premium

4 GB

16 GB

not supported

 

Windows 7 Basic

2 GB

N/A

not supported

 


Windows Server 2012 Datacenter

-

4 TB

not supported

 

Windows Server 2012 Standard

-

4 TB

not supported

 

Windows Server 2012 Essentials

-

64 GB

not supported

 

Windows Server 2012 Foundation

-

32 GB

not supported

 

Windows 8, 10 Enterprise

4 GB

512 GB

not supported

 


Windows 8, 10 Professional

4 GB

512 GB

not supported

 

Windows 8, 10

4 GB

128 GB

not supported

 

Top

Copyright 1990-2016 BASIL Networks, PLLC. All rights reserved
webmaster