The Add-on Non-OSS CD image is 820.8 MiB. Could someone tell me how I’m
supposed to get that onto a 700MiB CD?
–
Graham P Davis, Bracknell, Berks., UK. E-mail: newsman not newsboy
“I wear the cheese. It does not wear me.”
Use a DVD, it will work just as well. Strictly speaking it’s an ISO image, suitable for either CD or DVD.
If you don’t have a DVD drive, sorry, my sympathies. I can’t speak for the developers on whether they intend to reduce the size for release or not.
ken yap wrote:
>
> Use a DVD, it will work just as well. Strictly speaking it’s an ISO
> image, suitable for either CD or DVD.
>
> If you don’t have a DVD drive, sorry, my sympathies. I can’t speak for
> the developers on whether they intend to reduce the size for release or
> not.
>
>
I tried a DVD but K3B kept telling me to put a CD in. Very frustrating.
–
Graham P Davis, Bracknell, Berks., UK. E-mail: newsman not newsboy
“I wear the cheese. It does not wear me.”
Can’t you choose the Tool called Burn DVD image?
Open K3B 1st (vice click on the ISO) ; select DVD as the device & then “Burn DVD image” should work:)
If not, add Index of /factory/repo/non-oss as a Yast source after the install.
snakedriver wrote:
>
> ken_yap;1994600 Wrote:
>> Can’t you choose the Tool called Burn DVD image?
>
> Open K3B 1st (vice click on the ISO) ; select DVD as the device & then
> “Burn DVD image” should work:)
>
“Should” being the operative word! What the stubborn so-and-so did was to
ignore the selected add-on image and go for the last DVD image it had
used. I then overrode that and got the right image. It started OK but then
failed because the device was allegedly busy. Busy being used by K3B? Then
I couldn’t unmount/eject the DVD. Eventually discovered I eject it by
using Dolphin instead of Konqueror. Then went through the rigmarole again.
Writing has now successfully completed but verification has stalled so I
expect it will fail this step as it always does. Yes - “error while
reading sector 0”. Judging by K3B’s reliability in being wrong, I’m 99%
sure the recording is OK.
Bring back K3B 0.8. Later versions have all been quite shambolic.
> If not, add ‘Index of /factory/repo/non-oss’
> (http://download.opensuse.org/factory/repo/non-oss/) as a Yast source
> after the install.
>
>
–
Graham P Davis, Bracknell, Berks., UK. E-mail: newsman not newsboy
“I wear the cheese. It does not wear me.”
I’m sure it’s wodim and not k3b the one broken.
Actually I’m certain k3b has always been like this. I always recall having to load the .iso in just the right fashion when putting a cd (oversize or not) to a dvd. @snakedriver gave directions. I can’t recall if that is the exact process, I always have to fiddle a bit getting it right. I mean, how often do have to do it, so you like forget 12 months down the line.
Yeah… that k3b design problem…
I stumbled upon this issue about 2 years ago and as I couldn’t find anything using google, I started to analyze the source code.
Well, it’s just simple:
If you click on an ISO, it does an automatic type detection, which is implemented as follows:
< 1GB: hey, it’s a CD!
>= 1GB: hey, it’s a DVD!
plain stupid if you ask me 
But that’s only the auto detection which is only triggered if you click on a ISO image in the file browser.
You can directly select CD or DVD image by just using the menu instead of clicking on the ISO:
Tools -> Burn CD Image
or
Tools -> Burn DVD Image
have fun 
rknapp wrote:
>
> Yeah… that k3b design problem…
>
> I stumbled upon this issue about 2 years ago and as I couldn’t find
> anything using google, I started to analyze the source code.
>
> Well, it’s just simple:
> If you click on an ISO, it does an automatic type detection, which is
> implemented as follows:
> < 1GB: hey, it’s a CD!
>>= 1GB: hey, it’s a DVD!
>
> plain stupid if you ask me
>
> But that’s only the auto detection which is only triggered if you click
> on a ISO image in the file browser.
> You can directly select CD or DVD image by just using the menu instead
> of clicking on the ISO:
> Tools → Burn CD Image
> or
> Tools → Burn DVD Image
>
> have fun
>
>
Yes, we know that. But what you missed is that the stupid system then
ignores what file you’ve selected in the K3B menu and obviously thinks to
itself “this guy hasn’t a frigging clue what he wants - selects a CD iso
then says to burn a DVD image - I’ll find a DVD image for this idiot”.
When it goes through the rigmarole of working out the MD5 for the file you
didn’t ask for, you then have to replace the that file with the one you
selected in the first place.
Also, K3B hasn’t properly verified a written iso for me since version 0.8.
A few years ago when I raised this problem, someone suggested I had a
dodgy drive or disk. The problem has persisted over five drives and three
or four different brands and types of disks. I can’t remember if I raised
a bug report - tut, tut - so I’ll check that and, if not, raise one.
–
Graham P Davis, Bracknell, Berks., UK. E-mail: newsman not newsboy
“I wear the cheese. It does not wear me.”
How would one go about changing the line of code in K3B mentioned in post 9?
One could then set it more like the real sizes like so:
< 700MB: hey, it’s a CD!
>= 701MB: hey, it’s a DVD!
It’s open source it can be redone right?
Here’s one way, there are others:)
I would try starting with something like “k3b-1.65.0alpha1.tar.bz2” @ SourceForge.net: K3b - The CD Creator for KDE: k3b Project: Platform Download
Untar it.
find the file with that code & change it with an editor
Compile IAW the install.txt or readme file except instead of “make install”, I’d use “checkinstall” and build the rpm.
Then, install that;)
snakedriver wrote:
>
> Sagemta;1995164 Wrote:
>> How would one go about changing the line of code in K3B mentioned in
>> post 9?
>> One could then set it more like the real sizes like so:
>> < 700MB: hey, it’s a CD!
>> >= 701MB: hey, it’s a DVD!
>> It’s open source it can be redone right?
>
> Here’s one way, there are others:)
>
> I would try starting with something like “k3b-1.65.0alpha1.tar.bz2” @
> ‘SourceForge.net: K3b - The CD Creator for KDE: k3b Project: Platform
> Download’
> (http://sourceforge.net/project/platformdownload.php?group_id=26138)
>
> Untar it.
>
> find the file with that code & change it with an editor
>
> Compile IAW the install.txt or readme file except instead of “make
> install”, I’d use “checkinstall” and build the rpm.
>
> Then, install that;)
>
>
Nice idea, if one’s that way inclined, but why not go for 1.66 (alpha-2)?
Though, having tried 1.66 (from rpm) by accident, I’d give it a miss.
After 25 years of programming for a living, and after five years
retirement, I still haven’t summoned up much enthusiasm for dipping my
toes back into the water. And I’m not sure that My knowledge of Fortran,
JCL, REXX, etc. would be much use to me.
–
Graham P Davis, Bracknell, Berks., UK. E-mail: newsman not newsboy
“I wear the cheese. It does not wear me.”
It’s not that tough…
Make a folder, copy the tar there; click on it, when it untars, copy it back to the folder
cd to that folder; look at the make.file with an editor & the 1st/2nd paragraph will have dependencies listed; resolve them or get another version that doesn’t create a bunch of dependencies.
use an editor as root & find the code & change it; save to the file & overwrite it. It will just be changing some numbers.
Then its (still in the folder & without reading the install.txt, etc:
“configure”
let that run w/o error(s)
then
“make”
for sure that has to run w/o errors
then
“make install” but, I like “checkinstall” which you may have it install the checkinstall.rpm)
Then look @ /usr/src/packages/RPMS/x86_64 and there should be the rpm
(example: here is one I built doing that very thing /usr/src/packages/RPMS/x86_64/VMware-server-2.0.0-122956.x86_64.rpm)
Then just install the rpm.
Try it. I think you will find it easier than you think & a world of susers will be glad to jump in and help. Then you can come back and tell us all how to compile:)