URL error message
- From: Dave Symes <dfs@xxxxxxxxxxxxx>
- Date: Wed, 04 Jul 2007 21:36:01 +0100
In article <gemini.jkn9yg002vtsr00g0@xxxxxxxxxxxxxxxxxx>,
Jeremy C B Nicoll <jeremy@xxxxxxxxxxxxxxxx> wrote:
Dave Symes <dfs@xxxxxxxxxxxxx> wrote:
Everyone is getting sidetracked trying to interprete the minutia of
what I wrote.
The point was... It didn't matter where the damn URL was, single click
in some useless application, double click in another application, it
didn't matter, the action would not call a browser, just returned the
"Filename !Run is not recognised." error message.
This perhaps means that something (Frank's program I should think) was
written so that when a URL was clicked on it would issue a command like
*Run <browser$dir>!Run <yourURL>
Needs a CTRL double Click, it then adds the URL to a text file.
But, perhaps because you'd not booted any browser, "<browser$dir>" had no
value so the command issued would be
*Run !Run <yourURL>
and it would fail.
Though I'd not manually booted any browser, browsers had been seen by a
System Configure Filer_Boot.
One way to (a) get to understand more about what commands are issued on
your behalf everytime you run something, and (b) see what's going wrong
when it doesn't work, is always to have running Martin Avison's
!Reporter and have it configured to log "Cmds", which is to say, all
*commands. Then if a program or Obey file or something issues a *
command, you'll be able to see what it tried to do, and perhaps more to
the point, what the "it" that issued the command actually is.
Most people, if they install !Reporter at all, only do so to look into a
particular problem, and then stop running it. This is not sensible.
It's better to get used to having it running all the time, so that when
your next problem occurs, you already have the logged details available.
Yes I'd forgotten Reporter, however, it doesn't add much to the plot.
1: With URLd active, Ctrl-Doible click on a URL, machine beeps and it's
added to the URLd storage file.
Reporter shows no action.
2: Just double click the URL and reporter displays the following report:
*************************
Reporter 2.64d (23 May 2006) List Wed 4th Jul 2007 21:27
21:24:11.36 ** ReportSrceOn ** from Menu
21:24:20.06 ** ReportSave ** ADFS::HD4.$.Tempdir.Wednesday.Reporter
File name '.!Run' not recognised
File name '.!Run' not recognised
21:27:20.27 ** Error **
Error : &000000CC
Message: File name '.!Run' not recognised
21:27:20.33 ** WimpError ** from unknown task
Error : &000000CC
Message: File name '.!Run' not recognised
Reporter 2.64d (23 May 2006) Listed 10 lines
:
*************************
Not really much help is it?
[Snip]
[Here I have extra commands at the end of boot procesing which then saveGood idea, I'll think about it.
that information so that for every single boot (for months) I have a
record of what happened. So if one day something goes wrong during boot
processing I can look back at previous days logs to see what changed and
why. While it might be hard to understand some of the info that's in a
log, and hard to diagnose a problem, it's IMPOSSIBLE if there's no
information to look at.]
Cheers
Dave S
--
.
- Follow-Ups:
- Re: URL error message
- From: Jeremy C B Nicoll
- Re: URL error message
- References:
- URL error message
- From: Dave Symes
- Re: URL error message
- From: Martin Wuerthner
- Re: URL error message
- From: Dave Symes
- Re: URL error message
- From: VinceH
- Re: URL error message
- From: Adam
- Re: URL error message
- From: Dave Symes
- Re: URL error message
- From: Adam
- Re: URL error message
- From: Dave Symes
- Re: URL error message
- From: Adam
- Re: URL error message
- From: Alan Calder
- Re: URL error message
- From: Adam
- Re: URL error message
- From: Alan Calder
- Re: URL error message
- From: Dave Symes
- Re: URL error message
- From: Jeremy C B Nicoll
- URL error message
- Prev by Date: Re: URL error message
- Next by Date: URL error message
- Previous by thread: Re: URL error message
- Next by thread: Re: URL error message
- Index(es):
Relevant Pages
|