Welcome, Guest. Please login or register.
Amiga Kit Amiga Store Iridium Banner AMIStore App Store A1200/A600 4xIDE Interface

AuthorTopic: The Os 3.1.4 Thread  (Read 110262 times)

0 Members and 2 Guests are viewing this topic.

Offline Dege

Re: The Os 3.1.4 Thread
« Reply #780 on: October 16, 2020, 10:52:03 PM »
It worked!  Thank you!
 

Offline TribbleSmasher

Re: The Os 3.1.4 Thread
« Reply #781 on: October 18, 2020, 07:59:18 PM »
@Gulliver
as you seem to be involved in the 3... OS developement i'd like to address a wish as Thor is no longer feelin welcome here.

When something is launched from Workbench, mostly by dblclick, the very icon stays active, selected, even if the launched app opens a new screen. I wish the icon gets deactivated as it is no longer in the focus. Can this made an option in the future release someday as it bothers me for ages, really?
 

Offline Matt_H

Re: The Os 3.1.4 Thread
« Reply #782 on: October 18, 2020, 08:08:15 PM »
Going to change topics a moment.  Installing 3.1.4 on a 3000 with 3.1.4 roms.  Using a SCSItoSD interface for the scsi.  My dh0: drive is 20 gig.  I get a "error validating system: not enough memory" message and the disk won't format.  Is there a work around for this?  I've installed os3.1.4 on a 500 and a 4000 and haven't run into this particular problem.  The 500 didn't have a very large SD and the 4000 has 128 meg of memory.  My A3000 has 8 meg fast memory and 2 meg of chip. Suggestions?

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?
 

Offline TribbleSmasher

Re: The Os 3.1.4 Thread
« Reply #783 on: October 18, 2020, 08:16:04 PM »
As i recall all new media types, like SSDs and Flashdrives handling their storage internaly by 4k blocks, so whatever your filesystem reads or writes regarding block sizes the access is always done via 4k blocks in hardware at the end.

that being said, there was a survey with a tool send to participants before AOS4 release to test the amount of files/sizes of any storage and the result was like 75% of all files are smaller than 1kB, whatever that means. But i might be wrong as my brain memory fades away ... ???
« Last Edit: October 18, 2020, 08:17:04 PM by TribbleSmasher »
 

Offline nbache

Re: The Os 3.1.4 Thread
« Reply #784 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
 

Offline Matt_H

Re: The Os 3.1.4 Thread
« Reply #785 on: October 19, 2020, 07:06:41 PM »
@ nbache

Very helpful, thanks. So the logic in the old days was to use a small/512 block size to maximize drive space and since overall drive sizes were small it didn't have an adverse effect on memory consumption?

I'm in the processes of setting up a new SD drive for my 500. Looks like I'll be switching to 4096 before copying my files back. :)
 

Offline Gulliver

Re: The Os 3.1.4 Thread
« Reply #786 on: October 19, 2020, 08:29:21 PM »
@Gulliver
When something is launched from Workbench, mostly by dblclick, the very icon stays active, selected, even if the launched app opens a new screen. I wish the icon gets deactivated as it is no longer in the focus. Can this made an option in the future release someday as it bothers me for ages, really?

I took a note to be discussed by the time we get to plan AmigaOS 3.3.
In any case, it sounds like something like that could be implemented as a commodity, or even as an ARexx script.
 

Offline Gulliver

Re: The Os 3.1.4 Thread
« Reply #787 on: October 19, 2020, 08:34:24 PM »
In the old days, memory requirements for validation were not such a common issue because storage devices were not as big as what they are today.

To estimate the amount of free memory required to validate a volume, 
you can perform the following equation:

((S / B) / 32) * 8 = Free memory required for validation

  S  is the volume size in bytes
  /  is the division sign
  *  is the multiplication sign
  () are parentheses required to solve the expression inside first
  B  are the bytes per block as set by HDToolBox. Sizes start at 512
     and are capped at 65536 bytes

Make sure that you round up the numbers before dividing as we don't
want floating point numbers getting in the way.

Examples:

A 500 MB partition with 512 bytes per block = 256 KB of RAM required
A 1 GB partition with 4096 bytes per block = 64 KB of RAM required
A 1 GB partition with 512 bytes per block = 0.5 MB of RAM required
A 64 GB partition with 512 bytes per block = 32 MB of RAM required
A 64 GB partition with 4096 bytes per block = 4 MB of RAM required

So always use the bigger blocks you can afford as you will save more
RAM at the expense of storage space.