From: Eli Zaretskii Newsgroups: comp.os.msdos.djgpp Subject: Re: Red Ridge CD format Date: Sun, 23 Jan 2000 10:45:50 +0200 Organization: NetVision Israel Lines: 24 Message-ID: References: NNTP-Posting-Host: is.elta.co.il Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: news.netvision.net.il 948617342 20304 199.203.121.2 (23 Jan 2000 08:49:02 GMT) X-Complaints-To: abuse AT netvision DOT net DOT il NNTP-Posting-Date: 23 Jan 2000 08:49:02 GMT X-Sender: eliz AT is In-Reply-To: To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Errors-To: dj-admin AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Sat, 22 Jan 2000, Daniel Barker wrote: > I have written some files to CDs. I am told the system wrote the CDs > with Red Ridge extensions. I wrote them using a UNIX (IRIX) system. You probably mean Rock Ridge extensions, I never heard of Red Ridge. > Under Windows 98, I can see and read all the files but their names are > simplified to 8.3 format. I don't think Windows understands the Rock Ridge extensions. As usual, Microsoft implemented their own way of supporting long file names on a CD (it's called Joliet extensions) which is deliberately incompatible with Rock Ridge. There are ways to burn a CD in a way that both Rock Ridge and Joliet data is there, but you say you cannot rewrite the data, so I guess you are out of luck. Sorry. Perhaps you could find some program out there which can access the CD at a very low level, bypassing the Windows' CDFS layer, and which supports Rock Ridge. That could be useful for copying of files to your hard disk.