Who's Online |
113 user(s) are online ( 58 user(s) are browsing Forums)
Members: 1
Guests: 112
BillE,
more...
|
|
Headlines |
-
amidisas.tar.bz2 - development/utility
Apr 16, 2024
-
wildmidi.lha - audio/play
Apr 15, 2024
-
liba52.lha - development/library/audio
Apr 14, 2024
-
libcurl.lha - development/library/misc
Apr 14, 2024
-
libopenssl.lha - development/library/misc
Apr 14, 2024
-
bermudasyndrome.lha - game/action
Apr 14, 2024
-
amigagpt.lha - network/chat
Apr 14, 2024
-
curl.lha - network/misc
Apr 14, 2024
-
dgen_sdl.lha - emulation/gamesystem
Apr 12, 2024
-
amiarcadia.lha - emulation/gamesystem
Apr 11, 2024
|
|
|
|
|
Re: OWB 2.14
|
Posted on: 2008/11/17 2:46
#1121
|
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.
|
|
|
|
|
|
Re: OWB 2.14
|
Posted on: 2008/11/15 18:06
#1122
|
Just can't stay away
|
@nubechecorre Quote: Is the download function included in this version ?  No, I haven't implemented it yet.
|
|
|
|
|
|
Re: OWB 2.14
|
Posted on: 2008/11/15 18:01
#1123
|
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).
|
|
|
|
|
|
Re: OWB 2.14
|
Posted on: 2008/11/15 8:17
#1124
|
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.").
|
|
|
|
|
|
Re: Adding comments doesn't work
|
Posted on: 2008/11/15 0:46
#1125
|
Just can't stay away
|
@orgin Quote: 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.
|
|
|
|
|
|
Adding comments doesn't work
|
Posted on: 2008/11/14 18:39
#1126
|
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.
|
|
|
|
|
|
Re: AmigaOS4.1 [On a SAM] and WarpOS apps
|
Posted on: 2008/11/12 13:08
#1127
|
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.
|
|
|
|
|
|
Re: AmigaOS4.1 [On a SAM] and WarpOS apps
|
Posted on: 2008/11/11 17:18
#1128
|
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.
|
|
|
|
|
|
Re: [SAM] GLQuakeWOS Beta 10 and Amiga OS 4.1
|
Posted on: 2008/11/11 16:56
#1129
|
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.
|
|
|
|
|
|
Re: AmigaOS4.1 [On a SAM] and WarpOS apps
|
Posted on: 2008/11/11 2:13
#1130
|
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.
|
|
|
|
|
|
Re: AmigaOS4.1 [On a SAM] and WarpOS apps
|
Posted on: 2008/11/10 20:14
#1131
|
Just can't stay away
|
I've implemented the 440ep support and uploaded a new version to Aminet and OS4depot.net.
|
|
|
|
|
|
Re: Debian / Dual boot on Sam 440EP
|
Posted on: 2008/11/10 15:44
#1132
|
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).
|
|
|
|
|
|
Re: Debian / Dual boot on Sam 440EP
|
Posted on: 2008/11/10 0:56
#1133
|
Just can't stay away
|
@Elwood Quote: 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.
|
|
|
|
|
|
Re: Debian / Dual boot on Sam 440EP
|
Posted on: 2008/11/9 19:20
#1134
|
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.
|
|
|
|
|
|
Re: AmigaOS4.1 [On a SAM] and WarpOS apps
|
Posted on: 2008/11/9 19:10
#1135
|
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).
|
|
|
|
|
|
Re: AmigaOS4.1 [On a SAM] and WarpOS apps
|
Posted on: 2008/11/7 22:16
#1136
|
Just can't stay away
|
@freddix Quote: I've followed informations I've found over the net like downloading the WarpOSEmu.lha file from AMINET and installing it ... but ... no WarpOS application work. The WarpOS wrapper which is included in the AmigaOne version of AmigaOS 4.1, on Aminet and OS4depot.net only works on 60x, 750 and 74xx CPUs. It can't work on Book-E CPUs like the 440ep, some things required for it aren't compatible in such CPUs and I didn't have the time to reimplement it for the 440ep yet.
|
|
|
|
|
|
Re: CD-Rom Boot priority
|
Posted on: 2008/11/7 3:03
#1137
|
Just can't stay away
|
@Snuffy Quote:
Snuffy wrote:
Hi @joerg
No, -127 + (-1) = -128. There is no +128 in signed 8 bit integers, the range is -128 ... +127.
Oops, here come my favorite nightmares:
Yes, but 128 must exist before -128 because of signs.
No. The nice thing about twos complement is that you don't need special signed operators, and don't have to convert between signed and unsigned for calculations, but can use the same ones as for unsigned integers: %10000001 (-127) + %11111111 (-1) = %10000000 (-128). Quote: If it doesn't work there is a bug somewhere.
Yes, in the conditional compiler, I would guess. With a compiler that broken you couldn't produce any working executable, and boot priorty -1 would fail already.
|
|
|
|
|
|
Re: CD-Rom Boot priority
|
Posted on: 2008/11/6 18:31
#1138
|
Just can't stay away
|
@Snuffy Quote: Hi @joerg
-127 should work, only -128 isn't supported and using it disables booting for the partition.
'Should' ? If it doesn't work there is a bug somewhere. Quote: -127 + (-1) = 128 OR 'set sign negative' or bit flag = false. No, -127 + (-1) = -128. There is no +128 in signed 8 bit integers, the range is -128 ... +127.
|
|
|
|
|
|
Re: Debian / Dual boot on Sam 440EP
|
Posted on: 2008/11/5 19:29
#1139
|
Just can't stay away
|
@Faranheit Quote: Have you any idea in order to boot again AOS 4 or Linux please ?? Boot AmigaOS 4.1 form the CD, start MediaToolBox, select the HD, in Edit RDB/Install drive replace ub2lb by the SLB (L:SLB_v2) and save the changes to the drive.
|
|
|
|
|
|
Re: Debian / Dual boot on Sam 440EP
|
Posted on: 2008/11/5 19:25
#1140
|
Just can't stay away
|
@Mrodfr Quote: With the new Uboot, It will be possible to install THE ACTUAL Acube linux distributions/AROS/..... WITH AOS4.1 (wiTH SFS or FFS) together and use the sam as a multi-OS platform ???? AROS only if it can be loaded with the SLB as well, not if it only works with it's own nonsense SLB replacement "ub2lb". There can only be one SLB on a HD and you can either install the AmigaOS SLB to load AmigaOS and Linux, or the AROS ub2lb with with you can't load AmigaOS. On the AmigaOne you can use more than one SLB if you use more than one IDE controller (multiple HDs on the same controller are not enough), but IIRC the SAM440 U-Boot doesn't support booting from a sii680, sii3112, etc. Quote: I really want to use SFS with AOS4.1 and linux/aros/... (as new experiences) on the same Sam machine, in the futur  (I'm a SFS fan You have to be very careful when trying something like that ... The AmigaOS SFS and AROS SFS are compatible and you can use AmigaOS SFS partitions on AROS and AROS SFS partitions on AmigaOS, but they don't support the extensions of each other, for example the AROS SFS doesn't support AmigaOS SFS\2 partitions and the AmigaOS SFS doesn't support little endian AROS SFS partitions (DOSType sfs\0). There is no support for AmigaOS/AROS SFS partitions on Linux and you must never write to AmigaOS SFS partitions with a MorphOS version of SFS, like the 'asfs' one included in Linux! Since that can can destroy your data you shouldn't access SFS partitions on Linux, or at least only mount them read-only.
|
|
|
|
|
News feed
OS4 Feedback forum
OS4Depot Feedback forum
Amigabounty forum
OpenAmiga forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
