@number6

You mean amiga-news.de? Don't think I have a user there, at least I cannot immidiately see any comments.

EDIT: ah, ok, I found them.

Last edited by kolla on 26-Dec-2020 at 04:18 PM.

_________________
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC

@kolla

http://amiga-news.de/de/news/comments/312432.html

At least he's talking.

#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@kolla

Quote:

And why, for f... sake, can't we have publically available bug tracker where we can follow up and supplement logs etc.

I've seen this asked before and always responded to in similar fashion, even when asked privately.

Unless something has changed, they prefer sending reports to testers, who in turn decide the merit of said report and whether it's worthy of the bug tracker. Since testers read the threads, that is basically equivalent to sending a report -to- a tester I suppose.

Perhaps too many instances of user error in reporting?

@Kas1e

Please correct me if I am wrong about this.

#6

Last edited by number6 on 26-Dec-2020 at 05:48 PM.

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@number6

I do not know the reasons, but their Bugzilla still not open publically, because it used also for beta-releases.

Imho, will be good to have another Bugzilla, opened for everyone. That can help at least every user to put bugs in, and then beta testers can monitor them, and add things to internal Bugzilla, so developers will not upset by tons of "this crap didn't work!", or "it all stops working, you suckers!" and so on :)

But then, if I remember right Hyperion create a forum for such bug reports, but then I didn't see anything good come from it, because some people are lazy to register, wrote good reports, but instead just in forum posts: that all crap, nothing works :) Not sure if some public Bugzilla will change anything, but why not.

And add to that, not everything will be fixed ever. Not many developers, everyone busy and some code is written by someone who is not here anymore, and other devs fear or have no interest to even touch some components.

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites

I did see there are rtl8139 & rtl8169 devices in the update 2 package. Does this mean PCI rtl8139 cards are now also supported in A Classic setup with mediator?

Or are these the network drivers for the onboard network of the NG systems that were delayed so much?

@spud101

Those drivers have been there for I believe well over a decade, so they're nothing new. Just bug fixes and speed improvement.

I use the 8169 one on my X1000 with a NetGear GA311 (because, yes, the driver for the internal network on the X1000 never got to a fully working stage).

Best regards,

Niels

@kas1e

Hi! I have been a member here for some time, and I had to sound off on this update to AmigaOS 4.1 FE.

I am using this on my i7 6 core system and FlowerPot.

I did a fresh install of OS4.1 FE and did the updates 1 and 2 as instructed, and I am impressed with the performance. From what I can tell the performance falls somewhere between a Sam460 and a A1XE. DVPlayer works great as does TuneNET and AmigaAMP 3.

I am posting this using the Odyssey browser while listening to Slay Radio, no problems so far.

I'm still have some trouble with RUNinUAE, but that's ok, I'll figure it out

=Larry

@number6

Quote:

At least he's talking.

Sounds like a rushed update... “bring what you have ready, release next week!”

On the other hand, there has been years available for testing already.

Last edited by kolla on 28-Dec-2020 at 12:27 PM.

_________________
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC

@spud101

Quote:

by spud101 on 27-Dec-2020 23:39:15 I did see there are rtl8139 & rtl8169 devices in the update 2 package. Does this mean PCI rtl8139 cards are now also supported in A Classic setup with mediator? Or are these the network drivers for the onboard network of the NG systems that were delayed so much?

These drivers only works with systems capable of doing DMA so no mediator support.

@kas1e

What you say is even more reason for having a central location.

Not to add to the list of websites you have to search...but a lot still goes on in irc channels as well and there is no way of knowing whether this information gets to a central location either.

#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@kolla

Don't expect things to be sane enough in amiga land. You know it already with everything. Instead, if they deliver something with a gazillion of fixes, you have something to tinker with, even if new issues come up. You can mix update1 with update2 as you wish if want to have it bugless from the update2 (like, revert to the previous kernel for a while, or, like reverts some other component which you may think guilty now for something).

Maybe there will be a quick-fix update as usually happens after big updates in a sane world. But that to be seen, it's only IMHO. And this is amiga land.


@All

I was told that it's ok if I put online SDK addon from update2 publicly the same as changelog.guide. So there is:

http://kas1e.mikendezign.com/aos4/ChangeLog_os4fe_update2.guide

http://kas1e.mikendezign.com/aos4/SDK_addon_final_edition_update2.zip

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites

@kas1e

Noticed something.

Deficons.doc is located in sys:documentation/utilities/
but expected it to be found in sys:documentation/prefs/

I expected it to be in /prefs/ because it is a preference program.

Last edited by NutsAboutAmiga on 29-Dec-2020 at 12:35 PM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

After several Grim Reapers, when starting the installer of update 2 in Amigaforever 2016. I finally got it 100% running. Thanks for the update.

@NutsAboutAmiga

Quote:

Deficons.doc is located in sys:documentation/utilities/ but expected it to be found in sys:documentation/prefs/ I expected it to be in /prefs/ because it is a preference program.

Well, in fact it isn't. DefIcons is a commodity, and commodities are placed in a drawer inside the Utilities drawer. So the doc is in the right place.

Then there is a prefs program for the DefIcons functionality, that is placed in Prefs, of course, but has no separate doc.

Best regards,

Niels

@bennymee

Let me guess ... the python script failed when trying to clean out old zlib.so* files?

_________________
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC

@kolla

Possible, Snoopy did not see the error. But it happened directly after starting the installer and after seeing the filerequester upating Python. Like you wrote.

After reading through the update experiences here and over at amigans.net I get the impression it may be a good idea to hold off on doing it? Seems like the new kernal isn't very stable in a lot of things and people are reverting back to the one found in update 1?

_________________
I do motherboard recaps and other enhancement/upgrades! Visit. www.acill.com or PM for a quote.

@Acill

I came to the exact same conclusion. It seems to be e real mess (not mentionning the ESP possible incompatibility).

I'm not using my X1000 anymore anyway, prefering using a much more stable system (with only one maintainer and with regular updates).

_________________
PowerMac G5 2,7Ghz - 2GB - Radeon 9650 - MorphOS 3.14
AmigaONE X1000, 2GB, Sapphire Radeon HD 7700
FPGA Replay + DB 68060 at 85Mhz

@Acill

Quote:

After reading through the update experiences here and over at amigans.net I get the impression it may be a good idea to hold off on doing it? Seems like the new kernal isn't very stable in a lot of things and people are reverting back to the one found in update 1?

The only thing which may indeed be an issue is the new kernel (or, it's just a new kernel that shows up with other issues, dunno). But update2 contains quite a looooot of fixes, improvements, and changes. So it 100% must. But then after you install update2, all you may need is just to rollback only kernel to the update1 version, and all will be fine.

But again, if you expect the things which you shouldn't, maybe indeed better use MorphOS ?:)

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites

@Acill: I think it depends on your installation and the software you use. There are one the other hand users like me and others, who had no issues at all by now. But I had to admit that my AOS4 FE-installation was very basic with not much additional software added.

And switching to the old kernel till further official bugfixes could be a valid solution, too.

_________________
AmigaOne X5000/40, 2.2 Ghz, 4 GB RAM, Radeon R9 280X, M-Audio Revolution 5.1, 240 GB SSD