PeasyDisc CD/DVD/BR Tools
- nilsonmorales
- Posts: 972
- Joined: Fri 15 Apr 2011, 14:39
- Location: El Salvador
Maybe needs some review, but is a start
Edit: sorry was peasy, not peasi; pet re-uploaded
Edit: sorry was peasy, not peasi; pet re-uploaded
- Attachments
-
- peasydisc_NLS_es-3.2.pet
- .mo file and .desktop file | Spanish translate
- (5.19 KiB) Downloaded 333 times
Last edited by nilsonmorales on Tue 23 Dec 2014, 16:06, edited 1 time in total.
[b][url=http://nilsonmorales.blogspot.com/]My blog |[/url][/b][b][url=https://github.com/woofshahenzup]| Github[/url][/b]
[img]https://i.postimg.cc/5tz5vrrX/imag018la6.gif[/img]
[img]http://s5.postimg.org/7h2fid8pz/botones_logos3.png[/img]
[img]https://i.postimg.cc/5tz5vrrX/imag018la6.gif[/img]
[img]http://s5.postimg.org/7h2fid8pz/botones_logos3.png[/img]
- Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
Possible bug in Peasy disc?
Morning, all.
I run an old HP/Compaq desktop, circa 2005. It has an Athlon 64, 3 GB of DDR1 RAM, ATI Radeon Xpress 200 integrated graphics.....and a WD 160 GB IDE/PATA HDD.
I've been running 'Tahrpup' 6.0 on it since early November. Really like it. I originally started using it on my even older Dell Inspiron laptop, 'cos it was the only Linux distro that would work, out-of-the-box, with the Intel 'Extreme' graphics chip it has ('Brookedale', 82845 G/GL/GE/PE/GV); and I was so impressed with it that I did a frugal install on the Compaq, too. It simply FLIES on the desktop PC.
I don't know if this is a bug or not, but I used 'Peasydisc' for the first time night before last, to burn VectorLinux to a DVD, since I want to try it. Upon shutting the program down, after completing the disc, my CPU loading shot straight up to 100%, and just sat there. htop showed it was running flat-out (although it didn't show ANYTHING that could have been using it); and the CPU temps steadily climbed until the fan cut in on max.
That was at approx 65C; doesn't sound that warm compared to some Intels, I know, but this thing rarely gets much over 35C, even listening to streaming audio & playing vids at the same time. First time I've ever heard the fan on max, so.....I was a wee bit concerned.
Even half-a-dozen successive re-boots didn't seem to cure it. As soon as the desktop came up, pWidgets 'CPU-bar' showed it going straight to 100%, and not moving. tempiconsvg 0.21 showed it steadily climbing toward the cut-in point. Cursor movement was jerky (a sure sign of high CPU usage on this old girl), and response to ANYTHING was pretty sluggish.
I re-installed yesterday morning; understandably enough, that did fix it. But I'm curious as to what might have happened.....and whether or not Peasydisc WAS in fact responsible.
Regards,
Mike.
I run an old HP/Compaq desktop, circa 2005. It has an Athlon 64, 3 GB of DDR1 RAM, ATI Radeon Xpress 200 integrated graphics.....and a WD 160 GB IDE/PATA HDD.
I've been running 'Tahrpup' 6.0 on it since early November. Really like it. I originally started using it on my even older Dell Inspiron laptop, 'cos it was the only Linux distro that would work, out-of-the-box, with the Intel 'Extreme' graphics chip it has ('Brookedale', 82845 G/GL/GE/PE/GV); and I was so impressed with it that I did a frugal install on the Compaq, too. It simply FLIES on the desktop PC.
I don't know if this is a bug or not, but I used 'Peasydisc' for the first time night before last, to burn VectorLinux to a DVD, since I want to try it. Upon shutting the program down, after completing the disc, my CPU loading shot straight up to 100%, and just sat there. htop showed it was running flat-out (although it didn't show ANYTHING that could have been using it); and the CPU temps steadily climbed until the fan cut in on max.
That was at approx 65C; doesn't sound that warm compared to some Intels, I know, but this thing rarely gets much over 35C, even listening to streaming audio & playing vids at the same time. First time I've ever heard the fan on max, so.....I was a wee bit concerned.
Even half-a-dozen successive re-boots didn't seem to cure it. As soon as the desktop came up, pWidgets 'CPU-bar' showed it going straight to 100%, and not moving. tempiconsvg 0.21 showed it steadily climbing toward the cut-in point. Cursor movement was jerky (a sure sign of high CPU usage on this old girl), and response to ANYTHING was pretty sluggish.
I re-installed yesterday morning; understandably enough, that did fix it. But I'm curious as to what might have happened.....and whether or not Peasydisc WAS in fact responsible.
Regards,
Mike.
- Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
I appreciate your taking the time to have a look. As I said, it must have been some quirk of my system, although, 'off the top of my head', I don't know what it could have been.rcrsn51 wrote:I ran some tests in Tahrpup and cannot replicate the problem. PeasyDisc leaves no phantom processes running to eat up CPU.
And it has no persistence. After a reboot there is no way that PeasyDisc could be affecting your system.
As a footnote, I've used Peasydisc to burn another .iso file this morning; and upon shutdown, everything was behaving itself, so.....one of those short-term mysteries, it seems.
When you had to reboot several times, were these warm or cold reboots?
I wonder if after the burn, your optical drive was left in some "undefined" state and the Puppy drive detection routines went crazy trying to detect it again?
The only way that PeasyDisc physically interacts with the drive is through the Eject button.
I wonder if after the burn, your optical drive was left in some "undefined" state and the Puppy drive detection routines went crazy trying to detect it again?
The only way that PeasyDisc physically interacts with the drive is through the Eject button.
- Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
The first 2 or 3 were warm reboots, followed by a couple of cold reboots (power off, leave for 5-10 minutes, then full 'normal' start-up again).rcrsn51 wrote:When you had to reboot several times, were these warm or cold reboots?
I wonder if after the burn, your optical drive was left in some "undefined" state and the Puppy drive detection routines went crazy trying to detect it again?
The only way that PeasyDisc physically interacts with the drive is through the Eject button.
I wouldn't want to even hazard a guess as to what happened. I've had this machine about a year now; got it from my sister, when she replaced it before XP went EOL. 99% of the time it runs very reliably; but on rare occasions, it will inexplicably freeze, crash, jam-up on me.....call it what you will. But I don't really intend changing it; more likely steadily upgrade it, and modify parts as time goes by. I know its history, you see!!
I'm already planning on upgrading the mobo, CPU, RAM, HDD & PSU for something a wee bit more 'current' when funds permit.
Probably move up to a dual-core, with DDR2 RAM, and probably a SATA HDD...
Regards,
Mike.
BTW: My money's on the gremlins..!
menu Multimedia Tahrpup 5.8.3
PeasyDic makes me happy ! (menu Multimedia Tahrpup 5.8.3)
Viva Puppy con sus applicacciones ligeras... good tools, Peasydisc tried to day for ripping an audio CD. nothing more needed.
Merci (from european latin citizens).
PeasyDVD tried to-day, does the job.
Viva Puppy con sus applicacciones ligeras... good tools, Peasydisc tried to day for ripping an audio CD. nothing more needed.
Merci (from european latin citizens).
PeasyDVD tried to-day, does the job.
Last edited by Pelo on Thu 30 Apr 2015, 18:42, edited 1 time in total.
on test bench QtPuppy Warz
on test bench QtPuppy Warz (an old on, revitalized)
pCD is really without problems, on each Puppy i tries.
pCD is really without problems, on each Puppy i tries.
-
- Posts: 807
- Joined: Mon 12 Oct 2009, 17:11
-
- Posts: 807
- Joined: Mon 12 Oct 2009, 17:11
Burned Ubuntu-15.04 night before last with it. Enough patience for ya?rcrsn51 wrote:Yes, but it will take some patience on your part to learn how it works. You should start with a simpler task, like burning an ISO.B.K. Johnson wrote:
Can your application, PeasyDisc, make a music CD of .mp3 files working from tahrpup-6.0.2?
-
- Posts: 807
- Joined: Mon 12 Oct 2009, 17:11
Hello PeasyDisc fans
After a failed audio cd burn with pBurn I posted in the pBurn-4.3.14 thread my experience with that software and my attempts with using PeasyDisc to blank the rewritable. I thought it inappropriate then and even now to duplicate the post here as all of the post would not be of interest to those following the Peasy thread. Quoted below is an excerpt from the post of the section related to my use of PeasyDisc. I have reluctantly provided a link to the post in the pBurn thread at the end of this post for those who may be interested.
Here is the link to the post in the pBurn thread.
http://murga-linux.com/puppy/viewtopic. ... 849#847849
On another matter, I answered on offer for help from him on May 5th, but no activity from him since.
http://murga-linux.com/puppy/viewtopic. ... 625#844625
B.K. Johnson
tahrpup-6.0.2 PAE, slacko-5.7, frugal install, pupsave file, multi OS flashdrive, SYSLINUX boot, CPU-Dual E2140, 4GB RAM
After a failed audio cd burn with pBurn I posted in the pBurn-4.3.14 thread my experience with that software and my attempts with using PeasyDisc to blank the rewritable. I thought it inappropriate then and even now to duplicate the post here as all of the post would not be of interest to those following the Peasy thread. Quoted below is an excerpt from the post of the section related to my use of PeasyDisc. I have reluctantly provided a link to the post in the pBurn thread at the end of this post for those who may be interested.
I concluded by openly suggesting that:I launched rcrsn51's PeasyDisc to see it it would blank the disc. It went through the process seemingly without a problem but pBurn still reported the RW as a read only CD. I concluded that PeasyDisc only did a "Fast Blank", not a full erase.
I again blanked the RW in PeasyDisc, then chose to burn an ISO. As reported in the first line of the screen output, the media was recognized as removable and the software completed the burn of the ISO - 437MB . But when I clicked on the CD icon a pBurn dialog appeared, informing that the disc was most likely blank and invited me to run pBurn. This I did. To my surprise, pBurn now showed the RW as blank - 652 MB free. The PeasyDisc burn of the ISO did not happen, but the process fully erased the disc.
I then chose to burn with pBurn the same SRCD iso that Peasy failed to burn. It went through the process and deliveed a bootable CD.
The same day, I sent a PM to rcrsn51 with the link to the post. That was on Tue 26 May 2015. As you all know, rcrsn51 gets very antsy when posters take a day to respond to his proffered help. He hasn't responded in mail or here or in the pBurn thread .rcrsn51's PeasyDisc needs to offer full erase, not only "fast erase". The full erase seems to have happened during the burniso but the data was not written.
Here is the link to the post in the pBurn thread.
http://murga-linux.com/puppy/viewtopic. ... 849#847849
On another matter, I answered on offer for help from him on May 5th, but no activity from him since.
http://murga-linux.com/puppy/viewtopic. ... 625#844625
B.K. Johnson
tahrpup-6.0.2 PAE, slacko-5.7, frugal install, pupsave file, multi OS flashdrive, SYSLINUX boot, CPU-Dual E2140, 4GB RAM
Hi, I am ripping an audio CD (peasydisc 3.5) and would like to rip all tracks. The track selection window defaults to "1". Is there an easy way to rip "all" tracks if i do not already know how many tracks are on the CD? (Some of my CDs are things like "Greatest hits of 1975" and Lord only knows how many tracks are on the CD and I don't have the original cover).
Or some simple way for me to see the list of tracks so I can enter "1-x" in the track selection field? cheers!
EDIT : Just for the heck of it I tried putting "all" in the "Track" field and it works fine - ripped all the tracks! (It came up with a message about "tall" being an option that builds one large file from all tracks but it still produced the distinct individual files that I was looking for. Perfect!)
Or some simple way for me to see the list of tracks so I can enter "1-x" in the track selection field? cheers!
EDIT : Just for the heck of it I tried putting "all" in the "Track" field and it works fine - ripped all the tracks! (It came up with a message about "tall" being an option that builds one large file from all tracks but it still produced the distinct individual files that I was looking for. Perfect!)