MikeCarter (+1.0)
 3/12/06 6:11PM |
Absolutely Brilliant
Well done Rob. |
bluenose (+1.0)
 3/12/06 6:38PM |
Well done Rob.
Hopefully this allows Peter to concentrate on the Iyonix version as in the time honoured way of RISCOS someone else has added additional functionality.
I also hope that this spurs on people to contribute to Peter's port of Firefox irrespective of if they have a A9 or Iyonix as this way we all get a up to date browser. I contributed something for the initail release and now that is here I'll be contributing something for the next phase of FF2 that Peter has ststed he'll deliver. |
AW
 3/12/06 8:57PM |
Just need a patch for the StrongARM now! |
maikl 3/12/06 9:55PM |
Will Firefox also work on the Omega with this patch or does it require more emulation? |
highlandcattle (+1.0)
 3/12/06 10:46PM |
Why do you call it unofficial? It's opensourced anybody is allowed to work on it, so it is very much official |
VinceH (+1.0)
 3/12/06 11:19PM |
I'd guess he's called it unofficial because he hasn't recompiled it from the sources to run on the A9Home - it's a combination of the module to emulate the ARMv5 instructions and a patch to the already compiled binary. |
druck (+4.8)
 4/12/06 9:31AM |
AW8: That's a bit more tricky. Rob's module provides in a couple of non critical missing instructions, the CLZ (clear zero) and one of the signed multiply variants. The StrongARM has a few more missing instructions, but the crucial part is the codes use of LDRH/STRH (16bit load/store) instructions which are supported by the StrongARM but not by the RisIOMD memory manager. Any 16bit accessing missing the cache, or not in Kinetic fast RAM, will not be performed correctly.
But anyway, a little patch for the A9 is ok, but anything more is a waste of time, the source needs recompiling for a StrongARM machine or it would be even slower than necessary. Peter or another developer will support the older machines (if viable), when they are good and ready. |
nervus 4/12/06 11:33AM |
This would all be very niceĀ if it worked. Alas I could not force it to do so....
I took a copy of FF and replaced the binary with this patched one: no joy  |
lym (+1.1) 4/12/06 11:43AM |
In reply to nervus:
Did you also download the emulator module, and double-click it (before running FF)? You will also need to make sure that you replace firefox-bin (in the original application directory) with firefox-bin,ff8 (the patched version). Rename the firefox-bin,ff8 to firefox-bin, and make sure the filetype is Absolute. Any luck? |
nervus 4/12/06 11:56AM |
In reply to lym:
I just did that (seemed the most logical approach) and got: "no writeable memory at this address".
BTW I am using an A9home withh the latest patches. |
lym (+1.0) 4/12/06 12:07PM |
Hmm. My A9 seems to be running 4.42 (March 2006): as far as I know it's had all the patches applied, and no trouble here. Have you tried relaxing the compatibility conditions? Otherwise, I'm not sure what the issue is - sorry.  |
nervus 4/12/06 12:29PM |
Well just tried it once more with more lax compatbility :P Did not make any difference...
I guess I will have to ask PN to make an A9home variant of FF  |
EasyKees (+1.0)
 4/12/06 2:41PM |
In reply to nervus:
check the dutch support site for some more info  |
sa110 (+1.0)
 4/12/06 9:34PM |
Firefox does not work on the A9home if Minidisc is loaded or has been loaded. This was also the same with FF1.5. It simply starts then closes straight away. |
rjek (+1.1)
 5/12/06 12:39AM |
AW, maikl: No, this patch will not work on earlier machines. For reasons druck has already outlined, those machines are missing even more instructions, and in the case of the RiscPC, does implement two instructions, but they don't work reliably. (The same may be true for the Omega, I don't know.)
In reply to highlandcattle:
It's not offical. At all. I have nothing to do with the Firefox/Mozilla project, and I am not involved in Peter's efforts to port Firefox to RISC OS. Just because it's open source does not mean that it's "official".
In reply to nervus:
Make sure that you have unzipped the new firefox-bin file from the Zip file, change its filetype to Absolute (or ff8) if it isn't already, and then copy it over the original in your !Firefox directory. Then double-click on !Firefox, having first run the v5Emulator module.
In reply to sa110:
I've just downloaded Minidisc, and hacked it to work on the A9 Home I have here (it tries to load CallASWI when it really doesn't need to). Both with it seen by the Filer, and with it running, Firefox still works for me. (Downloaded the lastest version available from minidisc.iconbar.com this evening.) |
nervus 5/12/06 7:03PM |
In reply to EasyKees:
Did as you indicated on the dutch site: still no joy
in reply to rjek:
did just all that (as I wrote in my post of 4/12/06 11:56AM), tried it once more with the solution of EasyKees (a prefab patched FF2) and it really doesn't work.... back to the workbench???
Luckily I have also other means to access the Net (on my Macs), the A9home is a hobby IT-project for my son (an IT bachelor) and me. |
CKH2 7/12/06 6:31PM |
Firefox 2 does not work on my A9 - I get the error 'no writeable memory at this address'. I replaced the firefox-bin with the new file, filetyped absolute and put the emulator in PreDesk (and double clicked it). |
rjek (+1.0)
 7/12/06 7:44PM |
In reply to nervus:
In reply to CKH2:
I suspect these errors might be due to you not having at least 32MB of memory free before you try running it. Firefox 2 requires a 20MB WIMP slot - it may be that *WimpSlot cannot allocate that much memory. Other than trying to quit all other applications and such before trying to run Firefox 2, I don't know what to suggest. "It works for me" etc. |
rjek (+1.0)
 7/12/06 8:25PM |
Also, can either of you try http://www.rjek.com/firefox-a9home.zip instead? |
nervus 8/12/06 8:08PM |
In reply to rjek:
I tried your solution today. What happened is shown by this screenshot:
http://www.glimmerveen.net/problems.jpg
|
sa110
 8/12/06 8:38PM |
In replyto nervus:
Is that Aemulor I see loaded on your iconbar. If so I believe that maybe the cause of your memory problems. Quit Aemulor (the module not just the front end). Try FF2 agaiin. |
nervus 8/12/06 9:30PM |
in reply to sa110:
Just checked it once more without Aemulor (killed frontend and module). The ffault message has disappeared now, there is somme harddiscc activity and then: nothing... The bugger is not loading... Some more hounds to call in for this Fox-hunt??  |
sa110
 8/12/06 10:48PM |
In reply to nervus:
Go into your !UnixHome.home folder and delete /mozilla
Try to load FF2 again. |
nervus 9/12/06 8:18PM |
In reply to sa110:
well tried everything today: .... and it still won't work <sigh>
Ah well, at least I tried
Tnx for all the help!  |
| |