@kas1e

I think what you wanted to say is that only supports one controller not two controllers maybe..

Wont that be problem if the hardware is already used by different driver, maybe this is why.

@billyfish

Maybe better to convert to PDF, we have good PDF views on Amiga, and they do render all things we want, images, different kinds of fonts, and unicode support and so on, maybe a bit more light wight then a HTML.

About your mui class, the "litehtml" project can good thing to build a MUI class on maybe, sense it also support CSS. can be useful for email clients, and generally displaying formatted text, and readme's.

Perhaps a PDF mui class can be good idea, just an idea.

@joerg

almost forgot Anime datatypes are interactive, mostly use libpng, for image loading, but then again if do load any image, it some old code I wrote years ago.

@tekmage

Not sure what, multiview support regarding font size, bold, and italic and so on, while you can read markdown no problem, you might want to generate a image format, to support UTF8 and all the formatting, but that is kind of a memory hungry solution. Or maybe you just want something converts it into ASCII 8bit encoded text, that can be loaded as a readable format without all that.

Maybe a making MD viewer is more appropriate action.
Markdown support URL’s to images and tables, and links to web sites.

Its not a simple project, in particularly if need to display different parts of the documents with different fonts based on UTF8 codes ranges (See the Unicode table). But anyway 50% is better then 0% markdown support.

Not sure what the best approach is, its definitely good idea to have strategy before you start.
Or maybe there is existing project that can be ported over, it can save you lot of hazel.

Reading MD, before reinventing the wheel best to look into following projects.

https://github.com/mity/md4c
https://github.com/commonmark/cmark
https://github.com/goldsborough/markdownpp
https://github.com/litehtml/litehtml

@NinjaCyborg

Do you think he should support Windows, Linux, MacOSX too?
was not the point of using AI lack of time.. to do it all.

@Deniil

Just remeber to nuplug the power, I bet its not RAM issue..
unless you want to spend a month hunting down some old DDR2 ram, with right specs.

CFE error about no ram, is a general error, used if it does find CDROM or HD.

@Hitman

I use samsung and EVO ssd's

@kas1e

newlib, sfs2

@balaton

RadeonHD_RM.resource is the direct hardware API to 3D stuff.
not sure how documented it is..

this what Warp3DNova uses.

https://www.youtube.com/watch?v=oDpgNZESHgI

@kas1e

NVIDIA is not so closed sourced as it used to be.

@LyleHaze

Can be good idea to replace hard drives at some point, if things start getting unstable.

I have PATA to SATA adapter in my old XE, works well, I now use SSD, feels like a newer machine, access times has probably dropped like a stone, pretty much guaranteed max read speed of the via shipset, sense I have the IRQ/DMA fix. I use 2K block sizes, sense it reduces fragmentation.

I restored my dead, X1000, back to life by replacing ram,
(battery was not the issue.)
and the instability by also replacing ssd disks there, a complete new install of the OS.

I also downgraded SFS to an older version, that did not give me all the read errors.
sense it was almost impossible to backup files, while having to click in the request boxes.

I believe having different versions of SFS on XE and X1000, caused disk corruption as well, when trying to back up the data.

@TSK

Boot from cdrom, and check that you don't have outdated tools in s:startup-sequence, or user-startup.
often when the OS is frozen its possible get into Amiga computer by using serial cable, but you need to setup a termial on aux: using newshell.

@ncafferkey

bad switch..

@OlafS25

Quote:

Well you have that problem on Linux as well..
everything is installed with sudo so everything you install can over write everything else.. the solution to incompatible packages is docker and kubernetes..

When it comes to Linux packages, security is maintained by the repositories not by the OS

@derfs

Amazing work..

@OlafS25

I can’t comment on what is not official or is not released..

I can merely comment on issue with SMP, and cache concurrency, from the information, I looked up or find lectures about it..

if it’s possible or not to do x/y/z, comes down to problem solving abilities, and what solution was chosen. Something can be hard to do, when you have a lot of stuff running in background tripping all over the place.

So far from what I have lookup, it’s normal for cores to have their own MMU, so a exception should not affect other cores. something some people suggests that’s not case, but as pointed out by Gemini, it won’t be possible for threads to have its own virtual memory maps if that was the case.

cache concurrency has hardware solution, and software solutions, there are different ways this can be implemented, as outlines in YouTube lectures I have pointed to..

I can’t comment on the AROS solution.

If it is possible or not to run Petunia inside a sandbox, my guess is that’s its possible, however I do not know implementation, so I can’t say for sure..

I can say for sure that it is not possible to add 64bit support without a sandbox for 32bit programs..

My opinion about AmigaOS4.1 API is that is fragile and can need improved security, regarding stack, API’s and structurally.. and that major changes can require a sandbox solution.

I guess that a lot of AmigaOS libraries are not cache concurrency safe, and might need to be sandboxed. its far better if programs fail to open a library, then bring down the system

@joerg

with a sandbox approach you most likely end up width a different execbase anyway..

you need a ready list / wait list per core, and I think old linked list is a bit slow due to its scattered data, and its slow to index, as you need to walk the list up and down.

Quote:

page zero is already memory protected, if not you won’t get a DSI error on NULL pointers..

I have used exceptions in NallePuh, and I must say it works far better than I expected even on busy loops, pocking the same address repeatedly. No doubt is slow, but once you read address 0x00000004, into a register, you no longer reputedly poke that address.

@joerg

Quote:

Easy... set SysBase->ThisTask to 0xdeadcafe or something silly.

put a MMU protection on 0xdeadcfae, the exception routine calls IExec->FindTask(NULL); or something like that.. (might need to find correct the IExec sense that might be a different instance, per core)

"Per-Core Structure: Almost all modern multi-core processors have an MMU integrated into each individual core. This allows each core to independently translate virtual addresses to physical addresses for the thread or process it is currently executing."

So I guess you need to set that exception 4 times, if you have 4 cores..
you might perhaps have a slight different exception per core, that handles instance of IExec..

@tao

but if we are talking about 64bit, we don't need to guess. then we must have a sandbox.. so its just over the horizon anyway..

and frankly disabling multitasking to access a public stricture is not good idea... and even worse on SMP system..

Sure maybe solve the messaging API, but AddTail() is a macro, there if you have no function that you retro fit any cache flushes, then the pre-compiled code can't become SMP friendly.

for more info look here, also notice the warnings, and bad advice.

http://amigadev.elowar.com/read/ADCD_ ... cs_3._guide/node01E1.html

you will need to do it on forbid / permit, but that is already pretty bad.

@tao

forget DE/AA OS5, it was Amiga Inc project, that is out of the picture..

Not a lot information has shared about sate of SMP in AmigaOS4.1..
so we left guessing...

The fundamental issue for SMP is that core do not see the same content, etch core has unique L1 cache.. when data is shared between the core, the L1 cache, most be synchronized.

https://www.youtube.com/watch?v=r_ZE1XVT8Ao
https://www.youtube.com/watch?v=7yrK_9PderQ

protocol-driven cache coherence, has a lot issues.
1. Lack of Scalability (The "Bus Traffic" Problem)

Snooping Protocol Limits: Common hardware protocols often rely on "snooping" (broadcasting) to inform other cores of changes. This works well for a few cores, but as the number of cores increases, the traffic on the interconnect bus becomes a massive bottleneck, slowing down all processors.

2. High Performance Overhead (Latency and Bandwidth)

Coherence Misses: In a multiprocessor system, if multiple cores constantly write to the same data (false sharing), the hardware must invalidate the cache lines in other cores. This leads to high cache miss rates, which are far more costly than simple memory latency.

3. Inflexibility and Inefficiency

the basic issue you can do protocol-driven cache, but it inefficient, because flushes caches too often, you want the OS to control this..

this comes down to ownership of the data, what core has accessed what data, you don't want the cache to be flushed when its not needed, but you do want to flush it, if you most do so. so keeping tack of what core, did what when. to what data..

"to what data" part is the issue in AmigaOS..

Its up to AmigaOS programs to snoop public lists, because there is lack of locking mechanisms, that specify what data, that is locked, we often have to use the most powerful tool to get ownership, by disabling multitasking, for short periods. Instead of proper lookup functions. Lets say I want to obtain a task or process structure by pid, without blocking the OS, and without risk of reading something that might be freed from memory, without notice. Maybe I want to obtain a msgport by name. There is function called FindPort but does not guarantee ownership or shared lock. The msgport can be deleted without notice. unless you prevent other task form running.