Decompressing a .gz file

Gins · 06-29-2007, 01:45 PM

Thanks jschiwal

So I drag and drop the following two files to the K3b program to burn.

sp2sc-xiso.bin
sp2sc-xiso.cue

This will create bootable CD; I mean .iso CD so I can install the program.
Please tell me if I am wrong

truthfatal · 06-29-2007, 02:05 PM

That won't work Gins. as jschiwal said:

Quote:

Originally Posted by jschiwal

When you go to burn an image in k3b, click on the drop down box on the filetype filter, and select "cue files". The cue file will be used then to load in and burn the .bin file.

Is one way. In the version of K3b that I have, .cue files are already ascocited with K3b, so I just need to click on the .cue file from konqueror and it will automatically load in K3b.

OR, in the quickstart button on K3b's main screen, i can click the "further actions" button, followed by "Burn CD Image" and then select the *.cue file.

Hope that offers a bit of help

dark_negotiator · 06-30-2007, 12:47 AM

not to steal your thread but im trying to do the same thing with trying to get the rar to decompress.
I tried that unrar command but it says command not found.

jschiwal · 06-30-2007, 12:51 AM

Where is the unrar command? It may have been installed in /usr/local/bin. If so, add /usr/local/bin to your path.

dark_negotiator · 06-30-2007, 12:51 AM

nevermind lol I used wine and installed the windows version of winrar. soooo much easier.

Tinkster · 06-30-2007, 04:34 AM

Quote:

Originally Posted by Gins

I downloaded the following file. It is a free one.

unrar-linux-x64.gz
This file is a command line freeware x64 Linux UnRar.
http://www.rarlab.com/rar_add.htm

I created a directory named 'Winrar for Linux' and placed the file inside this folder.

-----------------------------------------------------------

[root@ Winrar for Linux]# tar -xvzf 'unrar-linux-x64.gz'
tar: This does not look like a tar archive
tar: Skipping to next header
tar: Error exit delayed from previous errors
[root@ Winrar for Linux]#
-----------------------------------------------------------
Why couldn't I decompress the file?
It doesn't accept the command ' tar -xvzf ... ' .

And once again you could have saved us (and posterity)
this thread if you had done a
man -k gz

and then read the man pages that are in section (1)
[pertaining to executables]. I still feel that after
all that time you've been a member of LQ you should
at least TRY to resolve some 'problems' (*cough*)
yourself...

Cheers,
Tink

Gins · 06-30-2007, 09:14 AM

I just tried to burn the way our friend 'truthfatal' suggested. It didn't work. I got an error message. Some problems with CDrao.

Then I looked at the .cue file. It is only readable. It is write and executable protected.

I have no experience in these matters. Please tell me whether it is impossible to burn and get an .iso image when it is write protected.

I am using my K3b program.

1. First I select the file.
2. Secondly I click 'Tools'.
3. I click 'Burn CD Image...'
4. Finally, I click the start button.
It checked the MD5 sum and reported fine. However, refuses to burn with an error message.

[K3b 0.12.15] --> The version number of my program

silencestone · 06-30-2007, 10:02 AM

Quote:

Originally Posted by Gins

I just tried to burn the way our friend 'truthfatal' suggested. It didn't work. I got an error message. Some problems with CDrao.

Post the exact error message. Maybe that'll give clues as to what's going wrong...

Quote:

Then I looked at the .cue file. It is only readable. It is write and executable protected.

I have no experience in these matters. Please tell me whether it is impossible to burn and get an .iso image when it is write protected.

...because I haven't had problems burning read-only files before. Folders may be different.

Gins · 06-30-2007, 10:24 AM

Thanks silencstone

The following is the message:

Cdrdao returned an unknown error (code1).
Operation not permitted.
Please report the debugging output in your problem report.

Gins · 07-01-2007, 07:11 AM

It seems none of our friends has any clue about the strange message.
Another idea crossed my mind. It may be K3b recognizes this in a non-acceptable manner;so it yields an error message.

I could try with some other burning program. Could you suggest me a simple program so I could download and install?
The only burning program I have is K3b. It is working fine.

druuna · 07-01-2007, 05:58 PM

Hi,

Quote:

Operation not permitted.

Looks like you aren't the owner of the file and/or the permission are wrong.
Did you unzip as root and use k3b as normal user?

You really need to take a better look at the error message(s)

Gins · 07-02-2007, 05:35 AM

druuna
Thanks for the comments.
I solved the problem. I just downloaded and installed 'gnomebaker' program. It worked smoothly. So this is a bug or some problem in K3b program. I have been using K3b program for many years. I have never heard or used 'gnomebaker' program.

I just tried and it worked!

b0uncer · 07-02-2007, 05:56 AM

Quote:

Ok, about burning the bin file: You state that you use k3b, if that is the case, nothing special needs to be done. Just start k3b and burn the bin file to disk.

Actually it doesn't work that way. If a first-timer just opened k3b up, dragged the iso file to the [data] disc and burned it, the result would be a data disc containing the .bin file. That would be ok if the aim was to backup that single file, but in case the user wanted to burn a bootable disc which contained the information stored in the .bin file, then the user would need to use k3b's "burn image" -tool rather than just write a normal data disc.

Before posting it's a good idea to read the forum rules etc.

If you intend to burn an image file such as .iso on a Windows system instead of Linux one, I recommend a "free" program called imgburn.

druuna · 07-02-2007, 06:05 AM

Hi,

Quote:

Originally Posted by b0uncer

Actually it doesn't work that way. If a first-timer just opened k3b up, dragged the iso file to the [data] disc and burned it, the result would be a data disc containing the .bin file. That would be ok if the aim was to backup that single file, but in case the user wanted to burn a bootable disc which contained the information stored in the .bin file, then the user would need to use k3b's "burn image" -tool rather than just write a normal data disc.

I thought that if the .cue file was in the same dir as the .bin file it would be picked up by k3b. If that isn't the case: My bad! Sorry for the confusion it might have caused.

Quote:

Before posting it's a good idea to read the forum rules etc.

?? Who is this pointed at and why.

b0uncer · 07-02-2007, 06:18 AM

Quote:

?? Who is this pointed at and why.

Everybody should read the rules. It's not something you do after posting bad stuff, it's something you do before posting anything. If you've already read, it's not for you. If you haven't, you should.

I haven't used k3b for a while so correct me if I'm wrong, but why do you use .cue files to burn .bin files onto a disc? Doesn't k3b just have a menu entry for burning image files (in common)? And in the dialog you just select the .bin file and go forward, without any .cue file hassle? I might be wrong (sorry if I am), but to me it sounds like the wrong way to play around with .cue files if the point is to burn a .bin file.

EDIT: I'm sorry but this has got way off the topic already. Me too.