Dingo 4 alpha3 Bugs/probs
Re: cant shutdown
Will someone please post a link to the Jan 5 version? I haven't seen it and I'm getting confused. I don't know which thread to post my bugs to.raffy wrote:Barry, I've tested the shutting down of alpha4 twice on the eee, always failing - no poweroff or reboot working.
Now, with the Jan 5 version...
This is a very marginal issue, and was present in previous Puppies too, but can become annoying:
if for some reason the mouse isn't working, in some instances it's not easy to select menu items from the keyboard (TAB, arrows, space and Enter) since the active item is not always clearly highlighted.
E.g., try changing the screen resolution this way in Dingo's XVesa wizard window: the chosen value can be clearly seen, as a dot appears in the corresponding button, but then neither the <CHANGE> nor the <OK> button get highlighted or focused to show which is the active one, so the job becomes a hit-or-miss game or guesswork (only the script name inside the text box goes in and out of focus by pressing TAB repeatedly).
if for some reason the mouse isn't working, in some instances it's not easy to select menu items from the keyboard (TAB, arrows, space and Enter) since the active item is not always clearly highlighted.
E.g., try changing the screen resolution this way in Dingo's XVesa wizard window: the chosen value can be clearly seen, as a dot appears in the corresponding button, but then neither the <CHANGE> nor the <OK> button get highlighted or focused to show which is the active one, so the job becomes a hit-or-miss game or guesswork (only the script name inside the text box goes in and out of focus by pressing TAB repeatedly).
dingo 5
don't know where to post the dingo 5 stuff.. so I do it here.
Issue with external PCMCIA CD-Rom Drive (sony vaio pIII 64MB RAM, subnotebook):
Until 1.07, the live CD booted with no problem
Until 3.01, and dingo alpha 2 the CD booted with boot-parameter "ide1=0x180"
Now it doesn't boot at all. The error is, that after loading the initrd (this still works), the system can't find the CD ROM...
Is there a new parameter available - or could be the PCMCIA stuff is missing in the kernel....?
Please help
Issue with external PCMCIA CD-Rom Drive (sony vaio pIII 64MB RAM, subnotebook):
Until 1.07, the live CD booted with no problem
Until 3.01, and dingo alpha 2 the CD booted with boot-parameter "ide1=0x180"
Now it doesn't boot at all. The error is, that after loading the initrd (this still works), the system can't find the CD ROM...
Is there a new parameter available - or could be the PCMCIA stuff is missing in the kernel....?
Please help
- Dougal
- Posts: 2502
- Joined: Wed 19 Oct 2005, 13:06
- Location: Hell more grotesque than any medieval woodcut
Assuming it's a gtk gui you're talking about, then it's a problem with the gtk-theme, so try changing it.capoverde wrote:E.g., try changing the screen resolution this way in Dingo's XVesa wizard window: the chosen value can be clearly seen, as a dot appears in the corresponding button, but then neither the <CHANGE> nor the <OK> button get highlighted or focused to show which is the active one, so the job becomes a hit-or-miss game or guesswork (only the script name inside the text box goes in and out of focus by pressing TAB repeatedly).
What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind
Some say your nose
Some say your toes
But I think it's your mind
Hi Dougal! That's it, for sure.
My point was this: if a total newbie boots Puppy, his mouse doesn't work and he doesn't give up at once, he'll try to play around the main settings from the keyboard; if still more difficulties come out there, he'll most certainly give up Puppy forever.
It's a margin issue, as I said. I quite like the Citrus theme of Dingo, and by far prefer it to the other available GTK themes; but its highlighting ought to be more visible. Most users may care more for this than for having an FTP client or a powerful partitioning tool at hand!
BTW, a review I recently read gave Puppy a big overall thumbs-up, except for a minus to the graphical looks. However silly, this is what gives the very first impression: and an uncertain visual feedback transmits a feeling of insecurity.
My point was this: if a total newbie boots Puppy, his mouse doesn't work and he doesn't give up at once, he'll try to play around the main settings from the keyboard; if still more difficulties come out there, he'll most certainly give up Puppy forever.
It's a margin issue, as I said. I quite like the Citrus theme of Dingo, and by far prefer it to the other available GTK themes; but its highlighting ought to be more visible. Most users may care more for this than for having an FTP client or a powerful partitioning tool at hand!
BTW, a review I recently read gave Puppy a big overall thumbs-up, except for a minus to the graphical looks. However silly, this is what gives the very first impression: and an uncertain visual feedback transmits a feeling of insecurity.
- Dougal
- Posts: 2502
- Joined: Wed 19 Oct 2005, 13:06
- Location: Hell more grotesque than any medieval woodcut
The Citrus theme is pretty bad since it's slow... Try running on old HW and changing between that and a different theme and you'll notice a big difference.capoverde wrote:I quite like the Citrus theme of Dingo, and by far prefer it to the other available GTK themes; but its highlighting ought to be more visible.
What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind
Some say your nose
Some say your toes
But I think it's your mind
Thank you Dougal for your hint.
I'm testing with a K6-II/400; changing from Citrus to any of the other themes I'm unable to detect a quicker response to window opening - maybe my manual test is insufficient: by clicking very quickly twelve times on the "file" (home) icon, with any theme it takes about 0,5 seconds to open the first 2 or 3 windows (about 0,2 sec each), then the subsequent ones open much faster (ten in less than 0,8 sec).
While doing this, I notice that Puppy isn't running entirely from RAM as I expected since this PC has 128MB RAM, the HD has a swap partition and there seem to be 186MB free with SeaMonkey and Geany running.
This happens whether or not I give pfix=ram at boot; I've surely missed something.
I'm testing with a K6-II/400; changing from Citrus to any of the other themes I'm unable to detect a quicker response to window opening - maybe my manual test is insufficient: by clicking very quickly twelve times on the "file" (home) icon, with any theme it takes about 0,5 seconds to open the first 2 or 3 windows (about 0,2 sec each), then the subsequent ones open much faster (ten in less than 0,8 sec).
While doing this, I notice that Puppy isn't running entirely from RAM as I expected since this PC has 128MB RAM, the HD has a swap partition and there seem to be 186MB free with SeaMonkey and Geany running.
This happens whether or not I give pfix=ram at boot; I've surely missed something.
Alpha 5 is identified as Alpha 5?
I've downloaded something I thought was Alpha 5 twice and it said it was Alpha 4. Am I getting the wrong one?
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Re: Alpha 5 is identified as Alpha 5?
I forgot to update the initial welcome/menu screen.geneven wrote:I've downloaded something I thought was Alpha 5 twice and it said it was Alpha 4. Am I getting the wrong one?
[url]https://bkhome.org/news/[/url]
- Dougal
- Posts: 2502
- Joined: Wed 19 Oct 2005, 13:06
- Location: Hell more grotesque than any medieval woodcut
There isn't much to render in a Rox window (what there is is the mime-types, which are dependent on the Rox-theme, rather than gtk).capoverde wrote:
I'm testing with a K6-II/400; changing from Citrus to any of the other themes I'm unable to detect a quicker response to window opening - maybe my manual test is insufficient: by clicking very quickly twelve times on the "file" (home) icon, with any theme it takes about 0,5 seconds to open the first 2 or 3 windows (about 0,2 sec each), then the subsequent ones open much faster (ten in less than 0,8 sec).
Tempestuous mentioned to me a couple of months ago that he's unhappy with Dingo because it's slow, so I tested and found that opening things like Geany is slower with the Citrus theme. It is also noticeable when you shade/unshade windows.
Since puppy3, the filesystem is only loaded into ram if you have more than 256MB of physical ram.While doing this, I notice that Puppy isn't running entirely from RAM as I expected since this PC has 128MB RAM, the HD has a swap partition and there seem to be 186MB free with SeaMonkey and Geany running.
This happens whether or not I give pfix=ram at boot; I've surely missed something.
What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind
Some say your nose
Some say your toes
But I think it's your mind
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
No, at least No for Dingo, I don't recall about Puppy3, pup_xxx.sfs is copied to ram if there is more than 230000KB (224.6MB) free physical ram. Maybe there are some systems that have 256MB but have less than 224.6MB free at bootup?Dougal wrote:Since puppy3, the filesystem is only loaded into ram if you have more than 256MB of physical ram.While doing this, I notice that Puppy isn't running entirely from RAM as I expected since this PC has 128MB RAM, the HD has a swap partition and there seem to be 186MB free with SeaMonkey and Geany running.
This happens whether or not I give pfix=ram at boot; I've surely missed something.
Also, Dingo supports 'puppy pfix=noram' to prevent the pup_xxx.sfs from loading into ram.
[url]https://bkhome.org/news/[/url]
- Dougal
- Posts: 2502
- Joined: Wed 19 Oct 2005, 13:06
- Location: Hell more grotesque than any medieval woodcut
Well, that's kind of nit-picking... Your comment in the script even makes a reference to it being 256MB or above. The point is that when someone with 192MB ram (like me) doesn't get the filesystem in ram (which they used to).BarryK wrote:No, at least No for Dingo, I don't recall about Puppy3, pup_xxx.sfs is copied to ram if there is more than 230000KB (224.6MB) free physical ram. Maybe there are some systems that have 256MB but have less than 224.6MB free at bootup?
What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind
Some say your nose
Some say your toes
But I think it's your mind
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Nitpicking? I only gave a factual reply to your comment:Dougal wrote:Well, that's kind of nit-picking... Your comment in the script even makes a reference to it being 256MB or above. The point is that when someone with 192MB ram (like me) doesn't get the filesystem in ram (which they used to).BarryK wrote:No, at least No for Dingo, I don't recall about Puppy3, pup_xxx.sfs is copied to ram if there is more than 230000KB (224.6MB) free physical ram. Maybe there are some systems that have 256MB but have less than 224.6MB free at bootup?
which is incorrect for Dingo.Since puppy3, the filesystem is only loaded into ram if you have more than 256MB of physical ram.
[url]https://bkhome.org/news/[/url]