Hi peebee, welcome
the missing images/icons tell me it is not matching the video driver, maybe you need to see what it is using and pick another
yeah, I forgot that orange on orange kills borders, the orange 'citrus-cut' was to define an alpha for me, go into jwm config and change one of them to something else such as the jwm theme to 'origonal' and that should fix that problem.
My website is in australia and is used by leadlighters and potters as well as puppy people, but it shouldn't be slow as I have open 1kmb bandwidth to the router, maybe there were a few downloading this or something else in one of my other groups or boards as I have three on the box.
I haven't gone further than the basics with touchpad 'stuff' yet as my one notepad with touchpad is slowly dying. And thanks for the offer of building a driver, if you put a url for it I shall download and add it to the default packagelist.
The default seamonkey is a fully stable one from the mageia 1 mage004 build so I have used it for testing. Have a look back in the replies as someone did update it. Mageia uses firefox by default, but their dillo is great as it has been debugged and speeded up. At the moment I am keeping to puppy and mageia standards, when I start back into qtpuppy things will change.
For the others,
- For those having hardinfo problems,
1- Also try going through the Lighthouse sys-info manu and see if that works?
2- Can you download and install from the Mageia core repositry the following two system packages
Code: Select all
libgdk_pixbuf2.0_0 and libuClibc-zlib1
, then install please, reboot and let me know if it fixes it. They are the full mageia packages that puppy has cut down, if it fixes it I shall add them to the default set.
I tried out the mageia hardinfo package, but can't see any differances against the puppy one except about 120k in size and it has no direct menu access so I would have to repackage it anyway for little gain.
And just on the qtpuppy topic:
I am comitted to matching the 'Puppy Standard Set' with mage2's mageia 2 puppy before I start cutting and pasting when I branch off with qtpuppy, it may not be perfect at that point, but should work on most ocasions and with most packages. If someone wants to take it on as a project at that point I will be happy to pass it on, giving help as I can.
I will build a mage 3 puppy when mageia 3 is out as I now have most of the necessary knowledge. Mageia 3 will be a different 'beastie' from the earlier ones though.
I am also considering a x86-64 mage 2 puppy as I am seriously considering paralleling qtpuppy, having it both in i586, and x86-64 with vm's for working with other platforms.
What I intend to do with mage2's first qtpuppy's, release codes 2.0.90 - 2.0.99, is to do what I did with my earlier warz builds and split all apps into their own sfs first. I can update/cut/kill and add at this stage and that is as far as I will be following puppy's standards. Things like removing mplayer and it's stuff and replace with mageia's gstreamer and it's kit, which is much better as well as being less processor intensive; getting rid of Seamonkey and replace with Mozilla packages is the second set; adding the latest stable qt4.8.x; adding the eggwm desktop as an alternate to jwm; and removing duplicate apps out of the default set are it's goal. Anything else will be by pet or a mageia package for the user to add into their savefile although I will have Pet Maker 2.2. so the user can build their own pets or sfs's.
Hopefully it will be out by October 2012.
In the following version (2.1.90 - 2.1.99), I shall remove quite a bit of what is unneeded in a qt development environment from the (2.0.9x) 'base system' and bring in some of the 'behind the scenes' parts of the dev tools I use now. The apps in the apps.sfs will shrink considerably and have the new qt and other development apps included in a qtapps.sfs, as well as reforming the Menu system to provide a separate 'Development' main Menu point and subpoints, rather than loading them into Utilities as is now (not barry's fault as it hasn't needed separating). It will also be the stage I bring the Razorqt/qlwm (pure qt) desktop into the 'visable world', as well as replacing quite a few apps and utilities we now use with qt equivalents.
This is planned at this stage for a Febuary 2013 release as quite a bit had already been done in warz until I hit too many problem blockers and decided to change bases.
That's my stop point for now, although I do have a page or two of items on my wish-list for the following one and will no doubt add or change some from sugestions appearing here, I need to get back on track.
On top of this i'm working in a small way with the mageia-dev team on mageia 3, and do have my Leadlighting business to keep going so things are not boring here.
regards to all
scsijon