Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re-Submission of Previous Account on 2nd Type Error Encountered

From: k.baratko+csuohio.edu@----.-------.---
To: XMLSchema-dev@--.---
Date: 5/14/2004 12:06:00 PM
Da: Fri,14th May, 2004<ReSent> 
Da: Sun, 9th May, 2004

To: XMLSchema-dev@w...   
cc: ht@i...

Fr: Kenneth D. Baratko
    <k.baratko@c...>
    Cleveland State University
    Cleveland, Ohio, USA

Re: Re-Sending this information
    Because it has taken over
    a week with no response.    
Re: XSV27 NEW ERR
==============================

Mssrs...:

PREVIOUS ERR
============
   I received previous correspondence
from HLT regarding the following:
  "ERR: Error loading Python
   DLL.C:\WINDOWS\TEMP\python22.dll 
Two questions were asked of me.
1. Is the (WINDOWS\TEMP) where you(I)
   installed XSV? Answer: NO
2. If not, try renaming C:WINDOWS\TEMP   python22.dll to ...\python22.dlx
   Answer: Since python22.dll never
   existed in this dir, it was impossible
   to rename it.
NEW ERR
=======
   Since it seemed somewhat clear that
the .dll should be going into the C:\W\T
directory, I first analyzed the c:\PROGRAM 
FILES\XSV DIR.  Upon looking at that DIR
with WindowsExplorer, it was evident that
NO .dll were even in that dir.  My wisdom
told me better, so I went to my friendly
DOS box, and behold, all 17 files were there
PLUS the 4 missing(HIDDEN) .dll files.  I
then copies them(the old fashion DOS way)
into c:\W\T.  For that I did NOT make any
new sub dirs.  At this point everything
seemed to be in order with 2 dirs, c:\W\T
having the .dlls and the c:\PF\XSV having
the xsv.exe 
   I then had a WD from which I would exe-
cute the program.  This name happens to be
C:\Costello\Examples\ISBN  In that ISBN dir
I had by xml, xsd, and xsv.exe files. Upon
execution with xsv BookCatalogue.xml, I got
the following:

C:\COSTELLO_STUFF\EXAMPLES\isbn>xsv bookcatalogue.xml
Traceback (most recent call last):
  File "<string>", line 1, in ?
  File "c:\Program Files\Installer\iu.py", line 274, in importHook
  File "c:\Program Files\Installer\iu.py", line 344, in doimport
  File "c:\Program Files\Installer\iu.py", line 181, in getmod
  File "c:\Program Files\Installer\archive.py", line 350, in getmod
ImportError: PYZ entry 'codecs' (0j) is not a valid code object
Traceback (most recent call last):
  File "<string>", line 110, in ?
  File "<string>", line 86, in parseAndRun
  File "c:\Program Files\Installer\iu.py", line 274, in importHook
  File "c:\Program Files\Installer\iu.py", line 344, in doimport
  File "c:\Program Files\Installer\iu.py", line 181, in getmod
  File "c:\Program Files\Installer\archive.py", line 350, in getmod
ImportError: PYZ entry 'XSV' (0j) is not a valid code object

NOTE: I HAVE NO SUCH DIR C:\Program Files\Installer ON MY C DRIVE 

  I am wondering if this moght have anything to do with a revised
path in my autoexec.bat which I had set as 
path=%PATH%;.\..\..\C:\PROGRA~1\XSV27

   I am running on a W98SE pltfrm.
   Thanking you in advance for your time.
   Sincerely,
Ken Baratko

From uche.ogbuji@f...  Tue May 18 07:25:37 2004
Return-Path: <uche.ogbuji@f...>
X-Original


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent