Messages

16

Zaurus - pdaXrom / Xmms - Need Mpeg 1/2/3 Plugin

« on: August 05, 2006, 08:38:22 pm »

Update:

I've now been trying to compile xmms (version 1.2.10 sources) myself in order to get the MPG123 plugin. However, although building and installing xmms works fine the build process wouldn't create the shared libraries "libmpg123.so"! It only creates static libraries "libmpg123.a". I have tried to run ./configure with and without the "--enable-shared" option (which should be on by default anyway), however, both to no avail. Also other plugins such as the OSS output plugin are not created as shared libraries only as static ones (so I can run xmms but don't hear anything). Only libwav.so and libtonegen.so are build as shared versions so building shared libraries in general should work.

When I run the exact same build process on my X86 desktop PC each plugin gets created as a shared library.

What would prevent the build process on the ARM architecture to create shared libraries? I must be missing something?

Help?

17

Zaurus - pdaXrom / Xmms - Need Mpeg 1/2/3 Plugin

« on: August 03, 2006, 07:09:23 pm »

Lately I came across a number of files which xmms would refuse to play on my C3000. Xmms on my desktop PC plays them fine. I checked those MP3's with the 'file' utility which prints:

Wamdue Project - King Of My Castle.mp3: RIFF (little-endian) data, WAVE audio, MPEG Layer 3, stereo 44100 Hz

Comparing the plugins on my desktop PC with those on my Zaurus I found out that I'm missing following plugin:

MPEG Layer 1/2/3 Player 1.2.10 [libmpg123.so]

Can somebody tell me where I can find this plugin for my C3000?

TIA!

18

Zaurus - pdaXrom / Python Support

« on: July 31, 2006, 03:38:03 pm »

On my C3000 with 1.1.0beta1, I'm trying to run PySol which provides tons of Solitaire-like games. The Python interpreter claimed about a number of missing modules which I copied from my desktop Linux box and their error messages went away.

However, now it claims that "TKinter" is missing. I couldn't find any module with that name. As far as I figured out "TKinter" has something to do with Tcl/Tk and needs somewhat compiled directly into the Python interpreter.

Q: Has somebody tried to compile Python for pdaXrom with "TKinter" support included?

19

Zaurus - pdaXrom / Breakout Game

« on: July 30, 2006, 06:34:12 pm »

LBreakout is a very nice breakout-style arcade game in the manner of Arkanoid.

Just found it, couldn't believe my own eyes! One of the best games ever made for Linux (and other OS's) runs smoothly on my C3000! Wow, simply amazing.

Everybody has to give it a try. Just addictive and a lot of fun. Mind you, earphones and mouse are strongly recommended for full experience. Especially the mouse since controlling the vaus (paddle) with keys or stylus is quite difficult and takes some time to get used to.

cortez, many thanks for porting it to the Zaurus!  

20

Zaurus - pdaXrom / Pdaxrom For C3000 Beta2

« on: July 30, 2006, 03:47:57 pm »

Thanks a lot for your suggestions! It seems to be a particular good idea to keep data files on separate data cards. And making regular backups is never a bad advice, however, humans tend to become very lazy in case everything seems to work fine and smoothly. Only in case of crashes one wished having made more frequent backups.

I'll try to remember those hints in future!

21

Software / Free Sudoku - Now All Zaurus And Archos Supported

« on: July 29, 2006, 10:57:06 am »

If you remove executable pieces from the binary the binary will not run anymore.  

22

Software / Free Sudoku - Now All Zaurus And Archos Supported

« on: July 29, 2006, 10:25:43 am »

No, you can't remove the way certain things are compiled by the compiler. You can perhaps remove symbols, copyright messages and such, but this is not what I meant.

Each compiler has something like a footprint, the way how it compiles certain constructs of higher languages. Each compiler compiles code according to specific algorithms. Of course, you need to know the inner workings of that compiler, but you can recognize these specifics in the binaries. May not be trivial, but possible.

Using a disassembler is a first step. Looking at the assembler code generated it will be possible to recognize specific characterics typical for the compiler being used.

23

Zaurus - pdaXrom / Pdaxrom For C3000 Beta2

« on: July 29, 2006, 07:24:36 am »

@Reaper:

Thank you very much for your detailed comments! Every day I work with pdaXrom I like it more! Because it comes closes to a "real" Linux system, IMHO. If you know Linux from your desktop PC it is relatively easy to get things done under pdaXrom. For example, I run Xfce4 as a desktop envionment on my C3000 since I also use it on my workstation. And it is absolutely the same look and feel. Amazing.

After all, I always can reflash. I keep "emergency kit" with .conf files, fonts, /etc scripts and alike on my SD card, so restoring my Z after reflashing is a matter of less than an hour, and most of this time is spent at downloading and installing new versions of programs not included.

This is, at the moment, the only thing of concern to me: How will I be able to make an upgrade to the next version of pdaXrom without losing all my individual settings? If you don't mind and if your time allows, could you shortly describe what exactly your "emergency kit" contains? I'm not worried doing some additional tweaking after having installed a new version of pdaXrom, however, I'm just afraid that I will have to do all of my customization again!  

24

Software / Free Sudoku - Now All Zaurus And Archos Supported

« on: July 29, 2006, 07:00:57 am »

So in truth if someone doesn't want to release the source all they need to do is say that it was written in machine code and there is nothing that anyone can do about it because the binary is all there is, no one can prove otherwise and the source is distributed when the binary is given out.

No, this is wrong. A compiler always leaves his own particular tracks in the binary. So, by looking at the binary you can always find out that it was compiled.

25

Software / Free Sudoku - Now All Zaurus And Archos Supported

« on: July 29, 2006, 06:57:52 am »

Ultimately, what would have been the big deal to wait or be less demanding?

What would have been the big deal to immediately release the source?

Figlabs chose to release the binary so it must have reached a mature enough state that they decided to give it to the public. Why not giving out the source code at the same time? It seems unlogical that one believes the binary is ready for the public but not the sources. And if time constraints prevent creation of proper documentation then this is exactly a very good reason to release them because of these constraints. There may be other people out there who could be more than happy to contribute to the program by writing the documentation. Because this is what Open Source is all about! The community allows that each other helps each other. This doesn't stop at the coding level but also extent to other areas such as documentation and testing and promoting and what have you.

So, Figlabs should not feel displeased. Not at all! Zudoku is now running fine under OZ, and this within hours after releasing the sources! And even w/o properly documented sources. In the Open Source community there is always somebody else who has time if you don't have it. You cannot do everything yourself. Let others help out if time is short.

Finally, look at the creator of Linux himself. If he had decided not to make his first version of Linux available to the public because that very first version contained ugly hacks and was not documented at all at that time, would we all be here now???

26

Software / Free Sudoku - Now All Zaurus And Archos Supported

« on: July 28, 2006, 07:01:25 am »

@arniel:

You shouldn't stop or delay releasing the source code just because documentation is not ready! It is, of course, much easier to work on documented source code if you want to make changes to the functionality of the program, however, for the purpose of porting to other platforms you can get around w/o it.

27

Software / Free Sudoku - Now All Zaurus And Archos Supported

« on: July 28, 2006, 06:56:25 am »

It seems there is little incentive for us to do that so, instead, here is the original source used to build the app.

You can still do that once you get your spare couple of days! Then you upload the new sources and the corresponding diff file and the community will very much appreciate your hard work on this nice little program. In the meantime those users who need to run it on other graphical platforms than Qtopia can look into the source code and see how it can be adapted to other toolsets.

Thanks a lot for the sources! And, as I said, the Zaurus community will definitely appreciate your work on this program!!  

28

Zaurus - pdaXrom / Stopping/starting Samba Automatically

« on: July 28, 2006, 03:19:54 am »

Thanks for these hints! That's something I'll can now dig into!

29

Zaurus - pdaXrom / Stopping/starting Samba Automatically

« on: July 27, 2006, 06:18:21 pm »

How do you connect and disconnect from the wireless network? Perhaps just insert the commands into your scripts for this.

When I manually suspend and resume I call self-made scripts containing "cardctl suspend", "cardctl resume", "cardctl insert" and "cardctl eject" commands and it would be no problem to also include the appropriate samba stop and start sequences.

However, when I plug in the WiFi card my C3000 automatically connects the card and I don't need to call one of my scripts. Also when suspending and resuming the whole Zaurus the WiFi stuff is automatically executed w/o the need to call my scripts. In these cases the samba server is not correctly stopped and started.

So I thought there must be some system scripts which are automatically called by some  mechanism. Is it hotplug? Dunno. I've not yet looked into the inner workings of hotplug and what scripts are involved.

Can somebody confirm whether it is hotplug doing this "magic stuff"?

30

Zaurus - pdaXrom / Stopping/starting Samba Automatically

« on: July 27, 2006, 03:41:57 pm »

I'm looking for ways to automatically start the samba server whenever a Wifi CF card is inserted or resumed. And to automatically stop it when the card is suspended or ejected.

Is there anywhere a central script which catches globally those resume/suspend and insert/eject events so that I can add the corresponding samba start and stop commands there?

TIA for hints!