Welcome, Guest. Please login or register.

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

Description:

0 Members and 1 Guest are viewing this topic.

guest11527

  • Guest
Re: The Os 3.1.4 Thread
« Reply #509 from previous page: July 11, 2019, 06:51:30 PM »
More on the update.

There is a new version of the FastFileSystem in the update as well. Actually, this is only a very minor update as there was nothing to fix, just a couple of things to improve. So, your data is not in danger.

If the FFS initialized a volume for long file names (DOS/6 or DOS/7), it also wrote administration information for directory caches. This data was actually never used, as the dircache remained disabled, so it did nothing bad. As the data is not needed, the new FFS no longer writes this useless data.

Then, when mounting multiple partitions, the 3.1.4. FFS mounted all partitions in parallel. This might have caused a lot of head movements on mechanical disks, so 3.1.4.1 reverts this to serial mounts.

There is a tiny improvement for users of the omniscsi.device, and probably some other devices in combination of removable media. In case you mounted such devices on a drive with a medium inserted, nothing would happen. The corresponding device does not return a proper result for TD_GETCHANGESTATE, such that the FFS would assume that no medium is inserted. The new FFS performs now a "dummy read" to "wake up" the affected device - this will avoid this problem.

The same issue also existed in CrossDos and the CDFileSystem where it was fixed (or rather, worked around) as well.

The FFS "bitmap" records which blocks of a volume are allocated and which are free. For large volumes, there can be many bitmap blocks, and these are recorded in "bitmap list blocks". Previous versions of FFS wrote the bitmap list blocks and the actual bitmap blocks "interleaved", which makes them slow to read. The new FFS writes them in a contiguous list of blocks. This would allow the FFS in a future release to read them in one single access, improving the startup time. The code for that is not yet there, but there is some preparation for it.

Last but not least, the "disk validator" in the FFS was also improved.  The previous version would read blocks in a rather simple-minded fashion: Allocate a block buffer, read the block, validate the block, release the block, then continue. Thus, a lot of rather useless memory allocation operation were performed, one after another - this made disk validation unnecessarily slow. The new FFS will allocate the block first, then use throughout the validation process, and release it when its done.

Oh, and one final change: The FFS creates (since 3.1.4) its own entries in the "FileSystemResource". In order to avoid problems with "HDToolBox" type programs that do not inidicate a proper stack size (due to a mix up of the unit), the FFS now creates the proper "PatchFlags" to indicate a stack size of 2048.

The next (major) release will include just another mechanism for file handlers to indicate their stack size that is a bit more "fool proof" than the current way... Live and learn....
 

Offline my_pc_is_amiga

Re: The Os 3.1.4 Thread
« Reply #510 on: July 12, 2019, 05:32:32 AM »
For the multiview issue, this one, and any other minor issue it doesn't sound like there is any plan for a 3.1.4.2...instead next release is a 3.2?

Cross-posting a copy command memory leak issue from here:

http://forum.hyperion-entertainment.com/viewtopic.php?f=15&t=4321
I afraid it is too late now.
 

Offline Rotzloeffel

Re: The Os 3.1.4 Thread
« Reply #511 on: July 12, 2019, 10:44:17 AM »
no, not realy
Save Planet Earth! It is the only one in the galaxy with fresh and cold beer :laughing:
 

Offline kolla

Re: The Os 3.1.4 Thread
« Reply #512 on: July 12, 2019, 03:32:30 PM »
That's how it goes when there's no official and publicly available bug tracker that users can compare bugs they find against. So unnecessary.
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
A600/A6095
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM440 and Mac minis with MorphOS
 

guest11527

  • Guest
Re: The Os 3.1.4 Thread
« Reply #513 on: July 12, 2019, 04:08:27 PM »
That's how it goes when there's no official and publicly available bug tracker that users can compare bugs they find against. So unnecessary.

There is one. There is a support thread at the Hyperion web side right for that. It doesn't take a bug tracker to collect bugs from users. But it doesn't matter if the bug is reported too late.
 

Offline kolla

Re: The Os 3.1.4 Thread
« Reply #514 on: July 13, 2019, 10:44:58 AM »
There is one. There is a support thread at the Hyperion web side right for that.

That is not a bug tracker - you don't know what a bug tracker is??

It takes a public bug tracker for _users_ to know what bugs are already _known_ and, potentially, addressed.
« Last Edit: July 13, 2019, 10:48:08 AM by kolla »
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
A600/A6095
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM440 and Mac minis with MorphOS
 

guest11527

  • Guest
Re: The Os 3.1.4 Thread
« Reply #515 on: July 13, 2019, 11:05:13 AM »
That is not a bug tracker
Yes.  But, guess what, you can still report bugs there. Is there a reason why I need to repeat this again?

It takes a public bug tracker for _users_ to know what bugs are already _known_ and, potentially, addressed.
My experience is that the barrier for *users* using bug trackers is too high, leave alone looking up what bugs are reported, leave alone providing useful bug reports that could be handled this way. So, yes, we do have an internal bug tracker where the bugs collected there go, but not for the public. A bug tracker is next to useless for the general audience.


 

Offline kolla

Re: The Os 3.1.4 Thread
« Reply #516 on: July 13, 2019, 11:31:54 AM »
I have zero interest in reporting bugs that may or may not be already known, it's just too much hassle.

At least you could have a text file somewhere, listing a summary of all known bugs. How hard can it be to generate such a list from your internal bug tracker
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
A600/A6095
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM440 and Mac minis with MorphOS
 

Offline TribbleSmasher

Re: The Os 3.1.4 Thread
« Reply #517 on: July 13, 2019, 11:41:10 AM »
Doesn't make sense. It is lot less work on your part if you just drop a few lines here instead of studying the whole buglist and then drop the very same text.
 

guest11527

  • Guest
Re: The Os 3.1.4 Thread
« Reply #518 on: July 13, 2019, 11:47:02 AM »
I have zero interest in reporting bugs that may or may not be already known, it's just too much hassle.
I had enough university projects where it was a quite hard fight to convince users (from academia) to use a bug tracker. Now do that with arbitrary users. Please go here, create an account, register your mail, select the subsystem, type the bug description here...

Be realistic: Forget it. Even in my unversity projects, most users wrote emails, much to my dislike, because it was just easier. Users know how to use a forum. We collect bugs, decide whether that even is a bug in first place. Keep the barrier low for users. A forum is ideal for them - easy access, known medium, low barrier. We filter, collect and feed the bugtracker.

At least you could have a text file somewhere, listing a summary of all known bugs. How hard can it be to generate such a list from your internal bug tracker
Not hard. But why would that help? Would users read them before reporting? No. Reading bug lists requires understanding bugs, requires some technical background, and investing time for it. Thanks, but no, thanks.

 

Offline kolla

Re: The Os 3.1.4 Thread
« Reply #519 on: July 13, 2019, 11:50:41 AM »
So dumb sheep, that is what we are.

(Begs the question - what do dumb sheep need "advanced" CLI for.)
« Last Edit: July 13, 2019, 11:56:38 AM by kolla »
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
A600/A6095
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM440 and Mac minis with MorphOS
 

guest11527

  • Guest
Re: The Os 3.1.4 Thread
« Reply #520 on: July 13, 2019, 11:55:22 AM »
So dumb sheep, that is what we are.

It is really that simple: If you want to get access to a bug tracker, become a beta tester. You get early access to the beta phase, a bug list, and a bug tracker. You don't what that? Well, then you're a user. Decide your role, but don't complain about the consequences.

Users don't want to be bothered with bug tracking, which is quite a task and requires in depth knowledge of the system and its components - this does not quality anyone as "dumb". I don't want to be bothered with the internal workings of my washing machine either, I just want that it does its job properly.
 

Offline kolla

Re: The Os 3.1.4 Thread
« Reply #521 on: July 13, 2019, 12:02:57 PM »
It is realy not my loss that you miss out on bug reports.
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
A600/A6095
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM440 and Mac minis with MorphOS
 

guest11527

  • Guest
Re: The Os 3.1.4 Thread
« Reply #522 on: July 13, 2019, 12:13:46 PM »
It is realy not my loss that you miss out on bug reports.

Should I be afraid? This is a free world. You can take decisions as you like, but don't make anyone else feel guilty for consequences of your decision you don't like. You can contribute in many ways if you like. You can report bugs in the Hyperion forum as user, and they will be read. Or you can become a beta tester if you like, and get better access, but more responsibility. Or become a developer, and get even more access, and even more responsibility.

It's really your choice to pick. What else should I say? You want to pout since you don't get what you want? Well, works for me, too. I cannot change the rules either.
 

Offline TribbleSmasher

Re: The Os 3.1.4 Thread
« Reply #523 on: July 13, 2019, 12:17:23 PM »
Googling kolla's sig brings out his interpretation of responsibility....
 

Offline kolla

Re: The Os 3.1.4 Thread
« Reply #524 on: July 13, 2019, 12:39:01 PM »
Googling kolla's sig brings out his interpretation of responsibility....

Yes, though it's much harder to spot now, due to it being my signature.

Right?
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
A600/A6095
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM440 and Mac minis with MorphOS