CelURL's not working...

[Chuft-Captain]

I'm experiencing a problem at the moment (in Celestia 1.6.0) where celURL's totally fail to work, and also fail to start up a Celestia instance as they should if there's not already a started instance.
Somehow the association is broken between the application and the celURL.
If I remember correctly, the solution I've seen mentioned here before may have mentioned something to do with patching a WINDOWS registry entry.

A re-install, usually sorts out these problems in my experience, but I'd like to track down the other solution involving the registry fix if anyone can remember that solution.

Here's the error popup I'm getting when clicking on any celURL in the forum:


Cheers
CC

[Chuft-Captain]

Note: that pop-up window appears whether or not a Celestia instance is already running..

No ideas? Anyone?

CC

[jogad]

hello

this is a .reg file that should do the job.

just unzip and double-click on it to repair your registry.

Note : if Celestia is not in "c:\program files\celestia", edit the file to match your celestia directory.

[Chuft-Captain]

Thanks Jogad,

I've already applied a version of that (from your earlier post in another thread), modified for my configuration, but unfortunately with no change in the behaviour....

... however, since then, I've discovered that the same celURL's work perfectly from Internet Explorer, so this looks like it's either a bug in Firefox, or some sort of interference from a Firefox addon, ...or perhaps even a virus has infected my Firefox browser and is trying to do something extra on the command line!

If anyone's using Firefox 3.6.3, can I impose on you to click on this celURL:
cel://Follow/Sol:Saturn/2010-06-07T06:34:24.80393?x=AMiLALjc2jc&y=AJZtzpoMBi0&z=AKA7Rdw8zWE&ow=0.606826&ox=0.307096&oy=0.00144729&oz=0.733111&select=Sol:Saturn:Titan&fov=0.0501826&ts=4&ltd=0&p=0&rf=40339&lm=32772&tsrc=0&ver=3
to confirm whether you can replicate the problem I'm getting.
If it's not just me, then we may need to report this as a bug to the Firefox developers.

Thanks in advance
CC

[jogad]

Hello,

Snap1.jpg

Very nice url
... and no problem for me with Firefox

Maybe a related OS behaviour? (I'm running XP)

Cheers

[Chuft-Captain]

Very nice url

I thought you'd like that one.

... and no problem for me with Firefox

Dammit! That means it's my problem alone, so I'll have to fix it myself! I was hoping it was a browser bug, which would make it SEP.

[duds26]

Works fine over here:

CelURL_Firefox3.6.3_Celestia_1.6.0_WindowsVista_Working.png

Firefox 3.6.3
Windows Vista Home Premium
Celestia 1.6.0

Maybe reinstalling Firefox could help?

[t00fri]

Very nice url

I thought you'd like that one.

... and no problem for me with Firefox

Dammit! That means it's my problem alone, so I'll have to fix it myself! I was hoping it was a browser bug, which would make it SEP.

CC,

your complaints about long "thumb" loading times etc in CM were also related to your firefox 3.6.3, which I could certainly not confirm as you know well...

Fridger

[Fenerit]

Chuft, if you have the java engine, check whether the Java Quick Starter ("jqs.exe") is cause of problem. Quit it with taskmanager and then try your business.

[Chuft-Captain]

CC,

your complaints about long "thumb" loading times etc in CM were also related to your firefox 3.6.3, which I could certainly not confirm as you know well...

Fridger

I was beginning to suspect that the 2 problems might be symptoms of the same ailment, however it was unclear to me from our discussion at CM whether you had actually gone through the whole process of saving the page to disk and confirmed the file-sizes on disk on your machine. I take it that you've done so now?

Chuft, if you have the java engine, check whether the Java Quick Starter ("jqs.exe") is cause of problem. Quit it with taskmanager and then try your business.

I've already got the quick starter disabled in the addon manager, but I'll try your suggestion of killing off the process altogether, to see if that makes a difference. I have a feeling however that I may have already tried that with no change, but I'll give it another go anyway.
EDIT: Just tried your suggestion.. No change, so it looks like that's not the source of the problem.

Thanks for the feedback.

[Chuft-Captain]

FWIW,

I've also started Firefox in Safe Mode:

FFSafe.jpg

...which disables all addons..... still with no success.

I originally assumed this was a problem with one of Celestia's registry entries, but if that was the case it would fail in in IE as well.

FWIW, here's my reg script:

Code: Select all

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\cel]
@="URL:cel Protocol"
"URL Protocol"=""

[HKEY_CLASSES_ROOT\cel\Shell]
@=""

[HKEY_CLASSES_ROOT\cel\Shell\open]
@=""

[HKEY_CLASSES_ROOT\cel\Shell\open\Command]
@="\"C:\\Celestia 1.6.0\\celestia.exe\" --once --dir \"C:\\Celestia 1.6.0\" -u \"%1\""

[HKEY_CLASSES_ROOT\.celx]
@="celestia_script"

[HKEY_CLASSES_ROOT\.cel]
@="celestia_script"

[HKEY_CLASSES_ROOT\.clx]
@="celestia_script"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.cel]
"Progid"="celestia_script"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.cel\OpenWithList]
"a"="celestia.exe"
"MRUList"="ab"
"b"="celestia-4855.exe"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.cel\OpenWithProgids]
"celestia_script"=hex(0):
"celestia-4855_script"=hex(0):

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.celx]
"Progid"="celestia_script"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.celx\OpenWithList]
"a"="celestia.exe"
"MRUList"="ab"
"b"="celestia-4855.exe"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.celx\OpenWithProgids]
"celestia_script"=hex(0):
"celestia-4855_script"=hex(0):

The only other frequent issue that I get is unresponsive script warnings as described here:
http://kb.mozillazine.org/Unresponsive_Script_Error but that should be ruled out by using Firefox SAFE MODE as those sort of problems are usually caused by FF extensions.

For now... I guess I'm resigned to using celURL's from IE only!

Cheers
CC

[Fenerit]

Chuft, just a workaround to think about. For editing purposes usually I do not associated Celestia's file associations, and when I check an URl as in the screendump below, a window pop up asking for the operation. Thus I wonder whether you remove the associations and got such windows, then you can re-associate the Celestia's file, and, if only, the problem can be fixed. (the button within the listbox says "choose" and the text "choose an application".

[Chuft-Captain]

Fenerit,

Do you mean that you delete these two?:

fileassoc.JPG

If there was a problem with these file associations I would expect it to affect Internet Explorer as well, and yet everything works perfectly from IE, so I doubt that this suggestion will fix it.
... although, I'm desperate enough to try just about anything at this point!

It seems to be a Firefox specific problem only, and the interesting thing is that these celURL problems seemed to arise around about the same time that I started getting the CHROME/JAVA script hanging problems described above, so there seems to be some connection there....
...ie. this would support the theory that this problem was being caused by a Firefox addon/extension, .... but if that was the case I would expect that Firefox safe mode would have allowed celURL's to work again.... which it didn't!

Thanks for all your suggestions though, keep 'em coming!
CC

[Fenerit]

yep! I'm a bit confusing... Unless such link are in there, of course IE works. I think you must change its association. For example, that FF windows do pop up with the wordpad association:



EDIT LATER:
Then, through such FF pop up window, is possible to associate the URL to Celestia. I wonder wheter this operation, mastered by FF can "settle" the relation amonst FF and Celestia.

EDIT EDIT LATER:
Yup! The details of your association says that CEL file is a CAB (Winrar archive)! Why that?

[Chuft-Captain]

yep! I'm a bit confusing... Unless such link are in there, of course IE works. I think you must change its association. For example, that FF windows do pop up with the wordpad association:

Are you suggesting to temporarily associate CEL and CELX with Wordpad?
OR, are you suggesting to delete them altogether?

Yup! The details of your association says that CEL file is a CAB (Winrar archive)! Why that?

I hadn't noticed that before. What's happening is that as I scroll through the different filetypes it updates that information (except for the CEL and CELX ones!!!)
CAB on this occasion just happens to be the one that was highlighted before I clicked on the CEL one, so the CAB info remains there.

[Fenerit]

Are you suggesting to temporarily associate CEL and CELX with Wordpad?
OR, are you suggesting to delete them altogether?[/quote]

Try both. First, try to delete it. Second, double click on it in file manager and when the file manager pop up window ask for associations, choose wordpad. Start FF and check the link.

[Chuft-Captain]

Are you suggesting to temporarily associate CEL and CELX with Wordpad?
OR, are you suggesting to delete them altogether?

Try both. First, try to delete it. Second, double click on it in file manager and when the file manager pop up window ask for associations, choose wordpad. Start FF and check the link.

I'm not quite sure why you want to associate CEL and CELX with Wordpad?
The usual procedure would be to delete them and then re-install Celestia which would re-create the file associations for CEL and CELX.
And as far as I know these 2 file associations don't have anything to do with celURL links, but are designed to associate CEL and CELX scripts with celestia.exe, so a quite different mechanism.
Is it your assertion that these 2 file associations have something to do with the way celURL's work?... or are somehow interfering with celURL's??

Anyway, I might just delete them anyway, and re-install Celestia, as that certainly won't do any harm, although I'd be very surprised if celURL links started working as a result.

CC

[Fenerit]

CC, isn't required to reinstall Celestia to associate its cel/celx extension. When they are deleted, once you do double click on its blank icons, the filemanager pop up the window for associate they; then you can re-choose Celestia again. I said the wordpad, to be more meeting with my situation, in which FF shows such behaviour.

[jogad]

Hello,

I can't reproduce exactly the bug described but I noticed that your celestia is in "celestia 1.6.0" directory
When I use such a directory with dots in it, I get this error

bug.jpg

And this happens only in Firefox and not in Internet Explorer.
Maybe you were right when you suspected a bug in Firefox.

Of course the problem is not exactly the same because, as you can see on the picture, the url is loaded.
But I suggest that you change "celestia 1.6.0" to "celestia 160" and see if the message is always the same.
Maybe...

[Chuft-Captain]

CC, isn't required to reinstall Celestia to associate its cel/celx extension....

I know, but the "surest" way is to re-install. "To be sure, to be sure, to be sure" (as the Irish would say.)

I can't reproduce exactly the bug described but I noticed that your celestia is in "celestia 1.6.0" directory
When I use such a directory with dots in it, I get this error

bug.jpg

And this happens only in Firefox and not in Internet Explorer.
Maybe you were right when you suspected a bug in Firefox.

Of course the problem is not exactly the same because, as you can see on the picture, the url is loaded.
But I suggest that you change "celestia 1.6.0" to "celestia 160" and see if the message is always the same.
Maybe...

No difference after a fresh install to "celestia 160".
Interestingly though, after installation, registry entries still had "celestia 1.6.0" in them.
Even more interesting: modification and application of your .REG file to replace "celestia 1.6.0" with "celestia 160" also had no effect on the registry. (Although it still claimed sucess...)
(I had to manually modify all registry entries to refer to the "celestia 160" folder, but celURL's still not working, even after this.)

I'm wondering if it is correct for the URL Protocol to be blank??

Code: Select all

[HKEY_CLASSES_ROOT\cel]
@="URL:cel Protocol"
"URL Protocol"=""

I'm not sure what the original value of this key was, but I notice that the .REG file sets it to "".

Cheers
CC