The new qemu v2.0 sfs and pet didn't work in Fatdog64-630.
When sfs is loaded all system fonts change to square blocks had hard time unloading the sfs. Problem went away when after unloading.

That's because the SFS keeps keeps stuff in /usr/etc instead of /etc.

So a couple of links could fix, I wonder.
Anyway, I've just compiled again (in Fatdog64 and correcting paths) 2.0.0. It works for LHP, too. I've tested both.
Please, note that this one will be, probably, my last effort in QEMU support for Puppy, because my hardware is going dated (I cannot use QEMU anymore since last versions, I can only make a very slow X-test after compiling). So, all my last packages were a gift for community, not usable by me.
I'm going to upload, on my repo, new packages (SFS and PET) in the next hours. Check availability in this thread, monitor for updates: http://murga-linux.com/puppy/viewtopic.php?t=88604.
For those of you that have still downloaded old SFS, to avoid mistakes, this is md5 checksum of the new one: ffe06d0edb37de3edf4797463053875b.

jamesbond wrote:

Whitesnow wrote:

Fatdog64 is based on Ubuntu

Fatdog64 is based on T2-build, similar to Puppy Wary/Racy (but 64-bit while Racy/Wary is 32-bit), not Slackware or Ubuntu.

I remembered that someone talked about what I wrote (I read that), maybe because, in the past, Fatdog64 wasn't build in pure T2 like it is now.

jamesbond wrote:

Whitesnow wrote:

I compiled QEMU for LHP 64 bit, that is based on Slackware binaries

LHP64 is a derivative of Fatdog64, with a lot of additional programs and libraries (and polish!) on top of Fatdog base. It is *not* based on Slackware. The problem is exactly that - LHP64 has many additional libs that Fatdog doesn't have.

Let me say what I read, one more time. LHP64 is, nowadays, based on Fatdog64 kernel (thank to you and Kirk), but core packages are from Slackware (glibc, gtk, cups, xorg-server and dependencies). This condition is relevant in our topic, as my old QEMU package compiled in LHP, as I just tested, can't run in Fatdog64 not only for lack of libraries, but for dissimilarity of glibc version, too.

Whitesnow, I can only say thank you for your service to the community here. My previous post was meant as a clarification for everyone concerned - not to discourage you at all.

I don't understand, though, why qemu 2.0 is giving you problem? I haven't tried it myself (I'm still on 1.6.2 - don't see the need to upgrade) but as far as I know if you don't enable kvm then it should work even on older machines without hardware VT-assist; and qemu is well known to have decent speed even without acceleration._________________Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread

Version 2.0 PET from @WhiteSnow works in Slacko64, FD630 and LH64-602b. The steps tested for each distro were the approaches shown in the Guide.

Simple to use
To use QEMU V2+, instead of the older PPM versions to gain QEMU on your system (shown in the Guide), advance to the bottom of the Guide, select and download QEMU V2, and install.

Also, note, that current versions of, both, QEMU by Puppy member @WhiteSnow and QEMU Launcher by Puppy member @MikeB can be obtained by the links in the Guide.

Here to help_________________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

Update 1_________________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

Update 1: The guide contains tested procedure for sharing content that the "Host" distro has with a distro running in the "Guest".

Thanks. The guide seems to imply that one can use FatDog64 to connect a share via the SAMBA server subsystem. It includes a picture of a desktop menu selection of Network>Samba Simple Management. I can't find such a tool in FatDog64-631. Is it an additional pet for FatDog?_________________FatDog64 631|Blue Pup 4|DebianDog+OpenMediaVault stick

... I can't find such a tool in FatDog64-631. Is it an additional pet for FatDog?

That tool, shown in the Guide, is one that is included in all Slacko64 and LightHouse64. It was developed by 01Micko 4 years ago to make life so very simple for Puppy Linux users to understand and share a folder with its LAN community of users. Thus Slacko and LightHouse64 users have it so easy with almost little thought to do this sharing from its desktop.

FATDOG64 is a bit behind the times as it uses an older SAMBA and it does NOT approach users the same way. FATDOG also has not adopted 01Micko's simple solution at this time.

But, I think, I can help. Do this and report what you see.

Open a terminal on FATDOG

Paste the results on this command to this thread

Code:

bash-4.1# smbclient -U% -L localhost

Someone will respond

UPDATE
I will make changes in the Guide for FATDOG in a pristine state. Your answer for FATDOG sharing is here.

Here to help_________________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 am posting this as a warning to others not to make the same mistake as I did which resulted in initial failure.
There is nothing wrong with gcmartin’s excellent guide but it needs to be followed exactly. The bash test in the guide which should indicate vmx or svm was passed and having a recent PC, I falsely assumed that KVM would be enabled in the BIOS. It was not and that test merely shows “capability”. I have no idea why it should be disabled by default on a new PC.
The attached screenshot shows it now enabled. Please note also that Intel refer to it as “Vanderpool Technology”.

In looking over the thread, I think this post may have been missed. I will attempt to help.

slavvo67 wrote:

I read between the lines and note you mentioned 64bit. Does this mean a 32 bit will not have this ability? I'm still leaning towards the 32 bit pups ...

The Guide was built and tested with the 64bit PUP distros shown. Once one of those PUPs is setup using the procedures in the Guide, the PUP will allow anyone to boot "any" x86 distro's ISO you might have...ANY.

slavvo67 wrote:

... Considering that I have a hundred or so cd's burned, this might be a nice alternative and certainly a more environmentally friendly one.

Correct. This means that you can use a single 64bit PC to run several virtual PCs at the same time. This is great for additional booting a test ISO or booting one for a special mission like banking or like a TOR or ... or ... or ...

This is easy and simple to do.

Hope this is helpful

P.S. The Guide was created using 64bit PUP PCs because most every non-ATOM PC, even some ATOMs, too, has adequate resources for a successful KVM venture with no trouble. There are 32bits which carry the KVM feature, but I leave that for user evaluation and testing. Thus, the intent is to provide a Guide with the greatest opportunity for user success and NO frustrations._________________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

Important Note:EmSeeV2 isthe very first (1st)32bit PUPPY distro that come with EVERYTHING preinstalled (OOTB) to immediately boot other distros, once on the EmSeeV2 desktop.

A tremendous speed increase is made available, primarily, thru the inclusion of the kernel's KVM module that some/many PC CPUs have from the factory.

There is an issue with hostname. FirstRUN is the simplest and best that resolves the problem without taking other steps and having to reboot EmSeeV2. Care must be taken should you want to ALSO run a 2nd EmSeeV2 as a VMguest while also running EmSeeV2 as the main system (VM host); or if you want to run several VMguests on an internal (to VM host) network with the VMguests LAN linked to each other.

Take it for a spin. I will bring an updated User Guide showing a one step boot a distro via the EmSeeV2 Menu, soon.

Here to help_________________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 DogPileEdited_time_total

On the desktop bottom right corner click setup > gui opens next click internet , another gui opens.... on the bottom right of that gui is the hostname, type any hostname in the field and click the big green tick! There hostname resolved!

Thanks @StemSee. I posted on the EmSee thread to show a bug in EmSeeV2 hostname processing. But, for all VMguests a user boots which has FirstRUN, this hostname issue does not exist in the system's fields or in the LAN announcements to set pathways by name.

The QEMU features do indeed work on this 32bit distro._________________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

And
A Puppy forum member, @Gobbi, explains here, how to assign a set of PC resources for use in a Guest virtual machine.

This is one additional solution on how to have 2 PUPs running off of one PC...protected from each other.

This allows a PC which has 2 video monitors, 2 keyboards, 2 mice, and optionally 2 sound cards to run separately on the same PC.

He explains how to assign those resources so that the 2nd distro boots using them, exclusively. Thus one person can have 2 systems on his physical desk running off one PC; or 2 people can individually, independently run, all the while on a single PC.

Here to help_________________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