From: Harry Lin
Subject: CLISP problem with MS-DOS console window code page
Date: 
Message-ID: <1122585510.738154.3580@f14g2000cwb.googlegroups.com>
Hi, there,
I am a newbie in both LISP and CLISP. When I start CLISP, the following
messages indicate that my MS-DOS console code page is not supported or
recognized by CLISP:

WARNING: locale: no encoding GBK, using UTF-8
WARNING: *TERMINAL-ENCODING*: no encoding CP936, using UTF-8
  i i i i i i i       ooooo    o        ooooooo   ooooo   ooooo
  I I I I I I I      8     8   8           8     8     o  8    8
  I  \ `+' /  I      8         8           8     8        8    8
   \  `-+-'  /       8         8           8      ooooo   8oooo
    `-__|__-'        8         8           8           8  8
        |            8     o   8           8     o     8  8
  ------+------       ooooo    8oooooo  ooo8ooo   ooooo   8

Copyright (c) Bruno Haible, Michael Stoll 1992, 1993
Copyright (c) Bruno Haible, Marcus Daniels 1994-1997
Copyright (c) Bruno Haible, Pierpaolo Bernardi, Sam Steingold 1998
Copyright (c) Bruno Haible, Sam Steingold 1999-2000
Copyright (c) Sam Steingold, Bruno Haible 2001-2005


*** - invalid byte sequence #xE7 #xD3 #xB0 in CHARSET:UTF-8 conversion
The following restarts are available:
ABORT          :R1      ABORT


If I enter :R1, CLISP crashes. What can I do next? Thank you very much
for your help in advance.

Harry Lin

From: Eric Lavigne
Subject: Re: CLISP problem with MS-DOS console window code page
Date: 
Message-ID: <1122586612.882966.74280@z14g2000cwz.googlegroups.com>
>When I start CLISP, the following
>messages indicate that my MS-DOS console code page is not supported or
>recognized by CLISP:
>...
>What can I do next? Thank you very much
>for your help in advance.

I would try running clisp through emacs, rather than through an MS-DOS
terminal. This is just a guess, though, as I have never had this
problem.

Try going to this page: http://common-lisp.net/project/lispbox/
Download and install the "base installer" and the "clisp module."
Then you will find lispbox as one of the programs in your start menu.
From: Sam Steingold
Subject: Re: CLISP problem with MS-DOS console window code page
Date: 
Message-ID: <u4qaemur4.fsf@gnu.org>
> * Harry Lin <···········@tznvy.pbz> [2005-07-28 14:18:30 -0700]:
>
> WARNING: locale: no encoding GBK, using UTF-8
> WARNING: *TERMINAL-ENCODING*: no encoding CP936, using UTF-8
>
> *** - invalid byte sequence #xE7 #xD3 #xB0 in CHARSET:UTF-8 conversion

<http://clisp.cons.org/faq.html#enc-err>
look for non-ascii file and directory names.


> The following restarts are available:
> ABORT          :R1      ABORT
>
>
> If I enter :R1, CLISP crashes. What can I do next?

I cannot reproduce this.
what does :bt1 print?

-- 
Sam Steingold (http://www.podval.org/~sds) running w2k
<http://www.camera.org> <http://www.mideasttruth.com/> <http://www.iris.org.il>
<http://www.dhimmi.com/> <http://www.honestreporting.com>
Beauty is only a light switch away.
From: Harry Lin
Subject: Re: CLISP problem with MS-DOS console window code page
Date: 
Message-ID: <1122621145.279132.270510@g47g2000cwa.googlegroups.com>
Sam Steingold wrote:
> > * Harry Lin <···········@tznvy.pbz> [2005-07-28 14:18:30 -0700]:
> >
> > WARNING: locale: no encoding GBK, using UTF-8
> > WARNING: *TERMINAL-ENCODING*: no encoding CP936, using UTF-8
> >
> > *** - invalid byte sequence #xE7 #xD3 #xB0 in CHARSET:UTF-8 conversion
>
> <http://clisp.cons.org/faq.html#enc-err>
> look for non-ascii file and directory names.
>
>
> > The following restarts are available:
> > ABORT          :R1      ABORT
> >
> >
> > If I enter :R1, CLISP crashes. What can I do next?
>
> I cannot reproduce this.
> what does :bt1 print?
>

Hi, Sam,
The :bt1 print the following messages:

Break 1 [2]> :bt1
<1> #<SYSTEM-FUNCTION SHOW-STACK> 3
<2> #<COMPILED-FUNCTION SYSTEM::PRINT-BACKTRACE>
<3> #<COMPILED-FUNCTION SYSTEM::DEBUG-BACKTRACE>
<4> #<COMPILED-FUNCTION SYSTEM::DEBUG-BACKTRACE-1>
<5> #<SYSTEM-FUNCTION SYSTEM::READ-EVAL-PRINT> 2
<6> #<COMPILED-FUNCTION SYSTEM::BREAK-LOOP-2-2>
<7> #<SYSTEM-FUNCTION SYSTEM::SAME-ENV-AS> 2
<8> #<COMPILED-FUNCTION SYSTEM::BREAK-LOOP-2>
<9> #<SYSTEM-FUNCTION SYSTEM::DRIVER>
- #<SIMPLE-ERROR #x19ECDE3D>
- NIL
<10> #<COMPILED-FUNCTION SYSTEM::BREAK-LOOP>
- #<SIMPLE-ERROR #x19ECDE3D>
<11> #<SYSTEM-FUNCTION INVOKE-DEBUGGER> 1
frame binding variables (~ = dynamically):
  | ~ SYSTEM::*PRIN-STREAM* <--> #<UNBOUND>
frame binding variables (~ = dynamically):
  | ~ *PRINT-READABLY* <--> NIL
frame binding variables (~ = dynamically):
  | ~ *PRINT-ESCAPE* <--> T
- #<SIMPLE-ERROR #x19ECDE3D>
- "C:\\"
- #P"C:\\"
- NIL
- NIL
- #S(HASH-TABLE :TEST FASTHASH-EQUAL ("C:\\" . T))
- NIL
- (#P"C:\\")
- NIL
- ".clisprc.*"
- #P"C:\\.clisprc.*"
- NIL
- #P"C:\\.clisprc.*"
<12> #<SYSTEM-FUNCTION DIRECTORY>
- #P"C:\\.clisprc.*"
- #P""
- (#P"" #P"C:" #P"C:\\CLISP\\**\\")
- NIL
- T
- #(NIL ("fas" "lisp" "lsp" "cl"))
- #<COMPILED-FUNCTION SYSTEM::SEARCH-FILE>
- ("fas" "lisp" "lsp" "cl")
- #P"C:\\.clisprc.*"
<13> #<COMPILED-FUNCTION SYSTEM::SEARCH-FILE>
- #<COMPILED-FUNCTION SYSTEM::OPEN-FOR-LOAD-CHECK-COMPILED-FILE>
- #<COMPILED-FUNCTION SYSTEM::OPEN-FOR-LOAD-MY-OPEN>
- #(#(NIL :DEFAULT NIL) #<COMPILED-FUNCTION SYSTEM::OPEN-FOR-LOAD-BAD>)
- #P"C:\\.clisprc"
- NIL
- T
- NIL
- #(NIL :DEFAULT NIL)
- #<COMPILED-FUNCTION SYSTEM::OPEN-FOR-LOAD>
- :DEFAULT
- NIL
- #P"C:\\.clisprc"
<14> #<COMPILED-FUNCTION SYSTEM::OPEN-FOR-LOAD>
- NIL
frame binding variables (~ = dynamically):
  | ~ *LOAD-OBSOLETE-ACTION* <--> NIL
frame binding variables (~ = dynamically):
  | ~ *LOAD-COMPILING* <--> NIL
- NIL
frame binding variables (~ = dynamically):
  | ~ *LOAD-ECHO* <--> NIL
frame binding variables (~ = dynamically):
  | ~ *LOAD-PRINT* <--> NIL
frame binding variables (~ = dynamically):
  | ~ *LOAD-VERBOSE* <--> T
- #<COMPILED-FUNCTION LOAD>
- NIL
- #<UNBOUND>
- #<UNBOUND>
- #<UNBOUND>
- :DEFAULT
- NIL
- #<UNBOUND>
Printed 14 frames


I hope this can give you information. Thank you very much.

Harry Lin
From: Sam Steingold
Subject: Re: CLISP problem with MS-DOS console window code page
Date: 
Message-ID: <uack5lpeu.fsf@gnu.org>
> * Harry Lin <···········@tznvy.pbz> [2005-07-29 00:12:25 -0700]:
>
> Sam Steingold wrote:
>> > * Harry Lin <···········@tznvy.pbz> [2005-07-28 14:18:30 -0700]:
>> >
>> > WARNING: locale: no encoding GBK, using UTF-8
>> > WARNING: *TERMINAL-ENCODING*: no encoding CP936, using UTF-8
>> >
>> > *** - invalid byte sequence #xE7 #xD3 #xB0 in CHARSET:UTF-8 conversion
>>
>> <http://clisp.cons.org/faq.html#enc-err>
>> look for non-ascii file and directory names.
>>
>>
>> > The following restarts are available:
>> > ABORT          :R1      ABORT
>> >
>> >
>> > If I enter :R1, CLISP crashes. What can I do next?
>>
>> I cannot reproduce this.
>> what does :bt1 print?
>>
>
> The :bt1 print the following messages:
>
> - #<SIMPLE-ERROR #x19ECDE3D>
> - "C:\\"
> - #P"C:\\"
> - NIL
> - NIL
> - #S(HASH-TABLE :TEST FASTHASH-EQUAL ("C:\\" . T))
> - NIL
> - (#P"C:\\")
> - NIL
> - ".clisprc.*"
> - #P"C:\\.clisprc.*"
> - NIL
> - #P"C:\\.clisprc.*"
> <12> #<SYSTEM-FUNCTION DIRECTORY>

so, do you have files/directories with non-ascii names in "C:\\"?

-- 
Sam Steingold (http://www.podval.org/~sds) running w2k
<http://www.camera.org> <http://www.mideasttruth.com/>
<http://www.iris.org.il> <http://www.memri.org/> <http://pmw.org.il/>
Trespassers will be shot.  Survivors will be prosecuted.
From: Harry Lin
Subject: Re: CLISP problem with MS-DOS console window code page
Date: 
Message-ID: <1122713065.761094.320580@g47g2000cwa.googlegroups.com>
Sam Steingold wrote:
> > * Harry Lin <···········@tznvy.pbz> [2005-07-29 00:12:25 -0700]:
> >
> > Sam Steingold wrote:
> >> > * Harry Lin <···········@tznvy.pbz> [2005-07-28 14:18:30 -0700]:
> >> >
> >> > WARNING: locale: no encoding GBK, using UTF-8
> >> > WARNING: *TERMINAL-ENCODING*: no encoding CP936, using UTF-8
> >> >
> >> > *** - invalid byte sequence #xE7 #xD3 #xB0 in CHARSET:UTF-8 conversion
> >>
> >> <http://clisp.cons.org/faq.html#enc-err>
> >> look for non-ascii file and directory names.
> >>
> >>
> >> > The following restarts are available:
> >> > ABORT          :R1      ABORT
> >> >
> >> >
> >> > If I enter :R1, CLISP crashes. What can I do next?
> >>
> >> I cannot reproduce this.
> >> what does :bt1 print?
> >>
> >
> > The :bt1 print the following messages:
> >
> > - #<SIMPLE-ERROR #x19ECDE3D>
> > - "C:\\"
> > - #P"C:\\"
> > - NIL
> > - NIL
> > - #S(HASH-TABLE :TEST FASTHASH-EQUAL ("C:\\" . T))
> > - NIL
> > - (#P"C:\\")
> > - NIL
> > - ".clisprc.*"
> > - #P"C:\\.clisprc.*"
> > - NIL
> > - #P"C:\\.clisprc.*"
> > <12> #<SYSTEM-FUNCTION DIRECTORY>
>
> so, do you have files/directories with non-ascii names in "C:\\"?
>
> --
> Sam Steingold (http://www.podval.org/~sds) running w2k
> <http://www.camera.org> <http://www.mideasttruth.com/>
> <http://www.iris.org.il> <http://www.memri.org/> <http://pmw.org.il/>
> Trespassers will be shot.  Survivors will be prosecuted.

Hi, Sam,
Yes, I have a directory with non-ascii in "C:\". I have changed the
name as an ASCII one. It works. Thank you very much for your time and
help.

Harry Lin