@AmigaSociety

Reasons could be that the RX 580 has more gfx memory and is about 2.5 times faster. If you don't care for those numbers then the RX 550 is just fine.

Of course there are not much games yet where you would notice the difference except for DOOM3 or Quake 4 maybe.

Infighting in the qemu subscene.

Now you have finished you initiation rituals.

@kas1e

I alway use -O3. Never experienced any issue with it. But sometimes you need to use volatile to prevent the compiler from over-optimizing volatile code.

@joerg

Quote:

Without diskcache of course. I only have SSDs.

But as final test I've also enabled diskcache in my kicklayout. Limit is the same. But at least now I can start the Spencer demo. So the truncated partition is usable.

Now this is really it. Sorry for those who are stuck with sfs2. But I am not going to spend more time on it.

@joerg

Quote:

Ok understood. I'll stop looking into it further because I cannot fix SFS2 itself.

@joerg

Quote:
Ah ok. I thought that you were saying that in the context of MediaToolbox. Anyways, a 1-2TB partition doesn't function properly on a >2TB drive. I can copy files and read back from it but the files are corrupted.

Quote:
That is not enrtirely correct. I do see filesystems sending the TD_GETGEOMETRY. Can't didn't watch closely if that is the case for SFS2 as well. But in any case, TD_GETGEOMETRY64 is not used except for mounter.library.

Quote:

Both the WB Disk info window and the WB drive root window top bar show the 3.72TB /xxxMB used correctly in case of NGF\01. In case of SFS2, the same windows shows 1.86TB. Of course I do not know if this is somehow an internal issue between SFS2 and WB which exist for SFS2 and not for NGF\01. But the partition doesn't function correctly anyway. In contrary to 1TB drives or NGF\01. This is at least a hint that somthing is wrong.

Quote:
From what I can tell, it doesn't. But these things happen when you don't have the tools at your disposal to check every corner of your software. I had to solve an issue with TD_GETGEOMETRY as well to make the >2TB drives get recognized correctly. Wouldn't have noticed the bug without having such a drive myself.

@Raziel

There's also Jxfs. I do not know the story behind it and why it is obsolete now according to this page: https://wiki.amigaos.net/wiki/JXFS

It still runs just fine on my sam440.

I think you need a pre final edition version because the final edition version is read only

@joerg

I've bought a 4TB NVMe drive which arrived today. Unfortunately, I've ran into the same problem as @Raziel. The disk capacity is shown correctly in MediaToolbox. I can define partitions of > 2TB. But they cannot be formatted. With SFS2, I get a disk is full. With NGFS, I get an uninitialised disk.

Now I was expecting the following sequence from Mediatoolbox:
- Mediatoolbox issues the read capacity (10) SCSI command -> opcode 25h
- driver returns logical block address as ffffffffh because the last LBA exceeds 32bit
- Mediatoolbox issues the read capacity (16) SCSI command -> opcode 9eh
- driver returns logical block address to the last LBA (64bit value)

But this does not happen.

Instead the following happens:
- Mediatoolbox issues the read capacity (10) SCSI command -> opcode 25h
- driver returns logical block address as ffffffffh because the last LBA exceeds 32bit
- Mediatoolbox issues the TD_GETGEOMETRY command
- driver returns struct DriveGeometry

And now things get tricky. Because how to I fill out the 32bit struct DriveGeometry for a >2TB drive?

I can break up the total amount of sectors into C*H*S. But what do I have to do with dg_TotalSectors. Set it to 0?

Anyways, When I do break up the amount of sectors into CHS, I get the correct value for my disk in Mediatoolbox.
But like Raziel, I get those red dots next to "Last usable cyl." and "Blocks per cyl." . When you click on those values with a red dot. The fields to the right give the range (minimum, maximum). When I enter those maximum values, my disk size is reduced to 1.86TB. When I create a partition in this situation, the maximum size is also 1.86TB of course.
Now the format succeeds and the disk is usable.

There's also a TD_GETGEOMETRY64 with a struct DriveGeometry64 defined for the mounter library. Struct DriveGeometry64 doesn't work with CHS but with a 64bit dg_TotalSectors. So I've added support for this command and it's indeed used by the mounter library. But not by MediaToolbox or any filesystem.

So the question is if I am doing something wrong. Or if MediaToolbox is limiting the maximum disk size to 2TB?

EDIT1:
Ok, forget about NGF\01. Apparently I did something wrong (maybe I've selected the old NGF\00)

So I've ignored the red dots in expert mode and defined a 3.72TB partition with SFS2. With a blocksize of 512 bytes, I cannot format and get the "Disk is full" format error.
When I increase the blocksize to 4096 bytes, I can format the drive but the result is only a 1.86TB partition. Further increasing the blocksize doesn't help.
With NGF/01, I can successfully format a 3.72TB Partition. No matter the blocksize.

So MediaToolbox does a lot of weird things with displaying values. It even shows red dots where it shouldn't. But ultimately it's SFS2 which limits the partition size to 1.86TB.

Hopefully we might see NGF\01 for other machines then the X5000 some day, otherwise those systems are limited in partition size.

EDIT2:
SFS2 partitions do not work reliable. Executing something will result in a GR. Not even if I split my 3.7TB into e.g. 3x 1.2TB. NGF\01 works fine in any case.
So it looks that SFS2 will not work with >2TB drives.

@TSK

Link to source in #32.

It gets updated in that location

@kas1e

Having an address bar would be great. And personally I don't mind that it (everything) is located at the bottom. Visuals can be improved. I'd be happy when I can add my own images because I am running the dark theme from ImagoDespira

@LiveForIt

Call me a heretic but the way you can navigate in Windows is rather nice. Having similar functionality in OS4 is nothing to be ashamed of.

@LiveForIt
Quote:

One of those small items that make the OS more pleasant to use.

I think because the current situation where all drawers open on top of eachother isn't really user friendly. At least I rather use the shell then use WB when I have to navigate further then two levels.

An easy way to navigate inside a single windows should be a part of the OS. Dopus still feels like it is stuck in the '80s.

Since it isn't and probably not will be part of the OS. A patch is the next best thing.

@joerg

Offtopic: It's such a shame that you don't code for os4 anymore. You obviously know a lot about os4 and its internals.

@sinisrus @kas1e

Would be nice to check if that tool could live up to the expectations.
Because I just checked the source. And like @kas1e already hinted, PowerWB works with OpenWindowTagList().
Unfortunately the interesting part is 68k assembly. So I need to do a speedcourse 68k assembly first

Edit: Looks like it's redirecting and replacing the OpenWindow routine of OS3. So a patch.

@kas1e

That is indeed a hack.

Or at least not the functionality that could be expected from the description. It's not a toolbar but more like an overlay of icons.

Looks like TSK (Tuomas Hokka) made a start for such an OS4 tool: WB Toolbar

Source in C is included so it should not be that hard to expand its functionality

@kas1e

Are you talking about your Pegasos2 with bboot and a RadeonHD/RX?

The audio device is just a second endpoint.

PCIe config register are always readable. Unless something is wrong with your card's address. The Bar spaces need to be enabled in the command register.

@Hypex

If the definition of "ppc for classic" is to run powerup or warpos then I do not see the point. The 68k emulation will probably run the 68k versions just as fast as a ppc emulation would run the warpos versions of an app.

If the reason is to run amigaos4.1 on a classic then the end result will probably be disappointing with a rpi4, compared to even a sam440, for running OS4 apps and games.
Nevertheless it's worth the effort IMHO. Owners of real Amiga hardware in combination with a PiStorm are probably more committed to the Amiga when compared to winuae users and alike. And therefore make better assets for the Amigaos4 community.

@Hitman

The AmigaOS install iso doesn't come with any RadeonRX driver. Only with a lite version of RadeonHD driver. So you'll need Enhancer for RadeonRX support.

Just adding the RadeonRX driver from Enhancer to your kickstart drawer is not enough.

You need to do the following:
1. Add RadeonRX.chip driver the "System/Kickstart" drawer.
2. Add "MODULE Kickstart/RadeonRX.chip" to both "Kickstart/kicklayout" and "/System/Kickstart/kicklayout"
3. Disable compositing in your "Installation-Support/startprefs.bat" by disabling the following lines:

;:Installation-Support/CheckHardwareCompose
;if $RC EQ 0
;copy :Installation-Files/GUI-compose.prefs env:sys/GUI.prefs
;setenv _INSTALL_HWACCEL 1
;else
copy :Installation-Files/GUI.prefs env:sys
setenv _INSTALL_HWACCEL 0
;endif


See this thread for more info:
https://www.amigans.net/modules/newbb/ ... id=135388#forumpost135388

@Mikey_C

Actually it does. It will definitly have an ENIG PCB surface finish and some headers might have gold plating as well