<< | Thread Index | >> ]    [ << | Date Index | >> ]

Subject: Re: Cipe for Windows
From: "Damion K. Wilson" <dkw,AT,rcm,DOT,bm>
Date: Tue, 17 Oct 2000 22:33:03 +0200
In-reply-to: <200010171247030374.00C02502@mail.sprint.ca>

Yes. The driver and service both use DbgPrint so download one of the
utilities that view these messages (I use Mark Russinovich's DebugView

I'm aware of the parser bug but I handle both types of static key in

*********** REPLY SEPARATOR  ***********

On 10/17/00 at 2:07 PM chris wrote:

>>Try setting the Key timeout value in the CIPE-Win32 control panel applet
>>something very high.
>Ok, I'll give that a try. So what this means in essense is that the setkey
>operation times out. I thought it might be failing. By the way, is there
any way
>to get debug info showing on the Windows end ?
>>Also, if possible, try using the same CIPE-Win32 instance against a CIPE
>>1.3.0 instance so we will know if it's something new with Cipe 1.4.x.
>Right. I'm trying to compile version 1.3.0 on my RedHat server right now.
>problem there is that I'm compiling for LRP ( Linux Router Project ) which
>still uses GLIBC 2.0.7, so I'm trying to work out how to link static or
how to
>edit the makefile to refer to the compat-glibc headers. Anyway, I'll work
it out :-)
>>I am actually rewriting CIPE-Win32 right now so if we can figure out what
>>causes this before I'm done, I should be able to incorporate the fix or
>>workaround in the new release.
>What I was thinking is that perhaps the key parser bug in CIPE has
>to do with this. All CIPE's prior to 1.4.0 had this parser bug but my
1.4.2 is compiled
>with backwards compatibility for earlier versions.

<< | Thread Index | >> ]    [ << | Date Index | >> ]