#physicalmemory | Explore Tumblr posts and blogs

senpenbanka0426 · 1 year ago

Text

【自分用】Rainmeterのスキン【メモ】

Windows11の時計と日付が余りにも小さくて見づらいからRainmeterのスキンを作る事に。パソコンやモニターサイズ買い換えた時にまた作り直せるようにメモしておく用の記事になりやす。

－－－－－－－－－－－－－－

日付用のスキン（Date.ini）

[Rainmeter] Author=pixeltoast Update=1000

[MeasureDate] Measure=Time Format=%Y / %m / %d %a

[MeterDate] MeasureName=MeasureDate Meter=STRING FontColor=0, 0, 0, 255 FontSize=24 FontFace=Impact AntiAlias=1

;曜日を日本語にしたい場合は[MeasureDate]にFormatLocale=Localを追加する。

－－－－－－－－－－－－－－

時間用のスキン（Time.ini）

[Rainmeter] Author=pixeltoast Update=1000

[MeasureDate] Measure=Time FormatLocale=Local Format=%H:%M:%S

[MeterDate] MeasureName=MeasureDate Meter=STRING FontColor=0, 0, 0, 255 FontSize=24 FontFace=Impact AntiAlias=1

－－－－－－－－－－－－－－

PCパフォーマンス用のスキン（performance.ini）

[Rainmeter] Update=1000 DynamicWindowSize=1

[MeterBackground] ;背景 Meter=Image X=0 Y=0 W=140 H=97 SolidColor=0,0,0,220

[MeasureCPU] Measure=CPU UpdateDivider=1

[MeterCPU] Meter=String MeasureName=MeasureCPU X=10 Y=5 W=130 H=20 FontSize=13 FontFace=Impact FontColor=255, 255, 255, 255 AntiAlias=1 Text="CPU : %1%"

[MeasureMemoryTotal] Measure=PhysicalMemory Total=1

[MeasureMemoryUsed] Measure=PhysicalMemory

[MeasureMemoryUsage] Measure=Calc Formula=(MeasureMemoryUsed / MeasureMemoryTotal) * 100

[MeterMemoryUsage] Meter=String MeasureName=MeasureMemoryUsage X=10 Y=27 W=130 H=20 FontSize=13 FontFace=Impact FontColor=255, 255, 255, 255 AntiAlias=1 Text="Memory : %1%" Format=%1f%%

[MeasureDiskFree] Measure=FreeDiskSpace Drive=C: UpdateDivider=10

[MeasureDiskTotal] Measure=FreeDiskSpace Drive=C: Total=1

[MeasureDiskUsage] Measure=Calc Formula=(MeasureDiskTotal - MeasureDiskFree) / MeasureDiskTotal * 100

[MeterDiskUsage] Meter=String MeasureName=MeasureDiskUsage X=10 Y=49 W=130 H=20 FontSize=13 FontFace=Impact FontColor=255, 255, 255, 255 AntiAlias=1 Text="Disk : %1%"

－－－－－－－－－－－－－－

超久々にディスクトップを整理して、超久々にRainmeter触ったらスキンの作り方を綺麗サッパリ忘れててﾜﾛﾀ。

ネットで探せばお洒落なスキンはたくさんあるが、自分の欲しいサイズに合わせるのが、なかなか難しいんだよな。（カスタマイズしてる時はめっちゃ楽しいけど(笑)）

#雑記

1 note · View note

co-iki · 4 years ago

Photo

UN/Learning Lab III : UN/Learn “Memory” of the Body 「身体記憶」をアンラーンする！喪失と回復のダイアローグ Natural Disasters in Japan, International Adoption in Canada.. Come listen to artists' genuine voices on their creative practices related to self-identity and identity crisis! We will have a great Japanese poet , @ryoichiwago 和合亮一 , from Fukushima devastated area of the great earthquake in 2011, and An Laurence @an_laurence_ a musician from Canada who has an experience as Chinese adoptee, to talk together on their personal experiences and how their creation relate to their own/social narratives. 自然災害、国際養子縁組・・記憶とアイデンティティの物語りからあたらしい継承のかたちを探索するセッション大震災から10年を迎える福島で活動する詩人��和合亮一氏と中国国際養子の経験からカナダで活動するミュージシャン、アンロレンス。真実の声をききに、また対話しに、是非ご参加ください😊 2021年12月11日（土）Dec 11th(sat) 20:00-21:30 JST@ZOOM 👇Get the ticket to join!! More details 詳細＆チケットはこちらより！ http://ptix.at/tf2GyQ FB Event Page : https://fb.me/e/WeAggUIM ------------ UN/Learning Lab Theme III : Physicality in the Time of Remote Communication The Archipelago of Memories: A Dialogue on Loss and Recovery テーマIII：リモート時代の身体性 vol.3 変わりゆく身体記憶と体験知～参加者とともに探索する、「新しい継承」のかたち～ ”記憶の島”　—　喪失と回復のダイアローグトークセッションー日本の自然災害、カナダの国際養子縁組・・危機的経験からつむぐアイデンティティの喪失と回復の物語、その生の声を聴くー身体記憶に残るものとは？記憶の在処とあらたらしい「継承」のかたちを考えるー創作活動が意味するもの、個人的記憶と集合的記憶をつなぐクリエーションについて知る —　Stories of identity loss and recovery from crisis experiences & listening to the genuine voices of the artists —　What remains in physical memory? Reimagine a new form of inheritance of memories and their whereabouts —　What does creative practice mean for the artist? Learn about creation that interweaves an individual with the collective memory ------------ More details in the link: http://ptix.at/tf2GyQ See you there! #unlearninglab #coiki #artistresidency #talksession #chinesedoption #internationaladoption #fukushima #earthquake #tsunami #identirycrisis #memory #physicalmemory #memoryofthebody #artisttalk #creativepractice #身体記憶 #記憶と創作 #アイデンティティ #創作とアイデンティティ #アーティストトーク #危機とアート #喪失と回復の物語 #中国国際養子 #東日本大震災 #詩人 #和合亮一 https://www.instagram.com/p/CXIuT8cPz7X/?utm_medium=tumblr

0 notes

projectandtaskrealtedposts · 4 years ago

Text

What is RAM, and how to read it.

1) what is RAM ?

RAM stands for random access memory. This is where a PC stores data before it's processed. ... RAM is a form of volatile memory, which means that it only holds onto data while the chip is powered and erases everything when you shut down the PC. RAM memory is measured in gigabytes (GB).

2)Why we use RAM ?

RAM stores the information.Your computer is actively using so that it can be accessed quickly. The more programs your system is running, the more memory you'll need.

3)Can you read RAM?

The answer is big yes. The contents of RAM can be changed at any time by overwriting it with other data and instructions. On Windows, the contents of physical memory can be accessed through the \Device\PhysicalMemory object in the Object Manager. This requires kernel-level access to the system, which means you would need to install a program, most likely a kernel-mode driver, to access this object.

Hope you get the short info about RAM guys , soon i will post the method of how to read RAM. Thank you!

#vimaldaga righteducation educationredefine arth2 rightmentor worldrecordholder linuxworld makingindiafutureready righteducation

1 note · View note

marcosplavsczyk · 5 years ago

Link

As known, the Microsoft SQL Server is a relational database management system with the function of storing and retrieving data requested by other corresponding software applications.

Knowing the configuration of a SQL Server is key to determine its edition, the sum of the memory that is being allocated for that instance, build number, and many more of the valuable information.

Let’s now consider one common situation in which there is a SQL Server DBA team that supports and maintains 100+ SQL Server instances, ranging from the SQL Server 2005 up to the latest SQL Server 2019 and all with different editions, service packs, and authentication modes. And what if they’ve been tasked with the critical mission to generate a report in Word, Excel, or PDF to show the details of basic information, configuration settings, and server objects of those instances.

This feat can be accomplished in various ways by using the SQL Server Management Solution (SSMS), but this approach can be exhausting and overwhelming since there is no way to access all valuable information in one place.

Having the option to view all SQL Server instance details at one easily accessible place without hassling with enormous T-SQL scripts or an endless stream of “button clicking” is the desired goal for any DBA.

The following article will shed some light on a few ways SQL instance details could be extracted within the SSMS and then provide an insight into a simpler and more productive alternative by using the 3rd party software.

View instance details using SSMS

Once the connection to the desired SQL Server is made, let’s move on to seeing its basic information. To accomplish this, right-click on the instance name and from the menu choose Properties:

Under the General tab of the Server Properties window, some basic SQL Server Instance information is displayed:

Product – the name of the product and its bit version

Operating system – information about the operating system the instance is installed on

Platform – the platform product belongs to

Version – version of the product

Language – the language of the product

Memory – memory allocated to the server

Processors – number of processors allocated to the server

Root directory – the server’s installation folder

Server collation – the name of the default collation for the server

Is Clustered – shows if server instance is configured in a failover cluster

Is XTP Supported – shows if server instance supports In-Memory OLTP

Is HADR Enabled – shows if Always On availability groups is enabled on the SQL Server instance

In the Advanced tab a few more information regarding a server instance can be found:

Containment – shows if the server instance is having contained databases, i.e., ones that are isolated from the instance itself

FILESTREAM – a SQL Server feature that stores data in the file system

Miscellaneous – some miscellaneous information related to the instance

Network – displays configuration settings related to the Network Packet Size and the Remote Login timeout

Parallelism – a SQL Server feature that divides a big task into smaller tasks to increase speed and performance

Get SQL Server information using system views

To pull SQL instance information by using system views, please refer to the Discovering SQL server instance information using system views article.

Get SQL Server information using T-SQL scripts

The following are few examples of using T-SQL scripts to get some information regarding a SQL instance.

Example 1

The following script will pull some basic information that can also be found in the General tab of the Server Properties window in SQL Server Management Studio:

USE master GO EXEC xp_msver "ProductName" ,"ProductVersion" ,"Language" ,"Platform" ,"WindowsVersion" ,"PhysicalMemory" ,"ProcessorCount" GO

Source

The output of this script is:

Example 2

The following T-SQL script will pull the SQL Server Instance information by executing stored procedures:

DECLARE @version VARCHAR(4) SELECT @version = substring(@@version, 22, 4) IF CONVERT(SMALLINT, @version) >= 2012 EXEC ( 'SELECT SERVERPROPERTY(''ServerName'') AS [Instance Name], CASE LEFT(CONVERT(VARCHAR, SERVERPROPERTY(''ProductVersion'')),4) WHEN ''11.0'' THEN ''SQL Server 2012'' WHEN ''12.0'' THEN ''SQL Server 2014'' ELSE ''Newer than SQL Server 2014'' END AS [Version Build], SERVERPROPERTY (''Edition'') AS [Edition], SERVERPROPERTY(''ProductLevel'') AS [Service Pack], CASE SERVERPROPERTY(''IsIntegratedSecurityOnly'') WHEN 0 THEN ''SQL Server and Windows Authentication mode'' WHEN 1 THEN ''Windows Authentication mode'' END AS [Server Authentication], CASE SERVERPROPERTY(''IsClustered'') WHEN 0 THEN ''False'' WHEN 1 THEN ''True'' END AS [Is Clustered?], SERVERPROPERTY(''ComputerNamePhysicalNetBIOS'') AS [Current Node Name], SERVERPROPERTY(''Collation'') AS [ SQL Collation], [cpu_count] AS [CPUs], [physical_memory_kb]/1024 AS [RAM (MB)] FROM [sys].[dm_os_sys_info]' ) ELSE IF CONVERT(SMALLINT, @version) >= 2005 EXEC ( 'SELECT SERVERPROPERTY(''ServerName'') AS [Instance Name], CASE LEFT(CONVERT(VARCHAR, SERVERPROPERTY(''ProductVersion'')),4) WHEN ''9.00'' THEN ''SQL Server 2005'' WHEN ''10.0'' THEN ''SQL Server 2008'' WHEN ''10.5'' THEN ''SQL Server 2008 R2'' END AS [Version Build], SERVERPROPERTY (''Edition'') AS [Edition], SERVERPROPERTY(''ProductLevel'') AS [Service Pack], CASE SERVERPROPERTY(''IsIntegratedSecurityOnly'') WHEN 0 THEN ''SQL Server and Windows Authentication mode'' WHEN 1 THEN ''Windows Authentication mode'' END AS [Server Authentication], CASE SERVERPROPERTY(''IsClustered'') WHEN 0 THEN ''False'' WHEN 1 THEN ''True'' END AS [Is Clustered?], SERVERPROPERTY(''ComputerNamePhysicalNetBIOS'') AS [Current Node Name], SERVERPROPERTY(''Collation'') AS [ SQL Collation], [cpu_count] AS [CPUs], [physical_memory_in_bytes]/1048576 AS [RAM (MB)] FROM [sys].[dm_os_sys_info]' ) ELSE SELECT 'This SQL Server instance is running SQL Server 2000 or lower! You will need alternative methods in getting the SQL instance level information.'

Source

The result of this script:

Can this be simpler?

In short, yes.

Let’s be honest, no one wants to hassle all day long with enormous T-SQL scripts to get some basic server information, especially when there is another solution, a different approach.

You don’t need to type anything, no T-SQL scripts are needed, or required cause all SQL Server instance information is just one click away and all mentioned info, and even more, is stored in one easily accessible place.

3rd party solution

Below is a look into a process of viewing SQL instance information by using a 3rd party SQL manage instance tool, ApexSQL Manage.

Before initializing the mentioned process, one first needs to add SQL instance in the SQL manage instance tool.

There are numerous different ways to add SQL instance in the SQL Manage instance tool.

To choose the one that suits your needs the best, please consult the following guide: Different ways of adding SQL Server instances in a SQL manage instance software

Once an instance is added, it will be shown in the main grid of the Inventory tab. Select it and click the Instance button:

All the SQL Server information is now easily accessible on the left side of the application window and is separated into two groups:

Server

Server objects

Simply pick your preferred category on the left, and its details will be shown on the right.

For a detailed guide on what each of the categories represents and what information it carries, please check the How to view SQL instance details in ApexSQL Manage article.

Conclusion

When in a rush to quickly pull all the accessible SQL Server instance information, there is no need to execute enormous T-SQL scripts or trying to find some basic information that is buried somewhere into SSMS property windows, especially when those don’t return all that is required.

This valuable information is stored in one centralized place within the SQL manage instance tool and can be easily accessed with a minimal amount of effort.

#SQL Solution Center

0 notes

ronaldmorton · 7 years ago

Text

#dogtraining #ndt Question All Assumptions https://goo.gl/fb/mE8Q5u #blog #crow #necrophilia #physicalmemory

#dogtraining #ndt Question All Assumptions https://goo.gl/fb/mE8Q5u #blog #crow #necrophilia #physicalmemory syndicated from https://thehappypoochweb.wordpress.com/

0 notes

just4programmers · 8 years ago

Text

Porting a 15 year old .NET 1.1 Virtual CPU Tiny Operating System school project to .NET Core 2.0

I've had a number of great guests on the podcast lately. One topic that has come up a number of times is the "toy project." I've usually kept mine private - never putting them on GitHub - Somewhat concerned that people would judge me and my code. However, hypocrite that am (aren't we all?) I have advocated that others put their "Garage Sale Code" online. So here's some crappy code. ;)

The Preamble

While I've been working as an engineer for 25 years this year, I didn't graduate from school with a 4 year degree until 2003 - I just needed to get it done, for myself. I was poking around recently and found my project from OIT's CST352 "Operating Systems" class. One of the projects was to create a "Virtual CPU and OS." This is kind of a thought exercise. It's not really a parser/lexer - although there is both - and it's not a real OS. But it needs to be able to take in a made-up quasi-Assembly Language instruction set and execute them on a virtual CPU while managing virtual memory of arbitrary size. Again, a thought exercise made real to confirm that the student understands the responsibilities of a CPU.

Here's an example "application." Confused yet? Here's the original spec I was given in 2002 that includes the 36 instructions the "CPU" should understand. It has 10 general-purpose 32bit registers address as 1 through 10. Register 10 is the stack pointer. There are two bit flag registers - sign flag and zero flag.

Instructions are "opcode arg1 arg2" with constants prefixed with "$."

11 r8 ;Print r8 6 r1 $10 ;Move 10 into r1 6 r2 $6 ;Move 6 into r2 6 r3 $25 ;Move 25 into r3 23 r1 ;Acquire lock in r1 (currently 10) 11 r3 ;Print r3 (currently 25) 24 r1 ;Release r4 (currently 10) 25 r3 ;Sleep r3 (currently 25) 11 r3 ;Print r3 (currently 25) 27 ;Exit

I write my homework assignment in 2002 in the idiomatic C# of the time on .NET 1.1. That means no Generics<T> - I had to make my own strongly typed collections. That means C# has dozens of (if not a hundred) language and syntax improvements. I didn't use a Unit Testing Framework as TDD was just starting around 1999 during the XP (eXtreme Programming) days and NUnit was just getting start. It also uses "unsafe" to pin down memory in a few places. I'm sure there are WAY WAY WAY better and more sophisticated ways to do this today in idiomatic C# of 2017. Those are excuses, the real reasons are my own ignorance, ability, combined with some night-school laziness.

One of the more fun parts of this exercise was moving from physical memory (a byte array as I recall) to a full-on Memory Manager where each Process thought it could address a whole bunch of Virtual Memory while actual Physical Memory was arbitrarily sized. Then - as a joke - I would swap out memory pages as XML! ;) Yes, to be clear, it was a joke and I still love it.

You can run an "app" by passing in the total physical memory along with the text file containing the program, but you can also run an arbitrary number of programs by passing in an arbitrary number of text files! The "TinyOS" will handle each process thinking it has its own memory and will time

If you are more of a visual learner, perhaps you'd prefer this 20-slide PowerPoint on this Tiny CPU that I presented in Malaysia later that year. You dig those early 2000-era slides? I KNOW YOU DO.

Updating a .NET 1.1 app to cross-platform .NET Core 2.0

Step 1 was to download the original code from my own blog. ;) This is also Reason #4134 why you should have a blog.

I decided to use Visual Studio 2017 to upgrade it, and even worse I decided to use .NET Core 2.0 which is currently in Preview. I wanted to use .NET Core 2.0 not just because it's cross-platform but also because it promises to have a pretty large API surface area and I want this to "just work." The part about getting my old application running on Linux is going to be awesome, though.

Visual Studio then pops a scary dialog about upgrading files. NOTE that another totally valid way to do this (that I will end up doing later in this blog post) is to just make a new project and move the source files into it. Natch.

Visual Studio says it's targeting .NET 2.0 Full Framework, but I ratchet it up to 4.6 to see what happens. It builds but with a bunch of errors about Obsolete methods, the most interesting one being this one:

Warning CS0618 'ConfigurationSettings.AppSettings' is obsolete: 'This method is obsolete, it has been replaced by System.Configuration!System.Configuration.ConfigurationManager.AppSettings' C:\Users\scott\Downloads\TinyOSOLDOLD\OS Project\CPU.cs 72

That's telling me that my .NET 1/2 API will work but has been replaced in .NET 4.x, but I'm more interested in .NET Core 2.0. I could make my EXE a LIB and target .NET Standard 2.0 or I could make a .NET Core 2.0 app and perhaps get a few more APIs. I didn't do a formal analysis with the .NET Portability Analyzer but I will add that to the list of Things To Do. I may be able to make a library that works on an iPhone - a product that didn't exist when I started this assignment. That would be Just Cool(tm).

I decided to just make a new empty .NET Core 2.0 app and copy the source .cs files into it. A few interesting things.

My app also used "unsafe" code (it pins memory down and accesses it directly).

It has extensive inline documentation in comments that I used to use NDoc to make a CHM Help file. I'd like that doc to turn into HTML at some point.

It also has an appsettings.json file that needs to get copied to the output folder when it compiles.

While I could publish it to a self-contained .NET Core exe, for now I'm running it like this in my test batch files - example:

dotnet netcoreapp2.0/TinyOSCore.dll 512 scott13.txt

Here's the resulting csproj file.

<Project Sdk="Microsoft.NET.Sdk"> <PropertyGroup> <OutputType>Exe</OutputType> <TargetFramework>netcoreapp2.0</TargetFramework> <GenerateDocumentationFile>true</GenerateDocumentationFile> </PropertyGroup> <PropertyGroup> <AllowUnsafeBlocks>true</AllowUnsafeBlocks> </PropertyGroup> <ItemGroup> <None Remove="appsettings.json" /> </ItemGroup> <ItemGroup> <Content Include="appsettings.json"> <CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory> </Content> </ItemGroup> <ItemGroup> <PackageReference Include="Microsoft.Extensions.Configuration" Version="2.0.0-preview2-final" /> <PackageReference Include="Microsoft.Extensions.Configuration.Json" Version="2.0.0-preview2-final" /> <PackageReference Include="Microsoft.Extensions.DependencyInjection" Version="2.0.0-preview2-final" /> <PackageReference Include="Microsoft.Extensions.Options.ConfigurationExtensions" Version="2.0.0-preview2-final" /> </ItemGroup> </Project>

Configuration is even more different on .NET Core 2.0. This little TinyOS has a bunch of config options that come in from a .exe.config file in XML like this (truncated):

<configuration> <appSettings>  <add key="PhysicalMemory" value="128" />  <add key="ProcessMemory" value="384" /> <add key="DumpPhysicalMemory" value="true" /> <add key="DumpInstruction" value="true" /> <add key="DumpRegisters" value="true" /> <add key="DumpProgram" value="true" /> <add key="DumpContextSwitch" value="true" /> <add key="PauseOnExit" value="false" />

I have a few choices. I could make a Configuration Provider and reach .NET Core to read this format (there's an XML adapter, in fact) or make the code porting easier by moving these "name/value" pairs to a JSON file like this:

{ "PhysicalMemory": "128", "ProcessMemory": "384", "DumpPhysicalMemory": "true", "DumpInstruction": "true", "DumpRegisters": "true", "DumpProgram": "true", "DumpContextSwitch": "true", "PauseOnExit": "false", "SharedMemoryRegionSize": "16", "NumOfSharedMemoryRegions": "4", "MemoryPageSize": "16", "StackSize": "16", "DataSize": "16" }

This was just a few minutes of search and replace to change the XML to JSON. I could have also written a little app or shell script. By changing the config (rather than writing an adapter) I could then keep the code 99% the same.

My code was doing things like this (all over...there was no DI container yet):

bytesOfPhysicalMemory = uint.Parse(ConfigurationSettings.AppSettings["PhysicalMemory"]);

And I'd like to avoid major refactoring - yet. I added this bit of .NET Core configuration at the top of the EntryPoint and saved away an IConfigurationHost:

var builder = new ConfigurationBuilder() .AddJsonFile("appsettings.json"); Configuration = builder.Build();

I've got a Dictionary in the format of the IConfiguration host called "Configuration." So now I just do this in a dozen places and the app compiles again:

bytesOfPhysicalMemory = uint.Parse(Configuration["PhysicalMemory"]);

This brings up that feeling we all have when we look at old code - especially our own old code. I should have abstracted that away! Why didn't I use an interface? Why so many statics? What was I thinking?

We can beat ourselves up or we can feel good about ourselves and remember this. The app worked. It still works. There is value in it. I learned a lot. I'm a better programmer now. I don't know how far I'll take this old code but I had a lovely afternoon porting it to .NET Core 2.0 and I may refactor the heck out if it or I may not.

For now I did update the smoke tests to run on both Windows and Linux and I'm happy with the experiment.