Puppy Linux Discussion Forum

[mouldy]

Bionicpup on desktop was getting bit crashy, so did fresh install, this time of dpupbuster64.

Installed wine64-5.0-rc1_v5.0-rc6.pet and it actually went pretty smooth for a wine installation. I just couldnt get portable wine I had been using to work in dpupbuster64.

However my main reason to install wine is to run KindleForPC 1.17, last version Kindle that will work in WINE that I know of. It wont install. Oh everything else works and this maybe first WINE I've used that wine"ie_explorer" will actually surf. Wouldnt recommend using it, but still wasnt all crashy with errors galore like in past.

Anyway when trying to install KindleForPC117, I get this:

[mouldy]

I would still be curious how to make it work. But its a mute point.

I finally used package manager to install PlayOnLinux. Found instructions to modify it so it will run in root. I let it download and install 32bit WINE 2.2 and KindleForPC117. Kindle now works though GoldenBird doesnt. But Kindle is the important app for me. Why they make it so hard to install 32bit WINE on 64bit system is beyond me. It should just come as part of the 64bit version cause most people use WINE to run older 32bit apps I think. Least I do.

UPDATE: Been playing more with PlayOnLinux. As annoying as it can be, it has some real virtues. I found I could choose to custom install a win app, but then choose version WINE I want to use. So I told it to use 32bit WINE 5.3. It downloaded and installed 5.3, I then directed it to my copy of windows programs and installed new instance of both Kindle 117 and GoldenBird. Both worked. I tried later version Kindle but it crashed during install. WINE still hasnt caught up enough to run newer versions.

PlayOnLinux takes lot getting used to if you are used to using WINE directly. You are adding a middleman. But there is NO easier way to install WINE, especially 32bit WINE on 64bit system, the version or versions of WINE you want. No idea how well it would work on other Puppies, but well worth trying. Works great on dpupbuster64.

[rockedge]

[jplt3]

Hi all ,

i'am about to be mad !

I want to install DpupBuster CE 64 : dpupbuster64-8.0.0-uefi-RC-2-28122019.iso

on an UEFI cheap machine :

Schneider SCL14
Processor : Intel Atom x5-Z8350
RAM : 2 Go
eMMC : 32 Go

it is a 64bit machine but the bios is a 32bit !!!

So i boot the machine via a usb key with dpupbuster64-8.0.0-uefi-RC-2-28122019 on it,
great it work quiet good .

But now how to install dpupbuster on this machine :

otherwise i have already an ubuntu 18.04 installed on it but it corrupted ! that's why i want a puppy on this machine

the harddrive :

[mikeslr]

@ jplt3,

Thought your problem looked familiar. See this thread, http://www.murga-linux.com/puppy/viewtopic.php?p=1050343#1050343

[mouldy]

Two or three years ago I bought a used Lenovo Ideapad 100s with the atom processor capable of 64bit and the 32bit bios. Cheap cause it had a hosed 32bit install of win10 on it and wouldnt run the built in win10 restore.

No problem booting linux from usb drive. I even installed some Puppy on eMMC and got it to boot. It wasnt easy, but then Puppy acted like it was running on dying hard drive, couldnt access some files, etc. Really acted wonky. I figured eMMC was dying. But I got hold of a 32bit copy win10 home (what it came with from factory so auto activated) and installed it from thumb drive via Rufus. It worked. Definitely designed for windows. Bios was UEFI only, no legacy option available.

Now also had a cheap Acer Aspire One Cloudbook. Similar but had Celeron processor and 64bit bios that did have legacy option. No problem booting and running I think Xenialpup on it with legacy option. Win10 on it would continuously lose driver for trackpad and keyboard. No idea why but it was PITA. Puppy worked with no hassles though did have to set trackpad in bios to basic. Since I had that option wasnt going to beat my head against wall setting up UEFI install Puppy. So its not really an eMMC kernel problem I think as the Acer definitely had same stupid soldered in place 32GB eMMC.

As experiment try installing Lubuntu 19.04 or whatever latest version is, see how it handles things. Lubuntu has an installer that deals with UEFI and it has apt-get which makes life whole lot easier to install stuff when experimenting.

EDIT: Oh didnt notice you have Ubuntu 18.04 on it. How well does that work?

[jplt3]

@mikeslr thanks for the link i will read this
@mouldy i think that i will install lubuntu even more lighter than xubuntu and then will try to make install puppy works ... will see

[foxpup]

[jplt3]

Why on DpupBuster CE 64 , because on bionipu64.8.0 i don't have this problem :

in firefox esr in dpupbuster sound work good but when launch my firefox 74.0 64bits NO SOUND ! :

[rcrsn51]

Open a terminal and run: alsamixer

This should open your default audio device. Does it look OK?

[jplt3]

I think so

[rcrsn51]

I have a machine with ALC269VC audio (almost like yours).

I ran the Buster Starter Kit with the latest Firefox v74 and apulse.

Audio worked fine. So I don't know why your situation would be different.

We appear to have the same version of ALSA.

[jplt3]

@rcrsn51

I resolve my problem :

i have a portable firefox profile :

[lvds]

Hi everyone,

I have hard time at installing the latest teamviewer in Dpup 64 8.00 XFCE, it seems to me I tried all the alternatives (apt, .deb or pet package, etc...) but teamviewer always crash and refuse to load. Maybe I messed up something in my setup.

Please, can someone help me and post a step by step "how to" install the latest teamviewer and have it run fine ? This tool is critical to have with the current corona covid-19 crisis and is an absolute need. Many thanks in advance for any help you can provide

Kind regards,
Laurent.

[rcrsn51]

The new versions of TeamViewer are designed to work in a full Linux like Ubuntu or Mint. They may be your best choice.

In particular, TV needs systemd and a login manager.

But I can get TeamViewer15 to work in the Stretch-Live Starter Kit using the instructions here (but not Buster).