We only officially support NT and 2000. I put a workaround in the code for Windows 98, but had no way to test it. I was assured by someone that the fix did work, so are you sure you're using Xalan 1.3?
See the following bug:
Remember that we don't actively test Windows 98 and Windows 95 is even more problematic.
Dave
01/13/2002 07:51 AM | To: <[email protected]> cc: Subject: win95 Error writing file: out1.html. The error code was 6 |
Hi
I've never been able to make Xalan 1.2 and now 1.3 work on win95.
It works only as long as I don't state any name for the output file. Otherwise:
�
E:\WINDOWS>testxslt -in D:\Autodoc\Doc\Main.xml -xsl D:\Autodoc\Xsl\ins2.xsl -out D:\Autodoc\Doc\out1.html
========= Parsing D:\Autodoc\Xsl\ins2.xsl ==========
Parse of D:\Autodoc\Xsl\ins2.xsl took 50 milliseconds
========= Parsing D:\Autodoc\Doc\Main.xml ==========
Parse of D:\Autodoc\Doc\Main.xml took 60 milliseconds
=============================
Transforming...
�
XSLException Type is: XalanFileOutputStreamWriteException
Message is: Error writing file: D:\Autodoc\Doc\out1.html.� The error code was 6. (Unkno
wn URI, line -1, column -1)
It works fine with xalan-j, so it's not a pb of read and write attribute. And on my win95, there no authorisation to get in the way.
�
When I first added
F:\xalan\Xalan-C_1_3-win32\xml-xalan\c\Build\Win32\VC6\Release
to my path I got this error message:
Can't find xerces-C_1_6.dll
�
I've added another link to my path pointing to xerces.lib
But the error remained.
�
So, I've put the path to xerces\bin directory.
Is that the wrong way to do it??
�
My path now �points to :
F:\xalan\Xalan-C_1_3-win32\xml-xalan\c\Build\Win32\VC6\Release;F:\xalan\Xalan-C_1_3-win32\xml-xerces\c\bin;
�
If someone could help me a bit with that.
Thanks
�
Vendo
<<inline: graycol.gif>>
<<inline: ecblank.gif>>
