home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Frozen Fish 1: Amiga
/
FrozenFish-Apr94.iso
/
information
/
problems
< prev
next >
Wrap
Text File
|
1994-04-07
|
8KB
|
177 lines
REPORTING PROBLEMS
(Updated 4/7/94)
If you experience any problems reading files off this CD-ROM, please
read this entire file and try all the suggested tests before contacting
me for help. I will be happy to try to resolve such problems once you
have tried the suggested tests and gathered as much information as
possible about your problem.
----------------------
CD-ROM DRIVER SOFTWARE
----------------------
Since beginning CD-ROM distributions, I have tested many different CD-ROM
driver packages (but not all of them), and found problems with many of
them. The distributers of the software have been very responsive about
fixing any bugs found, so current versions of CD-ROM drivers from third
party vendors should work fine. I strongly suggest that you stay current
with the latest version of whatever drivers you are using.
To see if your driver is capable of correctly reading every file on this
CD-ROM, run the following test, which may take between 2 and 24 hours
depending upon what software you are using, the speed of your drive, what
controller card you have, what CD-ROM drive you have, etc, etc. Be sure
that you have arranged for brik to be in your command search path and for
ixemul.library to be found in your LIBS: assign path.
cd FrozenFish-Apr94:
stack 100000
brik -Cb <CrcList or brik -Cb <crclist >ram:logfile
The test should run with no output to either the screen or the logfile, as
the case may be. If brik fails to find or correctly read any file on the
CD-ROM, it will generate a line of output giving the file name and an
appropriate error message. If you do get errors, I suggest sending the
list of files that have problems to the supplier of your CD-ROM software,
and inquire about an update.
In order to verify that the problem really does lie with the software
driver you are using, I suggest that you also try the freely distributable
AmiCDROM driver, which can be found on this CD-ROM in:
BBS/ALib/d9xx/d935/AmiCDROM.lha
This is one of the packages that I test every CD-ROM with, so I know that
it will work with this driver. If it does not work, then your problem
is most likely with your CD-ROM drive or you have a defective disk. I
have yet to find one defective disk, after more than 6 months of doing
CD-ROM distributions, so that should be the last thing you suspect.
If you do contact me to report a problem please include as many relevant
details about your hardware and software configuration as you can, and
in particular, what versions of the driver software you have tried.
------------------
REPORTING PROBLEMS
------------------
If you have problems running some program on this disk, or find bugs in a
program, you should report these problems to the author of the program, not
to me. I likely will not be able to help you and dealing with such problem
reports takes time away from other projects, like getting the next disk
out. Also, I generally have no more additional contact information for
authors than what is already provided on the CD-ROM, so please don't send
reports to me asking me to "pass them on" to the author.
About the only exception to this is problems with the GNU utilities.
Problems that appear to be Amiga specific should be reported to me. Other
problems, particularly if you can duplicate them on a UNIX system running
the same version of the GNU software without any Amiga specific patches,
should be reported to the FSF.
In summary, please only report problems to me when it seems like I'm the
most obvious person to deal with them. The address for reporting problems
to me is:
Amiga Library Services
610 N. Alma School Road, Suite 18
Chandler, AZ 85224-3687
U.S.A.
You can also FAX them to me at (602) 917-0917.
------------------------------------
COMPATIBILITY WITH NON-AMIGA SYSTEMS
------------------------------------
== ISO-9660 LEVELS ==
The ISO-9660 standard defines three "levels of interchange":
Level 1: Each file extent must be recorded on contiguous sectors.
A file name must consist of <= 8 characters + "dot" +
<= 3 characters (commonly called "8.3 names").
A directory name must consist of <= 8 characters.
Level 2: Each file extent must be recorded on contiguous sectors.
A file name must not be longer than 31 characters. It must
contain a "dot".
A directory name must not be longer than 31 characters.
Level 3: A file name must not be longer than 31 characters. It must
contain a "dot".
A directory name must not be longer than 31 characters.
In addition, there are two character classes that specify what characters
can be used in file and directory names:
d-characters: Upper-case letters, digits, and underscore ('_').
These characters can be understood by any ISO compliant
system.
d1-characters: Any character.
The interpretation of these characters is subject to
"agreement" between the system writing the CD-ROM and
the system reading it.
Most CD-ROM's intended for the IBM-PC market conform to level 1d of the
standard, while Amiga CD-ROM's tend to be closer to level 2d1, however
don't fully comply because they may have filenames without dots in them.
== Rock Ridge Interchange Protocol ==
Only CD-ROM's that conform to level 1d are guaranteed to be readable on all
systems that support ISO-9660. Because of this limitation, an extension to
the standard called the "Rock Ridge Interchange Protocol" has been developed
by the CD-ROM industry and is widely supported on a number of different
operating systems, including most UNIX systems and some MS-DOS and Apple
systems.
When read with a software driver that understands the Rock Ridge extensions,
a CD-ROM recorded with Rock Ridge extensions appears as a CD-ROM containing
30 character filenames with no restrictions on the characters used in
filenames, while still being ISO-9660 level 1d compliant and thus fully
readable by software drivers that do not understand the Rock Ridge
extensions. This is how most of the rest of the CD-ROM industry produces
and uses CD-ROM's that are compatible between the different systems.
Unfortunately, support for the Rock Ridge extensions is not common in the
Amiga CD-ROM market, and probably will not be until Commodore's standard
CD-ROM mastering software and drivers support Rock Ridge. The way Amiga
CD-ROM's preserve the ability to use long filenames with no limitations on
the character set, is to almost conform to level 2d1 of the ISO-9660
standard, and thus are incompatible with systems that only support level 1d
plus Rock Ridge extensions. Apparently this includes many (if not most)
MS-DOS systems, and quite a few UNIX systems.
== Bottom Line ==
The bottom line is that many producers of Amiga CD-ROM's, including me, wish
to preserve the original AmigaDOS filenames. This is absolutely required
for bootable CD-ROM's for the CDTV and CD32, and CD-ROM's where it is
desired to run the software directly off the CD-ROM (I.E. more than simply a
collection of "lha archives"). Even with lha archives, it makes it much
easier to keep track of where various versions of some program can be
found if the names of the archives are not munged to comply with the
strictest level of the ISO standard.
These CD-ROM's are not strictly compliant to the ISO-9660 standard, and the
point in the standard that they are closest to (level 2d1) is much more
"liberal" than what is tolerated by most PC systems and some Unix systems.
Thus I have no way to predict whether a specific non-Amiga system will be
able to correctly read my CD-ROM's (or any other Amiga CD-ROM's that don't
strictly conform to ISO-9660 level 1d) because it depends almost 100% on the
specific software driver which is responsible for reading the CD-ROM. In
most cases, asking your software vendor what level of ISO-9660 their
software complies with will not be very informative, and the only way to
know for sure is to get a CD-ROM and try it.
Some non-Amiga users have reported complete success at accessing all the
files, but sometimes only after consulting their software or hardware vendor
for appropriate configuration information and patches to the system's driver
software. Note that positive reports like "everything was fine" are just
as important as negative reports like "nothing worked". Otherwise the only
time I hear about the results is when people have problems.