Re: NCPFS 255 character support?

Alan, If NCPFS has little use these days, how are the linux users meant to sign on to Novell networks without using the (IMHO) bloatware provided by Novell? In fact, Novell's client only work on SLED first time lucky (everything else needs extra libs and a lot of work) so it's hardly much

[Fwd: Re: Google are using linux kernel - what do you know about the source?]

And copy to the list... --- Begin Message --- And where, may I ask, does one find the source of Google's modified kernel? (At least, the unmodified bits!) Chris Matti Aarnio wrote: On Wed, May 23, 2007 at 04:50:35PM +0200, Diego Calleja wrote: El Wed, 23 May 2007 16:23:44 +0200, Gergo

[Fwd: Re: Google are using linux kernel - what do you know about the source?]

And copy to the list... ---BeginMessage--- And where, may I ask, does one find the source of Google's modified kernel? (At least, the unmodified bits!) Chris Matti Aarnio wrote: On Wed, May 23, 2007 at 04:50:35PM +0200, Diego Calleja wrote: El Wed, 23 May 2007 16:23:44 +0200, Gergo

Re: NCPFS 255 character support?

Alan, If NCPFS has little use these days, how are the linux users meant to sign on to Novell networks without using the (IMHO) bloatware provided by Novell? In fact, Novell's client only work on SLED first time lucky (everything else needs extra libs and a lot of work) so it's hardly much

Re: NCPFS can't handle extended characters.

Alan Cox wrote: For any real hope to answer things like that it would be useful to have precise descriptions of what fails, any messages logged when it occurs etc. OK, What fails: A dir on the folder containing the offending file results in part listings or no listing at all. There are no

Re: NCPFS can't handle extended characters.

Oops, see inline comments! Chris Malton wrote: I found a bug in NCPFS that I haven't the time to fix right now. Here's the problem: if a file contains an extended (Charcodes 128-255) character, especially ` (or a even worse, an word converted ' (curled apostrophe) NCPFS goes butter side down

NCPFS can't handle extended characters.

I found a bug in NCPFS that I haven't the time to fix right now. Here's the problem: if a file contains an extended (Charcodes 128-255) character, especially ` (or a even worse, an word converted ' (curled apostrophe) NCPFS goes butter side down on the directory listing. It doesn't hand the

Re: NCPFS can't handle extended characters.

Alan Cox wrote: For any real hope to answer things like that it would be useful to have precise descriptions of what fails, any messages logged when it occurs etc. OK, What fails: A dir on the folder containing the offending file results in part listings or no listing at all. There are no

NCPFS can't handle extended characters.

I found a bug in NCPFS that I haven't the time to fix right now. Here's the problem: if a file contains an extended (Charcodes 128-255) character, especially ` (or a even worse, an word converted ' (curled apostrophe) NCPFS goes butter side down on the directory listing. It doesn't hand the

Re: NCPFS can't handle extended characters.

Oops, see inline comments! Chris Malton wrote: I found a bug in NCPFS that I haven't the time to fix right now. Here's the problem: if a file contains an extended (Charcodes 128-255) character, especially ` (or a even worse, an word converted ' (curled apostrophe) NCPFS goes butter side down

Saitek USB Gamer's Keyboard

I have been working on this device for a while, and have come up with the following: The protocol is simple: ?? ?? 52 70 ?? ?? ?? ?? KC 1 [DOWN] ?? ?? 52 70 ?? ?? ?? KC Key 48 1 49 2 50 3 51 4 52 5 53 6 54 7 55 8 56 9 57 Mode A 58

Saitek USB Gamer's Keyboard

I have been working on this device for a while, and have come up with the following: The protocol is simple: ?? ?? 52 70 ?? ?? ?? ?? KC 1 [DOWN] ?? ?? 52 70 ?? ?? ?? KC Key 48 1 49 2 50 3 51 4 52 5 53 6 54 7 55 8 56 9 57 Mode A 58