x
maxwell at umiacs.umd.edu wrote:
>> Some ideas about your problem:
>>
>> [1] When something does not work with XXE, please always remember to
>> restart XXE with a console. You'll probably see error messages printed
>> there.
>
> We have now done this. Nothing shows up on what I would have called the
> console (a sort of DOS box). After XXE started up, I did click on the
> icon for the Message Log; this is what I get on the PC where XXE isn't
> working right:
> ----------------------
> Loading configuration "S:\TTO1308\XMLEditor\addon\customize.xxe"...
>
> Loading configuration "C:\Documents and Settings\nlynn\Application
> Data\XMLmind\XMLEditor4\addon\customize.xxe"...
>
> Registering XSL-FO processor plug-in
> "com.xmlmind.xmleditext.fop1_foprocessor.FOP"...
>
> Registering XSL-FO processor plug-in
> "com.xmlmind.xmleditext.xep_foprocessor.XEP"...
>
> Registering XSL-FO processor plug-in
> "com.xmlmind.xmleditext.xfc_foprocessor.XFC"...
>
> Registering image toolkit plug-in
> "com.xmlmind.xmleditext.batik_imagetoolkit.BatikImageToolkit"...
>
> Registering virtual drive plug-in
> "com.xmlmind.xmleditext.dav_vdrive.DAVDriveFactory"...
>
> Loading configuration
> "S:\TTO1308\XMLEditor\addon\CASLGrammar\0CASLGrammar.xxe"...
>
> Loading configuration "C:\Documents and Settings\nlynn\Application
> Data\XMLmind\XMLEditor4\addon\CASLGrammar\0CASLGrammar.xxe"...
> ----------------------
>
> There are two "Loading configuration" messages at the beginning and the
> end because in an attempt to fix whatever was going on, we duplicated our
> local config files from S: (their network location) to the per-user C:
> location. This seems to have had no effect apart from duplicating this
> msg and the original error msg ('missing or invalid attribute
> "location"').
>
> Conspicuous by absence in the above log is the loading of any config files
> from 'C:\Program Files\XMLmind_XML_Editor\addon\config'; whereas there are
> several entries where XXE reports loading config files from that directory
> in the logfiles on the PCs where XXE is working OK.
>
> Again, the config files on the S: drive are (AFAIK!) identical on the
> network where this is working and on the network where it isn't working.
>
>> [2] The XML catalog resolver ``crashes'' when the current working
>> directory is a UNC pathname. More info in
>> http://www.xmlmind.com/xmleditor/known_problems.html
>
> I see the web page, but I'm unclear how this problem is caused, or how we
> would diagnose it. Does it only happen when the path in the startup icon
> is of the form //server/directory_path (or maybe \\server\directory_path)?
> If that's the case, then this is not the problem for us; XXE is installed
> on the local PC.
When you double-click on the icon of XXE, Windows assigns a current
working directory to XXE (right-click on the XXE icon and select
Shortcut Properties). If this current working directory is something
like \\server\share (S:\foo\bar is OK), then you should see error
messages printed on the console and after this the XML catalog resolver
(which is not the work of XMLmind) is broken.
I'm sorry but given this report, I have no clue on what could happen on
this particular PC.