@joerg

Awesome, thank you so much for taking the time

@joerg

Some more questions, if i may?

Does it make any difference speed-wise (access, i/o) if i'd adapt the block size depending on the maximum partition size used?

e.g. if i have a partition with 1 TB, would it make a difference using a block size of 512 (2 TB max size) instead of 256 (1 TB max size)

And do block sizes impact on ram usage to manage those partitions or is that only with the size of used buffers?

And finally, do buffers still impact on access speed with SSDs or just mechanical HDDs?

Thank you very much

@joerg

Thank you, that help a lot

@LiveForIt

I had that specific hdd 90% filled earlier, no problems, so I guess the max size *might* be 2 TB for SFS2 formatted devices, but there is no info I could look up.

What would the block size have to do with max partition size?

Since I cannot use NGFS due to it being held back for release for unknown reasons I'm stuck with SFS2 (which isn't a bad thing per se, just there doesn't seem to be much up-to-date information available nowadays)

I'd go with a 2 TB drive, but would like to know if larger size will/can work?

Thank you

This site tells me SFS2 has a maximum partition size of 1 TB, but that cannot be, since i'm using a 1.8 TB where 1.6 TB is available to the system.

Does anyone know how much is possible?
I' m looking to install a a new data grave and would like to make it as big as possible

Thanks a lot

Re-seat the sata cable on your hdd.

If it happens once in a while/often/repeatedly get new ones.

I had this a lot on my x1000 until I replaced the cables. Seems to be either a flaky connection or "cheap cable syndrome" or a combination of both

@geennaam


...and i'm not beta testing... :-O

@kas1e

Then it would have been nice if he informed others outside the beta world as well, since everyone, still using his software, is affected...just saying

@all

So, is amiupdate.codebench.co.uk down for good?

Quite some time has passed already

@LiveForIt

Yes, memory tests in cfe are bogus, they always fail

@LiveForIt

Measure the compile time and do a side by side comparision once your ram has arrived...just for fun

@mikro

Nope, i didn't.
I was about to let a profiler run, but didn't find any that doesn't break, came to a screeching halt or was screaming while going down in flames...so, no, no profiling done...but with all the configure settings in place right now, it does seem to run nicely.

Whenever there is a working profiler on AmigaOS4, i'll try to think about revisiting this and checking if there are any differences...and go with the optimal route.

LTO does seem to produce the same size binary (maybe even a litter bigger), same with -O3 speed-wise, but since it was added in a time i was able to annoy the gcc dev, i though, "why not"?

PS: Also, i'm learning while tinkering with the configure settings (i don't really know what i'm doing, anyway)

@K-L

You'll continue to get freezes until an updated RX gfx driver is released.

The problem has been found and fixed and reported working in beta

Leave your INTERRUPT setting on NO for the time being,otherwise you WILL get freezes

@derfs

The sdk server too?

New problems today

@geennaam

And a nice addition to the x1000 it was...Still using it today and still appreciating that you put so much work in it

Thank you very much once again

/me is cheering at everyone working on this and helping out

Thanks a lot

@Maijestro

What error message?

The game is supportedcsince some versions now. I don't have the gog version, but my cd based released worked last time I tried

@Maijestro

There'll probably be a new sdl2 version, maybe with the next big release or a bugfix release

@Capehill

Thank you