I have already gone into FATDOG Services and enabled&started BC WL, but the scan for wireless is still coming up empty using FATDOG._________________Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Engineor use DogPile

I know and understand the reason development decided to NOT activate the SWAP partition when present. But, would it be in user best interest to include a setting in FATDOG service manager to Enable it for detection and use upon reboot?

This would help the many who missed this until too late when RAM fills. It would negate the need to constantly use the SWAPON command.

An idea for ease of use.
Edit; 2nd paragraph into 2 sentences_________________Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Engineor use DogPileLast edited by gcmartin on Mon 09 Sep 2013, 19:38; edited 1 time in total

The 13.4 driver just said the card wasn't supported, the 13.8 beta2
driver compiled but after doing aticonfig --initial and rebooting it
gave several errors and wouldn't go to the desktup so I uninstalled it
and rebooted to get back to normal.

Billtoo , From your posted screenshot I can see you managed to make work Pwidgets with FD620 . Previously I did it on FD610 , but using the same pet didn't give the same result ( different kernel , I think ).
Did you use a new pet ?

Billtoo , From your posted screenshot I can see you managed to make work Pwidgets with FD620 . Previously I did it on FD610 , but using the same pet didn't give the same result ( different kernel , I think ).
Did you use a new pet ?

No, it's not a new pet, the only thing that would work is the clock which is all I really wanted so that was okay.

But, would it be in user best interest to include a setting in FATDOG service manager to Enable it for detection and use upon reboot?

Fatdog Control Panel already has an applet to create a swapfile and configure it for use on the next boot automatically.

rcrsn51 wrote:

Here is PeasyDisc v1.6 for Fatdog. I have also attached the Extras package for making DVD slideshows.

Much appreciated, this will be in Fatdog 630.
EDIT: Why the need for the extras? dvdauthor, pamscale and pnmpad are all in Fatdog already. Are they new versions?_________________Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread

I've just tried to reset the timezone, using Set System Timezone under Control Panel/Localization. It has no effect, either after restarting X, or rebooting. The symlink /etc/localtime gets reset correctly, but nothing else happens. I've tried several different time zones, none work. Oddly, I am sure that I have changed it at least once before. I'm dual-booting with win 7, so display time should = system time. So next I tried the option under Control panel/system/Set Date and Time. That worked, but very flakey. Initially I tried resetting by 1 hour and it worked after the expected brief black screen. Then I tried setting the exact time several times but nothing happened until I rebooted. Very weird!

I've just been playing with Radkey's Pupmenu. The program is supposed to start with [cntrl][shift][M] but doesn't. Works OK apart from that, except that the changes don't appear consistently in either the ghostly openbox menu or the LXPanel one. That may be because Pupmenu displays what is in the .desktop files and it seems that there are other factors involved, e.g. the openbox and lxpanel menus are not the same? PupMenu does have a way of getting stuff off the menu and onto the desktop though, which I was asking about earlier.

EDIT: Why the need for the extras? dvdauthor, pamscale and pnmpad are all in Fatdog already.

Pamscale and pnmpad are NOT in my copy of 621.

My mistake, those two are in devx. I run with devx attached at all times, so I never miss them

Quote:

Dvdauthor is present, but it's broken. (I saw the same thing in Wary.) This is the version from Ubuntu Lucid 64-bit.

Noted.

All in all, I'll get that in for 630. Thank you.

Snail wrote:

I've just tried to reset the timezone, using Set System Timezone under Control Panel/Localization. It has no effect, either after restarting X, or rebooting. The symlink /etc/localtime gets reset correctly, but nothing else happens. I've tried several different time zones, none work. Oddly, I am sure that I have changed it at least once before. I'm dual-booting with win 7, so display time should = system time. So next I tried the option under Control panel/system/Set Date and Time. That worked, but very flakey. Initially I tried resetting by 1 hour and it worked after the expected brief black screen. Then I tried setting the exact time several times but nothing happened until I rebooted. Very weird!

Odd. Try rebooting without savefile and then change the timezone, see whether you get the correct result?

Quote:

I've just been playing with Radkey's Pupmenu. The program is supposed to start with [cntrl][shift][M] but doesn't.

Haven't checked Pupmenu, but my guess the ctrl-shift-M hotkey is tied to JWM. Thus it has no effect on openbox. You can always re-configure the hotkey using sven if you wish (that little keyboard icon on the lxpanel).

Quote:

Works OK apart from that, except that the changes don't appear consistently in either the ghostly openbox menu or the LXPanel one. That may be because Pupmenu displays what is in the .desktop files and it seems that there are other factors involved, e.g. the openbox and lxpanel menus are not the same?

In theory they should be identical although openbox's and lxpanel's menuing code are different, so expect some discrepancy. Can you give me an example of the discrepancy (using the standard out of the box programs if possible).

EDIT: In 620/621 the lxpanel and openbox menu is different. In 630 they will be the same again (the lxpanel menu will look like openbox's menu) (I forgot that I'm running FatdogNext in which the lxpanel menu has been "fixed", and this fix will be in 630).

Last digit version number increase (620 to 621, 621 to 622) indicates bug-fix release, however in this case "622" is just a number we use to differentiate between the last public release (621) and the "testing stuff" (aka "Fatdog Next" aka "cooking" aka "trunk" aka "tip", etc). We could have stayed with 621 numbering but that would be confusing (to ourselves, see what I did to Snail's response above!) when our 621 isn't the same as public 621 , and at the time we increased the version number there were no updates (other than bugfixes). There aren't any major bugs that warrants 622 release so it never got released.

Middle digit version number increase indicates updates, like 600 to 610, 610 to 620, etc. So the next planned release, which is an update to 620, is appropriately called 630. So from today onwards what we'll have is pre-630, no longer 622 (as if the name matters! )

630 would contain all changes so far, plus application, Xorg and kernel updates. ETA in about one month's time.

OK thanks for clearing that up. My very early IT job, my manager would use Alpha, Beta, Gamma etc as release ids but did so backward to the way IT releases are done today, Out first sample release where Alpha, next Beta, then Gamma, and a few Deltas ( most full releases where Delta )

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum