The following warnings occurred:
Warning [2] Undefined array key "extra" - Line: 100 - File: inc/plugins/google_seo/url.php PHP 8.1.33 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/inc/plugins/google_seo/url.php 100 errorHandler->error_callback
/inc/plugins/google_seo.php 317 require_once
/inc/class_plugins.php 38 require_once
/inc/init.php 263 pluginSystem->load
/global.php 20 require_once
/showthread.php 28 require_once
Warning [2] Undefined array key "parent" - Line: 447 - File: inc/plugins/google_seo/url.php PHP 8.1.33 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/inc/plugins/google_seo/url.php 447 errorHandler->error_callback
/inc/plugins/google_seo/url.php 1144 google_seo_url_create
/inc/plugins/google_seo/url.php 174 google_seo_url_hook
/inc/plugins/google_seo.php 317 require_once
/inc/class_plugins.php 38 require_once
/inc/init.php 263 pluginSystem->load
/global.php 20 require_once
/showthread.php 28 require_once
Warning [2] Trying to access array offset on value of type null - Line: 198 - File: inc/plugins/google_seo.php PHP 8.1.33 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/inc/plugins/google_seo.php 198 errorHandler->error_callback
/inc/plugins/google_seo/redirect.php 133 google_seo_tid
/inc/class_plugins.php 142 google_seo_redirect_hook
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once
Warning [2] Undefined array key 375102 - Line: 198 - File: inc/plugins/google_seo.php PHP 8.1.33 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/inc/plugins/google_seo.php 198 errorHandler->error_callback
/inc/plugins/google_seo/url.php 1453 google_seo_tid
/inc/functions.php 6608 google_seo_url_post
/inc/plugins/google_seo/redirect.php 134 get_post_link
/inc/class_plugins.php 142 google_seo_redirect_hook
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once
Warning [2] Undefined variable $unreadreports - Line: 38 - File: global.php(961) : eval()'d code PHP 8.1.33 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/global.php(961) : eval()'d code 38 errorHandler->error_callback
/global.php 961 eval
/showthread.php 28 require_once
Warning [2] Undefined variable $mysupport_tech_notice - Line: 38 - File: global.php(961) : eval()'d code PHP 8.1.33 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/global.php(961) : eval()'d code 38 errorHandler->error_callback
/global.php 961 eval
/showthread.php 28 require_once
Warning [2] Undefined variable $mysupport_assign_notice - Line: 38 - File: global.php(961) : eval()'d code PHP 8.1.33 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/global.php(961) : eval()'d code 38 errorHandler->error_callback
/global.php 961 eval
/showthread.php 28 require_once
Warning [2] Undefined array key 375102 - Line: 198 - File: inc/plugins/google_seo.php PHP 8.1.33 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/inc/plugins/google_seo.php 198 errorHandler->error_callback
/inc/plugins/google_seo/url.php 1453 google_seo_tid
/inc/functions.php 6608 google_seo_url_post
/inc/functions_post.php 722 get_post_link
/showthread.php 1122 build_postbit
Warning [2] Undefined array key "additionalgroups" - Line: 7924 - File: inc/functions.php PHP 8.1.33 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/inc/functions.php 7924 errorHandler->error_callback
/inc/plugins/ougc_agi.php 307 is_member
/inc/class_plugins.php 142 ougc_agi_run
/inc/functions_post.php 917 pluginSystem->run_hooks
/showthread.php 1122 build_postbit
Warning [2] Undefined variable $theme - Line: 324 - File: inc/plugins/ougc_agi.php PHP 8.1.33 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/inc/plugins/ougc_agi.php 324 errorHandler->error_callback
/inc/class_plugins.php 142 ougc_agi_run
/inc/functions_post.php 917 pluginSystem->run_hooks
/showthread.php 1122 build_postbit
Warning [2] Trying to access array offset on value of type null - Line: 324 - File: inc/plugins/ougc_agi.php PHP 8.1.33 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/inc/plugins/ougc_agi.php 324 errorHandler->error_callback
/inc/class_plugins.php 142 ougc_agi_run
/inc/functions_post.php 917 pluginSystem->run_hooks
/showthread.php 1122 build_postbit
Warning [2] Undefined array key "mysupport_status" - Line: 23 - File: inc/functions_post.php(970) : eval()'d code PHP 8.1.33 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/inc/functions_post.php(970) : eval()'d code 23 errorHandler->error_callback
/inc/functions_post.php 970 eval
/showthread.php 1122 build_postbit
Warning [2] Undefined array key "mysupport_bestanswer" - Line: 25 - File: inc/functions_post.php(970) : eval()'d code PHP 8.1.33 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/inc/functions_post.php(970) : eval()'d code 25 errorHandler->error_callback
/inc/functions_post.php 970 eval
/showthread.php 1122 build_postbit
Warning [2] Undefined array key "mysupport_deny_support_post" - Line: 25 - File: inc/functions_post.php(970) : eval()'d code PHP 8.1.33 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/inc/functions_post.php(970) : eval()'d code 25 errorHandler->error_callback
/inc/functions_post.php 970 eval
/showthread.php 1122 build_postbit
Warning [2] Undefined variable $mysupport_options - Line: 52 - File: showthread.php(1651) : eval()'d code PHP 8.1.33 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/showthread.php(1651) : eval()'d code 52 errorHandler->error_callback
/showthread.php 1651 eval
Warning [2] Undefined variable $mysupport_status - Line: 65 - File: showthread.php(1651) : eval()'d code PHP 8.1.33 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/showthread.php(1651) : eval()'d code 65 errorHandler->error_callback
/showthread.php 1651 eval
Warning [2] Undefined variable $mysupport_options - Line: 88 - File: showthread.php(1651) : eval()'d code PHP 8.1.33 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/showthread.php(1651) : eval()'d code 88 errorHandler->error_callback
/showthread.php 1651 eval
Warning [2] Undefined variable $mysupport_js - Line: 109 - File: showthread.php(1651) : eval()'d code PHP 8.1.33 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/showthread.php(1651) : eval()'d code 109 errorHandler->error_callback
/showthread.php 1651 eval
Warning [2] Undefined variable $newurl - Line: 1609 - File: inc/plugins/google_seo/url.php PHP 8.1.33 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/inc/plugins/google_seo/url.php 1609 errorHandler->error_callback
/inc/functions.php 1148 google_seo_url_multipage
/inc/functions.php 4819 multipage
/inc/functions.php 298 build_breadcrumb
/inc/functions.php 22 parse_page
/showthread.php 1652 output_page



  Register Account

Earn real money $$ through NewPoints: Click Here x


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
RAMMon 3.1 Build 1000
#1
[Image: FhgBhUnp_o.png]
File size: 4 MB

Descriptions: RAMMon is a lightweight Windows application that reports memory timings, transfer rate, channel mode and other memory settings, as well as the Serial Presence Detect (SPD) data of RAM modules. SPD data allow users to identify a multitude of attributes, of which, includes the manufacturer, the clockspeed and other data of their DDR2, DDR3, DDR4, DDR5, XMP and EPP memory devices and even some older memory types.

In addition, performance benchmarks on cache and physical memory are collected and displayed.

It uses SysInfo DLL SDK to gather the memory-related information.

🌟 What is SPD?
Serial Presence Detect (SPD) is the standard set forth by JEDEC for a host system to retrieve attributes of memory modules. The SPD standard is intended for use on any memory module, independent of memory technology or module form factor.

RAMMon displays the values stored on RAM module such as the memory capacity, the manufactuer, serial number, model part number, the CAS latencies supported and the module voltage.

Also, depending on your RAM type, other specific SPD data can be retreived as well. Such as the module thickness, module width, maximum operating temperature and more.

🌟 Supported Hardware
Any x86 machine can run RAMMon, but not all information may be available as it is highly dependent on the motherboard/CPU chipset. If there is any missing information for your chipset, please let us know by following the instructions under the "Support" section in the help manual. Send in the files that are created for further analysis.

🌟 Customizing RAMMon
RAMMon is built with PassMark's SysInfo DLL SDK. If you would like to use this technology in your application, please check out the SysInfo DLL SDK or contact us at

[To see links please register or login]


🌟 Installation
Double click on the rammon.exe installer file to run the RAMMon installer. Additional information is provided in the included help file. You can view them from RAMMon's help button or open RAMMon_help.exe in the "HELP" folder.

🌟 Known issues
Some system vendors ship non standard systems, especially for Laptops. This includes some systems from Dell, HP, ASUS & Lenovo. Some laptops use RAM soldered to the motherboard (as opposed to being in a socket). On these systems the soldered chips might not contain any SPD data, as the corresponding data, that would be in the SPD, is hard coded into the BIOS on the machine instead. On other machines it might not be possible to locate the SMBus on these machines to collect the RAM's SPD data. (The SMBus is the low speed circuit on the motherboard that connections the CPU to various other components on the motherboard and it is used to transfer the PSD data from a RAM stick to the CPU). Also, you need to be the administrator to run the software.

By default on certain platforms (such as ASUS), the BIOS disables SPD Writes which prevents access to the SPD raw data on the module. Although no actual writes are performed on the SPD, SMBus write operations are required to access the full 1024 SPD bytes. This is because only pages of 128 byte SPD data can accessed at once, and SPD Writes are performed to read all 8 pages. Fortunately, on a few motherboards there is a BIOS setting for enabling SPD writes which should rectify the issue.

🌟 **Update** Since RAMMon v3.0, DDR5 SPD data can be read even with SPD write is disabled.

🌟 Whats New
Updates: official site does not provide any info about changes in this version

[To see links please register or login]


-----------------------------***[ softwarez.info (OP) ]***-----------------------------

⭐️ RAMMon 3.1 Build 1000 ✅ (4.02 MB)
NitroFlare Link(s)

[To see links please register or login]


RapidGator Link(s)

[To see links please register or login]

[Image: signature.png]
Reply



Forum Jump:


Users browsing this thread:

DL Warez BB