Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
130 user(s) are online (67 user(s) are browsing Forums)

Members: 1
Guests: 129

beworld, more...

Headlines

Forum Index


Board index » All Posts (joerg)




Re: OWB 2.15
Just can't stay away
Just can't stay away


@salass00

Quote:
@joerg

Quote:

* Built the current versions of libcairo and libpixman-1 as static link libraries, with the static libraries OWB works on AmigaOS 4.0 again.
I assume these are built with newlib, right?
Of course.

Quote:
If so could you upload them to OS4Depot? I tried building them a while back but I must have done something wrong because the program I compiled with them just crashed immediately (I didn't have this problem with Andrea's port).
I didn't have to port anything, for both it was just configure && gmake.
It's an incomplete version, I disabled everything not required by OWB (PDF, PostScript, etc.), it doesn't include the amiga bitmap surfaces of the AmigaOS 4.1 Cairo and I only built static link libraries, no shared objects, but if that's no problem I can upload the libraries and includes.

Go to top


Re: OWB 2.15
Just can't stay away
Just can't stay away


@nubechecorre

Quote:
Are the gif supported ?
Gif anims currently don't work in OWB (all versions, it's not related to the AmigaOS 4.x port).


@Kicko

Quote:
When i start OWB it asks me for..
Please insert volume file: in any drive. If i press cancel then it goes to my page.
Here it even crashes after pressing cancel
Network handling, incl. file:// URLs, is done by libcurl in OWB. As I wrote in the release notes the static versions of most libraries I have are older and may have more bugs than the shared versions, the static libcurl.a is obviously such a case and handling of file:// URLs is broken in it.

Go to top


Re: OWB 2.15
Just can't stay away
Just can't stay away


@ShInKurO
Quote:
Quote:
* OWB 2.15 is linked with static libraries. Might fix the startup crashes I never get on my systems,

I've isolated this problem: it depends by SFS. I've moved my entire system from SFS partitions to FFS2 partitions, and now OWB doesn't crash anymore, and even NewsCoaster now right works...
Please joerg test yourself,
Except for test partitions for the PartitionWizard FFS functions I don't have any FFS partitions, my SYS: partitions and the ones on which OWB is are SFS partitions.

Quote:
Here A1 G4 underclocked to 800mhz, 256mb ram, OS4.1, hd IDE on SiL060...
Try if it works using a slower speed, for example if you HD supports UDMA5 use UDMA4, and make sure the cables are correct (80 wire flat, don't use round cables and check that the master/slave drives are connected to the matching connector).


@nubechecorre
Quote:
For os 4.1 user is better to use this version or the previous one about the speed ? as the previous one used the Cairo.. ?
2.15 uses Cairo as well, even a newer version than the one included in AmigaOS 4.1. OWB never used the AmigaOS bitmap surfaces which are only in the AmigaOS 4.1 version of Cairo. With static libraries it should be a little bit faster than with shared ones, and it's loaded much faster.


@walkero
Quote:
Have you ever thought to use one of the existing download managers like Charon or HttpResume through ARexx (http://www.heightanxiety.com/)?
That would have the same problems as the download hack in OWB Blastoise: OWB would abort the download and pass the URL to the download manager which would download it again, and that doesn't work on some sites which only allow a single download per IP.

Go to top


Re: OWB 2.14
Just can't stay away
Just can't stay away


@Swoop

Quote:
OK, Does anything in the crashlog indicate ony other source of the crash?
No.

Quote:
Any idea what libxml calls, or uses?
Nothing external in the xmlCharEncInFunc() function which crashes at line 1864 of encoding.c (if addr2line returns the correct data in this case, often it doesn't for shared objects), except for indirectly realloc() or malloc() maybe.

Go to top


Re: OWB 2.14
Just can't stay away
Just can't stay away


@Swoop

Quote:
Swoop wrote:
@Raziel

Quote:
I filed a Crashlog report for joerg to investigate, maybe we can nail those damn suckers once and for all
It doesn't look like the usual crashes when loading shared objects, which I never get on my systems either. But as long as nobody builds a current, static libcairo.a, I wont do it, I can't build a statically linked executable of the current OWB like I did for an old version ( http://strohmayer.org/sfs/download.php/OWB_Doduo_static.lha ) for testing if it's related to using shared objects or not.

If libxml2 2.702 causes more problems I'll include the old 2.701 again in the next OWB update, I don't have the time to maintain the AmigaOS 4.x ports of the libraries OWB uses as well, or even search and fix bugs in them, if I'd do that it would take me 20 years instead of "only" about 5 to create a usable browser from OWB ...

Quote:
I can confirm that. I get the same crash.

Visiting http://tamar.4players.de/phpBB, OWB 2.14 crashed everytime using the latest 2.702 14/11/08 version of libxml2-2.6.so, but if I downgrade to version 2.701 it loads fine.
I doesn't crash with libxml2 2.702 on my A1 with 750FX.

Go to top


Re: OWB 2.14
Just can't stay away
Just can't stay away


@COBRA

Quote:
I didn't know that OWB even supported context menus.
It doesn't, at least not the SDL and AmigaOS 4.x versions, it's been a long time since I last build a GTK version of OWB. But WebKit does, and like for a lot of WebKit features there are some empty functions in OWB for which "just" platform specific implementions have to be done.

Go to top


Re: OWB 2.14
Just can't stay away
Just can't stay away


@nubechecorre

Quote:
Is the download function included in this version ?
No, I haven't implemented it yet.

Go to top


Re: OWB 2.14
Just can't stay away
Just can't stay away


@orgin

Quote:
The descriptive text in the openamiga pdf is just a guideline to describe what the pointer type could be used for, it does not prevent you from using it for other similar purposes. For example the context menu pointer type is suitable to use to indicate that the pointer is currently hovering over a position that would produce a popup menu when left clicked.
As Chris wrote not with the current image, with the different shadow representing a smaller distance to the background, the raised menu, it's the correct image while displaying a (popup) menu, but it doesn't fit to indicate there is one at the current position. When others create pointer themes they'll very likely use the ones from Mason as reference.

Quote:
The latter description just didn't end up in the pdf since the most common way of activating the popup menu is to right click at an arbitary position that wouldn't normally produce a popup menu had you left clicked.
That's the common way to access the general (popup) menu of an application, right click somewhere where no special context menu is. But for that you have to know where context menus are. For example in a web browser there can be a context menu for images (without link, for images with link the linkpointer would be used even if there is a context menu as well) with "Save image as ...", "View separately", etc. If it's activated with the right mouse button the OWB contextMenuCursor can be used to indicate you'll get a special context menu there instead of the "Project", "Edit", etc. menu you get everywhere else on the page.

Quote:
In which case you couldn't display another pointer type before the popup menu opens. If you want me to I could easily add that to the pointer description in the document for the next release.

Note that I said 'pointer type' above. The type is still applicable in this situation even if masons graphical representation might not be.
Since the image doesn't match the description the docs should be updated to clarify the purpose, but IMHO it would be even better to include both since the images have a different purpose and we have both already, for example rename the current one in the openamiga archive to menupointer (to be used while a menu is active) and use the OWB version as contextmenupointer (to indicate there is a context menu at the current mouse position).

Go to top


Re: OWB 2.14
Just can't stay away
Just can't stay away


@orgin

Quote:
Btw the sys/def_contextmenupointer.info is in the openamiga pointer archive. It just looks similar to the normal one. Mason wanted it like that for his 'theme' of the pointers.
Maybe I didn't understand the docs correctly, but IMHO it's something different. If it supposed to be the same the image used for it doesn't make sense.

The OWB contextMenuCursor will be displayed if there is a context menu at the current mouse pointer position and clicking the mouse will open a context menu, IIRC it's the same in NetSurf, but the openamiga contextmenupointer should be used while the context menu is displayed ("To indicate that a context menu is active.").

Go to top


Re: Adding comments doesn't work
Just can't stay away
Just can't stay away


@orgin

Quote:
Just tested with firefox, ibrowse,owb,epiphany and opera without problems:

http://os4depot.net/index.php?functio ... ibrary/misc/warposemu.lha

I cannot reproduce your problem.
Seems it has problems if there are ">" chars, since [ quote ] isn't supported I tried to use that instead. In the preview it works, just not when adding the comment.

Go to top


Adding comments doesn't work
Just can't stay away
Just can't stay away


I tried to add a comment to library/misc/warposemu.lha with FireFox, OWB and IBrowse but it's the same with all browsers, preview works but adding the comment doesn't and always results in an empty comment.

Go to top


Re: AmigaOS4.1 [On a SAM] and WarpOS apps
Just can't stay away
Just can't stay away


@nexus

Quote:
But what is the reason, that everything with warposemu behaves so different compared to AOS4.0 classic?
Do you have a sound card in your classic Amiga? If not a part of the problem is AHI. No idea why, but AHI causes problems in nearly all WarpOS games, for example background music has to be disabled in FreeSpace, Herertic II and Shogo or they crash. Try if disabling sound helps in other games as well.

Additionally there could be some hardware banging, for example the WOS version of one game (IIRC Payback, but I'm not sure) accesses the classic Amiga audio hardware directly and only the m68k version supports sound in a system legal way, WipeOut2097 writes some debugging information to a fixed address in chip RAM without even trying to allocate it (the OS4 powerpc.library includes a workaround for this bug), etc.

When using hardware 3D it should be obvious why there are much more problems on Radeon cards than Voodoo and Permedia: There was no Warp3D support for Radeon gfx cards yet when these games were written and they could only be tested with Permedia and Voodoo cards, bugs which don't cause problems on these cards couldn't be found.

Go to top


Re: AmigaOS4.1 [On a SAM] and WarpOS apps
Just can't stay away
Just can't stay away


@corto

Quote:
And thank you again for the technical explanations. I understood them but how did you fix the problem for the Book-E model ?
With an ISI handler (IExec->SetTaskTrap(TRAPNUM_INST_SEGMENT_VIOLATION, ...)) which adds the executable bits in the TLBs in WarpOS tasks.

Quote:
If I really understand, on G3 for example, you did set the execute flag of the page where the code was copied ?
Yes, but it's not page based, the segment registers (16 * 256 MB) are used for it.

Quote:
With the MMU related functions in exec ?
No, they don't support something like that, for normal OS4 code it's not required, and shouldn't be possible, to mess around with such things.

Quote:
On Sam440, what happened before the fix ?
Nothing, the OS4 powerpc.library checks the supported hardware and version 16.39 couldn't be opened on the SAM440.

Quote:
I just try to improve my knowledge in AmigaOS programming.
Most of it isn't AmigaOS related, just low-level PPC assembler programming.

Go to top


Re: [SAM] GLQuakeWOS Beta 10 and Amiga OS 4.1
Just can't stay away
Just can't stay away


@Rogue

Quote:
That doesn't have anything to do with the SAM. There are general incompatibilities with WOS programs and Radeons.
No only Radeons, although for example hardware 3D in Heretic II worked correctly with 2 or 3 beta versions of the OS4 Voodoo3 Warp3D driver it doesn't with the release versions.
Shogo doesn't work correctly with hardware 3D on Voodoo3 either.
FreeSpace does, but only after changing some of the default settings (en-/disabling some 3D gfx options).

Quote:
But plainly, for the few WOS programs around where there is no AmigaOS 4.x native version, I am not going to bother with these.
AFAIK the only Warp3D game without software 3D support is WipeOut2097 and that one is working (the 3D gfx parts, not everything else of it). On Voodoo3 without any problems, and IIRC only very minor gfx errors were reported on Radeon cards.
The other 3D games support software rendering, and since they were written for A1200/A4000 with slow CPUs (150-200 MHz 603/604), slow 3D gfx cards (Permedia2) and WarpOS which slowed everything down even more with it's m68k<>PPC context switches they are probably faster with software rendering on a SAM440 than they were with hardware 3D on the classic Amigas.

Go to top


Re: AmigaOS4.1 [On a SAM] and WarpOS apps
Just can't stay away
Just can't stay away


@nubechecorre

Quote:
There is an error on the archive infact the wrapper doesn't work here on sam, the powerpc library is the version 16.39 and not 16.40..
Ooops. The library in the archive is the new version, but it had the old version string and therefore wont be installed if you had the AmigaOne/classic Amiga version 16.39 installed already.
I'm uploading it again with the correct version.

Go to top


Re: AmigaOS4.1 [On a SAM] and WarpOS apps
Just can't stay away
Just can't stay away


I've implemented the 440ep support and uploaded a new version to Aminet and OS4depot.net.

Go to top


Re: Debian / Dual boot on Sam 440EP
Just can't stay away
Just can't stay away


@Elwood

Quote:
Could you try with the Parthenope which is in this CD?
What for? He wants to use AmigaOS 4.1 and Linux, not AROS and Linux.

Until the SLB parts in the SAM440 U-Boot are fixed the only way to install Linux and AmigaOS 4.1 is using the old kernel partition boot method for Linux (dd the kernel to an unused partition and use diskboot for loading it).

Go to top


Re: Debian / Dual boot on Sam 440EP
Just can't stay away
Just can't stay away


@Elwood

Quote:
@joerg

Are you sure?
Yes, I did build the SAM440 version of the SLB (the one with SFS/2 support added). Nothing has changed since Linux booting support was added and it's still working without any problems on my A1, if it doesn't work on the SAM there is a bug in the SAM version of U-Boot.

Quote:
Uboot has ext2 commands but no ext3 commands:
For reading there is no difference anyway, ext3fs is nothing but ext2fs with added journalling, but they probably don't have anything in common with the Linux booting parts of the SLB, which had to be put inside of U-Boot because they use GPL code.

Go to top


Re: Debian / Dual boot on Sam 440EP
Just can't stay away
Just can't stay away


@Elwood

Quote:
I found that the Linux partition must be formated in Ext2 in order for SLB to find the a1boot.conf (so SLB does not support Ext3).
Then it's a bug in the SAM440 U-Boot, the Linux booting code incl. the ext2fs/ext3fs parts isn't in the SLB but in U-Boot, the SLB just calls the U-Boot functions for Linux booting.

Go to top


Re: AmigaOS4.1 [On a SAM] and WarpOS apps
Just can't stay away
Just can't stay away


@corto

Quote:
From a technical point of view, I would be curious to learn what you do that is not compatible with Book-E processors. I suppose it is related to MMU ...
Since WarpOS executables use the m68k HUNK executable format their PPC code is loaded in non-executable RAM and the OS4 powerpc.library has to make it executable. On the other CPUs that's done with the segment registers which don't exist in Book-E CPUs.

Quote:
Edit : Hum ... maybe about the FPU ?
That didn't even work on 60x, 750 and 74xx CPUs, a lot of WarpOS software uses unaligned FPU accesses which even those CPUs don't support and a lot of WarpOS software can only work because powerpc.library installs alignment exception handlers which emulate them using integer accesses.
On the SAM440ep that's probably not required since the SAM440ep kernel includes an alignment exception handler already, unlike on 60x, 750 and 74xx CPUs on the 440ep 4 byte alignment isn't enough for 64 bit FPU accesses (it must not cross a 16 byte boundary, which is automatically the case if the alignment is correct: 4 bytes for float, 8 bytes for double).

Go to top



TopTop
« 1 ... 52 53 54 (55) 56 57 58 ... 83 »




Powered by XOOPS 2.0 © 2001-2023 The XOOPS Project