Wary and Racy 5.3 final
Latest WakePup2 .pet file creates floppy and works fine with 4.x Puppies and Wary 5.1.1.
The problem is with Wary 5.1.4.1.
After .pet is installed, floppy cannot be created, as dialog box will not open.
Check dependencies installed pkg shows nothing missing.
Launching from terminal generates error message (see attached).
This might also affect later Wary builds.
I only have Wary 5.1.1 and 5.1.4.1 (and dial-up); that's why I'm referring strictly to those two.
(I'm also curious as to whether this problem affects recent builds of Lucid and Slacko.)
The problem is with Wary 5.1.4.1.
After .pet is installed, floppy cannot be created, as dialog box will not open.
Check dependencies installed pkg shows nothing missing.
Launching from terminal generates error message (see attached).
This might also affect later Wary builds.
I only have Wary 5.1.1 and 5.1.4.1 (and dial-up); that's why I'm referring strictly to those two.
(I'm also curious as to whether this problem affects recent builds of Lucid and Slacko.)
- Attachments
-
- Wakepup2-error.jpg
- From terminal
- (8.85 KiB) Downloaded 1480 times
Dewbie,
That was part of my crusade to get rid of gtkdialog2 awhile ago, so i patched it, actually only took a minute. I can't test as I have no working floppy drives.
NOTE: the image is not present in the pet, if you want the image to do a proper test download wakepup2 first.. either get the one from the link in Dewbie's post or from ibiblio/pet_packages-4
That was part of my crusade to get rid of gtkdialog2 awhile ago, so i patched it, actually only took a minute. I can't test as I have no working floppy drives.
NOTE: the image is not present in the pet, if you want the image to do a proper test download wakepup2 first.. either get the one from the link in Dewbie's post or from ibiblio/pet_packages-4
- Attachments
-
- wakepup2_NOIMAGE-120804.pet
- (1.93 KiB) Downloaded 521 times
Puppy Linux Blog - contact me for access
Thanks for posting, 01micko.
Is the NOIMAGE .pet supposed to be installed with the WakePup2 .pet?
I tested this; makes no difference with Wary 5.1.4.1; same problem.
Again, my concern is that this might also affect later Wary builds.
NOIMAGE .pet also blocks WakePup create boot floppy when tested with Wary 5.1.1 and 4.x Puppy Linux. Without NOIMAGE .pet, everything works OK.
So apparently the gtkdialog / WakePup2 issue started somewhere between 5.1.2 and 5.1.4.1.
Attached is an image of what's supposed to appear when everything is working correctly with a WakePup2 .pet installed.
Is the NOIMAGE .pet supposed to be installed with the WakePup2 .pet?
I tested this; makes no difference with Wary 5.1.4.1; same problem.
Again, my concern is that this might also affect later Wary builds.
NOIMAGE .pet also blocks WakePup create boot floppy when tested with Wary 5.1.1 and 4.x Puppy Linux. Without NOIMAGE .pet, everything works OK.
So apparently the gtkdialog / WakePup2 issue started somewhere between 5.1.2 and 5.1.4.1.
Attached is an image of what's supposed to appear when everything is working correctly with a WakePup2 .pet installed.
- Attachments
-
- Create-wp2.jpg
- (47.48 KiB) Downloaded 1409 times
Last edited by Dewbie on Fri 10 Aug 2012, 08:24, edited 2 times in total.
Yes.Dewbie wrote:Is the NOIMAGE .pet supposed to be installed with the WakePup2 .pet?
Install the NOIMAGE pet second. Maybe those older wary versions don't have gtkdialog4? It requires gtkdialog4 as the older gtkdialog3 has a bug where it can't read from stdout, resolved by moose-on-the-loose I believe. If there is no gtkdialog4 in your wary you can download it and install it from ibiblio or mirrors. I'm pretty sure all wary versions have the prerequisites.
Your screeny looks almost identical to what displays on my desktop. I just can't test the underlying code. ie: writing the image.
- Attachments
-
- capture32552.png
- (37.97 KiB) Downloaded 1778 times
Puppy Linux Blog - contact me for access
I tried 01micko's fix and it writes a boot floppy fine using Wary Puppy 5.3.
I'll take a look at the script and see if it can be modified with an "if exist" branch or something so it works with all versions of Puppy.
/// Edited a few hours later:
Attached is an "A" version of 01micko's pet file. It works with either the older or newer versions of Puppy Linux. It looks for gtkdialog4 and uses that if it exists. Otherwise, it uses gtkdialog2.
/// Edited Aug. 9:
I replaced the "A" version with the attached "C" version (the "B" version didn't work too well).
This version first tries to use gtkdialog2, then gtkdialog4, and then gtkdialog3 as a last resort.
This isn't too hard to do in a ten line program, but would be kind of a pain in a thousand line program.
/// Third edit Aug 15:
I posted a full version of Wakepup 2, using this script and an updated floppy image, at
http://www.murga-linux.com/puppy/viewtopic.php?t=80291
///
I'll take a look at the script and see if it can be modified with an "if exist" branch or something so it works with all versions of Puppy.
/// Edited a few hours later:
Attached is an "A" version of 01micko's pet file. It works with either the older or newer versions of Puppy Linux. It looks for gtkdialog4 and uses that if it exists. Otherwise, it uses gtkdialog2.
/// Edited Aug. 9:
I replaced the "A" version with the attached "C" version (the "B" version didn't work too well).
This version first tries to use gtkdialog2, then gtkdialog4, and then gtkdialog3 as a last resort.
This isn't too hard to do in a ten line program, but would be kind of a pain in a thousand line program.
/// Third edit Aug 15:
I posted a full version of Wakepup 2, using this script and an updated floppy image, at
http://www.murga-linux.com/puppy/viewtopic.php?t=80291
///
- Attachments
-
- wakepup2_NOIMAGE-120804C.pet
- (2.04 KiB) Downloaded 478 times
Last edited by Crash on Wed 15 Aug 2012, 08:06, edited 3 times in total.
Multisession boot-up ignores file deletions
Barry,
While attempting to develop in a multisession environment, I discovered that if I delete a file, save to CD, then reboot (without further saving), the deleted file remains in place. The whiteout file for it does get written to the generated delta directory but appears to be ignored in the process of setting up the pup_ro1 layer in the reboot session.
I assume the fix belongs in the initrd.gz file, which is currently outside of my "territory". Now that I have pointed out the issue, I trust that the solution will be obvious to you. Please consider correcting this during your woof upgrade. Thanks.
Richard
While attempting to develop in a multisession environment, I discovered that if I delete a file, save to CD, then reboot (without further saving), the deleted file remains in place. The whiteout file for it does get written to the generated delta directory but appears to be ignored in the process of setting up the pup_ro1 layer in the reboot session.
I assume the fix belongs in the initrd.gz file, which is currently outside of my "territory". Now that I have pointed out the issue, I trust that the solution will be obvious to you. Please consider correcting this during your woof upgrade. Thanks.
Richard
I would like to add a request for pupzip script.
After a while running Puppy Linux i found out that I do not like files to be extracted with the original file "being deleted" .
Cause is if it is a .diff file for example, any accidentally changes to that file are permanent, for example.
I have added these two lines to the .gz and .bz2 parts :
before bunzip2 or gunzip is executed
to create a temporary file
and
afterwards to restore
.
Not sure about .wh. whipeout files created in that process, though.
I am starting to use the term "whipeout" for the "official" term "whiteout" , because these .wh. files mainly get created while removing files.
After a while running Puppy Linux i found out that I do not like files to be extracted with the original file "being deleted" .
Cause is if it is a .diff file for example, any accidentally changes to that file are permanent, for example.
I have added these two lines to the .gz and .bz2 parts :
Code: Select all
cp "$1" "${1%/*}"/tmp-"${1##*/}"
to create a temporary file
and
afterwards to restore
Code: Select all
mv "${1%/*}"/tmp-"${1##*/}" "$1"
Not sure about .wh. whipeout files created in that process, though.
I am starting to use the term "whipeout" for the "official" term "whiteout" , because these .wh. files mainly get created while removing files.
Wary and Racy 5.3 final
Hi Barry,
This is a follow-up to my post from July 8th concerning a bug with partview. I had a look at the file, and, where the optical drives are tagged, I changed the value on line #63 from:
to:
So, now partview is showing a respectable 683 mb capacity for my CD rom drive as seen in my screenshot. Please check and confirm if this simple fix is all that is needed here.
Thanks,
Monsie
This is a follow-up to my post from July 8th concerning a bug with partview. I had a look at the file, and, where the optical drives are tagged, I changed the value on line #63 from:
Code: Select all
ASIZE=4300000
Code: Select all
ASIZE=700000
Thanks,
Monsie
- Attachments
-
- partview-fix.tar.gz
- (155.59 KiB) Downloaded 482 times
My [u]username[/u] is pronounced: "mun-see". Derived from my surname, it was my nickname throughout high school.
Wary and Racy 5.3 final
Barry,
On second thought...
I believe that partview is supposed to show the size of the disk partition and not necessarily the actual size of the drive --right? I also think there needs to be a value for the partition size whether the disk is a DVD or a CD, so, I changed line #63 to read:
Since I am using a CD-r that has been "finalized" the partition size of the CD is that portion which I actually used when I burned the data onto it. Since I did not use up the disk capacity, then I show a reduced partition with zero free space as shown in my new screenshot.
That said, is it also necessary to change line #56 to read the same, namely:
Hopefullly, I've got it right now...
Thanks,
Monsie
On second thought...
I believe that partview is supposed to show the size of the disk partition and not necessarily the actual size of the drive --right? I also think there needs to be a value for the partition size whether the disk is a DVD or a CD, so, I changed line #63 to read:
Code: Select all
ASIZE=4300000 700000
That said, is it also necessary to change line #56 to read the same, namely:
Code: Select all
ASIZE=4300000 700000
Thanks,
Monsie
- Attachments
-
- partview-fix2.tar.gz
- (155.68 KiB) Downloaded 502 times
My [u]username[/u] is pronounced: "mun-see". Derived from my surname, it was my nickname throughout high school.
For Barry's understanding.
Puppy handling of CD/DVD created by Windows user(s) and given to a Puppy user(s)....Problems exists. A shortcoming needed WOOF2 developer understanding!
Here to help
Here to help
Belkin F5D6050 wireless USB connection
deleted
Last edited by Clive on Sat 08 Sep 2012, 23:04, edited 1 time in total.
Re: Belkin F5D6050 wireless USB connection
Only 2 versions of F5D6050 exist; both apparently use theClive wrote:One other problem I did experience was in attempting to initially connect to the net via a Belkin F5D6050 USB wireless connection.
A Knoppix distro that I initially tried automatically detected and connected OK with that adapter, but non of the Puppy's detected it. I spent a couple of days trying everything I could find on the net about how to get it working, but to no avail. In the end I swapped connections with my son's so that he's now using the wireless whilst the PC I am using is hard wired.
I went through practically every USB wireless adapter driver listed, and even tried loading via ndiswrapper etc. But with no luck.
same driver.
http://linux-wless.passys.nl/query_part ... ame=Belkin
It's the at76c50x-usb and is in Wary but may need to be
loaded from "load modules" in the network wizard.
Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs
Have you tried this?Clive wrote:Thanks. I had tried that, but it came up with a 'nothing found' type message and suggested 'unload module'.It's the at76c50x-usb and is in Wary but may need to be
loaded from "load modules" in the network wizard.
http://murga-linux.com/puppy/viewtopic. ... 672#627518
Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs
Osmo bug?
Osmo does not have the most intuitive interface in the world.Clive wrote:. . . right clicking a day and selecting the day color option only has a choice of NONE, so you can't highlight particular days to particular colours.
In order to be able to select colours you need to define additional colours. Very likely you have already tried to do so, but have not found out where they can be defined. This is because the preferences dialog refers to them as "Day categories", not "colors".
Go to Preferences -> Calendar -> Day categories and click the button below the bottom left corner of the big empty list box -- that's the mystery button that is not labeled except for a big grey rectangle. This brings up a colour selector dialog. Choose your colour, click OK, then type a name in the box to the right of the mystery button (whose rectangle should now be filled with your chosen colour), and hit Enter or click the + button.
The background colour of text entry boxes in Osmo dialogs turns yellow to indicate that the user is editing the entry. When the user finishes editing the entry, she needs to press Enter or the edit will be ignored. The backgound colour of the entry will then turn white again.Clive wrote:I can't seem to change the "Day note marker" to any other character (or rather you can change it, but it resets back to the default each time).
I suspect that this works as intended by the Osmo developer, although many users might expect that closing the dialog would also indicate that the edit was complete. If you would like to see this changed, you could post to the Osmo Tracker at Osmo Tracker: Feature Requests or Osmo Tracker: Bugs.