Puppy Linux Discussion Forum

[ttuuxxx]

Well I just tried this version for the first time and as it sits, I had no problems with connecting to the internet, actually I've had no problems at all:)
Pburn&Pfind need updating but still work,
I do like the new Pburn with small graphic theme that it has as an option. maybe next release??
The Smooth-Saphire theme is 563kb so I did the old transfer to my lite theme package and now its 188kb
I'll included it as a pet package.
I'll keep testing and report any problems.
I like the Gtk2 theme also the firefox them
ttuuxxx

[tronkel]

Alienjeff wrote:

[tronkel]

@ttuuxxx

OK thanks for the reduced-size Saphire theme. I'll replace the older larger version with this one in the next version of Chihuahua.

@prehistoric

OK, good work with nailing this bug. Freememapplet has been suspect for ages in other respects as well. Could be time to replace it - if such a replacement exists. I used something in 2.16CE but forget what it was. I'll have a look in the 2.16 Unleashed directory.

I'll alter killconky to toggle itself rather than restart from the menu item.

[ttuuxxx]

tronkel just wondering which pmount are you using?
when I mount cd or hdd it displays mini-filemgr.xpm
when it should be showing mini-hdisk-green.xpm & mini-cd-green.xpm
also it doesn't show my usb swap drive. I have a 1 gig swap usb flash drive that I use on this pc. But conky shows its being used.
Pmount on my 3.01 retro FH shows the usb swap.
ttuuxxx

[tronkel]

ttuuxxx,

Pmount is the latest one from Barry, V3.96 Jan 2008
As far as I remember, probepart was also replaced in Chihuahua by a later version from someone or other.

I'm not sure if Dingo has had further alterations made to it since.
Maybe worth a try to try the Dingo versions of both and see if that helps. My hardware here has had continual problems with USB, so it's hard to test.

Puppy Linux has on-going problems with USB from what I know. This is one of the things in 3 series Puppies that needs fixing.

edit:

[prehistoric]

@tronkel,

Freemem tray applet is only part of the problem, there are still some race conditions between other Icewm processes and Xorg shutdown. One hack, not really debugging, is to insert a sleep in front of the command that actually kills X. If shutdown sometimes works correctly on this machine, the required delay can't be very much.

@AJ,

I have a slightly wild idea for an experiment. Have you tried running wNOP? If you can get through Xorg setup with any configuration, it will use that to get an initial configuration of proprietary drivers, including Intel's unified driver, which subsumes the i810 driver. Once that works you should be able to change resolution to your liking. I'm just curious about what will happen. This may yield clues about how to make i810s work.

[alienjeff]

[gerry]

@Tronkel: I know about lpr -P "printername". It does not work for me. The only time I can print is when the app gives a list of installed printers or "default printer". Abiword just gives "Generic Postscript", not the same thing at all. Except in Dingo, where the installed printers are listed and selecting my printer produces print.

I un-installed Ted, and had another go at installing it. This time it installed properly, but, there is no menu entry (there is in Puppy 214R and 301), so I have to start it from the console. At print time it offers "Default printer", and printing works OK. So printing works, the problem is in the way Abiword connects to the printing system.

Gerry

[cthisbear]

" And the highest resolution that would work in xvesa was 800x600 "

alienjeff:

I haven't tried this version yet but in your Bios....
have you set up a bigger video size?

I fixed up a Dell Optiplex SX260 last week, and tried Puppy 4 Beta
on it. I always use Xvesa myself...but I only got one screen size,
so I rebooted and changed the Bios setting.
I then had much more choice.

So I wonder if that works.

Regards .......... Chris.

[tronkel]

Alienjeff wrote:

[alienjeff]

Dear Tronkel,

In the immortal acronym of the long gone but dearly remembered Amish, "OFFS!"

My qualifier in the initial post was "In the real world..." Everyone knows, or should, that this isn't the real world. This is an illusion of bits and bytes and packets and bursts of data.

I am not a computer expert, nor do I play one on TV. I'm a half-assed quasi-power user reporting bugs. You two are the experts. You two are spearheading this CE. If you note my original post, I listed several problems with this alpha. Other than ttuuxxx's "works for me" reply and prehistoric's suggested ad hoc testing Xorg from within NOP, you've chosen to focus on my opening quip about this icewm faux-"lite."

Way to go!

v2.12 faithful,

Jeff

[tronkel]

Dear Alienjeff,

Although you did indeed qualify your statement by stating that you meant in the context of "the real world", the implication about ttuuxxx's work was more than clear. That's the whole point here.

[ttuuxxx]

I agree 100% with tronkel, If we had more people like prehistoric & tronkel this project would be further off. Icewm has had a few problems always, but what is does do is
- fixes the fullscreen issues that JWM can't do with Gxine, which makes 80% of Gxine complainers happy
- It gives very light eyecandy that just about everyone loves.
- themes are easily found and installed or altered
- Low memory resources
- stable
- Icewm is the only reason why I stayed with puppy in the beginning, 2.15ce was what finally sold me, I tried each of the 1&2 series but it was too windows 98 look and feel. So i just kept looking. That's why I took on this icewm lite version. I seen a need for for a small and attractive window manager.
The shutdown problems don't happen on my computers so its hard for me to fix a problem I don't have.
But if anyone finds a fix I would be more than happy to look at it:)
meanwhile I'll be looking for a replacement memory display application.
ttuuxxx
Ps keep up the excellent work tronkel

[prehistoric]

@tronkel, ttuuxxx,

Still haven't managed to eliminate the problem, though killing the freemem tray applet does change probability. The difference in timing between reboot and shutdown is tiny, yet the behavior is different. Everything so far points to a race between processes in Icewm and the shutdown of X. The cases which fail have slightly more to clean up before exiting. Sticking a sleep 1 in a couple places didn't help. There may be an event looked for before the exit. I'm guessing there's a "deadly embrace" between two processes, but when it occurs I can't see it, and writing to a persistent file creates a new source of deadlocks. The situation is so bad I may have to think!

Second the motion to congratulate tronkel. Getting past the alpha stage always takes stamina.

[tronkel]

prehistoric wrote: