From zaphod42@u.washington.edu Wed Aug 15 16:30:12 2001 Received: from jason04.u.washington.edu (jason04.u.washington.edu [140.142.8.53]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7FNUB020088 for ; Wed, 15 Aug 2001 16:30:11 -0700 Received: from dante15.u.washington.edu (zaphod42@dante15.u.washington.edu [140.142.15.84]) by jason04.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7FNU9r29406 for ; Wed, 15 Aug 2001 16:30:09 -0700 Received: from localhost (zaphod42@localhost) by dante15.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7FNU8X64216 for ; Wed, 15 Aug 2001 16:30:08 -0700 Date: Wed, 15 Aug 2001 16:30:08 -0700 (PDT) From: "'Lumberjack' A. Parker" To: UW Linux Group Subject: Re: xcdroast problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 7.2? I don't think there is a redhat 7.2 yet. I checked the xcdroast site and I see RPMs for RedHat 7.1 and SuSE 7.2. If you grabbed the SuSE rpms you might want to try uninstalling them and trying the RedHat ones instead. As for what that error actually means, I'm not exactly sure. Andy ------------------------------ "...it's no challenge to destroy the weak." - Abner Doon, _Breaking the Game_, Orson Scott Card zaphod42@u.washington.edu On Wed, 15 Aug 2001, Steven C Cramer wrote: > Dear all: > > I recently tried updating xcdroast. I am using Redhat 7.1. The xcdroast > site only had update for 7.2, which others have assured me would work. I > downloaded all the rpms as directed, I can run xcdroast, master > tracks, etc, EXCEPT > after I make tracks and go to burn, I'm told of the following Error > writing tracks: > > Calling: /usr/lib/xcdroast-0.98/bin/xcdrwrap CDRECORD dev= "1,6,0" > fs=4096k -v -useinfo speed=12 -dao -eject -pad -data "/dos/track-01.img" > ... > > pregap1: -1 > cdrecord: Invalid argument. Cannot get mmap for 4198400 Bytes on > /dev/zero. > Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jrg Schilling > > > Does anyone have a suggestion as to how to address this? Many thanks, > > Steve > > > > .