On Sat, Jun 07, 2008 at 07:59:52PM +0200, Rien Mertens wrote: > In message <[EMAIL PROTECTED]> > John Tytgat <[EMAIL PROTECTED]> wrote: > > > I have a quick look at the source of WimpSWIve and it makes some assumptions > > which are a bit questionable (like having the same SWI chunk as the > > WimpManager...) so I would suggest that someone takes this up first with > > the WimpSWIve author(s) (<URL:http://www.ajb121.net/riscos/>) and/or > > try to identify the problem in more detail instead of bothering Advantage6 > > or RISCOS Ltd.
If you read the ReadMe that comes with WimpSWIve it does say that assuming the same SWI chunk is a bit dodgy but that it's the only way to act without sitting on the SWI vector and dealing with every single SWI that happens to quite some performance penalty. It's always been a bit of a hack. > OK, I have just sent a message to the maintainer of WimpSWIVe. I hope > his address is still correct. I see now that he does not have any RISC > OS machine anymore; I was not aware of that at the moment I wrote the > e-mail. I hope he wants to have a look anyway, I have suggested I can > test it on two A9 computers. The original author Andrew Clover has been off the scene (or at least very quiet) for at least 8 years, and AFAIK Andrew Booker just did the 32 bit conversion. The sources to WimpSWIve are available so I suggest anyone who wants to look at this does it themselves, as A9 owners can test it much more easily. On the subject of LegacyHAL, I'm told that my CryptRandom module causes the A9 to crash when some HAL options are turned on (which exactly, I don't know). I've never actually seen an A9 to test the problem - someone's offered to lend me one but so far we've not succeeded in getting me and it in the same place at the same time. UnixLib uses CryptRandom for providing /dev/(u)random, and Firefox probably uses that for SSL code (among other things). UnixLib will still work without CryptRandom but refuse to open /dev/(u)random. Apps like Firefox might possibly have a backup plan if this happens, so try removing CryptRandom from your System: path and seeing if you can get Firefox to work, first without LegacyHAL and then with it. Don't try any sensitive SSL sites in this state as your SSL connections won't be secure, so this is just for testing. Theo _______________________________________________ GCCSDK mailing list [email protected] Bugzilla: http://www.riscos.info/bugzilla/index.cgi List Info: http://www.riscos.info/mailman/listinfo/gcc Main Page: http://www.riscos.info/index.php/GCCSDK
