Netsurf V3.0 Amiga release 2

[unusedunused]

thanks for your results.

The time 17,5 is this load full page ?

what internet stack you use on classic(miami or amitcp) ?

the scroll speed 7 sec is because your GFX card do not support rbg15 mode (no PC)
what gfx Card you have ?

[unusedunused]

Yes, full page load of amigaworld.net is 17.5.

And after how many seconds does the page first show and load visible more data ?

the number of the fetchers is important that you can scroll the page before it is full load.
If you have too much fetches there is no time to scroll the page.

so try out to scroll page as soon it is show.most time to read a page or click on a link you need not wait until all is load.

>According to scout, Netsurf always picks the "PC" mode even though non-PC modes are >available and working.

you can maybe try a screenmode Promoter to choose a non PC 16 bit mode.but make sure that you dont change the depth and size of the promotet screen.

but anyway when i have time, i look wy it is so slow.when scroll there need only 10% of the screen new draw and byteswap.the rest of the image can copy 10% up or down with GFX Card blitter

so its strange wy the wrong pixel Mode slow so much down

[unusedunused]

maybe you look in scout at the screen and screenmode ID, if thats really a rgb16 screen and no rgb16 PC.

or the P4 do not support this really and work in both modes same.

what do you use P96 or CGX ?

[unusedunused]

>If your screen is 1024x768 from boot, Netsurf will scroll very slowly.

I think the problem is the 4 megabyte GFX Mem only.SDL need a mirror map that is on GFX Card.

1024*768 are 1,6 megabyte of GFX ram.
this mirror map is used so a scroll work well when the netsurf window is partly cover by other windows.

if you open a WB then you need too 1,6 megabyte GFX Ram.so you need 3,2 megabyte of GFX RAM.that can all run well but....

Have you background images that need lots of RAM ?

If you have a background image that is show in this 1024*768 size, need too 1,6 megabyte of GFX RAM.and thats too much.and when you load another wb lister background thats again 1,6 megabytes.

maybe you use only small tiles instead of a full picture as background, this can save you lots mem.maybe this help also that the p96speed benchmark run always fast.when teh bench run slow, then P96 begin to move out GFX data to amiga ram or do not alow malloc of data in GFX Card ram and then its go slow

[unusedunused]

>Same results as selecting "NoBlitter=No

this is the setting that should use and then Hardware Blit work.

when set  NoBlitter=YES then the P96 bitblit test should go slow.

@MozzerFan

You can show amigaworld page faster than other.Have you cyberpatcher or oxypatcher install ?
.maybe that speed up things. netsurf is compile for 68040.

>Is it posible to run Netsurf on it's own separate screen ?

yes, see old posts here, but there are reports that also with screenmode promoter and rgb16 it scroll not fast.

maybe P96 do not remove the workbench screen and background pictures. also when there is another screen open.

then need 1,6 megabyte wb screen 1,6 megabyte background but now a 1,6 megabyte new screen and when the 1,6 megabyte mirror map for SDL is alloc it get no data on GFX Card mem.

[unusedunused]

Winuae.

68040 with FPU and JIT turned on, AGA, 8mb fast + 128MB Z3 fast ram, 2mb chip, rom version 3.1 and 32mb RTG.

You need a 68040.library that is install from AOS.the one i have is from 1994 and 43.888 bytes in size.

but when you move files from a classic 68060 install you have a 68040.library that want load the 68060.library

if you want use that you can choose as CPU 68060 in winuae.then it should work as before.

but never switch on in winuae 68060 CPU if you have not the phase 5 or from somebody else 68040 and 68060 library install

also i think best is use 68040, if you notice any problems in winuae 060 mode.

[unusedunused]

Here is a program that show what PixelModes your GFX Card support.seem not all Amiga GFX Card choose the in the CGX Manual suggestet RGB16 Pixelmode for screens.And when this is not done, data need convert and slow all down.

I change now in test SDL so it ask for a Pixelmode that the GFX Card support.This work ok with P96 and Voodoo 3.

maybe there is some common pixel Mode all GFX Cards support.The test can run from shell and check if a mode id is here for RGB16, RGB16PC and BGR16PC

winuae can support screens in RGB16 and RGB16PC when choose in Page expansions the mode all.

when use RGB16 also SDL games run 60% faster on winuae.

Here can download and should start from shell

http://www.daten-transport.de/?id=D2npn5h4tcyW

so please post values you get and the GFX Card you use.If you have CFX and P96 install and you are able to post both values, its also usefull to see what P96 and CFX do.

Try also the test 2* to see if the values are the same

[unusedunused]

>Update: I did a little research on the problem. I think there is a bug in the new version >and it is triggered by the fullscreen setting!
>When it is set to 0, everything works ok. When it is set to 1, NetSurf insists to open in a >window at the WorkBench screen.

too bad, before i post a link to test what pixel mode the gfy cards of the user support, but nobody test this and give feedback.

to see what happen look in sashimi output what sdl tell you.
maybe your GFX Card driver is broken in some kind and report SDL that there is a RGB16 screenmode, but you have none.

I see that happen on a SPectrum GFX Card on CGX.I use then iscybermode id and so i can see that the mode report is wrong.

maybe you can do the pixelmode test from shell and post results and your GFX Card

http://www.daten-transport.de/?id=yXDfJTmY7sMG

To get netsurf fast scroll you need a GFX Card that support RGB16 mode (pixel Format 7)
and need this settings for fullscreen

fullscreen:1
window_depth:16        

or you can run your workbench in a RGB16 pixelmode and use netsurf on window