Re: Windows advantage: quality of applications

Liste des GroupesRevenir à ol advocacy 
Sujet : Re: Windows advantage: quality of applications
De : nospam (at) *nospam* dfs.com (DFS)
Groupes : comp.os.linux.advocacy
Date : 08. May 2024, 14:31:35
Autres entêtes
Message-ID : <663b70a7$0$8099$882e4bbb@reader.netnews.com>
References : 1 2 3 4 5
User-Agent : Betterbird (Windows)
On 5/6/2024 11:46 PM, vallor wrote:
On Mon, 6 May 2024 17:19:55 -0400, DFS <nospam@dfs.com> wrote in
<6639497b$0$6450$882e4bbb@reader.netnews.com>:
 
On 5/6/2024 2:43 PM, vallor wrote:
On Mon, 06 May 2024 14:29:47 -0400, Joel <joelcrump@gmail.com> wrote in
<ib8i3jpsn8qgcsl4l3a5lin9lan9men5t1@4ax.com>:
>
vallor <vallor@cultnix.org> wrote:
>
https://imgur.com/tpY1als
>
>
I got that easily with Mint Software Manager.  Works very well.  DFS
is easily impressed.
>
I don't think there was anything in his pretty gui that couldn't
be sussed-out through the Linux command line -- either by examining
/proc or /sys; or running tools like dmidecode, cpuid, lscpu, or lsmem
(to name a few).
>
>
Hours if not days of combing thru command-line output to assemble what
HWiNFO for Windows shows in 2 seconds, in a perfect and easily navigated
layout.
 Hours if not days?  Exaggerate much?
That statement lets me know you haven't taken even a casual glance at HWiNFO.
I seriously doubt you can use any or all Linux tools to duplicate the info provided by HWiNFO (Windows).

You should try dmidecode -- I think it's been ported to Windows. 
https://gnuwin32.sourceforge.net/packages/dmidecode.htm

Handy for things like discovering what memory is installed in a machine,
including brand name, part number, and serial number.
zowie!   For memory modules, HWiNFO only gives you:
--------------------------------------------------------------------
  [General Information]
   Total Memory Size:                      16 GBytes
   Total Memory Size [MB]:                 16384
  [Current Performance Settings]
   Maximum Supported Memory Clock:         Unlimited
   Current Memory Clock:                   1855.6 MHz
   Current Timing (tCAS-tRCD-tRP-tRAS):    16-20-20-38
   Memory Channels Supported:              2
   Memory Channels Active:                 2
   Command Rate (CR):                      1T
   Read to Read Delay (tRDRD_SC) Same Chipselect: 1T
   Read to Read Delay (tRDRD_SG/TrdrdScL) Same Bank Group: 5T
   Read to Read Delay (tRDRD_SD) Same DIMM: 4T
   Read to Read Delay (tRDRD_DD) Different DIMM: 4T
   Write to Write Delay (tWRWR_SC) Same Chipselect: 1T
   Write to Write Delay (tWRWR_SG/TwrwrScL) Same Bank Group: 5T
   Write to Write Delay (tWRWR_SD) Same DIMM: 6T
   Write to Write Delay (tWRWR_DD) Different DIMM: 6T
   Read to Write Delay (tRDWR_SC) Same Chipselect: 10T
   Read to Write Delay (tRDWR_SG/TrdwrScL) Same Bank Group: 10T
   Read to Write Delay (tRDWR_DG/TrdwrScDlr) Different Bank Group: 10T
   Read to Write Delay (tRDWR_SD) Same DIMM: 10T
   Read to Write Delay (tRDWR_DD) Different DIMM: 10T
   Write to Read Delay (tWRRD_SC) Same Chipselect: 2T
   Write to Read Delay (tWRRD_SG/TwrrdScL) Same Bank Group: 2T
   Write to Read Delay (tWRRD_SD) Same DIMM: 2T
   Write to Read Delay (tWRRD_DD) Different DIMM: 2T
   Read to Precharge Delay (tRTP):         12T
   Write to Precharge Delay (tWTP):        35T
   Write Recovery Time (tWR):              24T
   RAS# to RAS# Delay (tRRD_L):            9T
   RAS# to RAS# Delay (tRRD_S):            6T
   Row Cycle Time (tRC):                   75T
   Refresh Cycle Time (tRFC):              560T
   Four Activate Window (tFAW):            34T
Row: 2 [P0 CHANNEL A/DIMM 1] - 8 GB PC4-25600 DDR4 SDRAM Corsair CMK16GX4M2E3200C16
  [General Module Information]
   Module Number:                          2
   Module Size:                            8 GBytes
   Memory Type:                            DDR4 SDRAM
   Module Type:                            Unbuffered DIMM (UDIMM)
   Memory Speed:                           1600.0 MHz (DDR4-3200 / PC4-25600)
   Module Manufacturer:                    Corsair
   Module Part Number:                     CMK16GX4M2E3200C16
   Module Revision:                        0.0
   Module Serial Number:                   N/A
   Module Manufacturing Date:              N/A
   Module Manufacturing Location:          0
   SDRAM Manufacturer:                     Samsung
   DRAM Steppping:                         0.0
   Error Check/Correction:                 None
  [Module Characteristics]
   Row Address Bits:                       16
   Column Address Bits:                    10
   Module Density:                         8192 Mb
   Number Of Ranks:                        1
   Number Of Bank Groups:                  4
   Device Width:                           8 bits
   Bus Width:                              64 bits
   Die Count:                              1
   Module Nominal Voltage (VDD):           1.2 V
   Minimum SDRAM Cycle Time (tCKAVGmin):   0.93800 ns (1066 MHz)
   Maximum SDRAM Cycle Time (tCKAVGmax):   1.50000 ns
   CAS# Latencies Supported:               7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24
   Minimum CAS# Latency Time (tAAmin):     13.500 ns
   Minimum RAS# to CAS# Delay (tRCDmin):   13.500 ns
   Minimum Row Precharge Time (tRPmin):    13.500 ns
   Minimum Active to Precharge Time (tRASmin): 33.000 ns
   Supported Module Timing at 1066.7 MHz:  15-15-15-36
   Supported Module Timing at 933.3 MHz:   13-13-13-31
   Supported Module Timing at 800.0 MHz:   11-11-11-27
   Supported Module Timing at 666.7 MHz:   9-9-9-22
   Supported Module Timing at 533.3 MHz:   8-8-8-18
   Minimum Active to Active/Refresh Time (tRCmin): 46.500 ns
   Minimum Refresh Recovery Time Delay (tRFC1min): 350.000 ns
   Minimum Refresh Recovery Time Delay (tRFC2min): 260.000 ns
   Minimum Refresh Recovery Time Delay (tRFC4min): 160.000 ns
   Minimum Four Activate Window Delay Time (tFAWmin): 21.000 ns
   Minimum Active to Active Delay Time - Different Bank Group (tRRD_Smin): 3.700 ns
   Minimum Active to Active Delay Time - Same Bank Group (tRRD_Lmin): 5.300 ns
   Minimum CAS to CAS Delay Time - Same Bank Group (tCCD_Lmin): 5.356 ns
  [Features]
   Module Temperature Sensor (TSOD):       Not Supported
   Module Nominal Height:                  31 - 32 mm
   Module Maximum Thickness (Front):       1 - 2 mm
   Module Maximum Thickness (Back):        1 - 2 mm
   Address Mapping from Edge Connector to DRAM: Standard
  [Intel Extreme Memory Profile (XMP)]
   XMP Revision:                           2.0
  [Certified Profile [Enabled]]
   Module VDD Voltage Level:               1.35 V
   Minimum SDRAM Cycle Time (tCKAVGmin):   0.62500 ns (1600 MHz)
   CAS# Latencies Supported:               7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24
   Minimum CAS# Latency Time (tAAmin):     10.000 ns
   Minimum RAS# to CAS# Delay (tRCDmin):   12.500 ns
   Minimum Row Precharge Time (tRPmin):    12.500 ns
   Minimum Active to Precharge Time (tRASmin): 23.750 ns
   Supported Module Timing at 1600.0 MHz:  16-20-20-38
   Supported Module Timing at 1466.7 MHz:  15-19-19-35
   Supported Module Timing at 1333.3 MHz:  14-17-17-32
   Supported Module Timing at 1200.0 MHz:  12-15-15-29
   Supported Module Timing at 1066.7 MHz:  11-14-14-26
   Supported Module Timing at 933.3 MHz:   10-12-12-23
   Supported Module Timing at 800.0 MHz:   8-10-10-19
   Supported Module Timing at 666.7 MHz:   7-9-9-16
   Minimum Active to Active/Refresh Time (tRCmin): 36.250 ns
   Minimum Refresh Recovery Time Delay (tRFC1min): 349.000 ns
   Minimum Refresh Recovery Time Delay (tRFC2min): 259.000 ns
   Minimum Refresh Recovery Time Delay (tRFC4min): 159.000 ns
   Minimum Four Activate Window Delay Time (tFAWmin): 22.000 ns
   Minimum Active to Active Delay Time - Different Bank Group (tRRD_Smin): 3.750 ns
   Minimum Active to Active Delay Time - Same Bank Group (tRRD_Lmin): 5.625 ns
<then the same info for each memory module>
-----------------------------------------------------------------------
HWiNFO is doomed by dmidecode -t 6

Have you checked out the 6,646-line hobbyware mess that 'hwinfo' gives you?
 Why would I?
'Cause the mission is in the name.

Or, you can get really fancy:
>
https://www.brendangregg.com/perf.html
>
Nice profiling tools.  Not meant to do what HWiNFO does, though.
 How much would the Windows license be for something like "perf", which
comes with the Linux kernel?
It's all free on Windows.
Profiling tools with:
  Visual Studio Community
  Windows Performance Analyzer
  Windows Assessment and Deployment Kit
And from everything I read online, the Windows tools are far superior to perf.

Say...when _are_ you going to try building Linux from vanilla
source? 
Good question.  In 2 decades I've tried it a couple times.

(You won't be able to build Windows from sources, of course,
because you don't *have* the sources...doesn't that *bother* you?)
A tiny bit.  But it's not my code to have, unless MS wants us to have it.
The FSF crybabies are dead wrong that it's a "user's right" to have the source code to commercial programs.

You should try it at least once.  Even if it won't boot, you can't
deny you'll learn something.
No doubt.
I actually messed with kernel compilation back in '97, right after I bought my first distro (RedHat 4.2, on CD-ROM in a book at CompUSA or Circuit City).
I remember going through that mind-boggling menuconfig and thinking "What the hell?  This puts the toy DOS to shame."

Or even, just download the source and poke around -- it is well laid-out.
I've done that many times.  Had to set Feeb straight on some things, by going to the kernel source.
I keep a folder of the extracted latest stable kernel code around at all times, for light reading.

You might even read the documentation for the mount options for the new
ntfs3 driver.  Could come in handy if you ever need to get at an NTFS
volume without Windoze getting in the way.
 Documentation/filesystems/ntfs3.rst
I mounted my DVD player from within Ubuntu WSL the other day, and it worked fine:
sudo mount -t drvfs G: g

Date Sujet#  Auteur
6 May 24 * cpu-x250vallor
6 May 24 +* Re: cpu-x74Joel
6 May 24 i+* Re: cpu-x25vallor
6 May 24 ii`* Re: cpu-x24DFS
7 May 24 ii +* Re: cpu-x15Joel
7 May 24 ii i`* Re: cpu-x14DFS
7 May 24 ii i `* Re: cpu-x13Joel
8 May 24 ii i  `* Re: cpu-x12DFS
15 May 24 ii i   `* Re: cpu-x11Lawrence D'Oliveiro
15 May 24 ii i    `* Re: cpu-x10DFS
15 May 24 ii i     `* Re: cpu-x9vallor
15 May 24 ii i      `* Re: cpu-x8DFS
17 May 24 ii i       `* Re: cpu-x7vallor
17 May 24 ii i        `* Re: cpu-x6DFS
17 May 24 ii i         +- Re: cpu-x1vallor
17 May 24 ii i         `* Re: cpu-x4vallor
18 May 24 ii i          `* Re: cpu-x3DFS
18 May 24 ii i           `* Re: cpu-x2vallor
18 May 24 ii i            `- Re: cpu-x1DFS
7 May 24 ii +* Linux advantage: open source (was: Re: cpu-x)5vallor
8 May 24 ii i`* Re: Windows advantage: quality of applications4DFS
8 May 24 ii i `* Re: Windows advantage: quality of applications3rbowman
8 May 24 ii i  +- Re: Windows advantage: quality of applications1DFS
9 May 24 ii i  `- Re: Windows advantage: quality of applications1Chris Ahlstrom
12 May 24 ii +- Re: cpu-x1Lawrence D'Oliveiro
12 May 24 ii `* Re: cpu-x2Lawrence D'Oliveiro
14 May 24 ii  `- Re: cpu-x1candycanearter07
6 May 24 i`* Re: cpu-x48DFS
6 May 24 i `* Re: cpu-x47Joel
8 May 24 i  +- Re: cpu-x1Joel
9 May 24 i  +* Re: cpu-x3rbowman
9 May 24 i  i`* Re: cpu-x2Joel
9 May 24 i  i `- Re: cpu-x1rbowman
9 May 24 i  `* Re: cpu-x42rbowman
9 May 24 i   +* Re: cpu-x23Chris Ahlstrom
10 May 24 i   i`* Re: cpu-x22vallor
10 May 24 i   i +- Re: cpu-x1%
10 May 24 i   i +* Re: cpu-x8rbowman
10 May 24 i   i i`* Re: cpu-x7vallor
10 May 24 i   i i +- Every cult needs an apocalypse.1Relf
10 May 24 i   i i +- Re: cpu-x1vallor
10 May 24 i   i i +- Re: cpu-x1Andrzej Matuch
10 May 24 i   i i +* Re: cpu-x2Chris Ahlstrom
11 May 24 i   i i i`- Re: cpu-x1RonB
10 May 24 i   i i `- Re: cpu-x1rbowman
10 May 24 i   i `* Re: cpu-x12Chris Ahlstrom
10 May 24 i   i  +* Re: cpu-x3vallor
10 May 24 i   i  i`* Re: cpu-x2Chris Ahlstrom
11 May 24 i   i  i `- Re: cpu-x1rbowman
10 May 24 i   i  `* Re: cpu-x8RonB
10 May 24 i   i   `* Re: cpu-x7rbowman
11 May 24 i   i    +* Re: cpu-x5RonB
11 May 24 i   i    i+- Re: cpu-x1rbowman
12 May 24 i   i    i`* Re: cpu-x3RonB
12 May 24 i   i    i `* Re: cpu-x2Andrzej Matuch
12 May 24 i   i    i  `- Re: cpu-x1RonB
11 May 24 i   i    `- Re: cpu-x1Chris Ahlstrom
18 May 24 i   `* Re: cpu-x18DFS
18 May 24 i    +* Re: cpu-x10Joel
19 May 24 i    i`* Re: cpu-x9candycanearter07
19 May 24 i    i `* Re: cpu-x8Joel
19 May 24 i    i  +* Re: cpu-x2rbowman
19 May 24 i    i  i`- The almighty LLama has the final say.1Relf
24 May 24 i    i  `* Re: cpu-x5candycanearter07
24 May 24 i    i   `* Re: cpu-x4Joel
25 May 24 i    i    `* Re: cpu-x3candycanearter07
25 May 24 i    i     `* Re: cpu-x2Andrzej Matuch
25 May 24 i    i      `- Re: cpu-x1Joel
18 May 24 i    `* Re: cpu-x7rbowman
18 May 24 i     `* Re: cpu-x6DFS
19 May 24 i      `* Re: cpu-x5rbowman
19 May 24 i       +* Re: cpu-x2rbowman
19 May 24 i       i`- Re: cpu-x1Stéphane CARPENTIER
19 May 24 i       `* Re: cpu-x2Chris Ahlstrom
19 May 24 i        `- Re: cpu-x1rbowman
6 May 24 +* Re: cpu-x173Andrzej Matuch
7 May 24 i`* Re: cpu-x172DFS
7 May 24 i +* Re: cpu-x6Andrzej Matuch
7 May 24 i i+- Re: cpu-x1DFS
7 May 24 i i`* HyperV error (was: Re: cpu-x)4vallor
7 May 24 i i +* Re: HyperV error2DFS
7 May 24 i i i`- Re: HyperV error1Joel
7 May 24 i i `- Re: HyperV error1Chris Ahlstrom
8 May 24 i `* Re: cpu-x165Lawrence D'Oliveiro
8 May 24 i  `* Re: cpu-x164Andrzej Matuch
8 May 24 i   +* Re: cpu-x8Andrzej Matuch
8 May 24 i   i`* Re: cpu-x7candycanearter07
8 May 24 i   i `* Re: cpu-x6Andrzej Matuch
10 May 24 i   i  `* Re: cpu-x5Lawrence D'Oliveiro
10 May 24 i   i   +- Re: cpu-x1RonB
14 May 24 i   i   `* Re: cpu-x3candycanearter07
14 May 24 i   i    `* Re: cpu-x2Lawrence D'Oliveiro
14 May 24 i   i     `- Re: cpu-x1Andrzej Matuch
10 May 24 i   `* Re: cpu-x155Lawrence D'Oliveiro
10 May 24 i    +- Re: cpu-x1RonB
11 May 24 i    `* Re: cpu-x153DFS
12 May 24 i     +* Re: cpu-x7RonB
12 May 24 i     i`* Re: cpu-x6Andrzej Matuch
12 May 24 i     i `* Re: cpu-x5RonB
15 May 24 i     i  `* Re: cpu-x4RonB
15 May 24 i     i   `* Re: cpu-x3Andrzej Matuch
13 May 24 i     +* Re: cpu-x125Lawrence D'Oliveiro
13 May 24 i     +* Re: cpu-x16Lawrence D'Oliveiro
14 May 24 i     `* Re: cpu-x4candycanearter07
6 Jun 24 `* Re: cpu-x2vallor

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal