Interesting error...

[Lawrence Lee]

If you swap in a backup of Frontier.root (rename your existing one) do you
still get the error message?

You might be able to set user.scheduler.prefs.runThreads in
frontierStartupCommands to see if that lets you startup Frontier and
possibly jettison that bad object.

http://frontier.userland.com/reference/environment/frontierStartupCommandsTx
t

http://frontier.userland.com/reference/environment/runtime/schedulerThreads

Lawrence Lee
UserLand Software
www.userland.com
 

> -----Original Message-----
> From: frontier-users-bounces at userland.com 
> [mailto:frontier-users-bounces at userland.com] On Behalf Of 
> Christopher.Short at abare.gov.au
> Sent: January 31, 2005 3:06 PM
> To: Frontier-Users at userland.com
> Subject: Interesting error...
> 
> Upon restarting frontier, I'm getting the following error message:
> 
> The instruction at 0x0049e551 referenced memory at 
> 0x00000000. The memory could not be 'read'.
> 
> Any suggestions on what this is?
> 
> The problem surfaced last night in my automatic frontier 
> restart routine and has led to an interesting problem at the 
> moment - an error occurs, Frontier shutsdown, flaunch 
> restarts it and then Frontier crashes, flaunch restarts it 
> and then Frontier crashes etc etc etc...every 30 seconds.
> 
> I suspect I have a corrupted table in user.scheduler.tasks - 
> but I appear to only have 5 seconds upon start up to find it 
> and dump it...and it would appear that I am not quick enough!
> 
> Thanks,
> Christopher
>