nero

[Igor Gueths]

Hi Greg. What version of Cd creator did you use when you burned the Cd? I am using version 5 platinum, which I got for free (no way I would buy it). Smile. Anyway, when I set the filesystem to iso9660 and try to add speakup-1.00.tar.gz or linux-2.4.18.tar.gz to the Cd project, I actually get a box that displays a re-named version of the file. If I tell it not to change the name, it doesn't get added to the Cd project or layout. I was just asking about the version you used because I could just dig up the version you used, if I knew it wouldn't give me any problem. Thanks for the help! 
----- Original Message ----- 
From: Gregory Nowak <gnowak1 at uic.edu>
To: <speakup at braille.uwo.ca>
Sent: Sunday, March 03, 2002 9:52 PM
Subject: Re: nero


No, the file was simply burned as speakup-1.00.tar.gz, no file renaming took place. I am using slackware 8.0 with my own kernel 2.4.18 that includes the iso9660 fs and does not build it as a module. You are right, the behavior you're describing is strange from my point of view. Also, when I untared the file from the cd on a gnu/linux box, tar gave me no errors.
Greg


On Sun, Mar 03, 2002 at 09:07:54PM -0500, Igor Gueths wrote:
> Hi Greg. But if you had something like speakup-1.00.tar.gz, did your file get re-named to speaku~1.gz if you are using ms-dos 8 character filename, or speakup_1_00_tar.gz if using 30-character filename? Also, once I coppied the file from the Cd to my linux box, tar terminated saying that there were too many corrupted garbage bytes or something. Did this happen to you? What distro are you using? If you are using Debian, are you using an iso9660 module that was installed during the installation process? Because I am not using a module because I didn't think that I needed it. The reason is that I installed my system using the idepci kernel image. I got to the modules section, and didn't install the iso9660 module because I thought I didn't need it. I installed the base system and installed packages using apt with no problems. But I can't untar an archive that I burned from a winBlows box and coppied to /usr/src? This doesn't make sense. I can't seem to figure out where the archive is getting corrupted. Any insight into this would be apreciated. Thanks in advance! As this post is quite long, please try to quote the parts you are replying to if possible. It just makes it easier to follow. Thanks again!
> 
> Igor
> ----- Original Message ----- 
> From: Gregory Nowak <gnowak1 at uic.edu>
> To: <speakup at braille.uwo.ca>
> Sent: Sunday, March 03, 2002 8:31 PM
> Subject: Re: nero
> 
> 
> > On Sun, Mar 03, 2002 at 05:33:33PM -0500, Igor Gueths wrote:
> > has anyone successfully used Adaptec to make a Cd with the speakup or linux kernel archives, and then put them on the linux box, and untar it with no problems? 
> > 
> > 
> > Yes. Simply choose the iso 9660 filesystem instead of joliet. I've put tar.gz and tar.bz2 archives on more then one cd with easy-cd creator, so I know that it works.
> > All of that is easier with mkisofs and cdrecord though once you get it all set up.
> > Greg
> > 
> > 
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup at braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> 
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup at braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
Speakup at braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com