9:59 a.m.
K3b is a piece of work...
I have 2 CD/DVD burner drives
Plextor $120+
Sony $50
Fedora doesn't like the Plextor...I guess
after downloading F10 for 9.5 hours, I tried to burn a ISO-DVD.
The simplest operation?
I wasted 4 blanks making 3 final copies that haved been checked to be good!.
The Plextor would get an error and then hang K3B
I'd kill it with kill -9 and then the drive would be locked up and even hung the eject
command.
I had to reboot to open the drive. Sometimes I have to reboot to do a second operation!
and even once the "bring things back" facility had the #$%& thing running
again.
OH YES! an old error reported forever
When making an ISO DVD, the verify write facility still doesn't work
even on the Sony drive. It says "couldn't find a DVD to verify.
Make things easy: if there is an error:
(1) release the drive announcing ithat the DVD is no longer blank!
(2) eject the DVD
(3) terminate all processes and subprocesses that stay running(i.e. die and go away)
(4) work on the program some more.
1:35 p.m.
bennett78 wrote:
I hope it's still supported...It recognizes my CD & DVD-R
runs great on
CentOS5 (close to RHEL5)
# uname -r
2.6.18-92.1.22.el5
and puts a Blank DVD-R Dicc icon on the Desktop
I trying to get MongoArchive to backup my new, clean installation but it's
wimmy scripts can't find
my DVD drive, because it looks like it doesn't show up in a grep of the
mount command or a mount
on /mnt/cdrom and is not auto-mounted. My /etc/fstab:
# /dev/hdc /media/cdrom auto
pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed 0 0
/dev/hdd /media/cdrecorder auto
pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed 0 0
How does K3B find the DVD drive in my case /dev/hdd?
thanks,
-Frank
I used k3b last night on F10. Only one issue and that is a reported
upstream bug with verify and auto-eject. It seems that k3b isn't
waiting until the disk is settled before trying to access it with some
burners.
A disk isn't mounted when it is inserted if it is blank. In KDE, I get
asked what to do with a full disk. Last night I was playing with
burning and to test the DVD image, I ended up using /dev/sr0.
--
Robin Laing
4:53 p.m.
On Wed, 26 Nov 2008 14:23:11 -0600
Rex Dieter <rdieter(a)math.unl.edu> wrote:
Unfortunately, I don't know how to fix it. Do you?
Yes: go back to the old dvd drivers which were apparently
changed for no reason, because they didn't have this bug,
and if the change fixed some other problem it was a
much rarer and hard to encounter one, so we are better
off with the old bug than the new one :-).
6:19 a.m.
On Friday 28 November 2008, Tim wrote:
On Thu, 2008-11-27 at 09:48 -0500, Gene Heskett wrote:
> I have never had a drive, and by now I've had 7 or 8 of them hit the
> bin, a computer compatible cd or dvd drive that recognized a disk in
> under 30 seconds.
I can't say that I've timed them, but I'd guess my experience is getting
close to that. Most drives are slow to figure out that there's a disc
in, spin up, find out what type, and then the OS has to periodically
probe the drive to see if it's not empty (there's a hardware disc change
flag, but I'm told it's rarely made use of, where the drive tells the
system there's been a disc change).
The best drive I've got is an older, 6x spin speed, SCSI CD-ROM. It's
faster to get going, is faster to restart after it's gone idle for a
moment, and very fast to seek across the drive. Because of that, for
many things it's quicker to use than a faster spin speed drive. Of
course it was a damn expensive drive, and none of my current systems
have a SCSI host.
Pursuant to my long time bitch about k3b not waiting for the drive to accept
the disk, I ran thru my services and stopped anything that looked like a bus
scanner, then tested it by inserting a good dvd to see what the system did.
Nothing, not even a log entry.
So I then used k3b to burn the F10-i386-DVD.iso and told it to verify. Of
course it failed the verify, pulled the disk back in and reported "no media"
about .2 seconds or less from the drawer closing.
I stopped k3b, and did this:
[root@coyote Fedora-10-i386-DVD]# dd if=/dev/sr0|sha1sum -c SHA1SUM
Fedora-10-i386-DVD.iso: OK
So once again all the other excuses, having been removed from the scene, are
proven to just excuses, k3b needs fixed. And it should be using sha1sum too.
Somebody said konqueror had that built in, but I looked its menu's over
without seeing that. How does one enable this?
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Nothing is easier than to denounce the evildoer; nothing is more difficult
than to understand him.
- Fyodor Dostoevski
11:07 p.m.
On Wednesday 26 November 2008, Anne Wilson wrote:
On Wednesday 26 November 2008 16:50:47 Rex Dieter wrote:
> Fred Silsbee wrote:
> >> > K3b is a piece of work...
> >>
> >> the presence of a bug (arguably here in kernel-space) does
> >> not imply abondonment.
> >
> > The no verify ISO write is very very old!
> > I remember it back when I was reporting to bugzilla!
>
> I'm aware of that. All signs (still) point to a kernel issue, potentially
> limited to certain brands/models of burners.
That has to be the most likely explanation. Here k3b verifies on some boxes
but not on others.
Generally, I gave up on asking k3b to verify anything. Why? Because when its
about to do the verify read, it ejects the disk and immediately pulls it back
in. Then it waits for the disk to be recognized by the drive NOT! At that
point it will kick out from the error, no disk in drive. It would be nice if
it would then ask you to put the disk back in the drive and click proceed
when you have pushed the drawer closed again and given the drive time to
recognize the disk as evidenced that the activity led has stopped blinking.
ISTR I even filed a bz on that 2, maybe 3 years ago, so far back up the log I
expect the bz server has been wiped. I sure don't recall the bz number. And
it was never acknowledged either.
k3b is a heck of a good proggy, and I fail to see why that hasn't been fixed
years ago. New eye candy, re-arrange the menu's etc has been done 2 or 3
times now, but a simple lack of a time delay bug is too much trouble to fix I
guess.
Anne
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Dr. Livingston?
Dr. Livingston I. Presume?
8:06 a.m.
On Wed, 2008-11-26 at 07:59 -0800, Fred Silsbee wrote:
K3b is a piece of work...
I have 2 CD/DVD burner drives
Plextor $120+
Sony $50
Fedora doesn't like the Plextor...I guess
after downloading F10 for 9.5 hours, I tried to burn a ISO-DVD.
The simplest operation?
I wasted 4 blanks making 3 final copies that haved been checked to be good!.
The Plextor would get an error and then hang K3B
I've experienced the same or similar errors with K3B. It used to work
properly.
4:57 a.m.
On Monday 01 December 2008, Michael Schwendt wrote:
On Mon, 1 Dec 2008 00:48:40 -0500 (EST), D. Hugh Redelmeier wrote:
> I never use k3b's verify anyway. I'm too impatient to let it complete
> the calculation of the hash of the .iso file. k3b seems to forget
> that the hash is wrong (not completely calculated) and thus the
> subsequent verification is reported as failing rather than being
> impossible to perform.
Another bug? Interesting.
Is this in bugzilla (also upstream) already?
I think the md5sum it calculates is correct, but it does not remember how many
bytes to check on the disk check, so like I just demoed with dd, you have to
divide the iso's size by 2048, and tell dd to read count blocks of 2048
bytes. Then, as I just demoed with dd and sha1sum, it Just Works(TM). If
left to its own devices, dd reads 2 blocks too many and the sum is then
contaminated by the extra data.
k3b worked fine back at F2, but hasn't worked since, and the first problem now
is that it doesn't wait for the drive to recognize the disk after it is
pulled back in, and instead reports instantly that there is no media
available.
I know enough C to be dangerous, but much of k3b is in C++ and I've never been
able to get my aged wet ram wrapped around C++, or I would have fixed it. At
least 2 years ago.
And yes, it was bz'd and close with a won't fix, long enough back up the log I
have NDI what the number may have been. 2-3 years ago anyway.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
General Protection Fault! [ Ignore ] [ Reboot ] [ Install Linux ]
-- From a Slashdot.org post
4:21 a.m.
On Monday 01 December 2008, D. Hugh Redelmeier wrote:
| From: Gene Heskett <gene.heskett(a)verizon.net>
|
| [root@coyote Fedora-10-i386-DVD]# dd if=/dev/sr0|sha1sum -c SHA1SUM
| Fedora-10-i386-DVD.iso: OK
[Spaces around the pipe symbol would help readability. Partly because
at least some fonts don't make that glyph very distinct.]
I don't think that that pipeline did what you think that did.
The dd command piped the raw disk contents to sha1sum (as you expect).
The sha1sum command ignored its standard input and checked .iso files
named within the SHA1SUM file (surprise!).
The current working directory had those .iso files. Try the same
pipeline from within another directory and you will see what I'm
talking about.
So your disk was not checked.
But there is a better way to verify: just do a cmp between the raw
disk and the .iso file.
Why is this better? Because you can tell cmp how many bytes to read
from the raw disk. Remember, the raw disk read may appear to have
more bytes than the .iso, and those bytes should be ignored: EOF is
not well defined on a raw disk. This could also trip up k3b
(speculation on my part).
I use a script called "isoburn" for this stuff. There are two
relevant features of this script:
- when burning, it pads the file. Otherwise, on some drives, the
kernel will generate read errors when a program tries to read near
the end of the burned part (the kernel does a read-ahead past the
end and gets upset when the drive gives an error).
- when verifying, it does a cmp with the actual proper length filled
in. This uses a feature of GNU cmp not documented in the man page.
Damn GNU's contempt for man pages.
Here, in essence, is how the verify works (replace file.iso with the
pathname of the .iso file):
cmp --bytes `isosize file.iso` file.iso /dev/sr0
I'd forgotten to divide the size of the iso by 2048 to get the number of
blocks dd should read. If left to its own devices it reads 2 too many and
the sum is wrong.
Doing it this way, the sum is correct on both disks I've now burnt:
[root@coyote misc]# dd if=/dev/sr0 bs=2048 count=1788366 | sha1sum
1788366+0 records in
1788366+0 records out
3662573568 bytes (3.7 GB) copied, 252.066 s, 14.5 MB/s
086fd570518ac58d3966c43c1b6d146e38919d8d -
From the SHA1SUM file:
086fd570518ac58d3966c43c1b6d146e38919d8d
*Fedora-10-i386-DVD.iso
From the second disk:
[root@coyote misc]# dd if=/dev/sr0 bs=2048
count=1788366 | sha1sum
1788366+0 records in
1788366+0 records out
086fd570518ac58d3966c43c1b6d146e38919d8d -
3662573568 bytes (3.7 GB) copied, 246.414 s, 14.9 MB/s
So they all match. An FU8 dvd boots, an FU9 dvd boots (its installed now), a
Ubuntu-8.04 cd boots, but these F10-i386-DVD dvd's are ignored, no change in
the bios settings.
Is iso-linux linked wrong or what?
| So once again all the other excuses, having been removed from the
scene,
| are proven to just excuses, k3b needs fixed. And it should be using
| sha1sum too.
Which I will keep hammering on till it does work again, it did once, early in
its history. k3b worked fine when I was running Fedora 2. But it hasn't
worked since.
I never use k3b's verify anyway. I'm too impatient to let it
complete
the calculation of the hash of the .iso file. k3b seems to forget
that the hash is wrong (not completely calculated) and thus the
subsequent verification is reported as failing rather than being
impossible to perform.
Apparently the authors don't use it either.. Sad.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Your own qualities will help prevent your advancement in the world.
2:56 a.m.
On Mon, 1 Dec 2008 00:48:40 -0500 (EST), D. Hugh Redelmeier wrote:
I never use k3b's verify anyway. I'm too impatient to let it
complete
the calculation of the hash of the .iso file. k3b seems to forget
that the hash is wrong (not completely calculated) and thus the
subsequent verification is reported as failing rather than being
impossible to perform.
Another bug? Interesting.
Is this in bugzilla (also upstream) already?
11:48 p.m.
| From: Gene Heskett <gene.heskett(a)verizon.net>
| [root@coyote Fedora-10-i386-DVD]# dd if=/dev/sr0|sha1sum -c SHA1SUM
| Fedora-10-i386-DVD.iso: OK
[Spaces around the pipe symbol would help readability. Partly because
at least some fonts don't make that glyph very distinct.]
I don't think that that pipeline did what you think that did.
The dd command piped the raw disk contents to sha1sum (as you expect).
The sha1sum command ignored its standard input and checked .iso files
named within the SHA1SUM file (surprise!).
The current working directory had those .iso files. Try the same
pipeline from within another directory and you will see what I'm
talking about.
So your disk was not checked.
But there is a better way to verify: just do a cmp between the raw
disk and the .iso file.
Why is this better? Because you can tell cmp how many bytes to read
from the raw disk. Remember, the raw disk read may appear to have
more bytes than the .iso, and those bytes should be ignored: EOF is
not well defined on a raw disk. This could also trip up k3b
(speculation on my part).
I use a script called "isoburn" for this stuff. There are two
relevant features of this script:
- when burning, it pads the file. Otherwise, on some drives, the
kernel will generate read errors when a program tries to read near
the end of the burned part (the kernel does a read-ahead past the
end and gets upset when the drive gives an error).
- when verifying, it does a cmp with the actual proper length filled
in. This uses a feature of GNU cmp not documented in the man page.
Damn GNU's contempt for man pages.
Here, in essence, is how the verify works (replace file.iso with the
pathname of the .iso file):
cmp --bytes `isosize file.iso` file.iso /dev/sr0
| So once again all the other excuses, having been removed from the scene, are
| proven to just excuses, k3b needs fixed. And it should be using sha1sum too.
I never use k3b's verify anyway. I'm too impatient to let it complete
the calculation of the hash of the .iso file. k3b seems to forget
that the hash is wrong (not completely calculated) and thus the
subsequent verification is reported as failing rather than being
impossible to perform.
10:13 a.m.
On Fri, Nov 28, 2008 at 6:19 AM, Gene Heskett <gene.heskett(a)verizon.net> wrote:
So once again all the other excuses, having been removed from the
scene, are
proven to just excuses, k3b needs fixed. And it should be using sha1sum too.
Somebody tried this with Nautilus and had the same problem. Singling
out the wrong component and blaming a bug on it isn't going to help.
--
Fedora 9 : sulphur is good for the skin
( www.pembo13.com )
4:27 a.m.
On Thu, 2008-11-27 at 09:48 -0500, Gene Heskett wrote:
I have never had a drive, and by now I've had 7 or 8 of them hit
the
bin, a computer compatible cd or dvd drive that recognized a disk in
under 30 seconds.
I can't say that I've timed them, but I'd guess my experience is getting
close to that. Most drives are slow to figure out that there's a disc
in, spin up, find out what type, and then the OS has to periodically
probe the drive to see if it's not empty (there's a hardware disc change
flag, but I'm told it's rarely made use of, where the drive tells the
system there's been a disc change).
The best drive I've got is an older, 6x spin speed, SCSI CD-ROM. It's
faster to get going, is faster to restart after it's gone idle for a
moment, and very fast to seek across the drive. Because of that, for
many things it's quicker to use than a faster spin speed drive. Of
course it was a damn expensive drive, and none of my current systems
have a SCSI host.
--
[tim@localhost ~]$ uname -r
2.6.27.5-41.fc9.i686
Don't send private replies to my address, the mailbox is ignored. I
read messages from the public lists.
5:01 p.m.
--- On Thu, 11/27/08, Michael Schwendt <mschwendt(a)gmail.com> wrote:
From: Michael Schwendt <mschwendt(a)gmail.com>
Subject: Re: has K3B been abandoned?
To: fedora-list(a)redhat.com
Date: Thursday, November 27, 2008, 8:01 PM
On Thu, 27 Nov 2008 09:08:07 -0800 (PST), Fred Silsbee
wrote:
> turns out K3B is not the culprit
>
> Nautilus shows identical problems
HAL is not influencing this either.
Just burnt six CD-RWs on F-9 ( kernel-2.6.27.5-41.fc9 ) and
for all of
them, the verification step in k3b found that the written
image differed
from the original. Manually verifying the written images
(with readcd and
sha1sum) was successful as always.
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines:
http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
I usually don't have the problem on CDs
2:01 p.m.
On Thu, 27 Nov 2008 09:08:07 -0800 (PST), Fred Silsbee wrote:
turns out K3B is not the culprit
Nautilus shows identical problems
HAL is not influencing this either.
Just burnt six CD-RWs on F-9 ( kernel-2.6.27.5-41.fc9 ) and for all of
them, the verification step in k3b found that the written image differed
from the original. Manually verifying the written images (with readcd and
sha1sum) was successful as always.
2:45 p.m.
On Thursday 27 November 2008 20:01:35 Michael Schwendt wrote:
Just burnt six CD-RWs on F-9 ( kernel-2.6.27.5-41.fc9 ) and for all
of
them, the verification step in k3b found that the written image differed
from the original. Manually verifying the written images (with readcd and
sha1sum) was successful as always.
I can confirm that behaviour - I burned an ISO last week where the verify
appeared to complete, but fail, and md5sum and sha1sum said it was fine. I
didn't check whether a bug report has been generated for that.
Anne
11:25 a.m.
--- On Thu, 11/27/08, Gene Heskett <gene.heskett(a)verizon.net> wrote:
From: Gene Heskett <gene.heskett(a)verizon.net>
Subject: Re: has K3B been abandoned?
To: "Community assistance, encouragement, and advice for using Fedora."
<fedora-list(a)redhat.com>
Date: Thursday, November 27, 2008, 5:07 AM
On Wednesday 26 November 2008, Anne Wilson wrote:
>On Wednesday 26 November 2008 16:50:47 Rex Dieter
wrote:
>> Fred Silsbee wrote:
>> >> > K3b is a piece of work...
>> >>
>> >> the presence of a bug (arguably here in
kernel-space) does
>> >> not imply abondonment.
>> >
>> > The no verify ISO write is very very old!
>> > I remember it back when I was reporting to
bugzilla!
>>
>> I'm aware of that. All signs (still) point to
a kernel issue, potentially
>> limited to certain brands/models of burners.
>
>That has to be the most likely explanation. Here k3b
verifies on some boxes
>but not on others.
>
Generally, I gave up on asking k3b to verify anything.
Why? Because when its
about to do the verify read, it ejects the disk and
immediately pulls it back
in. Then it waits for the disk to be recognized by the
drive NOT! At that
point it will kick out from the error, no disk in drive.
It would be nice if
it would then ask you to put the disk back in the drive and
click proceed
when you have pushed the drawer closed again and given the
drive time to
recognize the disk as evidenced that the activity led has
stopped blinking.
ISTR I even filed a bz on that 2, maybe 3 years ago, so far
back up the log I
expect the bz server has been wiped. I sure don't
recall the bz number. And
it was never acknowledged either.
k3b is a heck of a good proggy, and I fail to see why that
hasn't been fixed
years ago. New eye candy, re-arrange the menu's etc
has been done 2 or 3
times now, but a simple lack of a time delay bug is too
much trouble to fix I
guess.
>Anne
--
Cheers, Gene
"There are four boxes to be used in defense of
liberty:
soap, ballot, jury, and ammo. Please use in that
order."
-Ed Howdershelt (Author)
Dr. Livingston?
Dr. Livingston I. Presume?
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines:
http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
same bug for years
I had the identical problem with Nautilus so K3B is not the problem
strange : after killing (kill -9) K3B or Nautilus, something is still running in the CPU
11:14 a.m.
--- On Thu, 11/27/08, Michael Schwendt <mschwendt(a)gmail.com> wrote:
From: Michael Schwendt <mschwendt(a)gmail.com>
Subject: Re: has K3B been abandoned?
To: fedora-list(a)redhat.com
Date: Thursday, November 27, 2008, 10:05 AM
On Wed, 26 Nov 2008 17:51:00 -0500, Tom Horsley wrote:
> Yea, but there is clearly something strange going on
> because the latest bug I see is k3b ejecting the media
> then not being able to reload it, yet on the same
system
> with the same kernel and same drive, the "eject
-T"
> command is perfectly capable of ejecting and closing
> the tray.
eject uses consolehelper+PAM, k3b doesn't.
Opening and closing the tray here has never been a problem.
Unless
background programs accessed the disc and blocked it
temporarily.
However, what likely got lost in bugzilla noise (#440343)
is the
difference in k3b's debug output compared with the
older working
kernel. Perhaps there's interference with other
components that
try to detect and auto-mount the disc as soon as it's
being reloaded.
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines:
http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
I had the identical problem with Nautilus so K3B is NOT the problem
sending my Plextor back to the factory.
Repeating: after killing K3B or after Nautilus hangs, something is still using the CPU
(GKRellm) green and orange
11:08 a.m.
--- On Thu, 11/27/08, Michael Schwendt <mschwendt(a)gmail.com> wrote:
From: Michael Schwendt <mschwendt(a)gmail.com>
Subject: Re: has K3B been abandoned?
To: fedora-list(a)redhat.com
Date: Thursday, November 27, 2008, 1:02 PM
On Thu, 27 Nov 2008 09:12:11 +0000, Anne Wilson wrote:
> On Thursday 27 November 2008 05:07:21 Gene Heskett
wrote:
> > Generally, I gave up on asking k3b to verify
anything. Why? Because when
> > its about to do the verify read, it ejects the
disk and immediately pulls
> > it back in. Then it waits for the disk to be
recognized by the drive NOT!
>
> Again, it depends on the drive. That happens on some
of my boxes but not all
> of them. For ISOs, though, it's just as easy to
do an md5sum (or sha1sum if
> you prefer it).
Timing issues with different drive hardware seem to be an
issue indeed.
Some drives take a long time to reload the tray and examine
the disc.
Other drives are quick at that.
As mentioned in bz #440343 I can verify ISOs in k3b just
fine _if_ burning
CDs or CD-RWs. Only temporarily it was broken just as with
DVDs. Meanwhile
I burn on a different Linux platform.
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines:
http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
turns out K3B is not the culprit
Nautilus shows identical problems
10 a.m.
turns out Nautilus has the identical problems so K3B is not the culprit
I'm sending the plextor to the factory.
Repeating: even after killing (-9) K3B, something keeps running (GKRellm) and a reboot is
required.
7:02 a.m.
On Thu, 27 Nov 2008 09:12:11 +0000, Anne Wilson wrote:
On Thursday 27 November 2008 05:07:21 Gene Heskett wrote:
> Generally, I gave up on asking k3b to verify anything. Why? Because when
> its about to do the verify read, it ejects the disk and immediately pulls
> it back in. Then it waits for the disk to be recognized by the drive NOT!
Again, it depends on the drive. That happens on some of my boxes but not all
of them. For ISOs, though, it's just as easy to do an md5sum (or sha1sum if
you prefer it).
Timing issues with different drive hardware seem to be an issue indeed.
Some drives take a long time to reload the tray and examine the disc.
Other drives are quick at that.
As mentioned in bz #440343 I can verify ISOs in k3b just fine _if_ burning
CDs or CD-RWs. Only temporarily it was broken just as with DVDs. Meanwhile
I burn on a different Linux platform.
4:05 a.m.
On Wed, 26 Nov 2008 17:51:00 -0500, Tom Horsley wrote:
Yea, but there is clearly something strange going on
because the latest bug I see is k3b ejecting the media
then not being able to reload it, yet on the same system
with the same kernel and same drive, the "eject -T"
command is perfectly capable of ejecting and closing
the tray.
eject uses consolehelper+PAM, k3b doesn't.
Opening and closing the tray here has never been a problem. Unless
background programs accessed the disc and blocked it temporarily.
However, what likely got lost in bugzilla noise (#440343) is the
difference in k3b's debug output compared with the older working
kernel. Perhaps there's interference with other components that
try to detect and auto-mount the disc as soon as it's being reloaded.
3:12 a.m.
On Thursday 27 November 2008 05:07:21 Gene Heskett wrote:
Generally, I gave up on asking k3b to verify anything. Why? Because
when
its about to do the verify read, it ejects the disk and immediately pulls
it back in. Then it waits for the disk to be recognized by the drive NOT!
Again, it depends on the drive. That happens on some of my boxes but not all
of them. For ISOs, though, it's just as easy to do an md5sum (or sha1sum if
you prefer it).
Anne
6:31 p.m.
On Wed, Nov 26, 2008 at 6:12 PM, Jose Celestino <japc(a)co.sapo.pt> wrote:
Hell. Even Gnome users use K3B. I changed to Gnome some months ago
TRAITOR!!
--
Fedora 9 : sulphur is good for the skin
( www.pembo13.com )
6:52 p.m.
Words by Arthur Pemberton [Wed, Nov 26, 2008 at 06:31:25PM -0600]:
On Wed, Nov 26, 2008 at 6:12 PM, Jose Celestino
<japc(a)co.sapo.pt> wrote:
> Hell. Even Gnome users use K3B. I changed to Gnome some months ago
TRAITOR!!
:)
--
Jose Celestino | http://japc.uncovering.org/files/japc-pgpkey.asc
----------------------------------------------------------------
"One man’s theology is another man’s belly laugh." -- Robert A. Heinlein
6:12 p.m.
Words by Arthur Pemberton [Wed, Nov 26, 2008 at 04:49:47PM -0600]:
On Wed, Nov 26, 2008 at 3:56 PM, Phil Meyer
<pmeyer(a)themeyerfarm.com> wrote:
> Fred Silsbee wrote:
>>
>> --- On Wed, 11/26/08, Rex Dieter <rdieter(a)math.unl.edu> wrote:
>>
>>
>>>
>>> From: Rex Dieter <rdieter(a)math.unl.edu>
>>> Subject: Re: has K3B been abandoned?
>>> To: fedora-list(a)redhat.com
>>> Date: Wednesday, November 26, 2008, 8:23 PM
>>> Fred Silsbee wrote:
>>>
>>>
>>>>
>>>> THIS is why I no longer post to bugzilla!
>>>> Ignore it and it will go away!
>>>>
>>>
>>> Relax.
>>>
>>> No one is ignoring it. It's *hard*. Hard problems
>>> take time and energy to
>>> solve.
>>>
>>> Unfortunately, I don't know how to fix it. Do you?
>>>
>>> -- Rex
>>>
>>> --
>>> fedora-list mailing list
>>> fedora-list(a)redhat.com
>>> To unsubscribe:
>>> https://www.redhat.com/mailman/listinfo/fedora-list
>>> Guidelines:
>>> http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
>>>
>>
>> Yes! I have dual boot! I'll switch to Bill Gate's XP Prof and do it
there
>>
>> sorry to have troubled you!
>>
>>
>>
>>
>
> Just a quick query ...
>
> Why not just bring up nautilus or equiv in KDE, right click .iso, and burn
> ??
>
> Most folks stopped using K3B when that functionality was added to the file
> browsers.
>
> Good Luck!
KDE users use K3B.
Hell. Even Gnome users use K3B. I changed to Gnome some months ago and I
can't let go of many KDE apps, K3B has no rival (the other apps are, if
you want to know, amarok, digikam and gwenview).
--
Jose Celestino | http://japc.uncovering.org/files/japc-pgpkey.asc
----------------------------------------------------------------
"One man’s theology is another man’s belly laugh." -- Robert A. Heinlein
5:27 p.m.
--- On Wed, 11/26/08, Tom Horsley <tom.horsley(a)att.net> wrote:
From: Tom Horsley <tom.horsley(a)att.net>
Subject: Re: has K3B been abandoned?
To: fedora-list(a)redhat.com
Date: Wednesday, November 26, 2008, 10:53 PM
On Wed, 26 Nov 2008 14:23:11 -0600
Rex Dieter <rdieter(a)math.unl.edu> wrote:
> Unfortunately, I don't know how to fix it. Do
you?
Yes: go back to the old dvd drivers which were apparently
changed for no reason, because they didn't have this
bug,
and if the change fixed some other problem it was a
much rarer and hard to encounter one, so we are better
off with the old bug than the new one :-).
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines:
http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
somewhere on today's post I was informed K3B was abandoned due to new features in the
file managers.
4:51 p.m.
On Wed, 26 Nov 2008 10:33:21 -0600
Rex Dieter <rdieter(a)math.unl.edu> wrote:
the presence of a bug (arguably here in kernel-space) does not imply
abondonment.
Yea, but there is clearly something strange going on
because the latest bug I see is k3b ejecting the media
then not being able to reload it, yet on the same system
with the same kernel and same drive, the "eject -T"
command is perfectly capable of ejecting and closing
the tray.
4:49 p.m.
On Wed, Nov 26, 2008 at 3:56 PM, Phil Meyer <pmeyer(a)themeyerfarm.com> wrote:
Fred Silsbee wrote:
>
> --- On Wed, 11/26/08, Rex Dieter <rdieter(a)math.unl.edu> wrote:
>
>
>>
>> From: Rex Dieter <rdieter(a)math.unl.edu>
>> Subject: Re: has K3B been abandoned?
>> To: fedora-list(a)redhat.com
>> Date: Wednesday, November 26, 2008, 8:23 PM
>> Fred Silsbee wrote:
>>
>>
>>>
>>> THIS is why I no longer post to bugzilla!
>>> Ignore it and it will go away!
>>>
>>
>> Relax.
>>
>> No one is ignoring it. It's *hard*. Hard problems
>> take time and energy to
>> solve.
>>
>> Unfortunately, I don't know how to fix it. Do you?
>>
>> -- Rex
>>
>> --
>> fedora-list mailing list
>> fedora-list(a)redhat.com
>> To unsubscribe:
>> https://www.redhat.com/mailman/listinfo/fedora-list
>> Guidelines:
>> http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
>>
>
> Yes! I have dual boot! I'll switch to Bill Gate's XP Prof and do it there
>
> sorry to have troubled you!
>
>
>
>
Just a quick query ...
Why not just bring up nautilus or equiv in KDE, right click .iso, and burn
??
Most folks stopped using K3B when that functionality was added to the file
browsers.
Good Luck!
KDE users use K3B.
--
Fedora 9 : sulphur is good for the skin
( www.pembo13.com )
3:56 p.m.
Fred Silsbee wrote:
--- On Wed, 11/26/08, Rex Dieter <rdieter(a)math.unl.edu> wrote:
> From: Rex Dieter <rdieter(a)math.unl.edu>
> Subject: Re: has K3B been abandoned?
> To: fedora-list(a)redhat.com
> Date: Wednesday, November 26, 2008, 8:23 PM
> Fred Silsbee wrote:
>
>
>> THIS is why I no longer post to bugzilla!
>> Ignore it and it will go away!
>>
> Relax.
>
> No one is ignoring it. It's *hard*. Hard problems
> take time and energy to
> solve.
>
> Unfortunately, I don't know how to fix it. Do you?
>
> -- Rex
>
> --
> fedora-list mailing list
> fedora-list(a)redhat.com
> To unsubscribe:
> https://www.redhat.com/mailman/listinfo/fedora-list
> Guidelines:
> http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
>
Yes! I have dual boot! I'll switch to Bill Gate's XP Prof and do it there
sorry to have troubled you!
Just a quick query ...
Why not just bring up nautilus or equiv in KDE, right click .iso, and
burn ??
Most folks stopped using K3B when that functionality was added to the
file browsers.
Good Luck!
3:10 p.m.
--- On Wed, 11/26/08, Nigel Henry <cave.dnb2m97pp(a)aliceadsl.fr> wrote:
From: Nigel Henry <cave.dnb2m97pp(a)aliceadsl.fr>
Subject: Re: has K3B been abandoned?
To: "Community assistance, encouragement, and advice for using Fedora."
<fedora-list(a)redhat.com>
Date: Wednesday, November 26, 2008, 9:02 PM
On Wednesday 26 November 2008 20:15, dexter wrote:
> On Wed November 26 2008 15:59:49 Fred Silsbee wrote:
> > after downloading F10 for 9.5 hours,
>
> Downloading on release day is for n00bs, I learnt this
some time back!
> take it some days before or after.
>
> ...dex
9.5 hours is peanuts. Try it on dialup. Downloading my 6 cd
iso's for F9 took
between 12, and 14 days. You need a lot of patience when on
dialup.
I'm not even considering F10 at the moment. I'll
have to psyche myself up once
again, before going for the F10 iso downloads.
Regarding burning. I've no experience with burning to
dvd media, but have read
that Plextor optical drives, expensive as they are, do have
problems.
I always burn to cd at the lowest speed (I did have
problems burning at higher
speeds with K3b), and havn't had any failures when
burning at the lowest burn
speeds.
You mention that you have 2 burners, the Plextor one, and
the Sony one, and
when you had the dvd media in the Sony one, K3b
couldn't find the media.
That's probably no surprise, as K3b's
config/preferences is no doubt set to
look for media in the block device which is set for the
Plextor optical
drive.
Saying that though, looking at K3b's settings >
configure K3b > Devices. It
says here.
<quote>
K3b tries to detect all your devices properly. You can add
devices that have
not been detected, and change the block values by clicking
in the list. If
K3b is unable to detect your drive, you need to modify
their permissions to
give K3b write access to all devices.
< end quote>
Looking at the Devices page on this machine which only has
one optical drive,
the line, "System device name" says /dev/scd0
(4.0.0).
There is an "Add Device" button on the devices
page. I'd suggest using that,
and entering /dev/scd1, which may well pick up your Sony
optical drive.
Then (perhaps after a reboot) see if K3b will detect dvd
media in your Sony
optical drive.
Just some thoughts, and only trying to help.
Nigel.
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines:
http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Thanks lots of great ideas! I now remember years ago angry posts somewhere about the
failed verify.
The verify was not the problem (see original post). The big problem was the locking up of
my drive and the ruining of 4 blanks! I had to reboot! If there is an error, kill the
whole thing and unlock the drives.OK!
The eject even locked up and after I did a kill -9, something was still running as
evidenced by GKRellm. I had to reboot!
F9 only took 2-3 hours and that is because I waited a few weeks after release.
Hey...email me and I'll burn the CDs or DVDs and mail them to you!
2:55 p.m.
On Wed, Nov 26, 2008 at 2:48 PM, Fred Silsbee <fredsilsbee(a)yahoo.com> wrote:
--- On Wed, 11/26/08, Rex Dieter <rdieter(a)math.unl.edu> wrote:
> From: Rex Dieter <rdieter(a)math.unl.edu>
> Subject: Re: has K3B been abandoned?
> To: fedora-list(a)redhat.com
> Date: Wednesday, November 26, 2008, 8:23 PM
> Fred Silsbee wrote:
>
> > THIS is why I no longer post to bugzilla!
> > Ignore it and it will go away!
>
> Relax.
>
> No one is ignoring it. It's *hard*. Hard problems
> take time and energy to
> solve.
>
> Unfortunately, I don't know how to fix it. Do you?
>
> -- Rex
>
> --
> fedora-list mailing list
> fedora-list(a)redhat.com
> To unsubscribe:
> https://www.redhat.com/mailman/listinfo/fedora-list
> Guidelines:
> http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Yes! I have dual boot! I'll switch to Bill Gate's XP Prof and do it there
sorry to have troubled you!
I am guessing you don't useful help from others often.
--
Fedora 9 : sulphur is good for the skin
( www.pembo13.com )
3:02 p.m.
On Wednesday 26 November 2008 20:15, dexter wrote:
On Wed November 26 2008 15:59:49 Fred Silsbee wrote:
> after downloading F10 for 9.5 hours,
Downloading on release day is for n00bs, I learnt this some time back!
take it some days before or after.
...dex
9.5 hours is peanuts. Try it on dialup. Downloading my 6 cd iso's for F9 took
between 12, and 14 days. You need a lot of patience when on dialup.
I'm not even considering F10 at the moment. I'll have to psyche myself up once
again, before going for the F10 iso downloads.
Regarding burning. I've no experience with burning to dvd media, but have read
that Plextor optical drives, expensive as they are, do have problems.
I always burn to cd at the lowest speed (I did have problems burning at higher
speeds with K3b), and havn't had any failures when burning at the lowest burn
speeds.
You mention that you have 2 burners, the Plextor one, and the Sony one, and
when you had the dvd media in the Sony one, K3b couldn't find the media.
That's probably no surprise, as K3b's config/preferences is no doubt set to
look for media in the block device which is set for the Plextor optical
drive.
Saying that though, looking at K3b's settings > configure K3b > Devices. It
says here.
<quote>
K3b tries to detect all your devices properly. You can add devices that have
not been detected, and change the block values by clicking in the list. If
K3b is unable to detect your drive, you need to modify their permissions to
give K3b write access to all devices.
< end quote>
Looking at the Devices page on this machine which only has one optical drive,
the line, "System device name" says /dev/scd0 (4.0.0).
There is an "Add Device" button on the devices page. I'd suggest using that,
and entering /dev/scd1, which may well pick up your Sony optical drive.
Then (perhaps after a reboot) see if K3b will detect dvd media in your Sony
optical drive.
Just some thoughts, and only trying to help.
Nigel.
2:48 p.m.
--- On Wed, 11/26/08, Rex Dieter <rdieter(a)math.unl.edu> wrote:
From: Rex Dieter <rdieter(a)math.unl.edu>
Subject: Re: has K3B been abandoned?
To: fedora-list(a)redhat.com
Date: Wednesday, November 26, 2008, 8:23 PM
Fred Silsbee wrote:
> THIS is why I no longer post to bugzilla!
> Ignore it and it will go away!
Relax.
No one is ignoring it. It's *hard*. Hard problems
take time and energy to
solve.
Unfortunately, I don't know how to fix it. Do you?
-- Rex
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines:
http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Yes! I have dual boot! I'll switch to Bill Gate's XP Prof and do it there
sorry to have troubled you!
1:19 p.m.
--- On Wed, 11/26/08, dexter <dex.mbox(a)googlemail.com> wrote:
From: dexter <dex.mbox(a)googlemail.com>
Subject: Re: has K3B been abandoned?
To: "Community assistance, encouragement, and advice for using Fedora."
<fedora-list(a)redhat.com>
Date: Wednesday, November 26, 2008, 7:10 PM
On Wed November 26 2008 16:50:47 Rex Dieter wrote:
> I can understand the frustration, but I'm failing
to see how these recent
> comments are in any way constructive or leading toward
helping find a
> solution.
>
> -- Rex
So, we should suffer in silence. Did you know being vocal
is a way to vent
frustration.
...dex
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines:
http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
also a way of getting things done...it bothers me when I see people streaming away from
Fedora because of something like this
yes I've heard it already...Fedora is not for everybody
I did a contract job where they had centos...I had never heard of it!
It was Fedora after castration! EEEWWWW!
If there is an error don't lock up my cpu and DVD drive.
Problem past! I have 3 good copies (verified several ways)
Are you and rex dieter the same guy?
1:10 p.m.
On Wed November 26 2008 16:50:47 Rex Dieter wrote:
I can understand the frustration, but I'm failing to see how
these recent
comments are in any way constructive or leading toward helping find a
solution.
-- Rex
So, we should suffer in silence. Did you know being vocal is a way to vent
frustration.
...dex
1 p.m.
--- On Wed, 11/26/08, Anne Wilson <annew(a)kde.org> wrote:
From: Anne Wilson <annew(a)kde.org>
Subject: Re: has K3B been abandoned?
To: "Community assistance, encouragement, and advice for using Fedora."
<fedora-list(a)redhat.com>
Date: Wednesday, November 26, 2008, 6:50 PM
On Wednesday 26 November 2008 16:50:47 Rex Dieter wrote:
> Fred Silsbee wrote:
> >> > K3b is a piece of work...
> >>
> >> the presence of a bug (arguably here in
kernel-space) does
> >> not imply abondonment.
> >
> > The no verify ISO write is very very old!
> > I remember it back when I was reporting to
bugzilla!
>
> I'm aware of that. All signs (still) point to a
kernel issue, potentially
> limited to certain brands/models of burners.
>
That has to be the most likely explanation. Here k3b
verifies on some boxes
but not on others.
Anne
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines:
http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
THIS is why I no longer post to bugzilla!
Ignore it and it will go away!
Anybody else have the iso dvd burn noverify problem?
12:50 p.m.
On Wednesday 26 November 2008 16:50:47 Rex Dieter wrote:
Fred Silsbee wrote:
>> > K3b is a piece of work...
>>
>> the presence of a bug (arguably here in kernel-space) does
>> not imply abondonment.
>
> The no verify ISO write is very very old!
> I remember it back when I was reporting to bugzilla!
I'm aware of that. All signs (still) point to a kernel issue, potentially
limited to certain brands/models of burners.
That has to be the most likely explanation. Here k3b verifies on some boxes
but not on others.
Anne
11:29 a.m.
try to run unlimit before running k3b
try with a rw disk
On 11/26/2008 1:59 PM, Fred Silsbee wrote:
K3b is a piece of work...
I have 2 CD/DVD burner drives
Plextor $120+
Sony $50
Fedora doesn't like the Plextor...I guess
after downloading F10 for 9.5 hours, I tried to burn a ISO-DVD.
The simplest operation?
I wasted 4 blanks making 3 final copies that haved been checked to be good!.
The Plextor would get an error and then hang K3B
I'd kill it with kill -9 and then the drive would be locked up and even hung the
eject command.
I had to reboot to open the drive. Sometimes I have to reboot to do a second operation!
and even once the "bring things back" facility had the #$%& thing running
again.
OH YES! an old error reported forever
When making an ISO DVD, the verify write facility still doesn't work
even on the Sony drive. It says "couldn't find a DVD to verify.
Make things easy: if there is an error:
(1) release the drive announcing ithat the DVD is no longer blank!
(2) eject the DVD
(3) terminate all processes and subprocesses that stay running(i.e. die and go away)
(4) work on the program some more.
--
------------
Itamar Reis Peixoto
e-mail/msn: itamar(a)ispbrasil.com.br
sip: itamar(a)ispbrasil.com.br
skype: itamarjp
icq: 81053601
+55 11 4063 5033
+55 34 3221 8599
10:53 a.m.
--- On Wed, 11/26/08, Rex Dieter <rdieter(a)math.unl.edu> wrote:
From: Rex Dieter <rdieter(a)math.unl.edu>
Subject: Re: has K3B been abandoned?
To: fedora-list(a)redhat.com
Date: Wednesday, November 26, 2008, 4:50 PM
Fred Silsbee wrote:
>> > K3b is a piece of work...
>>
>> the presence of a bug (arguably here in
kernel-space) does
>> not imply abondonment.
> The no verify ISO write is very very old!
> I remember it back when I was reporting to bugzilla!
I'm aware of that. All signs (still) point to a kernel
issue, potentially
limited to certain brands/models of burners.
I can understand the frustration, but I'm failing to
see how these recent
comments are in any way constructive or leading toward
helping find a
solution.
-- Rex
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines:
http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
happy to discuss off mailing list fredsilsbee(a)yahoo.com
10:50 a.m.
Fred Silsbee wrote:
> > K3b is a piece of work...
>
> the presence of a bug (arguably here in kernel-space) does
> not imply abondonment.
The no verify ISO write is very very old!
I remember it back when I was reporting to bugzilla!
I'm aware of that. All signs (still) point to a kernel issue, potentially
limited to certain brands/models of burners.
I can understand the frustration, but I'm failing to see how these recent
comments are in any way constructive or leading toward helping find a
solution.
-- Rex
10:43 a.m.
--- On Wed, 11/26/08, Rex Dieter <rdieter(a)math.unl.edu> wrote:
From: Rex Dieter <rdieter(a)math.unl.edu>
Subject: Re: has K3B been abandoned?
To: fedora-list(a)redhat.com
Date: Wednesday, November 26, 2008, 4:33 PM
Fred Silsbee wrote:
> K3b is a piece of work...
the presence of a bug (arguably here in kernel-space) does
not imply
abondonment.
-- Rex
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines:
http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
The no verify ISO write is very very old!
I remember it back when I was reporting to bugzilla!
3:25 p.m.
I hope it's still supported...It recognizes my CD & DVD-R runs great on
CentOS5 (close to RHEL5)
# uname -r
2.6.18-92.1.22.el5
and puts a Blank DVD-R Dicc icon on the Desktop
I trying to get MongoArchive to backup my new, clean installation but it's
wimmy scripts can't find
my DVD drive, because it looks like it doesn't show up in a grep of the
mount command or a mount
on /mnt/cdrom and is not auto-mounted. My /etc/fstab:
# /dev/hdc /media/cdrom auto
pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed 0 0
/dev/hdd /media/cdrecorder auto
pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed 0 0
How does K3B find the DVD drive in my case /dev/hdd?
thanks,
-Frank
--
View this message in context:
http://n2.nabble.com/has-K3B-been-abandoned--tp1581287p2380473.html
Sent from the fedora mailing list archive at Nabble.com.
8:48 a.m.
On Thursday 27 November 2008, Anne Wilson wrote:
On Thursday 27 November 2008 05:07:21 Gene Heskett wrote:
> Generally, I gave up on asking k3b to verify anything. Why? Because when
> its about to do the verify read, it ejects the disk and immediately pulls
> it back in. Then it waits for the disk to be recognized by the drive NOT!
Again, it depends on the drive. That happens on some of my boxes but not
all of them. For ISOs, though, it's just as easy to do an md5sum (or
sha1sum if you prefer it).
Anne
Anne, I have never had a drive, and by now I've had 7 or 8 of them hit the
bin, a computer compatible cd or dvd drive that recognized a disk in under 30
seconds. The current one in this box is:
scsi 6:0:1:0: CD-ROM HP DVD Writer 1040d EH24 PQ: 0 ANSI: 5
and it take it about 45 seconds to read and register a disk before it is
accessible to mount it, and has done that since day one. It claims to be a
16x drive, but at 16x the recording can't be seen and isn't readable later,
so I run it at 4x and it leaves a nicely visible recorded area that reads in
any other dvd.
I just installed the F9 respin on an older hp box, and the dvd reader in it,
the OEM RO drive hp puts in at the factory, takes over a minute when booted
to the install disk in order that the diskcheck function of the install disk
can run. I put one of my original but slow dvd writers in the box that runs
my milling machine, and it has always taken 40 some seconds to become ready
for outside access when a disk is inserted.
Some older cd readers may do that in 10 seconds, but I've never had one faster
than that unless it was some specialty thing in the bottom of a tv. But
those are stripped, emasculated versions, one Magnavox a neighbor owns can't
even play a vcd I'd made of their daughters wedding. I tried several
different video recording formats before I hit one that player could handle.
But, it was ready in just 4 or 5 seconds. Sometimes simple is faster.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
F: When into a room I plunge, I
Sometimes find some VIOLET FUNGI.
Then I linger, darkly brooding
On the poison they're exuding.
-- The Roguelet's ABC
5538
days inactive
5630
days old
46 comments
17 participants
participants (17)
-
Anne Wilson -
Arthur Pemberton -
bennett78 -
D. Hugh Redelmeier -
dexter -
Fred Silsbee -
Gene Heskett -
itamar -
Jose Celestino -
linux guy -
Michael Schwendt -
Nigel Henry -
Phil Meyer -
Rex Dieter -
Robin Laing -
Tim -
Tom Horsley