Hello All,
I have experienced some lockup/freeze of RPCEmu just recently, whilst
running TechWriter 9.01.
I had run that version of TW quite a bit over the last couple of days
without a problem, but have now had the lockup 3 times in quick succession.
I am running RPCEmu 0.8.9 on Fedora 17 x86_64, and working with files in a
shared dir (ie files in a Fedora dir) in hostfs.
I think the first thing I will try is to move/copy the files from the
fedora host dir to a native dir and see how that works...but as there
hasn't been any trouble until today, that won't necessarily prove much
unless the problem persists.
Any other ideas on how to best track down the cause of this, before I try
some experiments?
Cheers,
--
Regards,
Terry Duell
_______________________________________________
Rpcemu mailing list
Rpcemu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Monday, 2 July 2012
GC / remove global object, was: Patch: avoid repeated initialization/allocation of global object in js_newcompartment
Am Samstag, den 30.06.2012, 14:10 +0200 schrieb Vincent Sanders
<vince@netsurf-browser.org>:
> I suspect that previous editions may need the user to explicitly mark
> the global as ready for destruction before it is replaced. This
> should
> be put in as JS_VERSION conditional code within jsapi.h which
> implements JS_NewCompartmentAndGlobalObject()
I have created a GIT branch and added a few lines for GC the old global
object.
I would be happy if there is some other person who can review this.
The old docs say, that the global object is rooted. So I though calling
JS_RemoveRoot is
the right thing to do. I did not call GC explicitly and setting the
global object to NULL
afterward is mandatory.
Here is the branch patch:
http://git.netsurf-browser.org/?p=netsurf.git;a=blobdiff;f=javascript/jsapi.h;h=25175aa28b2099913d94b05134a5acaf66850329;hp=ac5ada79cece3cf05c2223df6fdb86fed667d747;hb=7d9a5844f9005bceca9337b592d80e30efde8157;hpb=e205f0f99e0cb6ffa0044c6c1322f5da8f795183;ds=sidebyside
Sorry, I don't know how to diff agains master, yet. Sorry, the next
time I will submit such thing as an diff file.
Greets,
Ole
<vince@netsurf-browser.org>:
> I suspect that previous editions may need the user to explicitly mark
> the global as ready for destruction before it is replaced. This
> should
> be put in as JS_VERSION conditional code within jsapi.h which
> implements JS_NewCompartmentAndGlobalObject()
I have created a GIT branch and added a few lines for GC the old global
object.
I would be happy if there is some other person who can review this.
The old docs say, that the global object is rooted. So I though calling
JS_RemoveRoot is
the right thing to do. I did not call GC explicitly and setting the
global object to NULL
afterward is mandatory.
Here is the branch patch:
http://git.netsurf-browser.org/?p=netsurf.git;a=blobdiff;f=javascript/jsapi.h;h=25175aa28b2099913d94b05134a5acaf66850329;hp=ac5ada79cece3cf05c2223df6fdb86fed667d747;hb=7d9a5844f9005bceca9337b592d80e30efde8157;hpb=e205f0f99e0cb6ffa0044c6c1322f5da8f795183;ds=sidebyside
Sorry, I don't know how to diff agains master, yet. Sorry, the next
time I will submit such thing as an diff file.
Greets,
Ole
Re: [Rpcemu] How to recover from bad monitor mode?
Hello Peter,
On Mon, 02 Jul 2012 19:24:56 +1000, Peter Howkins
<rpcemu.howkins@marutan.net> wrote:
> On Sun, Jul 01, 2012 at 02:51:29PM +1000, Terry Duell wrote:
>> Is there a way of booting RPCEmu into a safe screen mode, to allow
>> these sort of errors to be corrected, without having to resort to
>> replacing the hard disc image?
>
> There's a few methods (that apply to real hardware too).
>
> 1) Hold down 'shift' on startup to prevent !Boot from running (which
> loads
> the dodgy mode), and then poke around in !Boot to change which mode is
> used.
I tried to do that but never had any success, so assumed that it was not
possible.
I have experimented a few times since your message, but don't have any
luck in getting it to work.
>
> *or*
>
> 2) Wait till you're in the 'desktop' (or best guess when that it). hit
> F12
> and blindtype 'wimpmode 28' (without quotes) and hit enter. This should
> put you back into 640x480, and then poke around in !Boot to change which
> mode is used.
OK. That puts me in a mode where all I see is what looks like a task
window...nothing else, no desktop. If I type 'Desktop' I get told that the
desktop is running. Is that expected behaviour? At this stage I don't
think I would know how to fix the problem at this level of access, but a
bit of homework might sort that, not sure.
It looks like a backup of hd4.hdf and cfg files before monkeying with
monitor modes, is probably the best and most reliable way to recover.
Thanks for your help.
Cheers,
--
Regards,
Terry Duell
_______________________________________________
Rpcemu mailing list
Rpcemu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
On Mon, 02 Jul 2012 19:24:56 +1000, Peter Howkins
<rpcemu.howkins@marutan.net> wrote:
> On Sun, Jul 01, 2012 at 02:51:29PM +1000, Terry Duell wrote:
>> Is there a way of booting RPCEmu into a safe screen mode, to allow
>> these sort of errors to be corrected, without having to resort to
>> replacing the hard disc image?
>
> There's a few methods (that apply to real hardware too).
>
> 1) Hold down 'shift' on startup to prevent !Boot from running (which
> loads
> the dodgy mode), and then poke around in !Boot to change which mode is
> used.
I tried to do that but never had any success, so assumed that it was not
possible.
I have experimented a few times since your message, but don't have any
luck in getting it to work.
>
> *or*
>
> 2) Wait till you're in the 'desktop' (or best guess when that it). hit
> F12
> and blindtype 'wimpmode 28' (without quotes) and hit enter. This should
> put you back into 640x480, and then poke around in !Boot to change which
> mode is used.
OK. That puts me in a mode where all I see is what looks like a task
window...nothing else, no desktop. If I type 'Desktop' I get told that the
desktop is running. Is that expected behaviour? At this stage I don't
think I would know how to fix the problem at this level of access, but a
bit of homework might sort that, not sure.
It looks like a backup of hd4.hdf and cfg files before monkeying with
monitor modes, is probably the best and most reliable way to recover.
Thanks for your help.
Cheers,
--
Regards,
Terry Duell
_______________________________________________
Rpcemu mailing list
Rpcemu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Re: JavaScript
Hello
If the patch is in netsurf, is there a automatic build, or build instruction, what need to do to get
that compiling and working ?
Does the Atari netsurf now have Java script ?
>
> But there is also one important type missing within 1.7: c-types.
> I guess it will be used by developers quite often, because
> HTML5 brings also the ability to create files with javscript and offer
> them for download.
>
as far i understand it can not work on other than firefox or a OS the JS script developer know,
because it use firefox API. Or do you not mean this ?
https://wiki.mozilla.org/JSctypes
I dont understand wy such a risky funtion is add to java script. I guess virus programmers are the
most that use that. Now i understand more that i get before some weeks a bka virus when i surf with
firefox. I remove it and i remove Java. currently all work ok. but i think its better to not use
firefox, if this offer such functions.
Regards
If the patch is in netsurf, is there a automatic build, or build instruction, what need to do to get
that compiling and working ?
Does the Atari netsurf now have Java script ?
>
> But there is also one important type missing within 1.7: c-types.
> I guess it will be used by developers quite often, because
> HTML5 brings also the ability to create files with javscript and offer
> them for download.
>
as far i understand it can not work on other than firefox or a OS the JS script developer know,
because it use firefox API. Or do you not mean this ?
https://wiki.mozilla.org/JSctypes
I dont understand wy such a risky funtion is add to java script. I guess virus programmers are the
most that use that. Now i understand more that i get before some weeks a bka virus when i surf with
firefox. I remove it and i remove Java. currently all work ok. but i think its better to not use
firefox, if this offer such functions.
Regards
Re: [Rpcemu] How to recover from bad monitor mode?
On 2 Jul 2012, Tony Moore <old_coaster@yahoo.co.uk> wrote:
> On 1 Jul 2012, "Terry Duell" <tduell@iinet.net.au> wrote:
>
> [snip]
>
> > Is there a way of booting RPCEmu into a safe screen mode, to allow
> > these sort of errors to be corrected, without having to resort to
> > replacing the hard disc image?
>
> I was told, here, that Delete-power-on remains available
Sorry, that should have been Shift-power-on, as Peter says.
Tony
_______________________________________________
Rpcemu mailing list
Rpcemu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
> On 1 Jul 2012, "Terry Duell" <tduell@iinet.net.au> wrote:
>
> [snip]
>
> > Is there a way of booting RPCEmu into a safe screen mode, to allow
> > these sort of errors to be corrected, without having to resort to
> > replacing the hard disc image?
>
> I was told, here, that Delete-power-on remains available
Sorry, that should have been Shift-power-on, as Peter says.
Tony
_______________________________________________
Rpcemu mailing list
Rpcemu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Re: [Rpcemu] How to recover from bad monitor mode?
On 1 Jul 2012, "Terry Duell" <tduell@iinet.net.au> wrote:
[snip]
> Is there a way of booting RPCEmu into a safe screen mode, to allow
> these sort of errors to be corrected, without having to resort to
> replacing the hard disc image?
I was told, here, that Delete-power-on remains available - in theory.
However, in practice, I found it impossible to press Delete quickly
enough, following the appearance of the RPCEmu window. Maybe you have
faster reactions than I do!
Before making any changes to Boot, I now make back-up copies of hd4.hdf,
cmos.ram and rpc.cfg.
The problem can be avoided by booting from HostFS, in which case the
Boot files are accessible, without starting RPCEmu.
Tony
_______________________________________________
Rpcemu mailing list
Rpcemu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
[snip]
> Is there a way of booting RPCEmu into a safe screen mode, to allow
> these sort of errors to be corrected, without having to resort to
> replacing the hard disc image?
I was told, here, that Delete-power-on remains available - in theory.
However, in practice, I found it impossible to press Delete quickly
enough, following the appearance of the RPCEmu window. Maybe you have
faster reactions than I do!
Before making any changes to Boot, I now make back-up copies of hd4.hdf,
cmos.ram and rpc.cfg.
The problem can be avoided by booting from HostFS, in which case the
Boot files are accessible, without starting RPCEmu.
Tony
_______________________________________________
Rpcemu mailing list
Rpcemu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Re: [Rpcemu] How to recover from bad monitor mode?
On Sun, Jul 01, 2012 at 02:51:29PM +1000, Terry Duell wrote:
> Is there a way of booting RPCEmu into a safe screen mode, to allow
> these sort of errors to be corrected, without having to resort to
> replacing the hard disc image?
There's a few methods (that apply to real hardware too).
1) Hold down 'shift' on startup to prevent !Boot from running (which loads
the dodgy mode), and then poke around in !Boot to change which mode is
used.
*or*
2) Wait till you're in the 'desktop' (or best guess when that it). hit F12
and blindtype 'wimpmode 28' (without quotes) and hit enter. This should
put you back into 640x480, and then poke around in !Boot to change which
mode is used.
Peter
--
Peter Howkins
peter.howkins@marutan.net
_______________________________________________
Rpcemu mailing list
Rpcemu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
> Is there a way of booting RPCEmu into a safe screen mode, to allow
> these sort of errors to be corrected, without having to resort to
> replacing the hard disc image?
There's a few methods (that apply to real hardware too).
1) Hold down 'shift' on startup to prevent !Boot from running (which loads
the dodgy mode), and then poke around in !Boot to change which mode is
used.
*or*
2) Wait till you're in the 'desktop' (or best guess when that it). hit F12
and blindtype 'wimpmode 28' (without quotes) and hit enter. This should
put you back into 640x480, and then poke around in !Boot to change which
mode is used.
Peter
--
Peter Howkins
peter.howkins@marutan.net
_______________________________________________
Rpcemu mailing list
Rpcemu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Subscribe to:
Posts (Atom)