Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - darmabum

Pages: [1]
1
Zaurus - pdaXrom / Emacs Runs Fine. Pdaxrom Now Rocks
« on: June 09, 2005, 02:32:06 pm »
One final note regarding XEmacs with xslt.  I'm using xslide and it's fully functional, but transforms with xt break due to a java error.  Xsltproc, however, works fine.

2
Zaurus - pdaXrom / Emacs Runs Fine. Pdaxrom Now Rocks
« on: May 24, 2005, 01:45:40 pm »
As for the ftp problem, it seems I needed to install the net clients package (the ftp programs weren't allowing xemacs to play).  Now, everything seems to work like a charm.  I have installed most xemacs packages using the internal installer, including vm and gnus, as well as psgml and xslide, and it all WORKS!!

So, XEmacs in your pocket...not bad.

3
Zaurus - pdaXrom / Emacs Runs Fine. Pdaxrom Now Rocks
« on: May 23, 2005, 01:48:14 pm »
As for XEmacs, I can attest that the pckg available at unstable is 90% fine.  I've been incrementally trying many packages and most work although an ftp process error prevents (so far) the online package updater, and online connections such as efs from connecting.  Given other modem problems I have I'm not sure who to blame.

Some asides:  Dired failed to load until I recompiled the lisp files.  Now it's excellent.  Ediff is also cranky.  My goal:  xslide...

4
Zaurus - pdaXrom / modem
« on: May 23, 2005, 01:36:03 pm »
Quote from: henrysviper,Feb 27 2005, 01:10 PM
I have the same problem with Marcus. My setup is RC9 + Targus cf modem.

I cannot log in to any dial-up account: I have two that use PAP and one that uses CHAP and always the final message is "Failed to authenticate ourselves to peer" although username/password are correct. I had a look at the files under /etc/ppp and they look ok.
[snip]

It's even weirder than that.  Try this:  1.  Use the PPPDialer (it will fail as you described), 2. Then use a terminal program to manually enter the pppd command (it will also fail), 3. Now enter the same command in the terminal and it will probably succeed (enter route -n to verify).

I can't confirm the order, or the number of attempts, but basically the same command will usually succeed on the third try or so...

jb

Pages: [1]