Fatdog64-720 and 721 Final [11 Jan 2018]

Message

proebler · #301 Post by **proebler** » Tue 31 Jul 2018, 11:14

Anniekin wrote: anybody know the menu.lst entry to boot windows 10 off the first partition (0,0) ?

The attached Grub4Dos menu.lst works without any issues for me.
Win10, grldr and menu.lst are all on ntfs partition sda1 (hd0,0)

Anniekin · #302 Post by **Anniekin** » Mon 06 Aug 2018, 04:59

Grub4Dos is working now... I don't know why it was crashing the system when I booted from USB? Thanks!

dcung · #303 Post by **dcung** » Mon 06 Aug 2018, 08:29

Hi,

I'm looking for VLC player 3.0.3
I downloaded vlc-curses-3.0.3-x86_64-1.txz from the repo and installed it.
Got errors, missing some files (see attached).

I can't find it in repo nor thru Gslapt.
Any idea how to resolve that pls?

Thanks.

EDIT: <RESOLVED> Thanks.

dcung · #304 Post by **dcung** » Mon 06 Aug 2018, 09:51

Someone pointed out that I downloaded from wrong section of repo...

http://murga-linux.com/puppy/viewtopic.php?p=1001356

dcung · #305 Post by **dcung** » Tue 07 Aug 2018, 09:27

Chrome & Seamonkey OK, but Firefox - No sound. FATDOG64

http://www.murga-linux.com/puppy/viewto ... ?p=1001434

EDIT:
Solved.

dcung · #306 Post by **dcung** » Wed 08 Aug 2018, 10:03

A little background
http://murga-linux.com/puppy/viewtopic.php?p=1001494
Laptop Dell Latitude D630, Intel Core2Duo@2.20GHz, 2GB RAM, 60GB SSD.

I'm working to get wine working.
Following step's guidance to troubleshoot the problem. (TIA step)
I deleted savefile/savedir and start Fatdog64 from scratch.

Test following with no savefile, on each attempt.
Loaded wine SFS from /sda1/root (where SFSManager put by defautl), not working
Rebooted, Loaded wine SFS from 'home', and not working.
I have few frugal puppy (including Fatdog64) installed on the laptop (see screenshots).

Anyone can see what I did wrong?

Thank you.

mikeslr · #307 Post by **mikeslr** » Wed 08 Aug 2018, 12:13

Hi dcung,

I haven't used FatDog for a while. But AFAIR, being a 64-bit operating system getting wine applications to run under it requires the same steps as under any other Puppies.

Although a 64-bit version of wine is available from the Additional Software>Virtualization Section, it only works with 64-bit Windows applications of which there are few built for XP. WinAmp isn't among them. So, generally one needs a 32-bit Wine package.

But to run the 32-bit wine package under a 64-bit system, you first have to install or load a 32-bit compatibility layer. FatDog64 has one as an SFS. So download it and then SFS-load it. After loading it, you have to configure FatDog to use it:

Open a terminal and type, code "ldconfig" -- the first symbol is a small "EL", not a 1/one, nor a capital I/eye. It should take a couple of seconds to write the necessary connections. If the command prompt becomes available immediately somethings gone wrong, so enter the code again. Doing so can't hurt even if you did it right the first time. Using a Frugal install, remember to SAVE.

To test that the compatibility layer is working --before messing with wine-- I run some small application which doesn't need it. For example, download opera 12.16.tar.gz from opera's "Old versions", unpack it on /mnt/home and left-click the opera script.

With the 32-bit compatibility layer working, its time to obtain a wine package. IIRC, FatDog has it's own so that's probably the safest choice*. Again, IIRC, it's an SFS you download, and load. Then you have to configure it: Open a terminal and type, code "winecfg". Again, the terminal prompt should not become available immediately -- takes a second or two for the necessary files to be written. And remember to SAVE.

I don't know if FatDog's Wine includes menu entries. See this post: http://murga-linux.com/puppy/viewtopic. ... 255#882255

After wine is working, you should be able to just Left-Click a Windows setup file to install it into wine's false-c: drive except if the Windows application is a "portable". Portables can be run from anywhere EXCEPT c:drive. I create a folder on /mnt/home which I name something line "xp-apps" and into which I install portables. I bookmark the folder in rox for easy access.

mikesLr

* Generally, Wine is "agnostic" -- in that any version should be able to run under any Puppy (with 32-bit compatibilty layer present if the Puppy is 64-bit) But if you plan on using a lot of XP programs, or ones which take up a lot of space, you may want to consider portable-wine. It will reside on /mnt/home so programs installed don't take up space in your SaveFile/Folder. Unlike Mike Walsh's experience, I've found that the latest version runs any program (if it could run under wine at all) under any Puppy. You'll find the latest version here: http://murga-linux.com/puppy/viewtopic. ... 245#989245. But read from the beginning of that thread to understand its differences from other versions of wine, but especially the first page and from here:http://murga-linux.com/puppy/viewtopic. ... 452#971452.

step · #308 Post by **step** » Wed 08 Aug 2018, 13:13

How come your pictures show geany 1.27 when Fatdog64-721 has geany 1.32? Which Fatdog64 version is running?

The SFS Loader picture shows the path /aufs/pup_rw/root/wine-2.0.sfs. That's a strange (and troublesome in that context) path. It should be /root/wine-2.0.sfs. How did you get /aufs/pup_rw there in the first place?

To fix: move the path to the left column, tick the option to change the SFS directory, Apply, change directory to /root, move the path to the right column. It should be /root/wine-2.0.sfs.

Any objection to trying a more recent version of wine?

When you're ready to run winamp with wine, do it from a terminal window and show us the output you get, if any, error messages and all.

*** As mikeslr correctly pointed out, you should also load the 32-bit compatibility SFS. That's 32bit-fd64_721 in the SFS Manager download list.

Do not follow mikeslr's download pointers (certainly given in good faith). That's not how wine works for Fatdog64. Stay inside SFS Manager until you get winamp working.

As regards your question about VLC 3.0.3 - where did you download the txz package file? The latest version available from the Fatdog64 repositories on ibiblio is 2.2.6. You can install it with Gslapt, the Fatdog64 package manager.

step · #309 Post by **step** » Wed 08 Aug 2018, 13:24

One more thing, the psubdir boot code in your picture works for Puppy but it's meaningless for Fatdog. You can read about Fatdog boot codes in the help file right on your Fatdog desktop.

Read topics "Boot options",
also "Additional Software Packages",
also many others

dcung · #310 Post by **dcung** » Wed 08 Aug 2018, 19:09

step wrote:How come your pictures show geany 1.27 when Fatdog64-721 has geany 1.32? Which Fatdog64 version is running?

Good eyes!

I mentioned that I have multiple puppies on the laptop. I booted to XenPup to delete Fatdog64 savefile/savedir, so you saw geany from XenPup. I'm using Fatdog64-721.

step wrote:The SFS Loader picture shows the path /aufs/pup_rw/root/wine-2.0.sfs. That's a strange (and troublesome in that context) path. It should be /root/wine-2.0.sfs. How did you get /aufs/pup_rw there in the first place?

The SFS is on root of sda1. Didn't work.
2nd try - Rebooted with no savefile, copy SFS to 'home' (clicking home icon in Roxy), load SFS from there - Didn't work.

step wrote:To fix: move the path to the left column, tick the option to change the SFS directory, Apply, change directory to /root, move the path to the right column. It should be /root/wine-2.0.sfs.

Did that already - Didn't work.

step wrote:Any objection to trying a more recent version of wine?

Nope - no objection. I actually did all above with v2 and v3 SFS from SFSManager.
Just didn't post screenshots for both since they're the same outcome other than v2 vs v3 filename.
And I started from 'scratch' each time. Reboot, No savefile.

step wrote:When you're ready to run winamp with wine, do it from a terminal window and show us the output you get, if any, error messages and all.

You probably missed it. Already up there in the screenshot.

step wrote:*** As mikeslr correctly pointed out, you should also load the 32-bit compatibility SFS. That's 32bit-fd64_721 in the SFS Manager download list.

Did that already too. When I read his (actually both mikeslr & Mike W mentioned this) post then, I retried.

step wrote:As regards your question about VLC 3.0.3 - where did you download the txz package file? The latest version available from the Fatdog64 repositories on ibiblio is 2.2.6. You can install it with Gslapt, the Fatdog64 package manager.

You probably missed my next post (following that). That issue was 'resolved'.
.
.

dcung · #311 Post by **dcung** » Wed 08 Aug 2018, 19:13

step wrote:One more thing, the psubdir boot code in your picture works for Puppy but it's meaningless for Fatdog.

That was Grub4Dos menu (auto generated) being 'smart'.
I didn't mind it then. Maybe I'll delete that to see if it makes any difference.

dcung · #312 Post by **dcung** » Wed 08 Aug 2018, 19:24

dcung · #313 Post by **dcung** » Wed 08 Aug 2018, 22:19

@mikeslr, Mike Walsh & Step
Thank you all for your assistance. I really appreciate that

I formatted the disk, re-installed Fatdog64-721 from fresh iso.
Wine is working now...yay!

Must have stuffed something up in my tinkering before

Off to do more reading and tinkering now.
Hopefully you guys don't get tired seeing my posts.

dcung · #314 Post by **dcung** » Thu 09 Aug 2018, 05:00

I have question about multi monitor, not sure if I should posted here.
Somewhat Fatdog64 related (?)

http://murga-linux.com/puppy/viewtopic.php?p=1001630

step · #315 Post by **step** » Thu 09 Aug 2018, 20:26

dcung wrote:
step wrote:When you're ready to run winamp with wine, do it from a terminal window and show us the output you get, if any, error messages and all.
You probably missed it. Already up there in the screenshot.

dcung wrote: @mikeslr, Mike Walsh & Step

I formatted the disk, re-installed Fatdog64-721 from fresh iso.
Wine is working now...yay!
Must have stuffed something up in my tinkering before

I'm glad you got it working!
Indeed I had missed the terminal output in your screen capture. Now that I've seen it I can try to guess what was going on.
The message
... linux32: /opt/wine-2.0/bin/wine: no such file or directory
means that Fatdog64 can't run /opt/wine-2.0/bin/wine. Well, literally it means that the file isn't there, but I've seen that message happen before when an SFS is loaded but an existing symlink in the save folder "masks off" a path loaded from the SFS, in this case /opt/wine-2.0/bin/wine, or one of its parent components. Hard to say at this point after reinstalling the system, but I suspect your tinkering before had planted an innocent-looking symlink in the save folder, which masked off the wine executable path.

I admire your persistence in getting this issue resolved. Enjoy your music collection with winamp!

dcung · #316 Post by **dcung** » Sun 12 Aug 2018, 21:34

Hi all,

Looking to install PIA vpn.
I don't think this is Fatdog64 specific issue, but I'm installing it on Fatdog64.

http://murga-linux.com/puppy/viewtopic.php?p=1001913

jake29 · #317 Post by **jake29** » Thu 16 Aug 2018, 17:37

Anniekin wrote:anybody got a blue light filter working for fatdog?

I use Redshift (available via Gslapt) (Automatic Startup tutorial) without issue in Fatdog64-721.

Anniekin · #318 Post by **Anniekin** » Fri 17 Aug 2018, 03:06

Thanks, I didn't think there would be one in gslapt already, nice!

rufwoof · #319 Post by **rufwoof** » Tue 21 Aug 2018, 17:08

Burned FD 721 to a DVD-R and using that to save changes (multi-session LiveCD). Working well on my Acer Aspire Phenom X4 2GB with onboard Radeon ATI. Event Manager RAM save interval was set to 0 so to only save when the desktop Save icon is clicked and after several saves and reboots everything I've used so far has all worked well. Only thing I've added is xterm (native, as I prefer that over urxvt).

The boot message does say that it should be a +RW DVD, as I understand it +RW would enable the same DVD to be reused i.e. once its filled up, use pburn or whatever to clear the DVD and then re-write the FD 720 ISO image to that, and then click the desktop Save icon to save the latest snapshot/changes to that, but I'm happy to reuse another -R (in having a bundle of them laying around) that are write once only, but was wondering whether I shouldn't be using a DVD-R at all given the boot message? EDIT: I was confusing drive and disc here. RW drive is needed (in order to burn etc.), a DVD-R disc however works for saving multi-sessions (a rewriteable disc can be re-burnt freshly, DVD-R is write once only, cannot be erased).

Also, in Puppy multisession you can use something like pfix=1 to ignore the last saved session (or pfix=2 to ignore the last 2 sessions ...etc), but having looked through the FD documentation for boot parameters I see no such equivalent for FD?

Another question/observation - as multisession LiveCD is the least easily edited for boot parameters, would it not make more sense to have that as the default boot case. All other boot choices can more easily change that default choice (by editing grub.cfg or isolinux.cfg ??) being on rw media? As-is I have set BIOS to boot CD as the first choice, but then have to wait for BIOS mem checks ..etc. (a while) before the FD boot menu pops up and then arrow down to the multisession boot choice, otherwise it defaults to standard boot default choice ... and then wait for all the rows of dots as ram is loaded. If multisession was the default choice then I could do my more usual action of just pressing the power-on button and going off to make a brew and return with the desktop ready to go. I appreciate that multi-session is a less used choice, however its relatively trivial for the other boot choices to change that whereas that's not the case for multisession LiveCD.

EDIT: The way I addressed it was to update gslapt and install isomaster (surprised that isn't in the base FD system as its pretty small/light - but very useful), using isomaster open the FD iso and edit the isolinux.cfg/grub.cfg to set fatdog-multi as the default boot choice. Save that edited version and burn it to DVD, and then click the desktop 'save session' icon to save all changes to that newly burnt DVD. Now, in having CD/DVD set as my first boot choice in BIOS, pressing the power-on with the FD DVD inserted has it boot straight to desktop (multi-session LiveCD boot) without any other intervention being required (and presumably the same if there's a power-cut/restore).

rufwoof · #320 Post by **rufwoof** » Tue 21 Aug 2018, 20:28

Pup ad blocker is a nice touch IMO. Couldn't find one in FD so I appended https://github.com/StevenBlack/hosts to my /etc/hosts .. pretty much as good as ad-block.

Also added a xrdb -merge $HOME/.Xdefaults ... command to .xinitrc if a users home folder contains .Xdefaults (I like to use xterm (native) and have a .Xdefaults file content that makes that look/work nicely).

Changed the default # prompt in /etc/shinit to something nicer

I've backed up a copy of the fatdog iso to DVD, and with quite a few saves already having been made, up to around 873MB of the 4.7GB of DVD disk space having been used.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Fatdog64-720 and 721 Final [11 Jan 2018]