Tronkel is working on adding that option to his new Icewinconfig utility. Have you seen that yet?cthisbear wrote:Have a simple script to turn off or on..happy little vegemites all round.
We can't please everyone. If you don't like it, then you change it to something you DO like. Puppy 2.15CE must use what the majority want - that's democratic. Personally I prefer coloured icons, but this isn't MY distribution, it's the community's distribution.cthisbear wrote: The desktop backgrounds or icons for those of us with poor eyesight are a pain...personally I would like the blue lightened up.
Did you see the charter for Puppy 2.15CE? Specifically it is to be a CONSOLIDATION edition. That means no really new or cutting edge features, just updating, firming up and making reliable what is already there. The cutting edge stuff will be in Barry's next release ... Puppy 2.16cthisbear wrote:No internet connected by default...
Hello can't anyone ask Hacao how he did it? Although as I have stated before I don't know if he enabled the firewall by default at boot.
Hey, at least you got as far as choosing a location. Before Puppy 2.15CE you had to create a complete directory structure under /root before it would even offer you a choice! Not every problem will be resolved in a single release cycle. On Puppy's past record, miracles usually take at least two!cthisbear wrote:One glitch and I don't mean to be vague...was I tried choosing location?? by mistake, as I was just giving Viz a quick onceover look. I chose Au-English?
and then cancelled and went to the Black Scream Of Gloom...ha! ..ha! waited for a goodly amount of time but had to reboot. Velly interesting.
Beats me. The Xvesa that goes into a new release like 2.15CE comes straight out of Unleashed, where Barry put it! I have changed NOTHING about Xvesa from Barry's 2.14 release.cthisbear wrote:Once again I ask why just about the majority of releases of Puppy not originating from Barry himself.... do not run Xvesa when it is selected...and then annoyingly goes back to the prompt.
UPDATE: Your complaint piqued my curiosity, so I went back to see if Xvesa would run, and if not why not. I have resolved the issue. The file /etc/TZ needs to be made world writeable, and the file /etc/videomode doesn't exist so it needs to be created and also made world writeable. That fixes the problem. I have implemented that solution for Puppy 2.15CE Office Edition - due for release this weekend.
Ahem! That's precisely WHY this was a consolidation edition. We want to iron out those annoying "irritating pissant things at boot", and we are certainly trying. And yet you still want us to add AutoDHCP by default and risk all of the bootup glitches doing that might subsequently present? Consistency, Chris ol' stick, is the hallmark of quality.cthisbear wrote:If you want Windows refugees to use Puppy.....they don't want a problem at bootup...forget it...all that work...all the pretty pics...all the hard yakka...all the whingeing and or requests by myself or others went down the gurgler.
Irritating pissant things at boot will not cut it.
Personally I know quite a bit about computers...but only a tad about Linux.
You are not the only kennel occupant to have griped all over Puppy 2.15CE. That might be MY fault, as I did set the bar rather high for expectations. All the same, I'm not in the least bit unhappy with what has been produced so far, or with the mammoth effort behind the scenes from the likes of Pizzasgood, NathanF, PkaG, Tronkel, rarsa et al, and as the only puppy with access to Puppy 2.15CE Final at this stage, I am more than satisfied that we will soon have achieved most, if not all, of what we set forth to do with our first Community Edition for some time.
