Date: Mon, 25 Nov 1996 12:13:13 -0800 (PST) From: Doug White <dwhite@gdi.uoregon.edu> To: Gianmarco Giovannelli <gmarco@scotty.masternet.it> Cc: questions@freebsd.org Subject: Re: How to make a FreeBSD cdrom under w95 Message-ID: <Pine.BSI.3.94.961125121213.1255J-100000@gdi.uoregon.edu> In-Reply-To: <3.0.32.19961124030502.00686140@scotty.masternet.it>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 24 Nov 1996, Gianmarco Giovannelli wrote: > 1) I created a big tar of all the files I need under FreeBSD 2.2 . (so I > can store long filenames) > 2) I copied this tar in a msdos drive. > 3) I booted in win95 and I uncompressed the tar archive. (the long file > name are see by w95 but the dos name is now 8.3 with ~ inside.) > 4) I did the cdrom using the the joliet file name (win95 names and dos > names) unicode. > FreeBSD see the name with the dos name, so the cdrom is ok if I use w95, > but when I mount it under FreeBSD I only see the name 8 + 3. > 5) Easycd Pro can make the cdrom with the Romeo coding (W95 only file > names). Is perhaps this name coding better for FreeBSD ? > > > Is possible to create an image of the cdrom under FreeBSD and then burn it > in w95 with easycd pro ? > Or if it is not possible is there a way to do this cdrom ? To get the long filenames back, you must encode using ISO9660 and Rock Ridge extensions. The Windows 95 encoding schemes are not currently supported. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.3.94.961125121213.1255J-100000>