Since 6.7.0 | frontview status hdd drives has a bad layout

[TT_DE]

Since 6.7.0 the rontview status for hdd drives has a bad layout. 

What could I do to get back the proper layout?

[StephenB]

This was reported on another thread too.  AFAIK there is no workaround. 

[TT_DE]

OK, thank you. Sorry for double posting this issue.

Seems we have to wait to the next OS update ?

[TT_DE]

wasn't solved by firmware update to 6.7.1

@ netgear team: any ambition to solve this issue with the next update?

[Sandshark]

Looks like a failure to test with all languages and potential drive model number lengths.  It's fine on my Pro2 with 6.7.1.  But "Disk 2" is a lot shorter than the German equivalent and the drives are Seagates with an eleven character model number.

[StephenB]

It fails on both my RN52x NAS, which are both set to English.  

[Sandshark]

The length of the drive part number must be the factor affecting it, then.  I only have 6.7.1 on the one NAS with Seagate drives.

[cpu8088]

i cannot see the point of showing temperature in both C and F.

this has been around 3 years ago and not fixed.

[StephenB]

---

@cpu8088 wrote:

i cannot see the point of showing temperature in both C and F.

---

Most Americans are used to F, and can't easily translate from C without doing the math.  Many people in other regions have the same challenge going F->C. Whichever one you show, you will get complaints, and it doesn't seem to be worth a configuration item.

I think it's reasonable to show both, and they certainly have the screen real estate.  You don't want users to be mistaken about the termperature.

One place where configuration should be provided is the time and date format - another long standing complaint.

@Sandshark wrote:

The length of the drive part number must be the factor affecting it, then.

---

Could be.  That's the one line that isn't wrapped.

[BaJohn]

An easy workaround is to use Chrome instead of Edge on Windows 10.

I have both open at the moment (and if I were clever enough I would provide a screenshot).

Edge has the problem and Chrome does NOT.

Note I am running OS 6.7.1.

[BaJohn]

[BaJohn]

Managed it eventually.

Also both systems as displayed are not affected by scaling.

i.e. Edge is always a problem regardless of size.

and Chrome works correctly regardless of size.

Hope this helps.....

NOTE:- Still a problem at OS 6.7.1

[StephenB]

---

@BaJohn wrote:

Edge has the problem and Chrome does NOT.

---

Chrome is my default browser, and my screenshot earlier in the thread was taken from that.

Plus I see the identical layout with Firefox, IE-11, Edge and Safari (iPad).

[TT_DE]

I am using 6.7.1 and Chrome: still having a bad layout

[BaJohn]

---

@TT_DE wrote:

I am using 6.7.1 and Chrome: still having a bad layout

---

Maybe it is the Windows OS that is different ... My NAS is RN516, but I am running Win 10 Pro (64 bit).

[StephenB]

---

BaJohn wrote:

---

Maybe it is the Windows OS that is different ... My NAS is RN516, but I am running Win 10 Pro (64 bit).

---

Not in my case.  Every browser I've tried on win10, win7, and iOS all show the bad layout.

[jak0lantash]

The layout is OK for me.

Chrome on W10_x64, and Chrome on iPad.

[BaJohn]

---

@StephenB wrote:

---

@BaJohn wrote:

---

Maybe it is the Windows OS that is different ... My NAS is RN516, but I am running Win 10 Pro (64 bit).

---

Not in my case.  Every browser I've tried on win10, win7, and iOS all show the bad layout.

---

Are you Win 10 Pro (64 bit) .... you didn't say?

[Retired_Member]

This smells like a combination of issues from the hardware, operating system and browser. I do not experience this issue. If I would, I'd consider experimenting with the following parameters:

browser: reduce font size

os (win 10): decrease scaling in case you pushed that beyond 100%

hardware: increase screen resolution in case it is currently lower than the screens native resolution

I would start reducing the browser font size and increase complexity of the testing scenario, if necessary.

Oh, before doing any testing make sure you know the parameter settings you started with, should you not see any improvement while conducting this effort.

[cpu8088]

regarding C or F this can be fixed in having language English (UK Aus) and English (USA) for users to choose from

similar the date format can be incorporated in the language.

[StephenB]

---

@cpu8088 wrote:

regarding C or F this can be fixed in having language English (UK Aus) and English (USA) for users to choose from

similar the date format can be incorporated in the language.

I think many people want specific control over the time and date formatting (and they'd want that to include the formatting in the logs and the email alerts). Personally I want year-month-day, using numeric month, because it sorts properly in a spreadsheet.  I prefer 24 hour time for similar reasons.  I'm US, and I imagine other US folks will want a different format. So I don't think the browser language setting will work for that one. 

As far as C + F vs C or F goes, I personally don't see any reason to change to C or F.  Improving alert messages, better log filtering, reporting OS fullness, adding a CPU utilization graph are some items that are far more interesting.

[BaJohn]

---

StephenB wrote: 

As far as C + F vs C or F goes, I personally don't see any reason to change to C or F.  Improving alert messages, better log filtering, reporting OS fullness, adding a CPU utilization graph are some items that are far more interesting.

---

I'd go along with this as the logs and the CPU are crucial, whereas the temperature info is there for both 'currencies'.

[JBDragon1]

I'm running 64-bit Windows 10 Pro and am using Chrome.  On my ReadyNAS 516.   This is what it now looks like from going from OS6.6.1 which was just fine, to now 6.7.1 where my HDD info is screwed up!  It doesn't matter how large I make the browser window, it doesn't change.  

[StephenB]

---

@JBDragon1 wrote:

I'm running 64-bit Windows 10 Pro and am using Chrome.  On my ReadyNAS 516.   This is what it now looks like from going from OS6.6.1 which was just fine, to now 6.7.1 where my HDD info is screwed up!  It doesn't matter how large I make the browser window, it doesn't change.  

---

Yes, it does that on my systems also.  Win 7, Win 10, iOS, Edge, IE, Firefox, Chrome, and Safari.

[BaJohn]

---

@StephenB wrote:

---

@JBDragon1 wrote:

I'm running 64-bit Windows 10 Pro and am using Chrome.  On my ReadyNAS 516.   This is what it now looks like from going from OS6.6.1 which was just fine, to now 6.7.1 where my HDD info is screwed up!  It doesn't matter how large I make the browser window, it doesn't change.  

---

Yes, it does that on my systems also.  Win 7, Win 10, iOS, Edge, IE, Firefox, Chrome, and Safari.

---

Oh dear, oh dear .... re my comments and images on 1st May 2017, my system has changed/reverted to be the same as as yours.

i.e. It is a problem on Edge AND on Chrome.

To help with diagnosis of the root cause, my only significant change to windows since then has been the following.

Security Update for Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package (KB2538243)

Have either of you implemented this package recently on your systems?