I think you should be good if you delete MOSSYS:Libs/ddc.library. This disables automatic monitor detection and will let you keep the settings you've saved. Just make sure you have a boot CD/USB stick around in case it fails to boot (it shouldn't but better be safe than sorry).

@jacadcaps
thanks thanks thanks
now it works perfectly
the monitor is recognized by how I set it up and retains the settings
I will test all applications with this resolution
and finally I can start using morphos

thanks again if everything works I will buy the key for morphos

Just in case noone asked "how far will it go" :

2656x2160@30Hz !!!

Bunch of caveats:
- needs an active adaptor to convert from DualLink-DVI to DP
- needs a screen going down to 30Hz
- need to boot with CTRL pressed to force the buildin screen to 1024x768 (100% GFX trash otherwise)
- while the correct width at 3840 is listed there seems to be a hardcoded limit at 2656
- resulting screen is distorted to the point of being unusable
- smaller modes are also somewhat distorted

Under OSX it will max out at FullHD but looking good.

-> some fun stuff to tinker with

Quote:

Well, while some of it is true, it definitely depends on the type of monitor you attach to it.
It should be pretty OK if you just attach a FullHD display with some HDMI/DVI input connection to it and even some 2560x1600 (WQXGA) DualLink DVI display should still run OK.
I wouldn't try to get a 4K display (3840x2160) working with it as the GPU used across our supported PowerBooks is pretty much limited to accelerate screens with a max width of 2656 due to some hardware limitations of the clipping unit.
I successfully used a dual screen setup via digital DVI out on my PowerBook5,8 connected to some 2560x1080 or 2560x1440 (WQHD) screen at least.
I have no experience using any of the active DVI->DP converters, though. Using a HDMI input which is pretty common nowadays is probably the better option then. You are limited to single link DVI mode, though, which means it maxes out around FullHD resolutions.

The adapter has arrived now everything works simply by selecting the resolution now the mode is also available
Mob. 1

@cyfm

Bought the adaptor for some other use case and just thought "lets see what happens", bummer bout that HW clipping limit.

I am currently running the iMac + 2nd 1680 screen as my MorphOS machine and it's o.k. but with the adaptor working where it is supposed to work I might shuffle around some screen and end up using the PMacG5 with 2560x1440 + FullHD setup on the 9650 I got in there.

Quote:

ok, great to hear that using a digital out adapter helped your case. So it was down to the analog vga output after all.

@cyfm
the adapter I bought and this:
https://www.ebay.it/itm/274722401141?hash=item3ff6bb2b75%3Ag%3AoI4AAOSwxjZgUNY6&mkevt=1&mkcid=1&mkrid=724-53478-19255-0&campid=5337991599&customid=100t49

now i am rebuilding the system from scratch
i created 4 partitions
and I will try to organize the system differently

I noticed but I still have to check everything well
that previously the videos on youtube with OWB were fluid now seem to slow down somehow.

While wayfarer 1.21 continually crashes on youtube
(I sent all the logs with the program included in wayfarer)

the system is clean at the moment i only added wayfare 1.21

could it be due to the new adapter regarding OWB ?
due to the different frequencies with the external monitor ?

Today I will do some tests with the old adapter to verify

[ Edited by white 04.06.2021 - 13:26 ]

Quote:

I doubt that anything is directly related to the new adapter. Adding a 2nd screen has some impact, though. It requires additional video memory and showing video on the 2nd screen uses the additional video unit. You could try if there is any difference if you run Odyssey and/or Wayfarer on the internal or the external display. MUI offers some easy way to reassign windows to the next screen using the popup window/menu in the upper right corner of the window border.

Wayfarer's video playback should just fail it there isn't enough video ram. I've seen your bugreports but am unable to look deeper into those. One thing you could try would be to make sure that all additional codecs are disabled in settings. ffmpeg, unfortunately, isn't the most stable thing in the world.

@jacadcaps
Thank you,
I have two powerbooks
G4 1.5ghz ati 9700 64mb 512mb ram
G4 1.67ghz ati 9700 128mb 2gb ram

if I use the primary video card everything works perfectly on the external monitor. (1920x1080) with both machines
if select Mob.1 wayfarer crashes with external monitor (1920x1080)

Also with version 1.21 when I close the browser either with the menu or with the window gadget the application is not closed.

I hope it will be useful in some way.

To get the main video card I deleted ddc.library

@cyfm
I confirm OWB is smooth with video playback if I use the external monitor with the primary card without using Mob.1
(only with the G4 with ati 128mb)

[ Edited by white 04.06.2021 - 18:00 ]

Quote:

Due to your tests, I also gave it a quick try on my PBook5,8 with Wayfarer1.21 on an external Mob.1 2560x1080 screen playing some youtube stream and it seemed to work fine. So I guess it needs more details to run into any issues. At least with 128MB vmem it is less likely to run out of video memory but it definitely shouldn't crash as well. It also did set the whole external screen to black once I quitted WF1.21 on that MUI screen.
Did you send any reports to our internal bugtracker with all your crashes/tests ?

@cyfm
I have tried many times
But Wayfarer 1.21 I can never close it I always have to restart the system.
While watching videos works well it only crashes sporadically.

Probably even if it is not important if I use qemu with Wayfarer 1.21 the application closes without problems.

However, taking into account that using qemu I am unable to play videos due to the lack of overlay spoor.

Could it be somehow related to video playback?
And then Wayfarer then does not close because something remains pending?

I searched for previous versions of Wayfarer but can't find them is there a repository with previous versions?
Thanks again.

"I would like to try old versions to see if the problem is identical on my system."



[ Edited by white 11.06.2021 - 11:02 ]

Wayfarer 1.21 still doesn't close if I watch videos on youtube.
If, on the other hand, I navigate normally with Wayfarer 1.21, the application closes without problems.

Is it possible to have some suggestions,
because it doesn't happen every now and then but always.
Thank you.

It would be helpful to know what WkWebView:* processes stick around when you are shutting down. You can check those with ScoutNG or TaskManager.

@jacadcaps
I used "Scout"
it seems that the process that fails to quit is "wayfarer splash" only when I use youtube
I'd like to make a full report via a "log"
but i have no idea how to do it
Is it possible to make a more detailed report?

here a screenshot with the details of the "wayfarer splash" task:
https://imgur.com/iusJDhT


I also tried to force and terminate the process but i can't close it.

Thank you.

[ Edited by white 15.06.2021 - 12:30 ]

Can you retry opening the Tasks window only after you've quit Wayfarer? Scout doesn't update task names for pthreads, so the threads don't actually show up there. If this problem persists in upcoming Wayfarer 2.0, I'll send you a debug build...

@jacadcaps
Thank you,
Here is the new screenshot
this time I used scout as you suggested
I closed wayfarer first and then I launched scout.
After watching a video.

https://imgur.com/VNJlxaB

[ Edited by white 17.06.2021 - 13:32 ]

@jacadcaps
I tried Wayfarer version 2.0
Unfortunately for me
Wayfarer still does not close after watching videos on youtube.
I have tried many times but the problem remains.
(only after watching the videos on youtube)

I sent you a PM with my email in case it is useful for the "log-debug"
Thanks again.

Quote:
However it doesn't matter because Wayfarer is not only YouTube-player. :) The application allows to use many more important and more useful activities... :)

@MDW
Certainly,
I just don't understand why it only happens to me
I have not yet read that this happens to others.
There will be something blocking wayfarer from closing I'd like to fix it.

Quote:

Well, yea, I guess the best way to track this down is some debug build from jaca as it doesn't seem to be some generic issue.

Quote:

It doesn't only happen with your machine.
My sam460, macmini and ibook g4 all do the same.

https://morph.zone/modules/newbb_plus/viewtopic.php?forum=9&topic_id=12823&post_id=150059&viewmode=flat&sortorder=0&showonepost=1

https://morph.zone/modules/newbb_plus/viewtopic.php?forum=9&topic_id=12823&post_id=150065&viewmode=flat&sortorder=0&showonepost=1


[ Edited by Mozzerfan 20.06.2021 - 18:55 ]

Same issue here with iMac g5 20".

I've sent Jaca and Piru some screenshots on IRC too. I'm sure they will be able to track it down.

@All
It is good news
Of course only because it will probably be easier to solve this inconvenience.
Because there are more reports.
At this point you have to be patient a little wayfarer is a great browser.
Thanks again for your work.