HDDScan blocks colours

[dfr]

Couldn't they change in the future version of HDDScan colours of the blocks
in the map of surface scan, so that < 500 ms is yellow, > 500 ms is
orange, and bad blocks are red?
This is because at the moment it is very difficult quickly surveying the
map to spot dark blue blocks of bad sectors, as they are too similar to
dark grey.

[Doomer]

All the bad sector numbers are in report
Look there and you don't need to review the map

[dfr]

All the bad sector numbers are in report
Look there and you don't need to review the map

I know, but I want to see them on the map.
In my opinion the colours which I proposed would make more sense, than the ones which are there now.

[Doomer]

It would, for you, probably
But what about users who already got used to the current colors?

[dfr]

It would, for you, probably

For everyone it would be better, because the colours I proposed are objectively better for that purpose.

But what about users who already got used to the current colors?

Are you suggesting that they would have troubles to get used to new colours? I doubt it. I also doubt that there are many users who use this option of the software so often to really get used to it, but even if so, I believe that it shouldn't restrain the programmer from changing it into objectively better colours.

[Doomer]

I believe that it shouldn't restrain the programmer from changing it into objectively better colours.

sure
Once I'm convinced that it's a lot better I will change it

[dfr]

I believe that it shouldn't restrain the programmer from changing it into objectively better colours.

sure
Once I'm convinced that it's a lot better I will change it

Why aren't you convinced?
Can't you see that red is easier to spot than dark blue? Red also means warning about something, it draws your attention (hence red lights on streets, red, orange or yellow clothing for some workers or prisoners etc.), thus red is the perfect and the most obvious colour to mark bad sectors (because they are bad, and not good).

Also have a look at the colours of the rainbow: after green you have yellow, and then orange, and then red, that's because green has shorter wavelenght than yellow, yellow than orange, orange than red.
So it is natural to have yellow after green, yet in HDDScan yellow is missed, instead of it is orange, then red, which would have much better use for bad blocks.
Dark blue colour is cold colour - it does not warn us about bad blocks, quite the opposite this colour makes us calm, we associate it with dark blue ocean or sky, so "nothing happend, everything is ok, because the colour is blue".
So how can bad blocks be marked blue and not red? This is just illogical, there is no common sense in it.
I have marked some fonts here blue (colour as dark as bad blocks in HDDScan) and on my monitor (CRT) I can barely distinguish between them and black fonts, while red is drawing my attention, and bad blocks should be drawing my attention, shoudn't they.

[fzabkar]

What I don't like about HDDScan is the illogical SMART report format.

Why display the threshold values at the end of the line? Why not instead have the raw values at the end like everybody else?

I'd also like to see the actual raw value of the temperature attributes, not just their interpreted values.

And please correct the "Reallocation (sic) Sector Count" attribute line.

I agree with dfr in that red should be the obvious colour for bad sectors.

[dfr]

I also wish that it would be possible to save the whole map, so that it could be displayed later for example in a web broser or that it would be possible to make a screenshot of the entire map (not just the part visible at the moment, but entire map - I know that it would be a very, very long map, but nevertheless if saved in PNG or GIF format it would not take too much disk space, so it would be reasonable to be able to make that screenshot from within the HDDScan program).

[Doomer]

Why display the threshold values at the end of the line? Why not instead have the raw values at the end like everybody else?

so, what is so illogical in this?

I'd also like to see the actual raw value of the temperature attributes, not just their interpreted values.

Good point, worth to consider

And please correct the "Reallocation (sic) Sector Count" attribute line.

How exactly?

[Doomer]

dfr, how about magenta for bad blocks?

[guru]

Maybe you can make HDDScan_Hippy.exe which is full of rainbows, butterflies and LSD[/color]

Last edited by guru on February 7th, 2011, 10:48, edited 2 times in total.

[dfr]

dfr, how about magenta for bad blocks?

Much better than dark blue, but as fzabkar and I said red is the most obvious, as it is used internationally as a warning/attention colour.

[dfr]

[color=#FF80BF]Maybe you can make HDDScan_Hippy.exe which is full of rainbows, butterflies and LSD[/color]

Don't be ridiculous. We are serious here.

[guru]

it was just fun.... I'm waiting to be flamed!

[Doomer]

Much better than dark blue, but as fzabkar and I said red is the most obvious, as it is used internationally as a warning/attention colour.

red is already occupied
I prefer not to use occupied colors

[dfr]

it was just fun....

Yeah, I know.

[dfr]

Much better than dark blue, but as fzabkar and I said red is the most obvious, as it is used internationally as a warning/attention colour.

red is already occupied
I prefer not to use occupied colors

As you wish. I already suggested to add yellow between green and orange, and then red would move into bad block position, but magenta is acceptable - at least it would be much easier to spot than dark blue.

I hope that you can also do something to save the whole map to view it later.

[dfr]

One more request to add to wishlist of HDDScan improvements.

Have a look at this thread:
how-identify-which-files-are-assigned-bad-sectors-t18552.html

Could you please make it possible that when clicking on the bad sector on the map in HDDScan not only its LBA number could be seen but also a file name (and path if possible to that file) assigned to that bad sector?

[Doomer]

not possible
HDDScan doesn't work with filesystems