Just to let you know. Testing pgprs-2.0.4-beta.pet. Currently I'm online and posting with FossaPup64 and pgprs-2.0.4-beta.pet installed. Though, I'm running FossaPup64 with Kernel 5.0.21-rt15. Using the original kernel of FossaPup64 the modem is not detected. Ok, this is the info from my own Bionic...

Currently I'm online and posting with FossaPup64 and pgprs-2.0.4-beta.pet installed. Though, I'm running FossaPup64 with Kernel 5.0.21-rt15. Using the original kernel of FossaPup64 the modem is not detected. Thank you very much for testing pgprs. That is very good news that pgprs can work, if the d...

I have uploaded version 2.0.4-beta which changes the connect window to restore the scrolling of the connection log (in Puppies after BionicPup) and to continue to allow the window to be closed without disconnecting. This is intended to become version 2.1 once testers have verified whether the connec...

I notice there is no screen saver in FossaPup64's menu. Is that omission intentional? Or am I looking for the wrong name? I think it is good to let the user have the screen blanked when the computer is not being used, without having to install the package. Or is a screen-blacker no longer important ...

Thanks. But 9.0.3 does not change the misbehavior, as I expected. I mentioned earlier about checking the tail command. It turns out that it seems to work. My "alternate implementation" of the dialog works as expected. Screenshot1: Xdialog --center --wmclass pgprs --title "$(gettext 'P...

I installed 9.0.3 but see that it has a problem, maybe several. The desktop icons do not appear. Only gatotray and a cpu-load monitor appear in the tray, along with the 'menu' and 3 desktop icons. The task bar has the running programs, at expected. Conky displays as expected. Rox-filer does not appe...

Thank you for your help with this issue. None of the Xdialog pets updated the display beyond the first line. Although I don't expect that Xdialog-2.6.5-x86_64.pet will show anything but the first line, it actually did not get that far! It aborted with an exit code of 134. FWIW, here is the trace: + ...

Thanks, peebee. I have swapped Xdialog versions between BionicPup64 and FossaPup64 and find that both versions' updating works in BionicPup64 but not in FossaPup64! So it is not a problem with Xdialog, but with something else in the recent Puppies that impacts Xdialog. This looks messy. EDIT: I see ...

The issue on pgprs in FossaPup appears when it comes to connect. The output in terminal/window hangs after the first line, so no connection. . . . I am working to correct the failure to show the log in the window. While I have been working on an upgrade to pgprs, I have found that the reason for th...

WoofQ has version 2.0.2. /usr/sbin has 'pgprs', and 'pgprs-connect' and 'pgprs-shell' symlinks to it. I see that the 2.0.3 PET doesn't have those symlinks. is that OK? WoofQ doesn't have /usr/share/applications/pgprs-connect.desktop I don't recall how it was invoked in that case. EasyOS and EasyPup...

Thanks, Barry, for your posting. I am re-examining pgprs after several years of assuming it worked, but now am aware of some problems with it. My difficulty with testing it is that I do not have a 3G modem that works in linux, and I do not have a data option for my minimalist cell phone account. So,...

The issue on pgprs in FossaPup appears when it comes to connect. The output in terminal/window hangs after the first line, so no connection. I noticed this after I posted about running pdiag. Instead, please look at /tmp/.gprs_connect.log to see what should have displayed in the "terminal"...

A new version is uploaded to the first message: http://www.murga-linux.com/puppy/viewtopic.php?p=883858#883858 Pgprs-2.03 was submitted to woofCE in July of 2018, but inadvertently did not get added to this thread at that time. It simplifies the detection of modems by avoiding the use of the modem-s...

Testing FossaPup64-9.0.2. Could not connect to the internet unless I installed my locally available pgprs-s57-6.pet. After installation I could do this posting. You have also reported this in the BionicPup64 thread, to which I responded with a request for further information and assistance in my ef...

That firmware has been added, will be in the 2.3-final. You might not want to get into the business of trying to satisfy all users of b43 wifi. There are many variations of the firmware files. The full set is about a megabyte in size. While experimenting with the latest available firmware from gyro...

I have 2 64-bit PCs both of which are about 15 years old. One has a built-in Broadcom BCM4306 wifi device requiring the b43 driver. EasyOS 2.3RC shows the following messages about firmware files the device needs: b43 ssb0:0: Direct firmware load for b43/ pcm5.fw failed with error -2 b43 ssb0:0: Dire...

With 2.3RC on the initial boot-up, the ethernet connection is successful and the icon shows it so. On a reboot the connection was also successful.

Thank you, Barry, for fixing the problem of the initial connection not succeeding.
Richard

I discovered that the Error window was not displaying when an SNS connection attempt failed. Several years ago the definition of the window became corrupted, apparently during an editing session. In addition, I found that the SNS version was not showing in the main window, as I had intended in versi...

Since the beginning I'm using pgprs connect to connect to the web using a 3G modem. In the early days I wrongly thought I would have a gprs modem, but no, it's a 3G modem. Still using pgprs connect. Any other internet connection programs didn't work for me and the 3G modem. Thank you for reporting ...

I discovered that attempting to reconnect with the simple_network_setup network manager, the reconnect would fail because dhcpcd was already running! This was caused by networkdisconnect not stopping SNS correctly. I saw this with my single-core PC but not with the dual-core PC. But the latter was r...