Posted: Fri 16 Aug 2013, 19:25
That should already be supported. Perhaps you need a newer firmware. Try the attached files, put them into /lib/firmmailinator wrote:I would like to ask you, is it possible to install firmware for this wireless card? I am new to fatdog, and I don't know how to setup this wireless card. It is bcm 4313
Broadcom wireless device [14e4:4727]
Open terminal, then type:gcmartin wrote:The process/steps to carry out these task; could you share them.
Code: Select all
killall dhcpcd; udhcpc -qi wlan0
Thanks. The difference is indeed subtle. The "click on the green checkbox to unmount" is somewhat of a hack and is based on heuristics; these heuristics may not be correct for your screen size. For whatever it is worth, I have changed the icon placement algorithm in Fatdog Next, they may or may not solve the problem.snail wrote:Here they are jamesbond. As you can see, the amount of movement involved is subtle, within the precision that I can place the icons anyway.
Actually, now that I re-read your comment, I realise that I don't understand what you're trying to say. What exactly is the problem? What is the partition layout of the problematic computer? (ie what is sda1, what's the contents/partition types there, sda2, and so on and so on, and where do you install Fatdog)?This may be "expected behaviour when you move the Download folder outside the savefile" to experts like yourself. It is a serious potential usability issue to non-geeks. This case occurs whenever Fatdog is installed into the Windows partition, using fatdog's own installer, which is likely to be a very common case given how damned awkward NTFS partitions have been made to partition nowdays. mnt/sda2 is the most obvious route to the newb, although even that's none too obvious. As a suggestion, could the Fatdog installer be made to set up a symlink to /aufs/devsave called "Windows Partition" in /root, so it is easy to find in the Open File window, in the case of FatdoginWin installs?
Wpa-Gui isn't perfect and I'm glad that you have found a workaroundSince the "fix" I stumbled upon is doing nothing more clever than driving WPA-Gui, Surely the program should be able to be smart enough to realise that it's locked and automatically do what I have to spend several seconds doing, after about a week discovering how to?
Yes, one is not supposed to close Wpa-Gui window by clicking File/Exit. One learns the hard way of the mistake of doing so Anyway you can make changes persists by choose File/save.If you close the WPA-Gui window, by clicking File/exit, Not only does the WPA-Gui window close but the Taskbar icon also vanishes. There is no way of getting it back easier than running wpa-gui from the terminal, there are no icons in either the menu or the control panel. It also seems to loose any changes that you have just made in the Manage Networks tab. The wifi connection still persists however.
Yes, that's normal behaviour.The cross on the WPA-Gui window header bar seems OK, it closes the window but does not kill the taskbar icon.
As I said previously, Fatdog doesn't use symlinks for this, and gdmap is fooled by that. Just remember the fact that /usr/lib and /usr/lib64 is the same (also /usr/X11R7/lib64 and /usr/X11R7/lib); they don't use double the space as you think they are. This is one of the thing that one needs to learn about Fatdog.I know very little but I do know about symlinks. What confused me is that apparently, GDMap doesn't. Since the only point of using GDMap, apart from admiring the rather pretty graphic, is to find out what is eating your storage, surely it should ignore symlinks? At least as the default?
Can you tell me the exact steps to reproduce the problem?I did not use a terminal command, so it must have been xarchive from the menu that caused the problem. Fatdog started frantically warning me that I was eating the savefile but I couldn't come up with a solution in time to avert a smash.
Pupzip is called everytime you click a compressed file. It is the one that finally launches xarchiver for you. There is no icon to launch it manually.By the way, I see Pupzip is still in there but there is no icon to access it??
Well I'm glad you dochapchap70 wrote:I must be learning a little bit because I can now answer a couple of questions or at least know how to find the answer. That is better than before. I seem to be able to find my way around linux with X now.
No, there is no purpose there. This is a leftover of Puppy/Fatdog's desktop "quirks". Perhaps it is best to remove that "add-to-desktop" right-click menu altogether because it confuses people.When I tried this, I too expected an icon to appear right on my desktop so I can click on it just like all my other desktop icons. I found that right clicking these puts an icon in /root/desktop where you can drag the icon to the actual desktop. I don't see the purpose of this except it might be helpful for people who don't know to look for desktop icons in /usr/share/applications.Snail wrote:Right-clicking an item in the menu pops up a button labled "Add to Desktop". This is a great feature but unfortunately, it does nothing as far as I can see. Except that, after clicking the button, it vanishes and then left-clicking the desktop no longer banishes the menu. Only after the main menu is moused-over will such clicking make the menu disappear.
I will have to test this and get back to you.I discovered an annoying glitch with Osmo. It appears that Osmo does not save anything that you enter into notes until it is closed down completely. If you shut down Fatdog while Osmo is still open, you loose all your changes. It would appear that whatever mechanism the OS uses to clean up open applications during shutdown isn't as "good" as shutting down using Osmo's own methods.
If you run it with "Enable systray" ticked under options/general, which is the default, it is most likely that Osmo will still be running unseen in the background and a shutdown will therefore hose your data. Running it that way is therefore inadvisable and it is a pity that it is the default.
Osmo not saving on the fly seems weird to me, especially for an app that is designed to go to the tray by default. Fatdog's closing down mechanism is also not idiot proof enough for this idiot it would seem.
I assume by now you already find out how to do that? Right click on the panel, choose Panel settings, go to "panel applet" tabs, highlight the Digital clock, then click Edit.Running Osmo off the clock is what other Puppies do and seems a good idea to me. The Digital default is a crappy little calender display. The Fatdog developers substitute Clockset, but this is a wasteful use of systray space for a relatively rarely used app. It would be nice to have it available on right click though but I have no idea how to do that.
That's how Fatdog desktop works. You will just need to learn its quirks and behaviours (every operating system has one). Until we replace ROX-Filer as the desktop, this will be the norm.I wonder if the Desktop folder is work in progress? One would hope that clicking the button might finish the job of posting to the desktop.
It's not possible to make an error when dragging an icon from /usr/share/applications to the desktop. Where I went wrong was in trying to remove an icon from the desktop using the "Send to trash" right click option, rather than "Remove item(s)". I had to ignore a warning to do that - idiot.
The good thing is - if you make mistake, just reboot without savefile and everything will come back to normal. If you accidentally delete system stuff, copy them again - they are always available from /aufs/pup_ro.
Right click on the terminal icon, choose "application launchbar settings", and modify to your heart's contentI agree the documentation could be better. But I don't think creating a menu item for every single function is a good idea.chapchap70 wrote:I found it by poking around. Clicking the Home icon on the top left opens the /root directory. I clicked on the Startup directory and read the Readme. I also remembered that there is a Desktop directory when right clicking the dropdown menu to send an icon to desktop didn't seem to do anything. I opened the directory and the icon I sent to Desktop was there.Snail wrote:At least the /root/startup folder method is better than having to edit some script. It would be nice if there was a menu item sending you there. How did you find it chapchap?
Yes, the same, so don't do that.gcmartin wrote:A question for clarification
When connecting a removable device where the files are stored on a Memory device versus a rotating drive/device, is there a potential that if it is mounted and disconnected without a umount, for file-level destruction? Is that potential the same as a rotating device?
A phone should not refuse to boot when its end-user storage device is corrupted. That's a reflection of poor design.I ask because I saw this thread. I think I understand the issues with a rotating device with head-movements as its being yanked, but wonder about a memory storage device (xPhone) like the one described.
That sometimes happens to me too. It's a problem with Rox. You can usually fix the problem by deleting a folder called "/root/.config/rox.sourceforge.net" and then restart the X server.Was a bit surprised to find that neither .txt nor .html files had run actions associated with them, other than "$@". It's like that when booted up without a savefile, yet in that case both types open perfectly well in Geany or SeaMonkey, as appropriate!
The only reason that I noticed this was that using my savefile, at some time, this stopped working and clicking on a file icon in Rox didn't do anything. It certainly didn't happen after I first made a savefile, so it's something I've done but I can't think of anything I've done remotely likely to cause this. I fixed it by entering defaulttexteditor and defaultbrowser to the run actions.
Weirder still .PDF files continue to open just fine, even though they have only "$@" as a run action.
I have checked the effect of reverting to "$@" as the run action for .txt files. The files will no longer open until I re-add defaulttexteditor in the run action.
And in fact we are grateful for your testing and reports. We'll fix what we can, and in the long run it will help others too. But don't expect that every single thing will be fixed, for many different reasons.I seem to be a perfect tester. If it can be broken, I'll break it.
Why are half the icons in the bottom panels not showing in the Panel preferences edit box? See screenshot. How would I remove the Terminal icon from the Application Launch Bar, for instance, when I can't see it?
Is there any way to edit the icons, as the ones in the Application Launch Bar look rather dull? Better yet, can someone point me to where I can read up on this?