@Elwood

No, it's not just you—most of us have this issue. It was reported several times and rejected. Initially, it started after a commit a few years ago, and I reported it immediately. However, it was incredibly difficult to explain repeatedly what was happening and where the bug was—even when I provided video evidence and explained it in various ways with different approaches. Yet, each time, it was dismissed as if nothing was wrong. Then others reported it, and I brought it up again. Nothing changed. More recently, some people on os4depot reported it, and I highlighted it once more—still no response.

Every report about this issue is treated as if we (or I) are attacking without reason, when it's simply a legitimate bug report that, for some unknown, irrational, and illogical reason, keeps being ignored.

I pointed to LiveForIt exactly which commits introduced the issue (I don’t remember the commit number now, but it’s in the old thread about uae-improvements on amigans). The proper approach would be to understand what was changed, create a test case, test it on different machines, and then implement the fix correctly. But that requires a willingness to acknowledge the issue and trace the root cause in the code that broke things.

In other words, don’t get your hopes up. I’m only writing about it again—and again—holding onto a faint hope that LiveForIt will finally accept that there’s a problem, instead of simply saying, “It works on my X1000,” and actually try to create a small test case or investigate where the issue lies.

Because if this is being done for users, shouldn’t bug reports be accepted? If it’s only for personal enjoyment, then why make it public and avoid reports?

@sailor
Quote:
Speed of booting : bboot saves about 10-12 seconds on my peg2, i.e. instead of 40 something like 28-30 for full load up

@flash
Quote:
Yes, me. I use bboot for year or so once balaton make it, starting from v 0.4 and now 0.9 or so. Always works with everything, and why shouldnt it : you only need properly call it with point out on ffs partition with zipoed ks folder.

@flash
Dunno, but i didn't see anything pointing that os4.2 will skip support for any HW which we supported now, imho make no sense while it all powerpc still.

@flash
Quote:

Hans (our Hans who author of HD/RX drivers), add fixes for pegasos2 about half or year ago. I tested it all together with him till death until it start working more or less fine with more or less decent (for peg2) speed. You may find some older topic where i show progress about and results and benchamrks and co.

Now, this was added on top of beta kernel, which has bug making x5k acts bad. While on other platforms all was ok (i.e. on peg2) we can't release different kernels like 54.57 for x5k (latest working version which you all have, after which issues start), and other versions for other platforms, as it will just make mess. So "execsg-team-lead" (mr. Ssolie) were pointed on bug many times in 2 years, but .. well.. i have no words :) So, for update3 team can't wait any longer, and were released just latest working version, which mean, of course, no pegasos2 fixes, no other stuff, etc.

Of course in theory it all should be easy possible, just take peg2 fixes, add them on top of 54.57, and make it in update3, but this will be not done for sure, so the only hope is to wait for 4.2.

@AmigaSociety
Looking at your video i can say that all the modules load up fine to the memory, then, kernel calls fine, and then something at very begining borks : looks like when amigaboot tried to find bootable partition.

As usual in this kind of issues, you need to find a way to grab serial output, but before raise debug level to at least 3 or 5.

If github didnt remove it, why anyone worry about ? It just can be forked, patchs applied and readme written how to compile, at worst. At best just compile os4 version and put same at github. If action ever will be taken, remove and that all. No probs imho (and taking aside anyone from real world worry about os4 or mos ports today)

@Elwood
Quote:

$10,000? For a real port? Where do you find such prices and people willing to do so? :) $100,000, then yes, maybe you’ll find someone brave enough to spend years of their life fighting with this madness called the modern web. See how many years Jacadcaps spent on Wayfarer for MorphOS and how much he did, and in the end, what? A browser, which still doesn’t work on some pages being so slow that it’s impossible to use. Yes, it’s better than Odyssey, of course, but it’s really slow on our hardware, has no JIT, and has all sorts of related issues because of that. And that’s for a professional programmer spending years of his life on a proper port. Do you need a browser where you won’t be able to use modern sites and still have to use other hardware and another browser anyway? IMHO, the only real way is what K-L says. We have no other choice today.

@All
I may say unpopular things, but if asked for one feature, it should be “just more interesting and quality software,” and that’s all. Everything which we need OS provides already.

No need for SMP. That’s just banana thinking; it will change nothing. It will be ugly, buggy, and won’t speed up anything because of how the whole AmigaOS is designed. It will be the same as extended memory: hardly anyone uses it (i know about exceptions, but still).

No need for memory protection either. It’s Amiga; we’ve been here for 30 years, and everyone knows how it works. When we need real work, we all switch to Windows/Linux anyway. Without memory protection, we wrote software in a good way to avoid constant crashes. With memory protection, you’ll step onto the same road as other OSes : buggy and forgiving software. Maybe in one way it helps, but didn't in another one.

As we’re obscure, we have no viruses, no malware, no exploits, no need for security (I always laugh when people ask for “security fixes,” like someone uses AmigaOS 4 or MorphOS for reall important stuff, which can be easily hacked with or without those "security fixes").

So, for me—and this is, of course, IMHO—we only need new classes for ReAction, new native software, and to keep going the way we have until we all die or the whole Amiga thing fades away, just like other things before it. But after all these years, hoping and wishing for SMP, full memory protection, or someone making a browser again and again every few years… I don’t know. We just need to keep it as it is, just improved. IMHO.

@Capehill
I didn't test it yet, but just a wild idea after i watch smarkusg's video : is it possible to apply effects on top of the current (choicen) window/app ? What i mean, is that in real life have 2 similar windowses one with effect and another without kind of mess, but if you can just apply any effect you want on any window you choose (be it from list of opened windowses via some key, or via providing executable name when run ShaderNova) will surely make bigger use. IMHO, of course.

Will be a first one : yes! Dan again deliver quality stuff. Time for some tests

Browservice sounds like way to go for sure, just need a bit more polishing from our gui side.. On lastest videos from K-L i can see that scrolling of pages is pretty slow. So this need to be somehow sorted out in some (other than Odyssey?) gui. Also sound part need to be transfered too, if browservice support media transfers as well, and not only images. Also, proper address bar integration so to make it looks like native part of browser's gui need it too.

The best thing would be some board attached to PCI slot where we run browser, and a GUI specially written for from os4 side to access it. Browservice and co are only realistic way for us if we want to have up2date browser, IMHO. That were clear even few years ago for me.

@Petrol
Sadly with 2.0 there were 1 bug (in threads, Andrea aware, should be fixed soon) and 1 feature meaning changes in crtbegin code causes needs of recompile if you want to use clib4 2.x (that why there verdion bump). So for wget for time being use 1.6 one

@K-L
Quote:

I build all Odysseys on os4 with usage of casual libpng, and all os4 png datatypes we have use same libpng for png decoding (which add additional layer).

Why you necro 3 years old topics ? I dealt with it 3 years ago.

@balaton
Quote:

I just use one from https://qemu.weilnetz.de/w64/2025/qemu-w64-setup-20250422.exe. I also didnt' tested it on linux and macos, so dunno if network indeed works as expected on emulated peg2 on those oses.

Quote:

I tried those the versions of rtl8139:

53.6
53.7 (qemu fix)
53.8 (removed qemu fix as it cause issues on real hardware, and one who reported about qemu issues, says that after proper reconfigure of qemu bug is gone, while i can't confirm it, as at least on windows).
53.9
53.10
and 53.11

All of them fail in one or another way : or simple crashes, or stalls after few mb of downloading for few seconds, then speed drops, and bit by bit continue.

Quote:

Of course, i noted it "in better file sharing thread" about:

Quote:

@Balaton
Thanks for suggestions, will try it out, as for:

Quote:

Yeah, at least for me none drivers i tried (be it old ones, beta ones, etc) didn't work good enough on windows build of qemu : or crashes, or simple stalls, or simple madness slow. So only way usb stick :(

@joerg
Quote:

Reason is i weren't able to make alt key as amiga key to work with ps2 keyboard even if i have necessary settings in prefs for. Once i switch to USB one, it start to work as expected (i use amiga key offten for spawn a shell, like amiga+e , newcli, etc).

@joerg
Removing bootimage and bootmenu.kmod modules, together with commenting out everything non need it in diskboot.config, result now in 12 seconds boot instead of 15, which is good ! If remove USB stick, then it 10 seconds. But i need those 10 seconds with USB stick :)

Quote:

On peg2 there in kickstart 2 files: nvram.config and nvram_nodma.config, and both with same content:

peg2ide_xfer=FFFF
peg2ide_irq=1111

added to both:

peg2ide_maxbus=1
peg2ide_timeout=1

But so far not changes, will dig into docs , maybe params are different.

Wow ! Awesome ! As always quality stuff from you and Frank :)

@ktadd
Quote:

What is cleary state initialy (at least for me), it's secrecy about what core were used. Because Mattew as always play word-games and didn't credit a shit for the real hardcore part : a Chromium core, which done by non-amiga ppls, and make it sounds like everything were done for specially from scratch, while is not (see Andy comment).

Don't take me wrong, I see nothing wrong with this all, and definately Andy do quality stuff and it all good (and i wish we on OS4 have someday some HW dongle with some fast little endian cpu to run some browser and to have reaction gui utilizing it), just the way how Mattew made announcement misleading as always and words-cheating games and just make me mad.

@Andy
If this is not secret, what was the reason to go Chromium way, and not Webkit one for example ?

@amigakit
Quote:

Kas1e, Managing Director of myself, remarked:

Quote:


Are you still cheating ? Of course we see that GUI is 3.x mui app. But you can't create core with 1 or 2 programmers in even few years , which will support all modern web. This mean, that you use core done by someone else , be it Webkit or Chromium, and as always didn't credit ppls work (as always) and then, via some api or so you render pages on "real" browser on linux or whatever, and then blit ready images (via arm library i assume) to the os3 mui app. Or kind of.

And there is nothing wrong with, the same way should be done on OS4 for years, but then, there no needs for you to cheat us and take us like ones who understand nothing, and forget to point that all hardcore work on the core were done by relevant ppls having no connection not to amiga , not to you.

Creating a gui, with limited options and features, and blitting ready images from real core browser pretty possible in few weeks, of course. But creating from scratch a browser with support of all web stuff absolutly unreal to do by 1-2 or even 10 programmers in such a small timeframe today. We all know it , and we know how ppls at chromium, webkit and co works.

So.. the way you choose for browser for sure correct one for limited resources, but the way how you cheat us like this is "fully new done from scratch" again stinks a bit like the story with Yam, sadly.