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 - jandr

Pages: [1] 2 3
Zaurus - pdaXrom / Needsl-c7x0/860 Owner With Sd Mmc Cards Bigger 1g
« on: January 22, 2006, 02:46:10 pm »
Is there any chance the new driver will help with non-Japanese cards that the current driver chokes on?  I've got a Viking  made-in-Taiwan 256MB SD that my 760 throws I/O errors on when it's formatted ext2, and have been leery of getting any larger card for fear of the same thing happening.  The 760 is perfectly happy with a 128MB Japanese PNY.

Accessories / Zaurus-powered Usb External Storage
« on: January 11, 2006, 05:32:13 pm »
Hi everyone,
Here's a question that hopefully isn't too-too far off topic for this thread: does anyone know of a USB enclosure for 2.5" HD that will take an older 17mm high drive (8GB IBM Travelstar)?   Everything I've found so far is for newer 9.5mm drives only, with the occassional 14mm one.  It'd be great if the Z's USB could power it but far more important that my drive fit in the enclosure in the first place.


Zaurus - pdaXrom / A Couple New Packages
« on: December 07, 2005, 08:13:44 pm »
I've been trying to compile gnokii from sources but keep getting stuck shortly into the make with this error:
> make
make -C common/phones
make[1]: Entering directory `/mnt/card/gnokii-0.6.5/common/phones'
/bin/sh ../../libtool --mode=compile gcc -g -O2  -I../../include   -o generic.lo -c generic.c
 gcc -g -O2 -I../../include -c generic.c  -fPIC -DPIC -o .libs/generic.o
In file included from ../../include/gnokii-internal.h:39,
                 from generic.c:37:
../../include/compat.h:163: error: parse error before "__extension__"
../../include/compat.h:163: error: parse error before '&&' token
make[1]: *** [generic.lo] Error 1
make[1]: Leaving directory `/mnt/card/gnokii-0.6.5/common/phones'
make: *** [common/phones] Error 2
and I'm not versant in C enough to know what's up... although I do know that compat.h doesn't have any mention of "__extension__", so it's something more subtle.   I've tried gnokii 0.6.4 and 0.6.10 from fresh sources, and 0.6.5 with debian's 0.6.5-1 patch applied, all with the same error.  (Ditto with both the stock
zgcc-3.4.4.img and the qt-including zgcc-3.3.2.img from the "Native -- C++ / Qt, Compiling C++ w/ Qt natively on zaurus" thread.)

Zaurus - pdaXrom / A Couple New Packages
« on: December 05, 2005, 02:43:27 pm »
Does anyone have a copy of the gnokii 0.6.4 ipk ?

I can't find it on the www and the link seems to be dead.

[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

try [a href=\"]here.[/url]

Zaurus - pdaXrom / Mplayer Plugin For Firefox/mozilla Available
« on: November 29, 2005, 10:09:22 pm »
[hmm.... then it should handle whatever mplayer does already, right?  more testinng to do...
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

That's my understanding, but looking at the mplayerplug-in configuration it appears the plugin does need to be told to support the various formats (which it seems to try to do as much as possible by default).

Here's something more for you to test: I put together the newest version, 3.16, in order to try to get gtk widgets without crashing (the changelog hinted that bug had been fixed).  It still crashed, but a new without-gtk build did seem somewhat better about closing mplayer when firefox was closed, a small improvement.  The new ipk is in [a href=\"]my feed[/url] as usual.

Zaurus - pdaXrom / Pilot-link 0.12.0-pre4 And J-pilot 0.99.8 Ipks
« on: November 29, 2005, 06:08:23 pm »
Anyway, just thought I'd share - you can get them here
I've just upgraded to rc12, very nice, keep up the good work!
Can you also package jpilot-plugins? I miss keyring.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

I made my older jpilot (0.99.4) ipk from Pocketworkstation's .deb package, and they have a .deb for jpilot-plugins too.  So I packaged those up [a href=\"]here.[/url]  They're totally untested (except for making sure jpilot still runs and sees the plugins), and it's obviously not as good as having plugins to go with cjb's newer jpilot, but they still beat a boot to the head.

Zaurus - pdaXrom / Mplayer Plugin For Firefox/mozilla Available
« on: November 29, 2005, 06:03:18 pm »
testing today.

but..since this is a really good idea (aka something i'll use) ideas on how to get more codecs working?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=105398\"][{POST_SNAPBACK}][/a][/div]

That's really beyond my skills.  I'm more of the grab the source, run ./configure, symlink in all the missing headers and package it up type.  I think more codecs may be dependent on mplayer itself and not on this plugin, but that's just a guess.

An aside: I neglected to strip the .so file at first, so I've put up a new ipk to fix that.  And note that my version doesn't have any gtk widget support built in: with them in, my browser always crashed when using the plugin.

Zaurus - pdaXrom / Mplayer Plugin For Firefox/mozilla Available
« on: November 29, 2005, 01:24:27 am »
I've compiled and packaged up the mplayerplug-in version 2.70 & put it in my feed.  It's not perfect, but it lets you listen to NHL online game-radio!  Sometimes you have to explicitly kill the mplayer process when you're done, but other than that it works fine in my (minimal, testing.  I don't expect it to work with realplayer streams, and have no idea about QuickTime.  

It should work with firefox 1.06 out of the box; you'll have to move the mplayerplug-in.* files to use it with mozilla or older firefox.  Enjoy!

Zaurus - pdaXrom / Pilot-link 0.12.0-pre4 And J-pilot 0.99.8 Ipks
« on: November 26, 2005, 11:19:53 pm »
Hi cjb.
Thanks for the updates to jpilot & pilot-link!  I tried them on my rc12 C760 and PalmOS4.1 m505. pilot-link was fine (pilot-xfer worked as expected with both -l & -i <file.pdb> options).  But I couldn't get the new jpilot to sync at all.  It would either give an error "This palm has a NULL user id"
and suggest I install a new user on the palm -- which install-user handled admirably, but to no avail with jpilot -- or it would complain that the user on the palm didn't match the last user to sync and then ask would I like to sync anyway... but if I said "yes" it would immediately abort the sync.

I noticed that after using jpilot 0.99-8's "install a new user" function, my jpilot.rc would have a line like user_id -1073752484 instead of the usual positive (and smaller) number for user_id.

any idea what's up?  I've still got jpilot 0.99-4 working but of course that's older than is advisable.

Zaurus - pdaXrom / Ir Keyboard Drivers - Alpha Release
« on: November 15, 2005, 12:07:37 am »
For what it's worth, my Belkin F8U1500-E works great with the 1500t driver
under rc10 on my 760... I assume it'll be just as good with rc12.  Thanks a bunch!

Zaurus - pdaXrom / latex
« on: May 26, 2005, 01:13:07 pm »
I'd like to be updated about the development. So far, I use xdvi and xpdf,
both of which do excellent service. I am not sure how it works if I update to rc10. Is it worth it?
I remember rc9 having issues with cross compiling and that kpathsea had to be trimmed a little.
I vaguely remember that there was a plan that updates should not be a matter of reflashing
(is loosing the data and the installation that I have made to work). So any hints are welcome.

-- Marcus
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

I only left rc8 because I'd hosed my installation (which I later determined to be from using some fonts that  X didn't like).  I skipped rc9 after also having some difficulties with compiling on it, and have found rc10 to have two major improvements, one relevent to this topic & one not:

- xpdf now works out-of-the-box, with no funny library requirements;

- in rc8 some system apps (e.g. packagemanager) would silently fail if I had an SD card in the slot; that seems to be fixed.

Everything I installed under rc8, whether compiled by me or grabbed already built, seems to work fine. So for me rc10 is a minor improvement overall, but probably not worth moving to from rc8 unless you need to reinstall anyway.

I do have one issue with my new installation which is probably more due to my lack of understanding of latex than anything: whenever I use xdvi or dvips on my own latex files, I get an warning message about fonts "cmex8" and "msam8" not being found, and using cmr10 in their place.  I don't remember getting that error before but I can't figure out how to tell xdvi or dvips where those fonts are located (I do have them on the Z, copied over from my desktop tetex installation).  latex itself doesn't complain about the "missing" fonts.


EDIT: I solved the missing dvi fonts problem: latex was happy with the .tfm versions but xdvi wanted .pfb files, which I downloaded from [a href=\"]here.[/url]  (Note this is different from the missing-gv fonts problem described a couple posts back.)

Zaurus - pdaXrom / latex
« on: May 23, 2005, 08:15:44 pm »
Error: /undefinedresult in --div--

Hi again Marcus,
I just upgraded to rc10 and encountered the same problem as you... I think the solution is to populate /usr/share/ghostscript/fonts/ with whatever your desktop machine has on it.  According to the gs.README file, you might have to "update Fontmap if necessary".  (I didn't have to.)

Of course, you may have already figured this out.    


Zaurus - pdaXrom / Pilot-link Compiled
« on: May 23, 2005, 12:16:46 pm »
Yay!  I've got a working jpilot and malsync setup; you can grab my ipks here.

I wasn't able to successfully compile jpilot -- it wanted automake-1.6 but pdaX has 1.9 -- so I just packaged up pocketworkstation's version.  Kudos to them for figuring out how to patch it for the Z.

Zaurus - pdaXrom / Pilot-link Compiled
« on: May 20, 2005, 08:55:50 am »
Nice.  What does it sync with on the Z side of things?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=80329\"][{POST_SNAPBACK}][/a][/div]

It'd be great to get jpilot for pdaX, to act as a palm desktop on the Z.  I tried using the jpilot (and the pilot-link) from Debian woody with no luck; I think the old libs needed by those (including libpisock4) didn't play nice with irattach on the Z.

Strijar, your pilot-link worked great for me; any chance you'd be willing to compile up a new jpilot for us too, since you've already got the libpisock8 dev files set up?


[SL-C760, pdaX 1.1.0rc10]

Zaurus - pdaXrom / Native -- C++ / Qt
« on: April 12, 2005, 03:22:18 pm »
hmm, a general solution to what?
how is this the opposite of an SDK?
you can happily link against the qt libs given by pdaxrom, see my first posts.

When i compiled Qt3 i didn' t have to rename anything.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=74810\"][{POST_SNAPBACK}][/a][/div]

Ah, I was replying to both of the original post's questions at once, to wit: "yes I've managed to compile programs that use Qt natively on the zaurus (and here's how I did it)", but "no I don't have a working native SDK (and thus it's not a general solution)".

For what it's worth I wasn't able to link Konq against the qt libs provided by pdaxrom.  It was awhile ago so I don't recall why, but my guess is that Konq required some defs that weren't turned on by default.  And I only had to rename Xft.h if I wanted Qt's configure to find it; Qt did build quite happily without it.

Pages: [1] 2 3