Welcome, Guest. Please login or register.

Author Topic: The Os 3.1.4 Thread  (Read 239886 times)

Description:

0 Members and 7 Guests are viewing this topic.

Offline nbache

Re: The Os 3.1.4 Thread
« on: March 23, 2019, 10:25:35 PM »
Wild guess: Maybe the doctor needs to know who the patient is (i.e. device name)?

Best regards,

Niels
 

Offline nbache

Re: The Os 3.1.4 Thread
« Reply #1 on: May 07, 2019, 10:33:03 AM »
@pixie:

I think you are talking about the version numbering itself, right?

Note that 3.1.4 is not building upon 3.9 (nor 3.5), but developed on top of 3.1 as a new "branch". Therefore it would not make sense to give it a revision number which increases from .9 (like .14). Some of the features which were in 3.5/3.9 have (if I understand correctly) been redeveloped "from scratch" on top of 3.1 for 3.1.4. But in its nature it is an update of 3.1.

Best regards,

Niels
 

Offline nbache

Re: The Os 3.1.4 Thread
« Reply #2 on: September 06, 2019, 08:13:31 AM »
Try the singular: CycleToMenu

Best regards,

Niels
 

Offline nbache

Re: The Os 3.1.4 Thread
« Reply #3 on: October 18, 2020, 08:28:32 PM »
Use a larger block size in HDToolBox and you will be fine.
Go for 4096 bytes per block and it willl solve your issue.
Is 4096 bytes per block the new recommendation for all use cases? Under what circumstances should we use a different setting?
The larger you set the block size, the fewer blocks are needed to cover a given size volume. And if you have fewer blocks, the formatting procedure will need to allocate fewer data structures in memory to keep track of the blocks during formatting.

Possibly simplified a bit, but that's the main idea.

On all systems.

So use a larger block size if you don't have enough memory for a higher number of blocks/data structures. The price, as mentioned by TribbleSmasher above, is that smaller files take up more space, because you cannot use less than one block per file for its data, no matter how small the file is.

Best regards,

Niels