@xenic

Quote:
Confirming your statement about IBrowse. I just experienced the same issue with the submit button in my last post. I was using IBrowse, editted my post to add some "...." at the end and the submit button did not return me back to the forum page.

---
redfox

Just testing another theory. .......

@redfox

Hmmm ...

The "Post Comment" button works just as expected when posting a comment to a news item.

---
redfox

@redfox

Trying another option.

@redfox

Posting with OWB 3.14 to test a theory.

---
redfox

@redfox

This one is with OWB 3.14 again and I have to hit the cancel button to return to the forum.

---
redfox

@broadblues

Nor with OWB 3.13 (for me).

----
redfox

@redfox

OK ... it looks like the submit button does not return me to the normal webpage I was viewing before I hit the reply button. So far, this is amigans site only.

My post is actually submitted, but I have to click the cancel button to get rid of the post entry form.

---
redfox

@redfox

That was interesting. When I hit the Submit button for my previous post, I did not return to the webpage. I had to click the cancel button to return to the webpage, but my post came through ok.

---
redfox

@unimon

Posting with OWB3.14. Seems to work fine so far for me. Still checking out websites.

Thanks J?rg.
---
redfox

@MamePPCA1

What user name do you use on AW ? I could not find you over there.

I was able to stop most of the freezes on my system by disabling compositing features in AmigaOS 4.1.

I use the following theme, which disables the compositing features and some other stuff.
Prefs/Presets/Default/1024x768 no hwaccel

There are similar themes for higher screen resolutions.

If you have only 256 MB of RAM, this may also be a problem. If you have lots of programs running and open a new window or try to move a window, it creates a low memory condition. The system tries to move stuff out of memory and over to the SWAP partition and causes a freeze for several minutes while this is happening. If you wait long enough the system should eventually come back to life. I don't know how to disable this feature. I usually re-boot if it takes too long.

---
redfox

@jaokim

I just noticed that you have a Radeon 7000 grapics card and a SoundBlaster card. At one time this was not a good combination, not sure if they work ok together with OS4.1.

Not sure how much Video RAM is normally available on a Radeon 7000 graphics card, but you might try disabling the compositing stuff in Prefs/GUI.

With the MicroA1, we run into a problem with not enough onboard Video RAM. We have only 32 MB of Video RAM. I use the 1024x768 no hwaccel theme in Prefs/Presets/Default drawer. This kills most of the compositing and transparency effects on the Workbench, but also frees up alot more Video RAM for other stuff.

---
redfox

@ChrisH
@Chris
Quote:

Confirmed. I run with Compositing disabled ...
Confirmed, NetSurf runs just fine with Compositing enabled.
Thanks, mystery solved.

I have a MicroA1, which of course came with only 32 MB Video RAM soldered to the motherboard. I run into problems with system slowdowns and freezes if I enable the compositing modes, because these modes eat Video RAM for breakfast and the MicroA1 just doesn't have enough Video RAM available. Turning off compositing modes allows my system to function quite adequately.

I use Prefs/Presets/Default/1074x768 no hwaccel theme as my default theme. This disables all the compositing features.

So, I temporarily enabled Compositing mode as follows ...
I went into Prefs/GUI options and clicked on Compositing mode
left all compositing effects set to 0% (default)
clicked Use button to enable temporarily.
NetSurf worked as expected with all window contents preserved. I could open windows infront or move the NetSurf window off screen and contents did not disappear.

However, with compositing enabled and only one application running (NetSurf) I was already using up 24 MB of Video RAM with only 8 MB of video RAM left available for surfing and other windows, etc.

Reboot ... back to normal (compositing disabled).

---
redfox

@Chris_Y

Thanks for the update.

Using the graphics.library version of NetSurf 2.1 on Workbench screen.

I noticed that some of the contents of the NetSurf window tend to disappear if I open another window (such as About... or NotePad) in front of the NetSurf window and drag that window around. As soon as I make the NetSurf window active again and scroll, contents return. I have ClickToFront in my WBStartup drawer. Contents of the NetSurf window also tend to disappear if I move the NetSurf window part way off the screen and back.

My mouse pointer froze a mement ago when I was working on this post. Had to boot to wake up my system. Not sure if I can duplicate.

---
redfox

@xenic

Regarding the realtor site, on my system I see memory being gobbled up as the houses scroll past. It wasn't as bad as the animated gaah gif and animated avitar problem that occurred with an earlier version of OWB.

I didn't wait long enough to see if my system froze up, but I was down to 124 MB when I jumped away from the website. My system is a MicroA1 with 750GX CPU and 256 MB RAM.

---
redfox

@orgin

Installed OWB 3.13 just a few minutes ago and posting now.

@joerg

Smilies pages are working just fine now. Thankyou so much. I don't use smilies very often and was very surprised when the smilies pages caused a crash in version 3.12.

Thanks
redfox

Just when I thought it was safe to use OWB 3.12 exclusively, it crashed while closing the Smilies page on amiga.org. I can reproduce this crash about 6 times out of 10.

Reply to a post,
click on the (more...) smilies link below the text window.
it does not matter if you actually click on a smilie on the smilies page
click on the Close button at the bottom of the smilies page.

Guru Meditation: 80000003
Task 0x6cc1e910 ("OWB")
generated an error of type ISI (Instruction Storage Interrupt)

Crashlog sent to OS4Depot.

---
redfox


UPDATE ... crash happens at all three amiga sites...
amiga.org amigaworld.net and amigans.net

Crashes when I click the Close button at the botton of the Smilies page.

Thanks Joerg. OWB 3.12 is working fine.

The wunderground website is working fine now.

Thanks,
redfox

@redfox

I have been using OWB 3.11 for about two hours. Seems to be very stable so far. Typing posts at amiga.org, amigaworld.net and amigans.net is working just fine. Typing speed is just like OWB 3.7. I have also downloaded some stuff and that works just fine.

So far I have seen GR on two websites. Both sites work fine on OWB 3.7.

One site was reported by Tomas over at amigaworld.
http://www.wunderground.com/global/stations/01271.html
If I go directly to that link, I get a GR. However, if I start at the top and work my way down through the website most of the pages are just fine. Then I reach a point where I can pick a station. Does not matter which station I choose, I get a GR. Does not matter which country or city I choose, the final page gives a GR. Not sure what is different about the final page, may be different fonts or advertizing.

The other site where I get a GR is a very large collection of photos. I think I'm simply running out of RAM at that site.

MicroA1 with 750 GX and 256 MB RAM running AmigaOS 4.1 and OWB 3.11.

---
redfox

@orgin

Using OWB 3.11 right now. Seems much faster for typing a post than OWB 3.10. Will comment again later after I've driven it around the net abit.

---
redfox