Author Topic: graphic interface for smartahci  (Read 4242 times)

ivan

  • Hero Member
  • *****
  • Thank You
  • -Given: 2
  • -Receive: 35
  • Posts: 1043
    • View Profile
graphic interface for smartahci
« on: October 24, 2019, 02:40:48 pm »
This may be a strange request but does anyone know of a graphic interface to smartahci like the one for smartmon for IDE drives?  Also is there a way of reducing the information produced by smartahci -a hd1 to just the important info and temp?

Mentore

  • Jr. Member
  • **
  • Thank You
  • -Given: 15
  • -Receive: 1
  • Posts: 63
    • View Profile
Re: graphic interface for smartahci
« Reply #1 on: October 28, 2019, 08:32:20 am »
This may be a strange request but does anyone know of a graphic interface to smartahci like the one for smartmon for IDE drives?  Also is there a way of reducing the information produced by smartahci -a hd1 to just the important info and temp?

I feel like some Visual REXX could do the trick. Then I have to say I can't even start up my eCS machine right now, too bad...

Andi B.

  • Sr. Member
  • ****
  • Thank You
  • -Given: 1
  • -Receive: 21
  • Posts: 457
    • View Profile
Re: graphic interface for smartahci
« Reply #2 on: October 28, 2019, 09:41:33 am »
Isn't
Code: [Select]
smartahci -a hd1 | grep -i "temp" good enough? Should work with find instead of grep too.
« Last Edit: October 28, 2019, 09:43:13 am by Andi B. »

ivan

  • Hero Member
  • *****
  • Thank You
  • -Given: 2
  • -Receive: 35
  • Posts: 1043
    • View Profile
Re: graphic interface for smartahci
« Reply #3 on: October 28, 2019, 11:22:18 am »
Hi Andi,

Sorry that doesn't work because it 'sees everything after the -a as more device names and it requires only one device.

the error message is:
C:\smartahci -a hd1 | grep -i "temp"
smartctl version 5.37 [i386-pc-ibmvac365] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

ERROR: smartctl takes ONE device name as the final command-line argument.
You have provided 3 device names:
hd1
¦
grep

Use smartctl -h to get a usage summary

Edit:
I have found you can only pipe it off to a file which I then have to pick through to get the information I want, Dani managed to get a graphical interface for her IDE version so it must be possible
.
« Last Edit: October 28, 2019, 11:31:57 am by ivan »

ivan

  • Hero Member
  • *****
  • Thank You
  • -Given: 2
  • -Receive: 35
  • Posts: 1043
    • View Profile
Re: graphic interface for smartahci
« Reply #4 on: October 30, 2019, 05:21:01 pm »
OK, I have got a little further, I can now get the main information by using  smartahci -A hd1 > some text file  which gives

smartctl 6.6 2017-04-23 r4424 [i386-pc-os2-emx] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   116   099   006    Pre-fail  Always       -       109444736
  3 Spin_Up_Time            0x0003   098   097   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       26
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   076   060   030    Pre-fail  Always       -       47200953
  9 Power_On_Hours          0x0032   094   094   000    Old_age   Always       -       5878
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       29
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       1
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   062   051   045    Old_age   Always       -       38 (Min/Max 24/48)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       20
193 Load_Cycle_Count        0x0032   093   093   000    Old_age   Always       -       14984
194 Temperature_Celsius     0x0022   038   049   000    Old_age   Always       -       38 (0 14 0 0 0)
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       1021 (61 65 0)
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       995271562
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       880064779


Which leaves me wondering hoe to get a graphics display like the attachment.

Any Ideas?

Doug Bissett

  • Hero Member
  • *****
  • Thank You
  • -Given: 1
  • -Receive: 47
  • Posts: 1261
    • View Profile
Re: graphic interface for smartahci
« Reply #5 on: October 30, 2019, 05:51:16 pm »
I will comment here, that I do not trust anything that, so called, smart monitoring tells me. I have (had) one disk that never showed any problem, but just plain wouldn't work because of errors. I have another disk, that has been telling me that total failure has already happened, but it continues to work, with no problems, after 10 years (I do need to turn off the BIOS checking, or it refuses to use the disk). I had another one, that told me that all was well, and it became unusable 3 days later.

Use it if you want to, but be very wary of what it tells you. Better to spend your time doing backups.

ivan

  • Hero Member
  • *****
  • Thank You
  • -Given: 2
  • -Receive: 35
  • Posts: 1043
    • View Profile
Re: graphic interface for smartahci
« Reply #6 on: October 30, 2019, 06:18:43 pm »
I agree with you Doug especially about backups.  If used properly the SMART information can be useful (in the graphic the attributes marked with * are the ones to watch.  I have had a couple of disks that worked but it took them up to 5 minutes to spin up so they got pensioned off before the stopped spinning at all.  Relocated sector count is another one to watch because disks only have a limited number of sectors to relocate and when they are used up problems start.

SMART data isn't for general use, you have to know what you are reading and how it interacts with the disk electronics firmware.

Dave Yeo

  • Hero Member
  • *****
  • Thank You
  • -Given: 11
  • -Receive: 152
  • Posts: 2227
    • View Profile
Re: graphic interface for smartahci
« Reply #7 on: October 31, 2019, 12:48:02 am »
OK, I have got a little further, I can now get the main information by using  smartahci -A hd1 > some text file  which gives
...
Which leaves me wondering hoe to get a graphics display like the attachment.

Any Ideas?

Might be as simple as setting the correct terminal (doubtful as I don't see any ansi) or more likely, need compiling with ansi support. I don't have an ahci adapter so can't test but assuming it shares the same source as smartmon, it should be able to output the correct ansi.

Rick C. Hodgin

  • Newbie
  • *
  • Thank You
  • -Given: 1
  • -Receive: 1
  • Posts: 34
    • View Profile
Re: graphic interface for smartahci
« Reply #8 on: October 31, 2019, 02:42:29 am »
OK, I have got a little further, I can now get the main information by using  smartahci -A hd1 > some text file  which gives

Code: [Select]
=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   116   099   006    Pre-fail  Always       -       109444736
  3 Spin_Up_Time            0x0003   098   097   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       26
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   076   060   030    Pre-fail  Always       -       47200953
  9 Power_On_Hours          0x0032   094   094   000    Old_age   Always       -       5878
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       29
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       1
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   062   051   045    Old_age   Always       -       38 (Min/Max 24/48)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       20
193 Load_Cycle_Count        0x0032   093   093   000    Old_age   Always       -       14984
194 Temperature_Celsius     0x0022   038   049   000    Old_age   Always       -       38 (0 14 0 0 0)
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       1021 (61 65 0)
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       995271562
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       880064779

Which leaves me wondering hoe to get a graphics display like the attachment.

Any Ideas?

It looks like the Worst column is used for the indicator.  When it's 100, it has red, yellow, yellow, then full greens.  When it was 99, it drops down one, same with 92.  When it was 82 or 75, it had fewer greens.

It seems to just be a projection of that value relative to what it should be.  Some values seem to be up to 100.  Others 200.  Others 255.

Something like (off the top of my head, untested):
Code: [Select]
char ansi_red[]     = "whatever the code is for ANSI red";
char ansi_yellow[]  = "whatever the code is for ANSI yellow";
char ansi_green[]   = "whatever the code is for ANSI green";
char ansi_normal[]  = "whatever the code is for ANSI normal";

// See http://ascii-table.com/ansi-escape-sequences.php
// Possibly the codes are ... don't know, haven't used them since DOS days in 90s:
// ansi_red    = "\033[1;31;40m";
// ansi_yellow = "\033[1;33;40m";
// ansi_green  = "\033[1;32;40m";
// ansi_normal = "\033[0;37;40m";

char* get_indicator(int value, int max_value, int& len)
{
    int   s, d;
    char* ind;

    // Make sure the parameters are in range
    max_value = max(max_value, 1);
    value = min(value, max_value);

    // Get the length we'll need
    len = (int)(10.0f * (float)value / (float)max_value);

    // Allocate the maximum length we'll need for the indicator
    ind = malloc(   ((len >= 1) ? sizeof(ansi_red)    : 0)
                  + ((len >= 2) ? sizeof(ansi_yellow) : 0)
                  + ((len >= 4) ? sizeof(ansi_green)  : 0)
                  + len
                  + sizeof(ansi_normal) + 1  );

    // Render it in ANSI
    for (s = 0, d = 0; s < len; ++s)
    {
        // Add any ANSI codes:
        if (s == 0)
        {
            // Add red
            memcpy(ind + d, ansi_red, sizeof(ansi_red) - 1);
            d += sizeof(ansi_red) - 1;

        } else if (s == 1) {
            // Add yellow
            memcpy(ind + d, ansi_yellow, sizeof(ansi_yellow) - 1);
            d += sizeof(ansi_yellow) - 1;

        } else if (s == 3) {
            // Add green
            memcpy(ind + d, ansi_green, sizeof(ansi_green) - 1);
            d += sizeof(ansi_green) - 1;
        }

        // Store the thick hyphen character
        ind[d++] = 22;
    }

    // Add the trailing restore to normal coloring
    memcpy(ind + d, ansi_normal, sizeof(ansi_normal) - 1);
    d += sizeof(ansi_normal) - 1;
    ind[d] = 0;

    // Return our result
    return ind;
    // Note:  len is updated to the number of thick hyphen characters to be displayed, not the string length
}

If you are able to parse that data in raw text content, you could generate the display using something like ANSI escape codes and the ASCII 22 character.  Or paint it on the terminal using color attributes.  In either case, something like the above should work.

Make sure you free() the return value later.
« Last Edit: October 31, 2019, 01:36:23 pm by Rick C. Hodgin »

Rick C. Hodgin

  • Newbie
  • *
  • Thank You
  • -Given: 1
  • -Receive: 1
  • Posts: 34
    • View Profile
Re: graphic interface for smartahci
« Reply #9 on: November 01, 2019, 02:00:06 am »
It looks like the Worst column is used for the indicator.  When it's 100, it has red, yellow, yellow, then full greens.  When it was 99, it drops down one, same with 92.  When it was 82 or 75, it had fewer greens.

It seems to just be a projection of that value relative to what it should be.  Some values seem to be up to 100.  Others 200.  Others 255.

Something like (off the top of my head, untested):
Code: [Select]
// Snip

If you are able to parse that data in raw text content, you could generate the display using something like ANSI escape codes and the ASCII 22 character.  Or paint it on the terminal using color attributes.  In either case, something like the above should work.

Make sure you free() the return value later.

Here's an actual program that displays some colorize results.  It doesn't handle the ID#... header line properly, but it does demonstrate the general idea.

Code: [Select]
// Set your font small enough so you can see the screen
// [C:\] mode 120,40

// Compiled in Borland C++ for OS/2 Version 2.0

#include <os2.h>
#include <stdlib.h>
#include <stdio.h>
#include <memory.h>

#define max(a,b) ((a) >= (b) ? (a) : (b))
#define min(a,b) ((a) <= (b) ? (a) : (b))

char text[] = "  === START OF READ SMART DATA SECTION ===\r\n"
"SMART Attributes Data Structure revision number: 10\r\n"
"Vendor Specific SMART Attributes with Thresholds:\r\n"
      /*           111111111122222222223333333333444444444455555555556666666666777777777788888888889999999999 */
      /* 0123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789 */
"ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE\r\n"
"  1 Raw_Read_Error_Rate     0x000f   116   099   006    Pre-fail  Always       -       109444736\r\n"
"  3 Spin_Up_Time            0x0003   098   097   000    Pre-fail  Always       -       0\r\n"
"  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       26\r\n"
"  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0\r\n"
"  7 Seek_Error_Rate         0x000f   076   060   030    Pre-fail  Always       -       47200953\r\n"
"  9 Power_On_Hours          0x0032   094   094   000    Old_age   Always       -       5878\r\n"
" 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0\r\n"
" 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       29\r\n"
"183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0\r\n"
"184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0\r\n"
"187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0\r\n"
"188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       1\r\n"
"189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0\r\n"
"190 Airflow_Temperature_Cel 0x0022   062   051   045    Old_age   Always       -       38 (Min/Max 24/48)\r\n"
"191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0\r\n"
"192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       20\r\n"
"193 Load_Cycle_Count        0x0032   093   093   000    Old_age   Always       -       14984\r\n"
"194 Temperature_Celsius     0x0022   038   049   000    Old_age   Always       -       38 (0 14 0 0 0)\r\n"
"197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0\r\n"
"198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0\r\n"
"199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0\r\n"
"240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       1021 (61 65 0)\r\n"
"241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       995271562\r\n"
"242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       880064779\r\n";

// See http://ascii-table.com/ansi-escape-sequences.php
char ansi_red[]     = "\033[1;31;40m";
char ansi_yellow[]  = "\033[1;33;40m";
char ansi_green[]   = "\033[1;32;40m";
char ansi_normal[]  = "\033[0;37;40m";

char* get_indicator(int value, int max_value)
{
    int   s, d, len;
    char* ind;

    // Make sure the parameters are in range
    max_value = max(max_value, 1);
    value = min(value, max_value);

    // Get the length we'll need
    len = (int)(10.0f * (float)value / (float)max_value);

    // Allocate the maximum length we'll need for the indicator
    ind = (char*)malloc(  ((len >= 1) ? sizeof(ansi_red)    : 0)
+ ((len >= 2) ? sizeof(ansi_yellow) : 0)
+ ((len >= 4) ? sizeof(ansi_green)  : 0)
+ 10
+ sizeof(ansi_normal) + 1  );

    // Render it in ANSI
    for (s = 0, d = 0; s < len; ++s)
    {
// Add any ANSI codes:
if (s == 0)
{
    // Add red
    memcpy(ind + d, ansi_red, sizeof(ansi_red) - 1);
    d += sizeof(ansi_red) - 1;

} else if (s == 1) {
    // Add yellow
    memcpy(ind + d, ansi_yellow, sizeof(ansi_yellow) - 1);
    d += sizeof(ansi_yellow) - 1;

} else if (s == 3) {
    // Add green
    memcpy(ind + d, ansi_green, sizeof(ansi_green) - 1);
    d += sizeof(ansi_green) - 1;
}

// Store the thick hyphen character
ind[d++] = 22;
    }

    // Add the trailing restore to normal coloring
    memcpy(ind + d, ansi_normal, sizeof(ansi_normal) - 1);
    d += sizeof(ansi_normal) - 1;

    // Add in any trailing spaces
    for ( ; s < 10; ++s)
ind[d++] = 32;

    // NULL terminate and return
    ind[d] = 0;
    return ind;
}

int verify_hex(char* p, int len)
{
    int   i;
    char  c;


    // Must begin with 0x
    if (!memicmp(p, "0x", 2) == 0)
return 0;

    // Every character must be 0_9a_fA_F
    for (i = 2; i < len; ++i)
    {
c = p[i];
if (!(c >= '0' && c <= '9') && !(c >= 'a' && c <= 'f') && !(c >= 'A' && c <= 'F'))
    return 0;
    }

    // It's hex
    return 1;
}

int verify_dec(char* p, int len)
{
    int i;


    // Every character must be 0_9
    for (i = 0; i < len; ++i)
    {
if (p[i] < '0' || p[i] > '9')
    return 0;
    }

    // It's dec
    return 1;
}

int display_line(int tnOffset)
{
    int     lnLength, lnValue, lnWorst;
    int     llTest1, llTest2, llTest3, llTest4;
    char    c;
    char*   p;
    char*   p2;


    // Find out where this line ends
    for (lnLength = 0, p = text + tnOffset; *p != 0; ++lnLength, ++p)
    {
// Is it CR or LF?
if (*p == 13 || *p == 10)
{
    // We're done here
    break;
}
    }

    // Verify the signatures
    llTest1 = verify_hex(text + tnOffset + 28, 6); // hex at 28,6 flag
    llTest2 = verify_dec(text + tnOffset + 37, 3); // dec at 37,3 value
    llTest3 = verify_dec(text + tnOffset + 43, 3); // dec at 43,3 worst
    llTest4 = verify_dec(text + tnOffset + 49, 3); // dec at 49,3 thresh
    if (llTest1 && llTest2 && llTest3 && llTest4)
    {
// It's an indicator line
// Print up to the worst part
p2  = text + tnOffset + 43;
c   = *p2;
*p2 = 0;
printf("%s", text + tnOffset);
*p2 = c;

// Grab the value
lnValue = 100; // assume 100 atoi(text + tnOffset + 37);
lnWorst = atoi(text + tnOffset + 43);

// Print the indicator
printf("%s", (p2 = get_indicator(lnWorst, lnValue)));
free(p2);

// Print the trailing part
c = *p;
*p = 0;
printf("%s\n", text + tnOffset + 48);
*p = c;

    } else {
// Just a regular line
c = *p;
*p = 0;
printf("%s\n", text + tnOffset);
*p = c;
    }

    // Skip past any CR/LF combos
    for ( ; *p != 0; ++lnLength)
    {
c = text[tnOffset + lnLength];
if (c != 13 && c != 10)
    break;
    }

    // All done
    return lnLength;
}

int main(int argc, char* argv[])
{
    int lnI;

    // Code could be added here to read a file from the command
    // line and load into char* text, rather than using the hard-coded
    // example.  It could also be used to read from STDIN so it can
    // be piped to as in smartdrv > colorize.

    // For illustration purposes only.  Should be modified and extended if used.

    // Display each line
    for (lnI = 0; text[lnI] != 0; )
lnI += display_line(lnI);

    return 0;
}
« Last Edit: November 01, 2019, 02:09:41 am by Rick C. Hodgin »

Andi B.

  • Sr. Member
  • ****
  • Thank You
  • -Given: 1
  • -Receive: 21
  • Posts: 457
    • View Profile
Re: graphic interface for smartahci
« Reply #10 on: November 01, 2019, 11:16:06 am »
Hi Andi,
Sorry that doesn't work because it 'sees everything after the -a as more device names and it requires only one device.
....
I don't think that's true. Here is what I get -
Code: [Select]
{0}[m:\] smartahci -a hd1 | grep -i "temp"
194 Temperature_Celsius     0x0022   111   104   000    Old_age   Always       -       39

{0}[m:\]

{0}[m:\] smartahci
smartctl version 5.37 [i386-pc-ibmvac365] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

I guess you've no grep installed. As mentioned above you can use find instead.
Code: [Select]
{1025}[m:\] smartahci -a hd1 | find /i "temp"
194 Temperature_Celsius     0x0022   111   104   000    Old_age   Always       -       39

But the semi-graphic output you posted is from a different program namely smartmon. If you look into the readme you will see this is from
Code: [Select]
SMARTMON.EXE is maintained by Andrew Belov <andrew_belov@newmail.ru>.
Maybe you can convince Andrew to update his program to os2ahci. Or you look into the included source code and try to do it yourself.

Btw. I'm not sure if this version of smartahci was really build by Bruce Allen. I seem to remember David did this version. Please correct me if I'm wrong.

ivan

  • Hero Member
  • *****
  • Thank You
  • -Given: 2
  • -Receive: 35
  • Posts: 1043
    • View Profile
Re: graphic interface for smartahci
« Reply #11 on: November 01, 2019, 12:41:12 pm »
Hi Andi,

I have both smartahci and smartctl (smartmontools v6.6 r4424 from hobbes)installed on my test machine.  Both give the same information to the -A command with the difference being that smartahci requires the hd1 disk identifier while smartctl uses ahci1 for ahci drives and hd1 for ide disks.

I have to admit that I like the GUI from smartmon that I grabbed from my old Acer notebook.  As for me trying to modify any program, I don't stand a chance unless it is written in assembler, I am a hardware engineer not programmer.

I know there is a GUI for smartmontools for everything except OS/2 but again the problem is porting it - where would I start?.

 

Rick C. Hodgin

  • Newbie
  • *
  • Thank You
  • -Given: 1
  • -Receive: 1
  • Posts: 34
    • View Profile
Re: graphic interface for smartahci
« Reply #12 on: November 01, 2019, 01:09:13 pm »
As for me trying to modify any program, I don't stand a chance unless it is written in assembler, I am a hardware engineer not programmer.

Hi Ivan.  Have you ever designed a CPU?
« Last Edit: November 01, 2019, 01:12:34 pm by Rick C. Hodgin »

ivan

  • Hero Member
  • *****
  • Thank You
  • -Given: 2
  • -Receive: 35
  • Posts: 1043
    • View Profile
Re: graphic interface for smartahci
« Reply #13 on: November 01, 2019, 01:57:59 pm »
Hi Rick,

Not one of the latest ones but I did before the 8080 came out - it was a monster made up of discrete components on a bread board just to show ir could be done.

Rick C. Hodgin

  • Newbie
  • *
  • Thank You
  • -Given: 1
  • -Receive: 1
  • Posts: 34
    • View Profile
Re: graphic interface for smartahci
« Reply #14 on: November 01, 2019, 02:36:40 pm »
Hi Rick,

Not one of the latest ones but I did before the 8080 came out - it was a monster made up of discrete components on a bread board just to show ir could be done.

There was a movie I saw in the mid-90s called TimeCop.  A somewhat interesting movie, but there was a scene where a designer / visionary was creating his new CPU and you could see the design schematics on the huge floor display.  I remember thinking how neat that was.  Since then I've come across some documentaries I've found interesting:

Fairchild documentary on making transistors
Designer of the 6502
Reconstructing the 6502 from schematics

And of course there's the recent book "But How Do It Know?" made into a video with the Scott CPU:
How a CPU works

I wrote a single-step capable emulator for the Scott CPU. :-)

I've been working on two CPUs of my own.  One is a 40-bit in-order 80386 with several newer instructions.  It's 40-bit because that's 1 TB of data, and I can't imagine a CPU needing more than that, but I can imagine it needing more than 4 GB (32-bit).  It has a few models, the top model of which is four-core, supports a type of hyperthreading I call Love Threading because cores can sacrificially come over and help the other core out on its serial workload, making loop processing faster, for example.  And several other interesting extensions / features.

The other is a radical design I've never seen before.  I call it Inspire.  I hope to have it published by the end of next year.

-----
If you ever want help learning about GUI programming let me know.  I used to program almost entirely in assembly, then later C and C++.  Today I use multiple tools because I recognize that not every job needs to be fast.  At the higher levels you can sometimes do things that are pretty and awesome from a user's point of view, even if they're very inefficient from a hardware point of view.  Sometimes it's about productivity, not efficiency, at least when inefficiency on modern hardware runs far faster than efficiency did on the hardware of a couple decades ago.

I'd like to hear about your CPU project sometime.  PM me or email privately if you wish.
« Last Edit: November 01, 2019, 02:39:21 pm by Rick C. Hodgin »