Xorg auto configures itself and the default keyboard is "US" and the default timezone is gmt -5. You can change these in the setup menu. The old xorgwizard is still there, renamed xorgwizard-old. If you want a detailed xorg.conf go to Menu - Setup - Xorg Video Wizard.
Firefox (and Xine) runs as user spot, anything you download goes into the Downloads folder on the desktop. At the first shutdown, after making your save file, you'll be asked if you want to move the Downloads folder to the same place as your save file. Most will want to answer yes to that.
Fatdog64-500 uses many scripts from Woof, but Fatdog64 is not built using Woof due to Fatdog being 64bit.

OK I did not read this but on my system
it went into /root/spot/Downloads

Yes the folder on the desktop points to there. At first shutdown you are asked if you want to move that to the same location as your save file. One thing though, if you already have a folder named "Downloads" in the same location as your save file, it doesn't get linked correctly, so move/rename/delete it before shutting down the first time.

Quote:

Had to ensure I cleared all old remnants of previous fatdog64.sfs
from my hard drive - this is a known necessity.

Yes, I should have mentioned that!

Also, Jamesbond has found a couple ways of making Skype work in Fatdog64.

Great work, the speed and stability is amazing. Auto-configuration was flawless.

One serious problem though. Alsaconf finds the hda-intel Intel Corporation 82801JI (ICHIO Family) HD Audio Controller and appears to set it up properly, however no sound. Clicking on AlsaMixer just gets a flicker. Clicking on it's desktop icon cause the screen to go to black. The menu bar is available and a restartX restores the desktop.

Try to run alsamixer directly in terminal, and let us know what you see. How to do this - open terminal, then in terminal just type "alsamixer".
Also, from terminal, can you please tell me what's the content of /proc/asound/cards and /proc/asound/modules?
If possible, please also create a gzipped copy of dmesg (open terminal, and then type

Code:

dmesg | gzip - -9f > dmesg.gz

then upload it here.

Lob,
Let me know if the openshot works for you. If it does, I'm probably going to remove that pet and replace it with an SFS instead._________________Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread.

Try to run alsamixer directly in terminal, and let us know what you see. How to do this - open terminal, then in terminal just type "alsamixer".
Also, from terminal, can you please tell me what's the content of /proc/asound/cards and /proc/asound/modules?
If possible, please also create a gzipped copy of dmesg (open terminal, and then type

Code:

dmesg | gzip - -9f > dmesg.gz

then upload it here.

Thanks, jamesbond, when I started following your instructions above, my first command was alsamixer which resulted in no file found. /proc/asound/modules empty /proc/asound/cards --- no soundcards ---
I next executed the Alsamixer-sound-mixer.desktop which deleted the icons and gave me a black screen with the menu bar. Then I rebooted, and tried again.

After the reboot, Alsamixer came up properly when executed from a console, so I tried a test file and the sound is working perfectly now. Sorry, I should have done more testing before I reported it as a problem. Hopefully, it will continue to work after additional reboots.

There is no speaker icon on the menu bar and the Alsamixer-sound-mixer.desktop now starts AlsaMixer, but continues to provide a black screen and erases all icons, menu is operational and restartX restores the desktop. The exec line in the desktop file is unusual in that it uses Exec=xterm -e alsamixer instead of just alsamixer, maybe that's the reason for the black screen.

You and Kirk have really done a fine job with this distribution.
Again kudos,
Jim

No worries Jim. I got the idea from Jemimah, who did puppeee. She included the most amazing stuff in it, and I like so much, so I think - I also want this in my bigger laptop

FBReader needs liblinebreak (which is also on the repo) - get it and it will work. Apparently the dependency-checking doesn't work, otherwise it should have prompted you to download liblinebreak automatically.

Yeah the go-oo is a bit rough, it's just a direct extraction of the *.deb files and conversion to SFS. I'll make the icons and menu entries and then re-upload.

jre is java - is missing the plugins. See the post I gave to lobster to make sure java works from Firefox. I'll fix it up later as well.

p7zip is a dependency for xarchiver, it will make xarchiver able to open 7z-compressed files. You can access it from terminal by running "7z"

As per alsa - I'm happy that it works. Google told me your ICHIO chipset is actually supported in alsa version 1.0.22.1 - which is the version used in FD64 now (previous versions used 1.0.21). The ubuntu folks had some problems as well, which was resolved when they upgraded to 1.0.22.1. Your motherboard must be very nice.

As for the blank screen and lxpanel dying, let me guess - you choose Setup/ALSA Sound Wizard, did you? Because AlsaMIxer is actually available in Multimedia/AlsaMixer, and that is working fine (it doesn't kill lxpanel). That xterm -e alsamixer is fine - it's just telling the window manager that we need to run alsamixer in a terminal.

On the other hand, running ALSA Sound Wizard did the same thing to me - it kills the lxpanel, because it is supposed to do that - to kill any process that is using sound. In this case, the panel is using volume control, so it gets killed.

It's unfortunate really, ALSA Wizard is next to useless these days. Most ALSA features are auto-configured. It is only useful for legacy devices. So I think we should put a large warning dialog - if sound works, do not run it at all.

FBReader needs liblinebreak (which is also on the repo) - get it and it will work. Apparently the dependency-checking doesn't work, otherwise it should have prompted you to download liblinebreak automatically.

Actually fbreader-0.12.10-amd64.pet was used, I wasn't aware that the dependencies are checked automatically for pets. I tried to run it in a console where I discovered the missing dependency and just copied over the necessary file from Kubuntu64.

As for the blank screen and lxpanel dying, let me guess - you choose Setup/ALSA Sound Wizard, did you? Because AlsaMIxer is actually available in Multimedia/AlsaMixer, and that is working fine (it doesn't kill lxpanel). That xterm -e alsamixer is fine - it's just telling the window manager that we need to run alsamixer in a terminal.

It's unfortunate really, ALSA Wizard is next to useless these days. Most ALSA features are auto-configured. It is only useful for legacy devices. So I think we should put a large warning dialog - if sound works, do not run it at all.

I did use the Setup/ALSA Sound Wizard before I tried playing any sound. I tried again with no save file and found that sound is configured automatically. So running the Alsaconf is what messed up my sound.

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