Hi Alex,

This has been fixed in the repository.  You can get the latest code from
the repository and rebuild, or you can simply patch your local copy of the
source and rebuild.

A search of the archives and/or the bug database will give you some of the
history behind it.

Here's a link to the bug:

   http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3825

Here's a link to the diff, if you want to patch your local copy:

   
http://cvs.apache.org/viewcvs.cgi/xml-xalan/c/src/PlatformSupport/XalanFileOutputStream.cpp.diff?r1=1.7&r2=1.8

Dave



|---------+--------------------------->
|         |           Alex Brown      |
|         |           <alexb@griffinbr|
|         |           own.co.uk>      |
|         |                           |
|         |           04/26/2002 08:13|
|         |           AM              |
|         |           Please respond  |
|         |           to xalan-dev    |
|         |                           |
|---------+--------------------------->
  
>---------------------------------------------------------------------------------------------------------------------------|
  |                                                                                    
                                       |
  |        To:      "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>            
                                       |
  |        cc:      (bcc: David N Bertoni/Cambridge/IBM)                               
                                       |
  |        Subject: Windows platform woes?                                             
                                       |
  
>---------------------------------------------------------------------------------------------------------------------------|



Forgive me if this is a FAQ, but I have a Windows app. which invokes Xalan
simply using
XalanTransformer::transform.

All is well on Windows NT/2000 machines, but on a Windows 98 machine the
transformation fails. Calling XalanTransformer::getLastError yields:

"Error writing file <filename>. The error code was 6."

Scouting around on the web it seems this has cropped up before ... but I
could find no solution.

Any pointers on where to look gratefully received.

- Alex.





Reply via email to