@database english/FD/MakeCD.guide @Master english/FD/MakeCD.texi @Width 72 This is the AmigaGuide® file english/FD/MakeCD.guide, produced by Makeinfo-1.64 from the input file english/FD/MakeCD.texi. @Node Main "english/FD/MakeCD.guide" ********************************************** MakeCD Version 2.3 (15-05-1997) English User Manual ********************************************** @{B}CRACK WARNING: we received some "100 % cracked" versions of MakeCD which did not at all behave like fully registered versions. Instead, they pretend to work, but the result is not what you expected. Please do not use them and don't blame us for lame cracks! Instead, download the slightly unlimited version from the MakeCD homepage: http://www.uni-karlsruhe.de/~un60/MakeCD.html If there appear really cracked versions of MakeCD in the future and if these versions cause that almost all people don't register anymore, we will stop developing MakeCD, because it does not only cost us a lot of time, it also costs us a lot of CD-Rs, and we don't want to pay for the development of MakeCD by ourselves. WE do NOT need new drivers and new features for MakeCD -- this also includes DAO. REGISTERED USERS: In your own interrest, you should never use cracked/modified versions of MakeCD. Instead, always get unmodified versions and unlock them using your registration number. @{UB} You can test the most important binaries of this MakeCD distribution for changes by a virus/cracker. Just click on the following button. But please note that the virus/cracker could have changed our `CRCList-binaries', so the test succeeds, altough somebody has tampered with the binaries. In order to be totally sure, you have to check the PGP signature on `CRCList-binaries'. You can find the PGP public key file on our home page. >>> @{"TEST" SYSTEM "Run Execute //briktest-from-doc"} MakeCD binaries! <<< Note that you must have started this guide from Workbench in order to perform this test, otherwise the test might not find all files and might not work. ===================================================================== Note: this manual is still under construction. But it's getting better from release to release. ;-) Sorry for the missing or untranslated parts. We are working on it and soon there will be a complete English manual for MakeCD. @{" Legal " Link "MLEGL"} @{B}Registration@{UB} of MakeCD, legal notes @{" Features " Link "MFEAT"} Feature list of MakeCD @{" Hardware " Link "MHARD"} Supported CD writers and CD-ROM drives @{" Introduction " Link "MINTR"} Introduction to CD writers, MakeCD etc. @{" Installation " Link "MINST"} How to install MakeCD @{" Instructions " Link "MISTR"} Instructions how to use MakeCD @{" Beginner notes " Link "MBEGN"} Notes for beginners @{" Questions " Link "MFAQS"} Frequently asked questions (FAQ) @{" Glossary " Link "MGLOS"} Glossary @{" Support " Link "MSUPP"} Support for MakeCD @{" Authors " Link "MAUTH"} How to Contact the Authors @{" Acknowledgements " Link "MCRDT"} Who participated? @{" Index " Link "INDEX"} Keyword Index @EndNode @Node "MLEGL" "MakeCD.guide/MLEGL" @Toc "Main" @{B}Legal *****@{UB} As with most other software, there are legal conditions associated with MakeCD and you must read them before you first use the program. These conditions shall be interpreted according to the laws of Germany. The German text of these conditions shall take precedence over any translation thereof for the purposes of legal interpretation. @{" Copyright " Link "LCPYR"} Copyright Notice @{" Disclaimer " Link "LDISC"} Use at Own Risk @{" Alterations " Link "LALTR"} What can happen if MakeCD is patched @{" Trademarks " Link "LTRAD"} References may be (Registered) Trademarks @{" Licence Agreement " Link "LLICA"} Your Rights and Responsibilities @{" Registration " Link "LREGI"} How to Get the Registered Version @{" Authors " Link "MAUTH"} How to Contact the Authors @EndNode @Node "LCPYR" "MakeCD.guide/LCPYR" @Toc "MLEGL" @{B}Copyright =========@{UB} MakeCD is subject to Copyright 1996,1997 by Angela Schmidt and Patrick Ohly. All Rights Reserved, for both Software and the documentation. No part of this product shall be distributed, altered, manipulated or copied without the prior written authorisation of the authors. The freely distributable, unregistered version of MakeCD is covered by special conditions regarding its copying and distribution. @EndNode @Node "LDISC" "MakeCD.guide/LDISC" @Toc "MLEGL" @{B}Disclaimer ==========@{UB} The authors shall not be held responsible for any damages or losses, direct or consequential, resulting from the use, or inability to use the software. This applies even if the authors have been made aware of the possibility of losses or damage. @EndNode @Node "LALTR" "MakeCD.guide/LALTR" @Toc "MLEGL" @{B}Alterations ===========@{UB} MakeCD shall @{B}not@{UB} be altered (patched). Those who do this anyway, should not be surprised by extremely uncomfortable side-effects. Of course, MakeCD shall @{B}not@{UB} be distributed if it has been altered -- even when the altered software was based on the freely distributable version. If a modification is thought to be useful, it's worth your while to contact the Authors, who may after all have the desired function in the next version. @EndNode @Node "LTRAD" "MakeCD.guide/LTRAD" @Toc "MLEGL" @{B}Trademarks ==========@{UB} This documentation mentions various hardware and software by name. Such names are often protected Trademarks and their mention in this document shall in no way damage their legal status. @EndNode @Node "LLICA" "MakeCD.guide/LLICA" @Toc "MLEGL" @{B}Licence Agreement =================@{UB} This Agreement is a legal contract between you, the end user, and the authors of MakeCD. You agree to accept the conditions of this contract by use of the software. The @{B}registered@{UB} version with a valid registration number entitles you to use a @{B}single@{UB} copy of the software on @{B}one@{UB} computer (i.e. at only @{B}one@{UB} location for @{B}one@{UB} unit). Further details about the licence can be found in the section @{"Registration fess" Link "LREGF"}. If you want to sell a registered version of MakeCD to another person, @{B}both@{UB} parties have to inform us. Then, we will lock the old registration number and the new owner of this licence will get a new registration number after paying a small handling charge. If you use the @{B}unregistered@{UB} version of MakeCD, you may use as many copies as you like simultaneously, and distribute copies to as many people as you like at no charge. If you use MakeCD for more than 4 weeks, you @{B}must@{UB} get a licence, even if the functionality of the @{B}unregistered@{UB} version of MakeCD fulfills your needs. There is one single exception: if you use MakeCD @{B}only@{UB} to read/play CDDA data, and if you don't create ISO images or write CD-Rs, you don't have to register. However, in that case you must not expect any support from the authors. An @{B}unregistered@{UB} version of MakeCD can be recognized by the startup requester for registration number and user address. You are dealing with an @{B}unregistered@{UB} version when @{B}all@{UB} fields are empty (no default values). It is safest to only ever pass on the original archive -- nothing can go wrong that way. @EndNode @Node "LREGI" "MakeCD.guide/LREGI" @Toc "MLEGL" @{B}Registration ============@{UB} In case you like MakeCD, you should register. The development of MakeCD is very time and cost extensive and we really ask you to support us if you like it. However, if the unregistered version of MakeCD does not work with your configuration, please do not register and stop using MakeCD. Some people obviously think we @{B}must@{UB} add support for their systems after they have registered. But that's not how things work. Of course, we @{B}do@{UB} our best in supporting all systems, but in many cases, we @{B}can't@{UB} support their systems, e.g. because they have SCSI troubles or because we don't have programmer docs for their CD writers. Sorry. Since we don't like to have dissatified users, we really ask you not to register if you are not satisfied with the current version of MakeCD and to stop using MakeCD. If the unregistered version of MakeCD does not support your hardware, the registered version won't support it either. In that case you should check for updates of MakeCD from time to time and register after you found a working update. We reserve the right to lock single registration numbers in future versions of MakeCD without mentioning any reasons (1). Registration numbers are valid for the actual version and often also for following versions. If there are big new features, we might request an update fee. @{" Restrictions " Link "LLRST"} Restrictions of the unregistered version @{" Prices " Link "LREGF"} Registration fees ---------- Footnotes ---------- (1) Of course we do not plan to @{B}do@{UB} that without a good reason @EndNode @Node "LLRST" "MakeCD.guide/LLRST" @Toc "LREGI" @{B}Restrictions of the unregistered version ----------------------------------------@{UB} Compared to the registered version, the unregistered version has a few built-in restrictions: · The name of the CD-ROM and the "Publisher" entry in the primary volume descriptor cannot be changed. · You can write a maximum of ten tracks to a CD-R. Cracked versions of MakeCD often don't work at all. @EndNode @Node "LREGF" "MakeCD.guide/LREGF" @Toc "LREGI" @{B}Registration fees -----------------@{UB} As we think that about DM 200,- to 400,- is a very painful amount of money for a non commercial user to spend on this, we thought up something to still make some profit (as all the other vendors of mastering software): There are three classes of licensing. The more "commercial" the user uses our software (and the more money he makes with it), the higher his or her registration fee will be for MakeCD. Non commercial users pay only a small fee. User who burn CD-ROMs for anyone for a fee pay a currently common amount. User who have their mastered CD-ROM's duplicated commercially at a CD manufacturer (and usually sell them) pay a fee that has to be negotiated with the authors individually. We can think of several ways to license MakeCD here. Just contact us! We hope that this is a fair compromise. Why should someone who creates CD-ROM's just for fun pay the same amount as someone who makes large amounts of money on duplicating and selling CD-ROM's? Please remember that the development of MakeCD could not have been done without investing considerable amounts of money. If you use the software, consider registering seriously and support further development and enhancements to MakeCD as they will be costly, too! Private, non-commercial usage There is a registration fee of DM 75,-. Any CD-ROM's created with MakeCD may only be used for your private non-commercial needs. "Publisher" cannot be modified. CD-ROM recording service, non-commercial duplication. The registration fee is DM 300,-. This is in the range of other currently available software of this type for the Amiga. The recored CD-ROM's may be sold to the respective customers who may not re-duplicate them again for commercial purposes. CD-ROM's created by MakeCD with this license may not be used as masters for pressing CD-ROM's. An exception is the non-commercial duplication with CD-R's. "Publisher" cannot be modified. CD-ROM Manufacturer, commercial duplication. We don't have a standard price for this at this time. Please contact either Angela Schmidt or Patrick Ohly. We'll work up a license together then. This license allows you to press CD-ROM's with masters created by MakeCD. You will also be able to change "Publisher" as needed. The Application-ID field will always contain the serial number (which isn't the same as the registration number) of the registered version. A printed manual is planned, but not yet available. Once it is finished, you will have the opportunity to order it at a small extra fee. Additionally to the licence fee as described, we have to charge some shipping costs: Postage and Packing within Germany 5 DM for floppy only, or floppy with manual (manual is not available yet) Postage and Packing within Europe 5 DM for floppy only 10 DM for floppy with manual (manual is not available yet) Postage and Packing outside Europe (Air Mail) 10 DM for floppy only 20 DM for floppy with manual (manual is not available yet) Express Delivery 15 DM @{B}extra@{UB}. The Registration will be processed immediately and sent via Express delivery. Yet even normal registrations will be processed quickly by my sister - not like SASG where one often has to wait for weeks when Express is not chosen. Please understand that Katrin likes to take the occasional holiday, usually around Whitsun or in August or September, as well as at the start of January. Registrations cannot be processed at these times (usually about one to three weeks) and we beg your understanding. C.O.D. (only in Germany) 8 DM extra. This only makes sense if registering by telephone. A normal MakeCD Private registration will therefore cost 80 DM within Europe, including postage and packing. Express registration and delivery to the USA would cost 75+10+15=100 DM (Registration + postage + Express). You can send a cheque within Germany; the preferred and safest method. Of course you can send cash at your own risk. If need be, the registration can also be done via C.O.D. (for an extra 8 DM). You can also send a cheque from outside of Germany but please consider that this can present some difficulties and disproportionate costs (20 DM is not unusual). Please make sure that theres enough left over to pay your registration after all the additional costs have been paid -- otherwise your registration cannot be completed. As foreign cheques often cause trouble (Eurocheques in DM and cheques from a German bank are fine, though), we prefer foreign registrations to be made by postal money order or using cash (preferably DM, or US Dollars of equivalent value, at least 1 US $ for 1.50 DM). Send your registration (in German, English or if need be, in French) to: Katrin Schmidt Finkenweg 26 89233 Neu-Ulm Germany Tel.: 0731/712316 (9:00 to 21:00 CET) In case you have further questions, have a look at the @{"FAQ" Link "MFAQS"}. @EndNode @Node "MFEAT" "MakeCD.guide/MFEAT" @Toc "Main" @{B}Feature list of MakeCD ======================@{UB} · AMIGA protection bits and file comments in CD-ROM images @{B} MakeCD was the first program that brought this great feature to you. Meeting Pearls IV was mastered with MakeCD.@{UB} · online images (no second partition required) · flexible CD copying · plays CDDA data from CD or from file · supports ISO 9660 and Rock Ridge extensions · requires relatively few memory while generating the ISO 9660 structures. · supports CDTV and CD32 (bootable CD-ROMs possible) · Multivolume and Multisession support · The ISO image can be created on block-orientated devices (e.g. hard disk) and tested before writing a CD-R. · CD Extra support · All source directory trees for the ISO image are optionally put into one distinct subdirectory of the image´s root directory. · locale support (at this time English and German) · online help (Bubblehelp, can be disabled) · font-sensitive layout · style guide adhering (opens e.g. on a Public Screen) · easy to use · writes both data and audio tracks · modular concept (other CD-Writers can be supported if required) · recovery mode (dependent on CD-R driver!) · @{B}best value for your money@{UB}, especially for non-commercial users · compatible (tested on many different configurations) @EndNode @Node "MHARD" "MakeCD.guide/MHARD" @Toc "Main" @{B}Supported CD-Writers and CD-ROM drives ======================================@{UB} Please read the Compatibility List for further information. In general the following CD-Writers are currently supported: · JVC or TEAC compatible CD-writer: · JVC XR-W2010 (see `doc/Compatibility') · JVC XR-W2012 (see `doc/Compatibility') · TEAC CD-R50S · JVC XR-W2001 (not tested, try if it really works!) · JVC XR-W2022 (not tested, try if it really works!) · Pinnacle RCD-1000 (not tested, try if it really works!) · Pinnacle RCD 5040 (not tested, try if it really works!) · MMC compatible CD-writer: · Yamaha CDR 400 · Mitsumi CR2600TE (not tested, try if it really works!) · Philips CDD 3600 (not tested, try if it really works!) · Philips CDD 3610 (not tested, try if it really works!) · Yamaha CDR 200 (not tested, try if it really works!) · Philips CDD 2000 CD-Writer family: · Grundig CDR1001PW · HP SureStore 4020i · Mitsumi CDR 2401 · Philips CDD 2000 · Philips CDD 521 (no test mode!) · Philips CDD 522 · Kodak PCD225 (not tested, try if it really works!) · Plasmon CDR4220 (not tested, try if it really works!) · Philips CDD 2600 CD-Writer family: · HP SureStore 6020i · Philips CDD 2600 · Wearnes CDR632P · Traxdata CDR 2600 (not tested, try if it really works!) · Sony CD-Writers · Sony CDU926S · Microboards of America PlayWrite 2000 (not tested, try if it really works!) · Optima DisKovery 650 CD-R (not tested, try if it really works!) · Smart & Friendly CDR1002 (not tested, try if it really works!) · Smart & Friendly CDR2004 (not tested, try if it really works!) · Smart & Friendly CDR2006 (not tested, try if it really works!) · Sony CDU920S (not tested, try if it really works!) · Sony CDU924S (not tested, try if it really works!) · Sony CDU940S (not tested, try if it really works!) · Sony Spressa 9211 (not tested, try if it really works!) · Sony Spressa 9411 (not tested, try if it really works!) · Sony Spressa 9611 (not tested, try if it really works!) · Yamaha CDR 100 (and compatible drives): · Yamaha CDR 100 · Yamaha CDR 102 · Yamaha CDE 100 · Yamaha CDE 102 · Plasmon CDR-4400 · DynaTek Automation Systems CDM400 (not tested, try if it really works!) · DynaTek Automation Systems CDM240 (not tested, try if it really works!) · Microboards of America PlayWrite 4000 (not tested, try if it really works!) · MicroNet Technology MasterCD Pro (not tested, try if it really works!) · Procom Technology PCDR-4x (not tested, try if it really works!) · Smart & Friendly CDR4000 (not tested, try if it really works!) · Smart & Friendly CDR1004 (not tested, try if it really works!) · Plextor PX-R24CS(i) (and compatible drives): · Ricoh RO-1420C · Ricoh RS-1420C · Turtle Beach 2040R (not tested, try if it really works!) Additionally, MakeCD provides support for the following CD-ROM drives: · ATAPI CD-ROM (with CDDA reading) · NEC CD-ROM (with CDDA reading) · Pioneer CD-ROM (Sony compatible) · Plextor CD-ROM (with CDDA reading) · Sony CD-ROM (with CDDA reading) · Toshiba CD-ROM (with CDDA reading) · any other CD-ROM drive (without CDDA reading) @EndNode @Node "MINTR" "MakeCD.guide/MINTR" @Toc "Main" @{B}Introduction to CD writers, MakeCD etc. ***************************************@{UB} This introduction was written to help you understand better CD-Rs, CD writers and all related information. Additionally, valuable information on how to use MakeCD is included. @{" CD writers " Link "MICDW"} CD writers <=> CD-ROM drives @{" CD-Rs " Link "MICDR"} CD-Recordables @{" Buffers " Link "MIBUF"} Buffering @{" Tracks & sessions " Link "MITUS"} Interesting facts about tracks and sessions @{" Fixation " Link "MISCF"} Fixation of a session or a CD-R @{" Test mode " Link "MITST"} What happens during test mode? @{" Multisession " Link "MIMUS"} How multisession works @{" Multivolume " Link "MIMVC"} How to create multivolume CD-Rs @{" CD-Extra " Link "MICDE"} CD-Extra: audio and data on one CD-R @{" Mixed Mode " Link "MIMIM"} Mixed Mode: audio and data on one CD-R @{" ISO 9660 " Link "MIISO"} ISO 9660 and its background @{" Rock Ridge " Link "MIRRA"} Rock Ridge and AMIGA attributes @{" HFS " Link "MIHFS"} HFS for CD-ROM and hybrid CDs @{" Joliet " Link "MIJOL"} Joliet, the Windows95 extension @{" Romeo " Link "MIROM"} Romeo, another extension @{" Track-at-once " Link "MITAO"} TAO: Momentuous notes about track-at-once @{" Disc-at-once " Link "MIDAO"} DAO: Interesting facts about disc-at-once @{" Compatibility " Link "MICMP"} Which driver is compatible to which CD writer? @EndNode @Node "MICDW" "MakeCD.guide/MICDW" @Toc "MINTR" @{B}CD writers <=> CD-ROM drives ============================@{UB} CD writers usually resemble CD-ROM drives being equipped with either tray or caddy. In general, CD writers are capable of reading from CDs and CD-Rs and writing to CD-Rs. Those are basically CDs that can be written to. Due to the fact that the laser used for writing to the CD-R is significantly heavier than that of a conventional CD-ROM drive, the average transfer rate of a CD writer still is considerably lower as is the average seek time higher. Nevertheless, CD writers can be used for reading CDs and CD-Rs. Just like conventional CD-ROM drives, CD writers can be mounted via a CD filesystem and then be used to access CDs on your workbench screen. Mounting an already writing CD writer with a CD filesystem can result in a defective CD-R if the filesystem attempts to access the CD writer or dis- arranges it otherwise. While MakeCD accesses your CD writer, it @{B}tries@{UB} to recognize and lock all CD filesystems that are mounted on your CD writer. Unfortunately, this does not always work for technical reasons. @EndNode @Node "MICDR" "MakeCD.guide/MICDR" @Toc "MINTR" @{B}CD-Rs, CD-Rs ============@{UB} CD-Rs look like CDs and are mediums that can be written to with CD writers. After the process of writing, CD-Rs may, at least in general, be used with any CD player and CD-ROM drive. In contrast to conventional silvery CD-ROMs, common CD-Rs are green, golden or even blue. Further distinctions between CD-ROMs and CD-Rs concern the CD-R's labelling surface that may vary a lot in size. If labelling is required, do not use peaked objects and write on label area only. Damaging the label surface will always damage the data layer situated below. Take care when using additional labels. Labels attached on just one side will almost certainly make the CD-R wobble inside the CD-ROM drive. Removal of the label will damage the CD-R's surface (reflective layer). In that case you can only use the CD-R as a `coaster'. Be sure to buy larger quantities only of those CD-Rs that you have already tested and that actually work on your system. Some CD-Rs may survive the writing process but later fail on most CD-ROM drives. Some drives may read those CD-Rs flawlessly while others may take a long time to read and still produce read errors. We have had bad experiences with Toshiba drives and certain CD-R brands. Please pay attention to this fact. @EndNode @Node "MIBUF" "MakeCD.guide/MIBUF" @Toc "MINTR" @{B}Buffering =========@{UB} Once the process of writing has started, the CD writer has to write all the data to CD-R @{B}without interruption@{UB}. While in @{"Track-at-once" Link "MITAO"} mode, the finalization of the track is required. While in @{"Disc-At-Once" Link "MIDAO"} mode, the whole CD-R has to be finished. The reason for all this is, that the CD writer writes the data to CD-R several times to allow easier restoration in the event of a defect. While writing the block N, some data of blocks N-1 and N+1 are incorporated into block N @{B}simultaneously@{UB}. If the data of block N+1 doesn't exist, block N logically cannot be written. For that reason, programs for CD writers and the CD writer itself require adequate buffering to ensure that the flow of data @{B}never@{UB} stops. This is because the CD writer may later still restart writing but fail to fill the gap caused by the interruption. CD writers usually feature an internal buffer of 512kb to 2meg. MakeCD @{B}additionally@{UB} employs its own buffer to avoid the eventuality of the CD writer's buffer running low due to a slow flow of data. If reselection for the CD writer is @{B}turned on@{UB}, the SCSI bus will be blocked for a short time only while MakeCD sends data to the CD writer. With reselection @{B}turned off@{UB}, the CD writer will block the SCSI bus most of the time preventing you from reading data from the same SCSI bus. Reading data from the same SCSI bus @{B}with@{UB} reselection @{B}turned off@{UB}, the internal buffer of MakeCD will almost certainly run empty. In this case, a huge buffer of the CD writer comes in handy. If you have to @{B}turn reselection off@{UB} for your CD writer due to SCSI problems, try to read the data from another SCSI bus or from an IDE controller. Otherwise, the internal buffer will only be filled marginally causing the risk of buffer `underrun'. If you neither have another SCSI host-adapter nor an IDE controller as the source for your data, you will have to go with the almost empty buffer of MakeCD. @{B}Then@{UB}, turn `parallel reading/writing' @{B}off@{UB} in the preferences window. This will slightly improve the per- formance. In all other cases, @{B}turn on@{UB} `parallel reading/writing'. Make sure to intensively check your system's stability in test mode! @EndNode @Node "MITUS" "MakeCD.guide/MITUS" @Toc "MINTR" @{B}Interesting facts about tracks und sessions ===========================================@{UB} A finalized CD-R or a CD consists of one or more sessions. Each finalized session incorporates one or more tracks. A track @{B}can only@{UB} be part of one session. A CD-R with multiple sessions may look like this: ---- Lead-In (start of CD und 1. session) ---- (1) ---- track 1 ---- ---- track 2 ---- ---- track 3 ---- ---- Lead-Out (end of 1. session) ---- ---- Lead-In (start of 2. session) ---- (2) ---- track 4 ---- ---- track 5 ---- ---- Lead-Out (end of 2. session) ---- ---- Lead-In (start of 3. session) ---- (3) ---- track 6 ---- ---- Lead-Out (end of 3. session) ---- ---- Lead-In (start of 4. session) ---- (4) ---- track 7 ---- ---- Lead-Out (end of CD and 4. session) ---- Creating a new track requires a comparatively small capacity - about 300kb or 152 blocks plus the actual data for the new track that must be at least 600kb. In contrast, a new session takes up 22.5meg for the fixation of the first session and 13.5meg for the fixation of every next one plus the actual data. The more sessions a CD or CD-R incorporates the longer it takes the CD-ROM drive to read the table of contents (TOC). Given the example above, the index of tracks 1 to 3 (track list) would be stored at (1), that of track 4 and 5 at (2), that of track 6 at (3) and that of track 7 at (4). Therefore, the drive accesses four positions on the CD or CD-R to read the complete track list (TOC). Older CD-ROM drives or CD players not capable of multisession ignore the fact that more tracks are stored at (2) and thus access only tracks 1 to 3. While some CD writers are capable of displaying unfixed tracks in the track list (TOC), others require special commands to access those tracks. CD-ROM file systems can only recognize those tracks if the CD-R is situa- ted in a CD writer (not a CD-ROM drive) @{B}and@{UB} if that CD writer displays these tracks in the track list. If required, MakeCD additionally reads the PMA (a special area of a CD-R) to create an actually complete track list. CD-ROM file systems @{B}cannot@{UB} offer you this feature. Read errors may occur resulting in tracks being left out of the track list. This is commonly found with CD-Rs that contain many sessions. Reinserting the CD-R usually does the trick. CD-ROM drives generally cannot read tracks from unfixed sessions while CD writers can. A CD-ROM drive will only read the complete CD-R once it is fixed or otherwise read only the tracks already fixed. If you intend to use the CD-R exclusively with your CD writer @{B}and@{UB} if your CD writer shows unfixed tracks in the TOC, you may spare fixation of the session for the time being to save space. You may then add more tracks (including data tracks) and fix the session or CD at a later stage. You may thus create multisession tracks without fixing the CD-R, although the term "multisession" doesn`t quite fit here. The function of such a CD-R does not differ from that of a multisession CD-R incorporating fixed data tracks. @EndNode @Node "MISCF" "MakeCD.guide/MISCF" @Toc "MINTR" @{B}Fixation of a session or CD-R =============================@{UB} Users are often confused over whether to fix a session or a CD-R. Hence the following explanation: · Once the CD-R is fixed, you cannot add any more data to it. The CD-R can then only be @{B}read@{UB} from. · Fixing a session automatically creates a new session. All data on the CD-R from the sessions up to the last fixed session may be read. · Having neither fixed the CD-R nor the session usually @{B}prevents@{UB} a CD-ROM drive, unlike a CD writer, from @{B}reading@{UB} the data. Afterwards, you may add other data into the same session without prior fixation of the session saving a lot of space. · Both sessions and the CD-R can only be fixed when the last session incorporates at least one track. Empty sessions may thus not be fixed with either method. · Having fixed a session prevents you from fixing the CD-R in the next step as the fixation of a session @{B}automatically@{UB} creates a new and empty one which itself cannot be fixed. The process of fixation of a session is almost identical to that of a CD-R except that in the latter case @{B}no@{UB} new session is created. As a result, the CD-R is completed. · If you decide not to add any more data to the CD-R, you should fix the CD-R and not just the session. That is because it takes some drives signifi- cantly longer to read a CD-R that had only its sessions fixed searching for nonexisting tracks in the last empty session. @EndNode @Node "MITST" "MakeCD.guide/MITST" @Toc "MINTR" @{B}What happens during test mode? ==============================@{UB} There is a gadget both in the preferences and the writing window that lets you turn test mode on or off. But what happens during test mode? Once you turn on the test mode, the CD writer won`t write for real but just pretend to do so. MakeCD sends data to the writer as if test mode was turned off. The writer then performs almost the same, except that the laser is not activated and thus the CD-R is not written to. Given the fact that the process of writing in real mode and that in test mode are almost identical, the latter is just perfect to find out whether SCSI bus hangups may occur or whether the data is sent at the required speed. During test mode, most CD writers retain which tracks were written at what place. Those tracks are displayed in the target CD-R window track list although they do not really exist. Please note that some CD writers mix up information when sessions or the CD-R are fixed in test mode. We therefore recommend to every user of MakeCD to go through the process of test mode prior to the actual writing. Writing in test mode is also advised when reading data from a slow source drive or in the case of reading data not from an image file but directly from your hard disk (on-the-fly). The stream of data may cease abruptly especially with directories that contain many small files. Finding this to be true is significantly less costly in test mode than it is in real mode. ;-) @EndNode @Node "MIMUS" "MakeCD.guide/MIMUS" @Toc "MINTR" @{B}How multisession works ======================@{UB} What is multisession? Once you create a CD-R, you will sonner or later write the first data track. So far, the CD-R is a conventional CD holding data. Provided there still is free space left on the CD-R you may want to use it, too. This is where multisession comes handy enabling you to incorporate an @{B}older@{UB} track into a new one. For that, MakeCD has to read and remember the contents of this (normally) last data track. MakeCD particularly retains the position on the CD-R where the data is stored. The program then seeks all information about the new data from hard disk except the actual contents of those files. The table of contents written into the new track contains infor- mation on both the data of the old track as well as on the new data. As the actual data of the first track is already stored on the CD-R, all but a short reference to it is required. The data from hard disk however still has to be written to CD-R. In the case of a CD-R consisting of two tracks of which the latter incorporates data of the first one, only the second is added to the third track. If you forgot to add the data of the first track to the second, MakeCD allows you to incorporate both data from first and second track into the third. Data from all three tracks were then accessible through the third track. How does this work with MakeCD? MakeCD offers a very flexible way of creating multisession CD-Rs. You select the tracks to be incorporated into an already existing track via the `ISO settings window'. That is the same window that lets you select directories to be included in the image file. In the case of identical file names, the file of the track or directory scanned first will be selected and all other identical file names will be ignored. After selecting tracks and directories, you may write to CD-R as usual. MakeCD version 2.1 upwards has this multisession feature. @EndNode @Node "MIMVC" "MakeCD.guide/MIMVC" @Toc "MINTR" @{B}How to create multivolume CD-Rs ===============================@{UB} A CD-R can hold several tracks that are recognized as individual volumes by the filesystem provided the filesystem supports multivolume CDs and CD-Rs. To achieve this, write the tracks and fix them as soon as you want a CD-ROM drive to be capable of reading them. For instance, if you intend to write three tracks in a single operation and later want to read those tracks in a CD-ROM drive, fix the session (or the CD-R) as soon as you have written the tracks. If you intend to write the tracks separately and want to read the CD-R in a CD-ROM drive in between, you will have to fix the session before reading the CD-R in a CD-ROM drive. Fixing the current session is required, no matter whether one or more tracks were written into this session since the fixation of the preceding session. Each track of a multivolume CD-R corresponds to an independent volume, as can a hard disk be divided into several partitions.See @{"Fixation" Link "MISCF"}. The major difference between multisession and multivolume is the fact that tracks of multivolume CD-Rs cannot contain data from previous tracks. Multisession on a hard disk would look like this: the first partition had to be a conventional one, the second would hold new data and links to all data on the first partition and the third partiton would contain new data and links to all data on the second partition etc. Implementing multisession on hard disks would be rather confusing and useless. In contrast, the use with CD-Rs makes sense and is advised given the fact that filesystems supporting multivolume are rarely used. A filesystem supporting multivolume would either give access to all tracks (partitions on hard disk) or let you choose the desired track (partition). MakeCD version 2.0 upwards is capable of creating multivolume CD-Rs. Just perform as described above. You will need a filesystem that supports multisession to access the volumes (tracks). @EndNode @Node "MICDE" "MakeCD.guide/MICDE" @Toc "MINTR" @{B}CD Extra: audio and data on one CD-R ====================================@{UB} CD Extra holds the option of a CD-R containing both data and audio (mixed CD-R) that performs like a conventional audio CD which means that you don`t have to skip the first track using it with a CD player. The computer will still recog- nize the included data tracks. And this is how it works: Burn all audio tracks and fix this first session. That`s how your CD player recognizes the audio CD. Afterwards, write a data track within the following session. A filesystem with support for multisession detects this data track and allows access to it. MakeCD version 2.0 upwards has the option to create such CD Extra CD-Rs. Just write to your CD-Rs as described above. @EndNode @Node "MIMIM" "MakeCD.guide/MIMIM" @Toc "MINTR" @{B}Mixed Mode: audio and data on one CD ====================================@{UB} A Mixed Mode CD-R incorporates one data track and one or more audio tracks. The data track is always the first track followed by audio track(s). The session must only be fixed after the audio track(s). Create a list of tracks with MakeCD starting with the data track and continue with as many audio tracks as you like. Then write to CD-R. Any CD-ROM drive will access the data track as no multisession feature is required. When used with a CD player, skip the first track as it is a data track. Please make sure not to play the first track of a Mixed Mode CD or CD-R as this may damage your hifi equipment if your CD player is one of those that don't check for data tracks before playing a track. @EndNode @Node "MIISO" "MakeCD.guide/MIISO" @Toc "MINTR" @{B}ISO 9660 and its background ===========================@{UB} ISO 9660 is a very old filesystem that was developed to allow almost every computer system to access CDs. Out of regard for the then very popular PCs, file names can only consist of capitals A-Z, numerals 0-9 and the sub-stroke `_'. ISO level 1 is additionally restricted to the 8+3 standard. File names must not exceed eight characters in front of and three characters behind the dot. The dot must be present and at least one character, either before or behind the dot is required. ISO level 2 is more flexible - it allows up to 31 characters including the dot. But the same restrictions as above apply: only one dot in all can be used and small letters or even vowel mutation are not allowed. The restrictions above cannot be accepted for the AMIGA as a file and its corresponding icon do not match them. Under the ISO definitions, the file would miss a dot and if a dot was added, the icon file contained two dots, as itself consists of the file name and the ending `.info'. But two dots do not comply with the ISO restrictions. For this reason, it has become a common habit with the AMIGA community to forget about all the restrictions and to use file names as desired. Thus, MakeCD offers a feature called the `ISO 9660 AMIGA'. If selected, MakeCD uses the file names as stored on your hard disk without change. ISO 9660 has a further restriction. There must be no more than eight directory levels. MakeCD ignores this rule and writes as many levels as selected. AMIGA filesystems work flawlessly with more than eight levels, but an option to automatically move directories levels up is planned. @EndNode @Node "MIRRA" "MakeCD.guide/MIRRA" @Toc "MINTR" @{B}Rock Ridge and AMIGA attributes ===============================@{UB} Fans of UNIX computers weren`t too happy about ISO 9660 restrictons and defined an extension called Rock Ridge. A CD or CD-R with Rock Ridge extension is based on ISO 9660 but makes use of space reserved within the ISO norm. Filesystems with support for nothing but ISO 9660 will not detect those Rock Ridge extensions. Therefore, Rock Ridge cannot confuse the filesystem. It is difficult to measure the amount of space that the Rock Ridge extension occupies. It should roughly be of the order of 50 to 150 bytes per file or directory, thus very little. What is the advantage of Rock Ridge? The possibility to use multiuser attributes for unix systems is of little importance for the AMIGA. More important is that fact that the use of file names containing any type of characters is possible through this extension. There is no need to change characters or to shorten file names. A filesystem with support for Rock Ridge also supports ISO 9660 for technical reasons and will show the Rock Ridge file names if the extension was used to create the CD-R. Some of those filesystems feature the option of displaying only the ISO 9660 file names. If your filesystem misses to show the Rock Ridge file names, check whether the options are set correctly. Some filesystems may miss to identify a CD with Rock Ridge extension as such, because with previous versions of Rock Ridge such as v1.09, the identification of Rock Ridge was stored on the CD in another way than it is with version 1.12 which MakeCD makes use of. This is sometimes found with UNIX file systems and if your filesystem only supports RockRidge v1.09, update to v1.12. Around mid-1996, a new standard based on Rock Ridge was developed primarily by Angela Schmidt who worked in close cooperation with other AMIGA pro- grammers and the leading author of Rock Ridge. The standard has since been accepted by the AMIGA community as it is supported by all major file systems such as AmiCDFS, AsimCDFS and CacheCDFS. This implementation offers AMIGA protection bits and file comments on CD-R within the Rock Ridge extension. To save these AMIGA attributes, Rock Ridge extension @{B}is required@{UB}. You can finally backup your data on CD-R. The advantages: instant access and the AMIGA attributes won`t get lost anymore with a suitable filesystem. @EndNode @Node "MIHFS" "MakeCD.guide/MIHFS" @Toc "MINTR" @{B}HFS on CD-ROM and hybrid CDs ============================@{UB} Apple developed its own format for CDs and CD-Rs due to the limitations and insufficiency of ISO 9660 for the MacOS filesystem. MakeCD currently does not support HFS and support is unlikely as there seems to be no need for it. Hybrid CDs are CDs containing both the HFS and ISO 9660 format. The CD will be mounted as an ISO-CD on an AMIGA or a PC and as an HFS-CD on a Macintosh. As the data can be kept separately in ISO 9660 and HFS, the PC and AMIGA users only have access to their programs and the Mac user exclusively to his/her own. @EndNode @Node "MIJOL" "MakeCD.guide/MIJOL" @Toc "MINTR" @{B}Joliet, the Windows95 extension ===============================@{UB} Windows95 introduced a new filesystem format named Joliet. It is based on ISO 9660 and supports all standardized characters such as e.g. Chinese symbols. File names are no longer limited in variety, but in length. MakeCD doesn`t support this extension yet. It is however not certain that we will support it. @EndNode @Node "MIROM" "MakeCD.guide/MIROM" @Toc "MINTR" @{B}Romeo, another extension ========================@{UB} Romeo, too, is an extension supposed to allow more characters on PCs. MakeCD doesn`t support this extension yet and it is rather un- certain that we will ever implement this feature. @EndNode @Node "MITAO" "MakeCD.guide/MITAO" @Toc "MINTR" @{B}TAO: Momentuous notes about track-at-once =========================================@{UB} Most CD writers offer several modes of writing a CD-R. The most common and most important modes are TAO (track-at-once) and DAO (disc-at-once). The method easier to implement is track-at-once. The program sends track by track to the writer that itself takes care of the actual process of writing. The disadvantage of TAO is the fact that most CD writers put in a pause of approximately 2 seconds (152 blocks) between the tracks. This is annoying when you intend to write a live concert to CD-R using more than one track. DAO, with its own new restrictions, provides a solution to this. At the moment, MakeCD has support for TAO only. Support for DAO will follow for certain CD writers. @EndNode @Node "MIDAO" "MakeCD.guide/MIDAO" @Toc "MINTR" @{B}DAO: Interesting facts about disc-at-once =========================================@{UB} Most CD writers offer several modes of writing a CD-R. The most common and most important modes are TAO (track-at-once) and DAO (disc-at-once). While in track-at-once mode, little gaps between tracks have to be accepted. With disc-at-once, all tracks can be written without pauses in between and even the creation of index marks is possible. The CD-R is however limited to one session using disc-at-once. Therefore modern CD writers offer SAO (Session-At-Once), so you can write several sessions in Disc-At-Once mode. MakeCD doesn`t support DAO, but TAO. Support for DAO and SAO will follow for certain CD writers. @EndNode @Node "MICMP" "MakeCD.guide/MICMP" @Toc "MINTR" @{B}Which driver is compatible to which CD writer? ==============================================@{UB} We have tried to give you as many compatibility tips as possible in the file `doc/Compatibility'. Unfortunately, we are not aware of every existing CD writer and we cannot always tell you which driver you need for your CD writer or whether we have a driver for your CD writer. But you can select one driver after the other and try to write a CD-R in test mode (or without test mode). If the driver which you have selected is not compatible with your CD writer, you will usually get an error message. It might rarely happen that your CD writer misunderstands a command and then does something undefined with your CD-R, probably destroying it. If you find a working driver for your CD writer through testing and if your CD writer is not yet listed in our compatibility list, we are looking forward for a short note from you. @EndNode @Node "MINST" "MakeCD.guide/MINST" @Toc "Main" @{B}Installation ************@{UB} Sorry, this section is not yet written. @EndNode @Node "MISTR" "MakeCD.guide/MISTR" @Toc "Main" @{B}Instructions ************@{UB} NOTE: these instructions are not yet finished. They need a complete rework. Some parts are even missing and have to be added. Stand by. We are working on it! Although MakeCD is easy to use, you should read this section in order to understand it completely. If you don't read it, you could oversee quite a lot of useful features. @{" Settings " Link "MISET"} Settings window @{" Main window " Link "MIDMA"} Description of the main window @{" ISO settings " Link "MIIOP"} Description of the ISO options @{" Scanning window " Link "MIISW"} Description of the ISO writing window @{" Writing window " Link "MIWRW"} Description of the writing window @{" Target CD-R window " Link "MITGW"} Description of the Target CD-R window @{" Main Menu " Link "MIMEN"} Description of the main menu @EndNode @Node "MISET" "MakeCD.guide/MISET" @Next "MIDMA" @Toc "MISTR" @{B}Settings window ===============@{UB} Before you start working with MakeCD, you have to ajust the settings for your system. Start MakeCD and use the menu to open the settings window. *** Sorry, this section is still under construction. *** @EndNode @Node "MIDMA" "MakeCD.guide/MIDMA" @Next "MIIOP" @Prev "MISET" @Toc "MISTR" @{B}Description of the main window ==============================@{UB} The main window mainly consists of a list of tracks which you want to write, some settings for each of these tracks, and some buttons to start the process. Use the list view and its control buttons to add or remove tracks from the list, or to change their order. You can use the play button in order to play the currently selected track, if it is an audio track. For @{B}each track in the listview@{UB}, you have to specify some things. 1. Choose which typ of track you want to write. Usually this will be an data or audio track, but also other settings are possible. Use the cycle gadget to set the correct track type. 2. Now, you have to select the source for this track. There are several possibilities: Filesystem The data of the track will be read from a hard disk or other media and an ISO 9660 image will be created for it in order to make the data readable on CD. @{B} If you choose this option, you have to select the ISO settings now by pressing the popup button.@{UB} Track from CD You can read the data for your new track from another CD. This can be any kind of track. Using this option makes it possible to copy CDs with MakeCD. @{B} If you choose this option, you have to select a source track now. Click on the popup button and select the correct track from the appearing track requester.@{UB} Image file This option makes MakeCD reading the data from an image file which you have already created on your hard disk. This can be an ISO image or audio data or whatever. @{B} If you choose this option, you have to select the image file which you want to write to CD now. Click on the popup gadget, and a file requester will be opened which allows easy selecting of the file.@{UB} Block media This option reads the data from the block media as specified in the MakeCD @{"Settings" Link "MISET"}. Usually, you need this option only if you created in image file on that block media before and if you want to write it now. See below (description of the target) for more information. @{B} If you choose this option, you have to do nothing. But please make sure you selected a valid block device in the settings window.@{UB} 3. Now, select the target. There are several possibilities, too: Use Image File The data won't be written directly to the CD writer. Instead, an image file shall be created. After that, the image file shall be transferred to the CD writer. @{B} Use this option, if you have enough hard disk space and if you are not sure if the source can deliver the data quick enough.@{UB} @{B} Never forget to select the target file for that image that shall be created. Old files with the same name will be overwritten. Also select when you want the image file to be deleted.@{UB} Directly to CD writer This option will send the data directly to the CD writer. There will be no image file written. Make sure your source can deliver the data fast enough! Use Block Medium MakeCD supports writing data directly to a hard disk -- starting at a block as specified by you (usually block 0). This can be extremely useful for data CDs, if you want to test the image before writing a CD and don't want to use `cdromemu.device'. Also, data written directly to a block media can be accepted by most CD manufacturers. @{B} This option will use the block media as specified in the @{"Settings" Link "MISET"}, and create an image on this block media.@{UB} @{B} Please note that this option can destroy data on your hard disk, if you are not careful and don't know what you are doing. Don't use this option unless you are sure you know what you are doing!@{UB} There are some other symbols in the main window, that need some explanation: Base Dir You can set the directory for all image files that have to be created or read. Therefore, you have to fill the base directory gadget with the correct path name. This is useful if you want to have one directory for each CD you write. If you use this gadget before creating the track list, it's no longer nasty to choose image file names for all the tracks. This is extremely useful for CDs with a lot of tracks, like audio CDs. Start Block If you want to create a multisession/multivolume CD, but want to create the image file only so far, you must enter the correct start block value. The start block is the next block on CD-R that can be written to. On empty CD-Rs, that's block 0. If there are already tracks on CD, it is a positive value. When you insert the CD-R in your CD writer, MakeCD can read this block from CD and fill the correct value into the gadget. If your friend has the CD-R, you want to add data to, you can call him and ask him for the correct value. Then you can create an image without actually having the CD-R. This value is absolutely required for multisession/multivolume CDs. It must be a positive value if there's already written data to the CD-R, and must be 0 if the CD-R is still empty. Note that MakeCD automatically uses the correct value, if the CD-R is available or if you don't use the `write image files' button. If you try to write an image file that has been created with the wrong base block to a CD-R, MakeCD will complain. So you should not worry too much about creating a new coaster that way. Write Image Files... Pressing this button will cause MakeCD to look for all unwritten image files and tries to create them. Note, that you have to set the correct base block, if you use this command. This is 0 if the CD-R is still empty. Otherwise, MakeCD can calculate this value for you, if you press the popup gadget beside the base block gadget. Write Tracks... This command first writes all image files (if needed), and then transfers them (or the source, if no image file is given) to the CD-writer. Make sure your system is fast enough to handle this process, or you run in danger to produce coasters. Play Audio ... This command plays all audio tracks of the track list. That's how you can check the quality of your audio data before writing them to CD-R. @EndNode @Node "MIIOP" "MakeCD.guide/MIIOP" @Next "MIISW" @Prev "MIDMA" @Toc "MISTR" @{B}Description of the ISO options ==============================@{UB} If you want to create your own data CD, you have to create a data track and to select `Filesystem' as source for this track and to click on `Configuration...'. This section describes how to handle the window that opens after clicking on `Configuration...'. In the appearing window, you will see is a list. This list holds all sources which you want to appear in the image. This can be either a pathname, or a track from a CD-R, if you want to do MultiSession merging. Use the buttons at the list to add or remove entries, and for each entry, choose if you just want to add a path from your hard disk, or if you want to merge a track from CD-R. Then, use the popup gadget to choose either the path or the track. The order of the entries in this list is only important, if there are filename collisions. In case of file name collisions, the file of the @{B}first@{UB} source in the list is written to the ISO image and all files that cause collisions are ignored. If you want to create a MultiSession CD, you probably will already have at least one session with one data track. Now, add the path(s) which shall be scanned, and @{B}after@{UB} that the track(s), that shall be included to the image. Then, the first path will be included completely into the image, and all files of all following paths or tracks will be included, if their names do not collide with an already included name. If you create a data CD in e.g. four steps, and if you always want to see all data, just include the track which you have written last time, into your image, when you write a new track. So you always see all files that are contained on the CD. Should you forget this (e.g. you did not forget it until and including track 3, but forgot it with track 4), just include both, track 3 and 4 next time. If you don't add any further data to that new track, it will be written very fast (just a few seconds) and take only little space. However, fixing this new session will take about 15 MB as usual! There's a way to make sure there are no filename collsions: just put every path/track in its own directory. If you want to do that, checkmark `Image Path', and enter the name of the directory that shall be created to hold the contents of your source. So if you have four sources, you can create four directories and the contents of the four sources will be copied into the respective directory. So, now you have selected which sources shall be copied to the ISO image. The next step is to set the correct ISO options. First of all, you probably want to select the volume name. That's the name which for example appears on Workbench, if you put the written CD-R in your CD-ROM drive. System ID, Preparer and Publisher are not so important. Usually, you don't have to change them. We don't know any program that uses these strings and/or requires some special entries here. Copyright, Abstract and Bibliography are unimportant, too. We always leave them empty. If you want to create a CD that boot on CDTV/CD32, you have to edit the CDTV/CD32 options. Enable the CDTV/CD32 options and choose a correct trademark file. You find trademark files on Amiga Developer CD v1.1 in the directory CD32/ISO9660Tools_V1.04/ISOCD. Choose either CDTV.TM or CD32.TM. Please understand that for licence reasons, we must not include these files in MakeCD. There's no need to change the other values and their effects are not very well known. These values are passed to the Commodore Filesystem, which is used on CDTV/CD32. If you want, you can play around with them and look how the performance on CDTV/CD32 changes. Now, you have to change the ISO/Rock Ridge options, which is the most confusing part for most users. If a Meeting Pearls CD runs pretty well on your system, you can choose similar mastering options from the menu. There was no difference in the mastering options between Meeting Pearls II and III. Now, go through the following elements and change them, if needed. Sorting Order Maybe you have noticed that accessing icons is pretty fast with CDs mastered with MakeCD (and with most other Amiga mastering software, too). Although a fast CD-ROM drive needs about 1/10 seconds (a slow one needs 2/10 seconds) to access one file, a directory with 20 icons (20 short files) is usually shown faster than in 2 to 4 seconds. That's because MakeCD usually saves all `.info' files into the same chunk, so after the first `.info' file is accessed, the following ones are usually being copied into the cache of your CD writer, and can be accessed there very fast. This list view describes, which files shall be hold in the same chunk. Just add the corresponding suffix's to the list view. For example, if you want `.html' files being accessed fast, add `.html' to the list view. Default is `.info'. ISO Level ISO 9660 file- and directory names have a lot of restrictions. There may be only upper case characters, numbers and the underscore in those names. There must be exactly one dot in filenames, and zero dots in directory names. File names must not be longer than 31 characters and the limit for directory names is 30 characters. Since those Amiga CD-ROM filesystems which don't have Rock Ridge support (e.g. Commodore CDFS, which is included in OS 3.1) would not be very happy with these restrictions, we decided to break the standard, if you select ISO 9660 Amiga. CDs created with this option will work on most platforms, but e.g. on MS-DOS systems, they might cause some trouble, so be careful with this option. ISO 9660 Level 1 creates filenames that are fully compatible with MS-DOS systems. Additionally to the restrictions mentioned above, they are crippled to the 8.3 format. ISO 9660 Level 2 is not crippled to the 8+3 format, but the restrictions mentioned above are still valid. We recommend to use ISO 9660 Amiga, if the CD shall be only read on Amigas. If you plan to use the CD on MS-DOS systems, too, use ISO 9660 Level 1 with Rock Ridge Extensions. This requires to use a filesystem that supports Rock Ridge on the Amiga. See below. Convert .info suffix Workbench 1.3 does not display icons if their suffix is not exactly `.info'. E.g. `.INFO' or `.Info' files would not be displayed. This option makes sure that all `.info' files use only lowercase characters. You need this option only if you are going to use the CD under Kickstart/Workbench 1.3 or on a CDTV. Convert ISO names to uppercase If you don't want to get your ISO 9660 filenames crippled, but want to make it easier for MS-DOS machines to read your CDs, you can switch on this option. This converts all ISO names to uppercase, but does not strip/change illegal characters. All it does is changing a-z to A-Z. Then, your Amiga will display mostly uppercase characters, but the CD is easier to access under MS-DOS, although not all files will be accessable. Schatztruhe GmbH masters most if its CDs with this option. If you additionally use Rock Ridge (as Schatztruhe GmbH does), you will see the full Rock Ridge names, which of course are @{B}not@{UB} converted, if you use a CD-ROM filesystem that supports Rock Ridge. So CDs mastered with this option can be read without problems on the Amiga and can be read better on MS-DOS than a ISO 9660 Amiga CD without this conversion. If you switch on Rock Ridge, Amiga users who use a filesystem that supports Rock Ridge, won't notice any difference. If Rock Ridge is off, or the filesystem does not support Rock Ridge, you will see mostly uppercase filenames. Rock Ridge If you switch on this option, Rock Ridge extensions are written to the Image. CDs with Rock Ridge extensions are readable on every filesystem that supports ISO 9660. So there's full downward compatibility. If your filesystem supports Rock Ridge, you can make use of some additional features, like multiuser flags, Amiga file attributes, or uncrippled file names (even if the CD is mastered with ISO 9660 Level 1 or 2). In general, we recommend to switch on this option. AmiCDFS, AmiCDROM, CacheCDFS, BabelCDROMFS and AsimCDFS (latest versions of all these) are known to support Rock Ridge. CommoCDFS (included in OS 3.1) does not support Rock Ridge. World Access If you have switched on Rock Ridge, multi user flags will be written to the image. This option will cause all objects to get the same world access rights as the owner. This is extremly useful, if you want to use the CD on Unix systems. Group Access If you have switched on Rock Ridge, multi user flags will be written to the image. This option will cause all objects to get the same group access rights as the owner. This is extremly useful, if you want to use the CD on Unix systems. Include Amiga file attributes If this option is switched on, Amiga protection bits and Amiga file comments will be included in the image. If these file attributes are important for you, you should switch on this option. Please note that you need a CD-ROM filesystem that supports Amiga file attributes if you want to see these attributes when working the CD. The following CD-ROM filesystems are known to support these attributes: AmiCDFS 2.30 or better, AsimCDFS 3.7. Support for CacheCDFS is in work. @EndNode @Node "MIISW" "MakeCD.guide/MIISW" @Next "MIWRW" @Prev "MIIOP" @Toc "MISTR" @{B}Description of the ISO writing window =====================================@{UB} In order to build an ISO 9660 image, MakeCD has to scan the source paths, that shall be included into the image. Therefore, a window opens which shows you how MakeCD is scanning -- the ISO writing window. In the upper part of the window, MakeCD shows how many files/directories have already been scanned. At the bottom of the window, it shows which file/directory is just being processed. The display is updated 1-5 times per second, so not every file will be shown. That's done for performance reasons. After scanning is finished, the total image size can be calculated and will be shown. Then, MakeCD prepares the image and starts writing. It shows, how many files/directories have already been written and how many percent of the total data that is. You can break the whole operation any time, which will cause MakeCD to return with an "user abort" error. @EndNode @Node "MIWRW" "MakeCD.guide/MIWRW" @Next "MITGW" @Prev "MIISW" @Toc "MISTR" @{B}Description of the writing window =================================@{UB} The writing window opens whenever an ISO image is created, a track is written or audio data is played. It helps you to control the operation and shows you what's happening. It shows useful information about the buffer, about your source and your target, and some other informations. The "buffer display" shows you, how big the internal buffer of MakeCD is, and how much of it is filled with data. Don't mix it up with the buffer which your CD writer has. This is an additional buffer which is located in your CD writer and not shown in the writing window. Even if the buffer of MakeCD is empty, the buffer of your CD writer may still be full! You can adjust the size of the buffer of MakeCD in the @{"Settings window" Link "MISET"}. MakeCD might take a slightly bigger or smaller buffer. If there's not enough free memory left, the buffer might be much smaller. If you are writing a CD-R, a big buffer is useful to decrease the risk of a buffer underrun, which would cause a damaged CD-R. Note, that the buffer will stay almost empty, if you disable parallel reading/writing or if you disable reselection for the CD writer. That of course means, that it is more risky to write a CD-R. Unfortunatly, some CD writers do not support reselection correctly, and so you @{B}must@{UB} turn off reselection, otherwise the SCSI bus would hang up and nothing would work. If you are playing audio data, the buffer can be smaller, but should not be too small, because many drives trash audio data if there's a buffer @{B}over@{UB}run. That means, if your drive delivers the data faster than the buffer can pass it to your speakers (or to your hard disk or to your the CD writer), the buffer will get full and the next try of your drive to deliver audio data will have to wait. In this case, some drives deliver audio data which contains noise. If you use such a drive, you must make sure the buffer is big enough and/or the drive reads slow enough so that there are no buffer overruns. If you are just creating an ISO image on your hard disk, the buffer does not have to be big and buffer over- and underruns are not critical. The "source display" shows you, how much of the source data is already transferred, where the source comes from, and how fast the transfer is actually. Please note that the transfer rate can appear faster than the theoretical limit, especially when you are reading from a CD-ROM drive. This can be the case if -- while the CD writer is writing data -- the CD-ROM drive fills its cache with the data of the following sectors. Then, MakeCD requests data from the CD-ROM drive and gets it really fast -- directly from the buffer of the CD-ROM drive. Of course, MakeCD can't know if the CD-ROM drive reads the buffer from CD, or if the internal buffer of your CD-ROM drive already contained the requested data. MakeCD will simply show how fast it got its data from the CD-ROM drive. That's why the transfer rate can be faster than the speed of your CD-ROM drive. The "target display" shows you the same data about your destination: where your data goes to, how many data is already written, and how fast the transfer is. Furthermore, this window shows you how many data still has to be written and how long (in minute:seconds) it already wrote. There's also a display that sometimes shows you some messages. And if you are playing audio data, you can use some gadgets which are located in this window to jump from track to track or to jump within a track, switch on/off lowpass filter or control the volume. These gadgets can be saved using the menu. @EndNode @Node "MITGW" "MakeCD.guide/MITGW" @Next "MIMEN" @Prev "MIWRW" @Toc "MISTR" @{B}Description of the Target CD-R window =====================================@{UB} Sorry, this part of the documentation is not yet finished. @EndNode @Node "MIMEN" "MakeCD.guide/MIMEN" @Prev "MITGW" @Toc "MISTR" @{B}Description of the main menu ============================@{UB} Sorry, this part of the documentation is not yet finished. @EndNode @Node "MBEGN" "MakeCD.guide/MBEGN" @Toc "Main" @{B}Notes for beginners *******************@{UB} *** Sorry, this section is not yet written. *** @EndNode @Node "MFAQS" "MakeCD.guide/MFAQS" @Toc "Main" @{B}Frequently asked questions **************************@{UB} NOTE: This FAQ is beta and needs a complete rework. We are working on it. Please read these questions and answers carefully, before asking any questions. Maybe your question is answered in this list. We sorted the questions according to the following categories: @{" Support " Link "FSUPT"} Questions about support and registration @{" CD writer " Link "FWRTR"} Questions about CD writer support @{" Writer problems " Link "FWRTP"} Problems with some CD writers @{" SCSI problems " Link "FSCSI"} SCSI problems, SCSI hangups @{" Audio CDs " Link "FAUDI"} Questions about Audio CDs @{" Data CDs " Link "FDATA"} Questions about Data CDs @{" CD backups " Link "FBCKP"} Questions about CD backups and copies @{" Various " Link "FVRIO"} Various questions about burning CDs @{" GUI " Link "F-GUI"} GUI related questions @{" Settings " Link "FSETT"} Questions about the settings @EndNode @Node "FSUPT" "MakeCD.guide/FSUPT" @Toc "MFAQS" @{B}Questions about support and registration ========================================@{UB} Question: Why do I have to send the registration fee to Katrin and not to you, the authors? Answer: We are busy with writing MakeCD and if we made the registrations ourselves, it would take much more time than when Katrin's does this job. She's Angela's little sister and happy to earn some pocket money with this job. She especially enjoys nice persons at the phone and those letters which contain some nice words. ;-) Please note, that she can not answer technical questions. Please contact the authors directly, if you have such questions. Question: Are there any mailing lists for MakeCD? Answer: Yes, there are. Refer to the documentation of MakeCD. Question: I have entered and saved my registration number and address. Nevertheless, the next time the MakeCD registration requesters pops again. What's wrong? Answer: You are probably trying to register MakeCD on a partition with AFS (AMIGA File Safe) with a version older than 16.16. Update AFS and the registration will work. Question: I'ld like to pay with my VISA card (or any other credit card). Do you accept such cards? Answer: Unfortunately, VISA (and other credit card institutes) has quite strong conditions. If we accepted VISA cards, we would need one VISA registration about every two days. We are far from that limit. So, payment with VISA is not possibly, sorry. Question: I want to get registered by transferring the money on a bank account. Please tell me an account number. Answer: We did not include our bank account in these documents on intention. Often, name and address do not appear properly on our bank statements, so we can't send you the registration. Furthermore it will need more time to register you, as we don't get our bank statements very often and since we would have to transfer your data to Katrin Schmidt, who goes ahead with your registration. If you @{B}really@{UB} don't see @{B}any@{UB} other possibility, you can write us an email about that, but other possibilities are @{B}really@{UB} preferred! Question: I don't live in Germany, but I want to order MakeCD anyway. How can I transfer the money to Germany? Answer: There are several possibilities: Euro cheque in DM That's most likely the most comfortable method for both of us. But please make sure you write an DM amount on the cheque and not an amount of your national currency. We can only cash euro cheques without additional fees if they are in DM. If they are in a different currency they cost us a lot of fees. Cheque from German bank Ask your bank if they have a partner bank in Germany. In this case, your bank can ask that partner bank in Germany to write a cheque in DM. If the cheque is from a German bank and written in DM, we don't have to pay additional fees for it. In your own interrest, ask your bank which fees @{B}you@{UB} will have to pay for that! Postal money order Go to your post office and ask them to send us the money in DM. That's a safe method. In parallel, you should send your registration form to us, but in case the post looses your registration form, make sure to note your whole address and the use on the postal money order. Then we can send you MakeCD even if your letter gets lost. Cash Of course, that's your own risk. Just go to your bank and get some German bank notes. Some persons then send the money in registered letters, but this also can't guarantee 100 % safety. However, usually the money reaches us. ;-) Cheque from your bank Cheques from outside Germany, which are none of those as described above, cost us -- depending -- about 20 DM each to cash. This amount of money is taken by our bank from the amount of money which you have written on the cheque. Therefore, you have to add about 20 DM to your cheque, if you want to use this method. Question: I am registered and want to get the latest version. Where can I obtain it from? Answer: If you have internet access, have a look at our homepage: `http://www.uni-karlsruhe.de/~un60/MakeCD.html'. If you don't have internet access, use the register form to order a free demo version (you pay only shipping costs, which is 5 inside Europe and 10 DM outside Europe). This offer is limited to one disk per package. As soon as you enter your registration number in this demo version, you will have a registered version. BTW: You need not be registered to order the free (you pay only shipping costs) demo version. This offer also applies to all unregistered users who have old versions of MakeCD and want to see what's new. @EndNode @Node "FWRTR" "MakeCD.guide/FWRTR" @Toc "MFAQS" @{B}Questions about CD writer support =================================@{UB} Question: When will you add support for my CD writer XYZ? Answer: It is not easy to support all different CD writers, because there is no standard SCSI command set to access them. However, if you send us the command set of your CD writer, we will do our best in order to support it. Question: My CD writer often (or always) hangs after a while. The SCSI bus seems to be blocked. What can I do? Answer: Try if it helps to switch off Reselection or Synchronous Transfer Mode. There is a tool, called `CTRLscsi' (Archive name: `HWGCTRLscsi.lha'), which allows you to control Reselection of each Unit if you are using Commodore scsi.device V39/40. This tool is contained in most of the MakeCD distributions. @EndNode @Node "FWRTP" "MakeCD.guide/FWRTP" @Toc "MFAQS" @{B}Problems with some CD writers =============================@{UB} Question: I checked the audio on the CDs and at some random positions there was a burst of noise. Ouch. What happened? Answer: Somebody reported, that he had such a problem when a Zip drive is attached to the same SCSI bus. As soon as he removes his Zip, the noise disappears. Another person reportet, that switched on reselection causes more noise than switched off reselection. Best is to transfer the data directly to RAM or to use a huge buffer. We also have heard that you should check the termination of your SCSI bus. Question: I use a JVC CD writer and have several problems. When will you release a new driver that is not beta? Answer: The problem is not really located in the driver, but in the buggy firmware of the JVC XR-W2010 V1.51. Please read more about that in `doc/Compatibility'. The most important problems are: Reading delivers wrong data without error If you have a Meeting Pearls III or IV, please mount your CD writer as a CD-ROM drive, insert the Meeting Pearls and click on "Deutsch" or "English". Now, an AmigaGuide document should appear which includes a link that allows you to check the CD for errors. Check the CD! If there are shown any errors without an appearing Read/Write error, your JVC CD writer delivers wrong data without error message! Rejecting of write commands Obviously, some CD writers reject the commands to write or fix a CD or session with `ILLEGAL COMMAND'. It might be that you can fix this by using a shorter SCSI bus (that worked in Patricks tests) or by using a different, better media (that has been reported by JVC). Try both! Additional errors Please read the JVC sections in `doc/Compatibility'. Question: I use my HP 4020 CD writer (or Philips CDD 2000, Grundig and other similar drives) in test mode. Everything works fine. But when I switch to real mode, a lot of CD-Rs get damaged after a while. MakeCD reports a "write append error". This does never happen in test mode, but very often without test mode. My friend has the same CD writer, but didn't have these problems when the CD writer was new. But now, he has the same problems. What's wrong here? Answer: Most likely, you have got one of these defective CD writers. Your drive needs to get fixed. A new firmware or a new version of MakeCD won't help here. In internat, a user has reported, that HP seemed to be surprised, that he could write 200 CD-Rs without problems before getting that write append error. On Feb-25-1997, Alexander Becker reported in <5eu67r$1q0@enjoy.regio.net>, that HP sent him new CD-Rs, and that he got his money for the CD writer back, after he called them and faxed them the bill. Other users have the exchanged their CD writers twice or three times -- without staying success -- and finally got their money back. One of the MakeCD betatesters reported that the following company does very good support for those defective CD writers: Repair 2000 Hardware Service GmbH Werkstrasse 5 22844 Norderstedt Germany phone: +49 40 5225031 (ask for Mr. Peter and describe the error) fax: +49 40 5264811 In internet a guy has posted, how you can try to repair the CD writer by yourself, after the warranty is over, when you have the `write append error'. The authors of MakeCD shall @{B}not be respondable@{UB} for this text, but since it might help somebody, we decided to include it in this document. First a node: there's a different text in the German FAQ. The instructions of both texts differ -- but maybe both solutions work. We don't know. If you understand German, read that text, too. They add some grease there to the drive, there. @{I} From: telsat@cybernet.it (Peter Marchionda) Newsgroups: comp.publish.cdrom.hardware Subject: CDD-2000 / HP 4021i "spring" FIX >>>>READ INSIDE<<<< Date: Wed, 19 Feb 1997 02:53:20 GMT Message-ID: <330a6a70.13096048@news.supernews.com> After reading all those horror stories about the Philips CDD-2000 drive, I considered myself fortunate. My CDD-2000 gave me no problems to set up. I made about 40-50 burns without any problems using Easy CD Pro 95 on a 120 MHz Pentium with 2 Quantum Fireball 3.2 GB HDs, 64 MB of EDO-RAM and a cheap ($30 !) NCR C810 compatible PCI SCSI controller. Only a couple of times I lost about 30-40 megs of space because I forgot to turn off the screen saver, and the session closed with a buffer underun error 4-5 minutes from the start of the recording. But then.....disaster struck! After writing about 300 of 610megs, the session prematurely closed and I got an error code message of 171-00-50-00 (write or write append error)....I had just become a new member of the "COASTER CLUB". I restored my configuration files (win.ini, system.ini, system.dat and user.dat) from a version saved when I was sure that the drive worked, and using the speed test function I tried again (and again, again and again......), but the test failed ALL the time between 300 and 330 megs with that same 171-... error code. Apparently it wasnt the computer or the software, but the drive itself! I had read about "spring" problems with the CDD-2000, but nobody seemed to know exactly what could be done to fix the problem -- without sending it to the Philips service center. I wanted to send mine in too, but after they told me it would take from 25 to 40 days for the repairs, and not being very enthusiastic about purchasing a new drive, I decided to see myself what this "spring" problem was all about. I opened the drive (you will need a small TORX driver set) and removed the cover, then removed the main board, carefully disconnecting the 5 cables (open the 3 flat cable connectors on both sides before pulling!!). The loading mechanism flap, on the top side of the drive was removed by removing the spiral spring at its center, and disengaging the hinge by sliding it sideways. The drive mechanism can then be removed by gently pulling it out, it is only held down with 4 rubber grommet shock absorbers. The controller board must be now removed by unscrewing the 4 Torx screws, disconnecting the spindle motor connector and unsoldering the wires of the laser carriage motor. After you remove the board you will be able to see the culprit. It is a straight piece of round spring steel wire (25.4mm/1.0" long , 0.25mm/0.01" in diameter) that pushes the rack towards the pinion gear. It was easily removed by just gently pulling it out with a SMALL pair of pliers. DO NOT disassemble anything else to remove it. The spring MUST be replaced , you can not bend it to increase the tension to fix it, as it must be perfectly straight. Replace it with a larger diameter wire; it should be between 0.40mm/0.016" and 0.50mm/0.02" in diameter of high quality spring steel, be sure it retains its shape if bent, and that its length is exactly the same as the original one. Now, I know I should not admit this, but I used a straightened piece of spring from an old ball-point pen! Piano or guitar wire should also work. Be careful to not deform the new spring when replacing it. After the spring is replaced, verify that the carriage moves smoothly back and forth by applying 6 volts DC to the motor, inverting the voltage when it reaches the ends. The gear teeth should only jump when the carriage reaches the extreme ends and can not go any further. Dont burn the motor out or ruin the teeth by applying voltage for more than necessary. If the gear teeth jump in between, or if there is any play between the rack and pinion gears the spring tension is not high enough, probably caused by the spring being deformed when it was replaced or bad quality spring steel. Once you successfully perform this test, reassemble the drive and dont forget to reconnect the motor wires.....they should not cross each other. Reinstall the drive and try it using "Test recording speed". DISCLAIMER: Absolutely DO NOT try to repair a CDD-2000 yourself....... unless....you meet ALL 5 of the following requirements: 1. You are VERRRRRY experienced technician. 2. You are very impatient and dont want to wait for the repair. 3. You live in Antarctica and the nearest service center is very far away. 4. You must record a CD NOW! 5. Be sure that your drive has the "spring" problem; incomplete writes with the 171-00-50-00 error message (with Easy CD Pro 95 v 2) Otherwise....send it to the Philips service center! Please dont E-mail bomb me if you mess your drive up... @{B}I warned you not to do it!!@{UB} @{UI} Question: My Philips CDD 2000 (or similar CD-Writer like HP SureStore 4020, Grundig CDR100 IPW, ...) is able to write CD-Rs and to read original CD-ROMs, but it can't read CD-Rs -- even if they are readable in my CD-ROM drive. Answer: We've heard about this problem which some Philips CD writers obivously have. You CD writer needs to get repaired. Send it back. Question: I want to rip an audio track with my Philips CDD 2600 CD-Recorder. The inner tracks can be read, but on the outer tracks I get error messages. What can I do? Answer: This is a common problem with Philips CDD 2600 and HP SureStore 6020 (and similar drives). Use the settings window to slow reading audio data down to single speed. This might help. Question: I have problems with my JVC XR-W2010 CD writer, especially with Audio CDs. What can I do? Answer: Make sure you have the lastest firmware version (V1.51 or better). Older versions made a lot of trouble with Audio CDs. Question: I have an A3000 (scsi.device V40.12) and a Yamaha CDR 100. MakeCD works great. No problems at all. Seems to be a very good CD writer! However, my filesystem does not mount CDs from the CD writer. MakeCD can read the data tracks, but my filesystem (BabelCDROMFS) says "not a DOS disk". The same CD-ROM works fine in my CD-ROM drive -- even with the same CD-ROM filesystem. Strange, isn't it? Answer: We have the same configuration and had the same problems. The Yamaha CDR 100 is really a very good CD writer, and the problem it has is not its fault. The scsi.device cannot read from the CD writer using trackdisk commands. Something seems to be broken. Maybe, the same error happens with A2091 and other Commodore host adapters. On the A3000, we could fix the problem by installing the new V43 scsi.device. If you don't want to install V43 scsi.device, you should use a filesystem that uses SCSI commands to communicate with the CD writer. For example AmiCDFS (shareware) is a good choice. Make sure the filesystem uses SCSI commands (refer to its documentation). Then, everything should work. @EndNode @Node "FSCSI" "MakeCD.guide/FSCSI" @Toc "MFAQS" @{B}SCSI problems, SCSI hangups ===========================@{UB} Question: I have big problems. Nothing seems to work. MakeCD hangs up very often. What can I do? Answer: Try the following things -- of course, use test mode! · Select a small chunk size (32 KB or 64 KB) in the settings window and try if this already helps. We have been told that this helps some Phase5 host adapters. · Switch off parallel reading/writing in the settings window and try if this already helps. When parallel reading/writing is off, the buffer will stay almost empty all the time. That's normal, and of course more dangerous. Obviously, big buffers do not make much sense then. 1 MB should be more than sufficient. · Switch off reselection for all drives, especially for the CD writer. If this helps, play around with reselection until you find out where you can keep and on and where you have to switch it off. When reselection is off for some drives, the same as above applies for the buffer. · If nothing helps, borrow a 2nd host adapter and try if you get better results when connecting the CD writer to its own host adapter. Question: When writing a CD-R the CD writer suddenly stops, but MakeCD doesn't show an error description. I can select abort, but nothing happens. The computer doesn't crash and I can still use the SCSI bus. Is this a known bug? Answer: We have encountered this problem with a Oktagon V6.8 when writing audio tracks to a Philips CDD2000 V1.26 with enabled disconnect. It was reported for other controllers, too. It is a bug in the controller or the target drive: MakeCD is waiting for a write request that is never completed because reconnection failed. MakeCD can hardly do anything about this. You should disable disconnect for your target drive and/or try sequential reading/writing. Question: I have a Philips CD writer (or Grundig, HP SureStore or other compatible CD write, refer to Compatibility list). Writing in test mode works fine. But when I write a CD without test mode, I kill CD-Rs all the time when I am almost finished. The error is "write append error" or "buffer underrun". Why that? Answer: We heart several times about that problem. A user who seemed to be quite good informed told us, that this is a common problem with Philips and compatible CD writers. You CD writer has to get fixed. Contact your dealer. Question: While writing a CD, sometimes my SCSI bus hangs up. This happens in both, test mode and real writing. Is there anything I can do agains this? Answer: Obviously, your CD writer and/or your SCSI hostadapter have some problems. Sorry, we can't help you there. Have a look at our Compatibility list -- maybe a user with a similar configuration had the same problem and can tell you a solution. You might want to switch off reselection. There's a small tool for Commodore V39/V40 scsi.devices included in most MakeCD distributions. Also, you can try to switch off parallel reading/writing in the MakeCD settings window. Furthermore, you can choose a small (e.g. 32 KB) chunk size. If nothing helps, contact your dealer. There's a problem in either your SCSI hostadapter or your CD writer. Question: I have buffer underrun errors. What can I do? Answer (from `John Hendrikx '): I experienced buffer underruns when reselection on my CD writer was off. This meant that the hard disk couldn't do anything while the CD writer is using the bus (which can be quite a while). Putting on Reselection on both the CD writer and the HD resulted in SCSI errors (sometimes), but only having it on for the CD writer works fine and won't make much of a performance difference as the HD (which has reselection off) won't use the bus for an extended period of time anyway. I've succesfully burned CD's at 4x speed (!!) with a Yamaha CD writer when I still had a 030 22MHz system with only 8 MB of FastRAM. The data came from an IDE drive (I think that the seperate IDE controller made things a bit easier). I was pushing the limits with this system though: at one time I did get buffer underruns this way, and it turned out that I had to do a ReOrg on the source drive before it would work fast enough :-) Anyway, a few tips: · If you expect that your HD is not delivering data fast enough at some specific point in the process, try ReOrging the drive. · Use large block sizes on your image partitions. I use 2K blocks on all image partitions (some will probably set this even larger, but I want to be able to use such drives normally when needed as well). Fragmented files won't slow down your Hd that much anymore this way. · Check the reselection setting of your SCSI devices. It doesn't need to be on for any fast devices (like harddrives), but it should absolutely be on for the CD writer (I have reselection disabled for all drives, except the writer -- works like a charm). If you want to see what difference reselection makes try this: Set parallel reading/writing ON; start writing (testmode) a large image or something. Now use a reselection tool to turn on/off reselection for the writer. When it is off the writebuffer gradually becomes smaller, as soon as you turn it on the buffer is filled in a few seconds again (it may differ on your config but try it anyway). · If you suspect the SCSI controller simply can't handle the throughput, or setting reselection on for the CD writer causes SCSI errors then try getting the data from a different controller (a 2nd SCSI controller, or simply from an IDE controller). This should work even better since you never need to worry about reselection. BTW, turning reselection off for your harddrives also improves performance (atleast when using one of them at the time :-)). I've had almost a 20% performance boost when I turned it off for my Seagate drive (it didn't handle reselection correctly anyway -- it was the cause of some lockups I experienced at one time, not my writer). @EndNode @Node "FAUDI" "MakeCD.guide/FAUDI" @Toc "MFAQS" @{B}Questions about Audio CDs =========================@{UB} Question: When copying an audio CD, I get a buffer underflow. Obviously my 8x speed CD-ROM drive is not fast enough, although my CD writer writes only in double speed. What's wrong here? Answer: Many CD-ROM drives read CDDA data in single speed only. In order to copy an audio track, you should switch your CD writer back to single speed -- or use temporary files. Question: How can I set the length of the pauses between the tracks? Answer: This is not possible with any AMIGA CD writer software at the moment (27.12.96). MakeCD uses the track-at-once mode, too, i.e. it only sends the pure track data to the writer and leaves calculating checksums and writing of pauses and table of contents to the writer. This has the advantage that writing can suspended unlimitedly between tracks and multisession would be possible. Selecting the length of the pauses would only be possible in the disc-at-once mode. MakeCD will offer both modes alternatively as soon as possible. Question: Is there a possibility to copy a CD with multiple tracks without pauses despite of the fact that writing will add pauses? Answer: It is possible, however, the copy will consist of one large track. You have to select the first track of the original CD as source and set its length to the total length of all tracks (= "end last track" - "start first track" + 1). MakeCD will read all tracks in one piece. @EndNode @Node "FDATA" "MakeCD.guide/FDATA" @Toc "MFAQS" @{B}Questions about Data CDs ========================@{UB} Question: I have read that MakeCD is able to write AMIGA Protection Bits and file comments. I wrote an image file with Rock Ridge and AMIGA Attributes turned on -- but when I mount this image, all files have standard protection bits. The script bits are still lost. What is What is wrong here? Answer: You need a filesystem that supports AMIGA Protection Bits. The freely distributable AmiCDFS2 supports them since version 2.30. AsimCDFS supports them starting with version 3.7 (note that there's an old version string "AsimCDFS 3.6 (05.11.96)" in L:AsimCDFS). The author of CacheCDFS has promised to follow soon and has a working beta version. Question: I have created an ISO image of my data. But after I've written it to my CD-R, I noticed that you have put MakeCD into the image, too. I am a registered user, and I really don't like that! Please turn that off! Answer: We didn't put MakeCD into your ISO image on intention. You did it yourself. ;-) When you used the ISO settings to select the paths, that are supposed to be written to the image, you pressed the "New" button too often. So empty entries appeared in the list. This causes MakeCD to scan the directory "", which usually is the directory that contains MakeCD. So just make sure you don't have empty entries in that list. Question: Every time when I am going to burn a AMIGA CD, I browse through all directories to locate all directory levels that are more than eight levels deep, in order to avoid creating a corrupt image. When can I expect such a function in MakeCD? Answer: Don't worry -- even if you use more than eight directory levels, your image won't be corrupt. On the AMIGA, such images are even readable without any problems. Just DOS PCs are not able to change into those deep directories. But that's not a problem for most of the AMIGA users. However, we are going to implement such a function, as soon as we find time for it. Question: OK, now I know that the limit with the eight directory levels is not important for the AMIGA. But what's the restriction on the AMIGA? How many directory levels can I put on CD? Answer: There is no such limit on the AMIGA. But of course, directories are not easy to handle (very long pathnames etc.) if they are too deep. Many applications will probably crash or do wrong things, when they have to handle such long path names. You should be able to write any AMIGA directory with all its subdirectories on CD-R. Starting at some depth (undefined, because this is subject to change), MakeCD will run out of stack though, and your AMIGA will crash. But this requires really @{B}very@{UB} deep directories. Question: I want to create a multivolume CD, by just copying the data tracks of some empty CDs on one single destination CD-R. I have tried this by simply copying the tracks one after another and by fixing the session between the tracks -- without success. Just the 1st track is readable. What's wrong? Answer: Every multi session or multi volume track, which is not the very first track of the CD-R, has to be created especially for this CD-R, because every data track looks different -- depending on the block number on CD-R, where the data track is going to be stored. You can not write a track, which has been created for basis block 0, to a different block on the CD-R. MakeCD warns against this from V2.0 on, but previously tracks were written without protest, because baseblocks were not yet supported at all. Question: Now I have created a multi volume CD. I tried some CD-ROM filesystems, but I either can see the very first or the very last volume. Where are my other volumes? Answer: Unfortunatly, this still is a problem with multi volume: there are only a few filesystems, which suppurt this at the moment. However, multi volume updates for AmiCDFS, CacheCDFS and AsimCDFS already have been announced. Stand by. Question: My Workbench says, that e.g. Meeting Pearls II uses 650 MB. But when I ask DirOpus to calculate the size in bytes, I don't get 680,525,824 bytes as expected, but about 50 MB less. What happened to those 50 MB? Answer: A CD has to be written with blocksize 2048 bytes. This means that you loose 1024 bytes in average for each file, because file length usually are not a multiple of 2048 bytes. If there are 50,000 files in your image, this sums up to 50 MB. Now you can count how many files (and directories) DirOpus counts. By the way, ISO9660 wastes only little space for management data (directory structure etc.). @EndNode @Node "FBCKP" "MakeCD.guide/FBCKP" @Toc "MFAQS" @{B}Questions about CD backups and copies =====================================@{UB} Question: How can I backup my CDs (also some with several tracks)? Answer: Go to the settings to the audio part. Enter 0 start blocks and 152 pause blocks. Go back to the main window and append the whole CD using the menu. If necessary (depends on the performance of your system), activate temporary images now. Then, write the CD. With these settings you can successfully copy a lot -- but not all CDs. @EndNode @Node "FVRIO" "MakeCD.guide/FVRIO" @Toc "MFAQS" @{B}Various questions about burning CDs ===================================@{UB} Question: I cannot fix the CD-R! I have fixed all sessions and now I want to fix the CD-R, but this does not work. Answer: You can only fix the CD-R, if there are tracks written to the last session. By fixing a session, a new session (without any tracks) is opened. That's why you can not fix the CD-R, if you previously fixed the session and did not add any further tracks. By fixing a session the Lead In of this session is being written. Beside other things, it contains the track list of this session, which is required by CD-ROM drives to find the tracks. That's why unfixed sessions are unreadable on CD-ROM drives. Furthermore, the Lead In contains information, where the next session starts -- even if it is still empty. When fixing a CD-R, things are the same, except that there is a note that no more sessions will follow instead of information where the next session starts. Since a drive browses through all sessions when it reads the track list, it will -- if the CD-R is not fixed -- stumble at the last session, because it tries to read unreadable data (blocks on CD-R that are still unused). That's not a bad thing, however it slows down reading the track contents. Therefore, we recommend to fix the CD-R if you are sure you don't want to add any further tracks. Question: When I try to choose my CD writer in the device requester, MakeCD crashes. My friend has this problem only sometimes and another friend never has this problem. Answer: We could not locate such a bug. We connected the Plextor CD writer to the A3000 and started HDToolBox. This also caused a crash while HDToolBox was scanning the SCSI bus. MakeCD tries to find trackdisk compatible devices using NSD. If a device is buggy, it can cause a crash. Please use NSDQuery, which is located in Heinz Wrobel's NSDPatch archive, to locate that device, and tell us its name and version number. Just type in `NSDQuery CHECKALL'. If possible, send us a copy of that crashing device. Thanks to NSDPatch, you can patch the device in a way that does no longer cause crashes, without loosing any features. If you cannot choose the device using the device requester, you can activate the MakeCD program icon and choose "Info" from the workbench menu. Then, edit the tooltypes manually. Enter the correct values for `WRITE_DEVICE', `WRITE_UNIT', `WRITE_DRIVER', `READ_DEVICE', `READ_UNIT' and `READ_DRIVER'. You must not supply the `.device' suffix for the `#?_DRIVER' tooltypes. Question: I have written a CD, but it seems to be damaged. My CD-ROM drive cannot access it. :-( Answer: You have to fix the session or the CD-R in order to access the CD in your CD-ROM drive. Please @{B}do@{UB} take care that you don't use any cracked/virus infected versions of MakeCD, because some cracker are very lame and destroy more than they think they "enabled". Do @{B}not@{UB} blame us for non-working cracked/virus infected versions of MakeCD. Question: I have created a data CD-ROM using MakeCD. Although no errors were shown, the image is obviously quite damaged, because some icons are missing on Workbench and a lot of archives on that CD-R are damaged, too. I tried a different version of MakeCD and got a 2nd damaged CD-R. Sometimes, the disk icon of that CD even does not appear on Workbench, and sometimes even the filesystem crashes. Didn't you test at all? My configuration is: A4000, Yamaha CDR 100, Toshiba 4101, Noname CD-Rs. Answer: I guess you tested the CD-Rs on your Toshiba CD-ROM drive. Toshiba CD-ROM drives (and CD-ROM drives of some other companies, too) are known to cause problems with some special CD-Rs. The same CD-Rs run without any problems on other drives. Try it! Your "damaged" CD-R will most likely run without any problem on some other CD-ROM drive. Read the "Compatibility" file. It contains the name of some CD-Rs which seem to be good. Question: I tried to copy a CD to CD-R. I read from my CD-ROM drive and wrote directly to my CD writer, without using a temporary file. This worked fine for a while. My CD-ROM drive reads in 12x speed and my CD writer writes in 4x speed. But suddenly, the CD-ROM drive delivered the data very slow and I got a buffer underrun. Another coaster. :-( Please fix this. Answer: There's nothing to be fixed. CD-ROM drives usually slow down when they have to read from a scratched surface. After passing the scratch, some of them go back to full speed, others stay at the slow speed. That's what happened in your case. Sorry. You should either get a firmware update for your CD-ROM drive which fixes that (if available) or you have to use a temporary file for scratched CDs. Another thing that could help is reducing the speed of your CD writer. Question: Transfer rate My CD-ROM drive is faster than it is supposed to be -- at least it seems so. The MakeCD writing window shows very fast transfer rates for it. Why? Answer: MakeCD measures the time from sending a read request to the CD-ROM drive until the read request comes back with the required data. That's all. There's nothing magic in it. However, many drives are using intelligent buffer methods, and during the time MakeCD is not accessing the drive, they fill their cache with some data -- hoping it's the data which the application will try to read next time. Often, that's really the data which MakeCD will request next time, and then the drive can send the data directly from the buffer to MakeCD and does not have to access the CD at all. That's why it is seems to be so fast. If there were no pauses for the drive between two requests, which can be used to fill the internal buffer, it would be slower. Question: The idea of using the track name as the filename for the ISO image filename is good and saves time but these files are always written into PROGDIR: unless the path is changed manually. When dealing with many ISO files this is cumbersome. Could you please add a feature to allow a default directory to be set? Answer: You mean the "base dir" string gadget at the upper left corner of the main window? Just enter your working directory there. Question: I want to read a CD with data and audio tracks. However, at the end of a data track MakeCD reports a read error!? Answer: When listing the contents of a CD MakeCD only tries to remove the pause at the end of a track from the track's length since V2.0. If you use the length suggested by older versions you will get a read error as soon as MakeCD reaches the pause after a data track, because pauses can only be read after audio tracks. You can either reduce the size of the track before starting reading, or you can ignore the error by selecting "Use File" in the requester reporting the error -- or update to V2.0 :-) Question: Reading and writing of data tracks works fine even with disconnect, but I get into trouble when using other track types. Why that? Answer: Some controllers increase performance by making assumptions for example about the block size they are to transfer, e.g. block size is a power of two or an even multiple of x bytes (x = 32, 64, ...). These assumptions are wrong for such unusual block sizes like 2352 bytes (audio track) and the controller software fails. Question: With which CD writers can I use the repair option in the "Target CD-R" window? Which kind of damage can I repair? Answer: When the writing is interrupted by a loss of power, then the Philips writers and compatibles offer a command to make the CD-R useable again -- however, only if the CD-R was not removed from the drive yet! This is the feature the Philips drivers use. The Yamaha writers don't support this kind of repair. In case the data stream is interrupted while the writer is still working, most drives finish the last track automatically. The track is simply too short. Question: I accidently removed a small label attached on a CD-R, together with a small piece of gold surface on the label side. Now there is a see-through hole near the centre of the CD-R. Can I put some paint on it to cover the hole? I've tried to stick back the piece but the disc is still unreadable. Any other way to rescue the disc? Answer: Nope, it's a coaster. Removing a label often removes the reflective layer, which destroys a CD-R. Question: I just have updated MakeCD. But the new version obviousely does not work, because one of the .module files has a wrong version number. At least, a MakeCD requester tells me that. Answer: Of course, it @{B}could@{UB} happen that we release a buggy update. But usually this misbehaviour is caused by something different. Both, the .module and the .driver files are libraries (although you NEVER should copy them to LIBS:). This means, that they stay in your memory after you left MakeCD, until a memory allocation flushes them. So they are reloaded only if that's really needed when you restart MakeCD. If you have started an old version of MakeCD, before starting the new version, this misbehaviour might happen. Just reset your AMIGA -- after that everything should work as usually. MakeCD V2.0 tries to do a memory flush itself. @EndNode @Node "F-GUI" "MakeCD.guide/F-GUI" @Toc "MFAQS" @{B}GUI related questions =====================@{UB} Question: The online help of MakeCD causes trouble with CycleToMenu and MagicCX. What can I do against this? Answer: You should not install hacks. Well, probably you do not want to remove these hacks, do you? So after you have understood MakeCD, we suggest you to use the menu to turn off bubblehelp to avoid the problem. Note that the bubble help is from triton.library and so we cannot change its behaviour. Question: I want to save the window sizes or open the windows on a public screen. Is this possible? Answer: Since the windows are from triton.library, you can use the Triton preferences editor to achieve both. You don't have to register Triton for this -- but of course Stefan Zeiger would be pleased if you do so nevertheless :-) You can find the full Triton system with preferences editor on Stefan Zeiger's homepage `http://home.pages.de/~szeiger/'. See `doc/Triton.readme' for more details. Here's a part of the Triton documentation: @{I} If you want to register, please send DM20, US$15 or an equal amount in any other valid currency to me. See Support, for addresses. Send money by EuroCheque (only in German Marks (DM)!), postal(!) money order or cash! It's impossible for me to cash in foreign cheques, even if the amount is in DM. EMail: `triton-support@laren.rhein-main.de' Mail: Stefan Zeiger Seligenstädter Weg 24 D-63796 Kahl Germany Voice: +49-6188-900712 @{UI} @EndNode @Node "FSETT" "MakeCD.guide/FSETT" @Toc "MFAQS" @{B}Questions about the settings ============================@{UB} Question: What is the difference between sequential and parallel reading/writing? Which one should I use? Answer: MakeCD 1.0 always used the parallel method: Two independent processes read or write simultaneously. In the sequential mode buffers of the same size are read and written alternating. The parallel method is more demanding in regard to the system's reliability. It works only well if disconnect is supported properly and is enabled for both harddrives, CD-ROM drive and CD writer or different controllers are used for source and target. The sequential method avoids several potential flaws of controllers. It has another drawback: When a read request is delayed, the next write request cannot start and the data stream is interrupted even if the buffer is not empty, i.e. the buffer cannot compensate temporary fluctuations of read performance any more. @EndNode @Node "MGLOS" "MakeCD.guide/MGLOS" @Toc "Main" @{B}Glossary ********@{UB} Sorry, this glossary is not yet finished. A lot of expressions still have to be explained. Bug Report Larger projects invariable contain some ugly errors which the user may encounter at some time. In such cases, we ask that the user submit a "Bug Report". This is a description of the error which has been encountered. Check the circumstances under which the error occurs and write down everything! Note the @{B}exact@{UB} version of MakeCD which you are using and the configuration of your computer. CD-R A "CD-R" is a write once CD. It looks a bit like a normal CD, but uses a different color. The writable side usually is green, gold or blue. The non-writable side often covers some kind of label which you may write on. But sometimes, this side is totally unlabeled and unprinted, so some people get the idea to put the CD-R upside down into their drive. CD-RW "CD-RW"s are the new, rewritable CDs. This media can be written to up to 1000 times. CD-ROM image CD-ROMs, but disks, hard disks or just single partitions can be written to a single file, by means of "unrolling" them so that the file contains blocks starting from the lowest (0) through to the highest-numbered block at the end. Such a file contains a "Disk Image". At some time thereafter, the file can be written to a CD-R to yield an exact copy of the original CD-ROM. The CD-ROM has, in principle, been copied. However, if you want to save data from a hard disk to a CD-R, you can @{B}not@{UB} just copy the image of the hard disk to CD-R. That's why you need the image creation part of MakeCD: it scans one or more directory trees and creates an CD-ROM image file that can be written to a CD-R and yields to a valid CD-ROM. Coaster A "Coaster" is a damaged CD-R(W), which is totally useless (except you can put it under your programming cup). Coffee Break A coffee break is that amount of time required by a program to do a particular task in background. Most of the time, there's no precise indication of how long this is. Sometimes, it won't be long enough to get the kettle to boil, yet at other times, you'll have enough time to invite the neighbours around to share the latest gossip over some cake. I'd like to take this opportunity to apologize to those who may have been misled that a @{B}single@{UB} cup of coffee was sufficient, by my comments on "Meeting Pearls III". Of course, a @{B}bucket@{UB} of coffee was what I meant. :-) Device Unit See "Unit". Device Driver Every hard drive and every CD writer requires a "Device Driver" so that it can be used in the AMIGA in a system-conformant way. This driver is responsible for reading data from, and writing data to the CD writer, amongst other tasks. Devices drivers have a name ending in `.device'. For example; `scsi.device', `gvpscsi.device', `omniscsi.device', `z3scsi.device', `dracoscsi.device', etc. Installer Script A unified method of installation for all software packages on the AMIGA was developed to make this as simple as possible. Every package includes a plain-text file -- the Installer script -- to be interpreted by the Installer program at installation time to make the installation process as independent as possible of the prior knowledge of the user. Meeting Pearls You don't know about Meeting Pearls? That's got to be fixed straight away! Meeting Pearls is Germany's most popular CD-ROM series for the AMIGA as well as being extremely good value for money as the creators don't demand any payment for their work (1), so only direct production and distribution costs need to be paid. As you most likely have a CD-ROM drive or a CD writer, it's well worth a look. mkisofs A program which is quite popular on Unix system and which is used to create "CD-ROM images". Program Icon Many programs have an icon -- a small symbol on which you can click when it appears on the Workbench. Icons belonging to programs are called "program icons". Further information about this can be found in your Workbench manual. Progress Indicator The "progress indicator" indicates what proportion of work has been done by the use of a bar graph. On occasions, this indicator will move at a very uneven rate. This will always occur if the it wasn't possible to pre-compute how long the particular operation would take or if your system is too busy to update the GUI elements. Rock Ridge extensions "Rock Ridge extensions" have been defined for Unix machines, because under Unix -- like on the AMIGA, too -- there are some file attributes which have been unknown on those MS-DOS machines and so were not included in the ISO9660 standard. Rock Ridge extensions are extensions on ISO9660. Every correctly written CD-ROM, which has Rock Ridge extensions, can be also read by filesytems that don't support Rock Ridge. However, most likely some objects will look different. Angela Schmidt and some other persons have created a new AMIGA standard, that enables mastering software to write Amiga attributes for every single object on the CD-ROM to the CD-ROM. This is done by defining another Rock Ridge extension. Of course, MakeCD supports this special Rock Ridge extension, too. Session An emtpy CD-R always contains one open session, the 1st session. Before closing the session or the CD-R, you have to write at least one track into the session. When closing the session, a new session is automatically opened, and you may write further data into it. When closing the CD-R, no new session is opened, and you can't add any further data to the CD-R. A closed session always contains one or more tracks, an open session does not have to contain any tracks. A track must @{B}not@{UB} be spread over several sessions. Track A track is a continuous stream of data on CD. As for music CDs, each song usually gets its own track. So you can easily select the wished song using the display of your CD player. All you have to know is the track number. If you write a music CD, you should create a track for each song, and so a music CD often covers 10 to 20 different tracks. A simple data CD only covers one single track, which contains all data. A multisession or multivolume CD covers several tracks, which contain data, each. Unit A particular device, which is usually connected to the SCSI bus, is identified by its "unit" or "device unit". Valid unit numbers are typically between 0 and 6 for SCSI devices. If you have any external SCSI device, this may have a switch for setting a number. The number is usually the unit number of the device. The comfortable device requester of MakeCD shows you all devices that are connected to the SCSI bus. Volume Name The @{B}formatted@{UB} name of a disk or partition is the "volume name". This name is also visible on the `Workbench' screen. MakeCD can write such a volume name into an ISO 9660 image, if you are a registered user. However, according to the ISO 9660 specs, in ISO Level 1 or 2, only upper case characters, digits and the underscore are allowed in the volume name. ---------- Footnotes ---------- (1) although donations are most welcome :-) @EndNode @Node "MSUPP" "MakeCD.guide/MSUPP" @Toc "Main" @{B}Support *******@{UB} We do your best to offer you our support for MakeCD. If possible, we use the internet to support MakeCD since we think that this is a comfortable way. Answering letters costs a lot of time - much more than writing an email. So we ask persons who don't have email access, to call us instead of sending a letter, since letters might stay unanswered. Sorry, our time is limited. If you have internet access, we entitle you to use the possibility to get support from the internet. @{" Updates " Link "SUPDT"} Updates of MakeCD @{" Mailinglisten " Link "SMLLS"} MakeCD mailing lists @EndNode @Node "SUPDT" "MakeCD.guide/SUPDT" @Toc "MSUPP" @{B}Updates of MakeCD =================@{UB} MakeCD is still in development. You will find the latest versions of MakeCD, new drivers for CD-Rs etc. in internet: `http://www.uni-karlsruhe.de/~un60/MakeCD.html' Additionally, you can get the latest version for free (you only pay shipping costs) from Katrin Schmidt. Of course, this offer is limited to one disk per order. See Registerform. @EndNode @Node "SMLLS" "MakeCD.guide/SMLLS" @Toc "MSUPP" @{B}Mailing lists =============@{UB} There are three different, English-spoken mailing lists for MakeCD: `ml-makecd@unix-ag.uni-siegen.de' For discussions with other users of MakeCD. The authors of MakeCD will read this list, too. They can thus answer questions noone else possibly could. Sometimes the authors will ask you to comment about a new feature etc. `ml-makecd-announce@unix-ag.uni-siegen.de' No discussions, just announcements by the authors. For example, we will announce new versions and new drivers on this list. `ml-makecd-binaries@unix-ag.uni-siegen.de' This list delivers all new MakeCD binaries, including new releases of MakeCD and new drivers, right to your mailbox. It is useful for those who do not have access to ftp servers or homepages on the internet and thus usually are unable to download new MakeCD archives. To subscribe, send `SUBSCRIBE ' to `-request@unix-ag.uni-siegen.de', where `' is the name of the mailing list, e.g. `ml-makecd-announce'. Don't send requests to the lists themselves, i.e. don't forget the `-request' in the address! To subscribe the email address `user@my.email.address' to the announce list, send the following message: To: ml-makecd-announce-request@unix-ag.uni-siegen.de Subject: Anything SUBSCRIBE user@my.email.address To unsubscribe, send a similar message, but replace `SUBSCRIBE' with `UNSUBSCRIBE'. Send the following message to get further instructions: To: listserv@unix-ag.uni-siegen.de Subject: Anything HELP @EndNode @Node "MAUTH" "MakeCD.guide/MAUTH" @Toc "Main" @{B}Authors of MakeCD *****************@{UB} Two persons worked hard at MakeCD. EMail to both authors: `makecd@ira.uka.de' Patrick Ohly He programmes the GUI, all the SCSI stuff (including all the drivers for CD writers and CD-ROM drives) and almost everything of MakeCD except the ISO image creation routines. His address is: Patrick Ohly Weechstr. 1, WG E0/1 76131 Karlsruhe Germany Telephone: +49 721 615662 E-Mail: Patrick.Ohly@stud.uni-karlsruhe.de Homepage: http://www.uni-karlsruhe.de/~un60/ Angela Schmidt She programs the ISO image creation routines (and everything that has something to do with ISO images), most of the registration window and the installer script. She compiles the distribution archives and writes the manual. Her address is: Angela Schmidt Klosterweg 28/I501 76131 Karlsruhe Germany Telephone: +49 721 695307 E-Mail: Angela.Schmidt@stud.uni-karlsruhe.de Homepage: http://home.pages.de/~Angela/ @{B}Please read the docs and the FAQ very carefully before contacting the authors with your problems. Questions, that are answered there, won't be answered by the authors.@{UB} In case you have trouble with your SCSI devices, e.g. if suddenly nothing works anymore and MakeCD cannot be aborted and there's no error message, then contact your dealer, please. In this case either your SCSI hostadapter or your CD writer does not work as it is supposed to work. We can't help you in that case - sorry. If your SCSI bus "hangs up" while your CD writer accesses the SCSI bus, you most likely have such a SCSI trouble. However, if MakeCD creates an error message, then contact us, please. Switch on `DEBUG' in the tooltypes of the MakeCD icon, reproduce the error and send the debug output to Patrick. Before contacting your dealer, read our FAQ and our Compatibility list. @EndNode @Node "MCRDT" "MakeCD.guide/MCRDT" @Toc "Main" @{B}Credits *******@{UB} Heinz Wrobel · Valuable suggestions for a GUI that is easier to use. · English translation of some parts of MakeCD. · HWGCTRLscsi · NSDPatch · Hunting up JVC firmware bugs. HiSoft, England · English translation of parts of the manual · Distribution of MakeCD in Great Britain. Sven Hansen · English translation of parts of the manual · Great/many bug reports/suggestions Jean-Marc Boursot · French translation · Testing with care and very useful suggestions Frank Arlt · He lent us a JVC XR-W2010 for many weeks Matthias Supp · Great/many bug reports/suggestions · He lent us a Yamaha CDR 400 Oliver Kastl · Help with questions about SCSI or CD-ROM technology Christian Berger Frank Zündorff Friedhelm Bunk Horst Brand Jesper Tuck Klaus Melchior Magnus Bouvin Martin Schulze M. L. Lie Michael Knoke Mirko Schäfer · Great/many bug reports/suggestions Lars Eilebrecht · MakeCD mailing lists Michael van Elst · CDDA sources Michael-Wolfgang Hohmann · Most of the icons used in the MakeCD distribution. @EndNode @Node "INDEX" "MakeCD.guide/INDEX" @Toc "Main" @{B}Index *****@{UB} @{" MakeCD, latest version " Link "FSUPT"} FSUPT @{" Advantages of Rock Ridge " Link "MIRRA"} MIRRA @{" Alterations " Link "LALTR"} LALTR @{" Amiga attributes " Link "MIRRA"} MIRRA @{" Amiga file comments <1> " Link "MIRRA"} MIRRA @{" Amiga file comments " Link "FDATA"} FDATA @{" Amiga protection bits <1> " Link "FDATA"} FDATA @{" Amiga protection bits " Link "MIRRA"} MIRRA @{" Audio CDs " Link "FAUDI"} FAUDI @{" Audio CDs, copy of " Link "FAUDI"} FAUDI @{" Audio CDs, noise in music " Link "FWRTP"} FWRTP @{" Backups on CD-R " Link "MIRRA"} MIRRA @{" Bank account " Link "FSUPT"} FSUPT @{" Buffer underflow " Link "FSCSI"} FSCSI @{" Buffering " Link "MIBUF"} MIBUF @{" Bug Report " Link "MGLOS"} MGLOS @{" CD Extra " Link "MICDE"} MICDE @{" CD writer problems " Link "FWRTP"} FWRTP @{" CD writers " Link "MICDW"} MICDW @{" CD-R " Link "MGLOS"} MGLOS @{" CD-ROM drives " Link "MICDW"} MICDW @{" CD-ROM image " Link "MGLOS"} MGLOS @{" CD-Rs " Link "MICDR"} MICDR @{" CD-RW " Link "MGLOS"} MGLOS @{" Cheque " Link "FSUPT"} FSUPT @{" Coaster <1> " Link "MICDR"} MICDR @{" Coaster " Link "MGLOS"} MGLOS @{" Coffee Break " Link "MGLOS"} MGLOS @{" Compatible CD writers " Link "MICMP"} MICMP @{" Copy problem " Link "FVRIO"} FVRIO @{" Copyright " Link "LCPYR"} LCPYR @{" Cracked MakeCD " Link "FVRIO"} FVRIO @{" Crash, device requester " Link "FVRIO"} FVRIO @{" Damaged CD-R " Link "FVRIO"} FVRIO @{" DAO " Link "MIDAO"} MIDAO @{" Data CD, defective " Link "FVRIO"} FVRIO @{" Data CD, missing files " Link "FVRIO"} FVRIO @{" Data CDs " Link "FDATA"} FDATA @{" Device Driver " Link "MGLOS"} MGLOS @{" Device requester, crash " Link "FVRIO"} FVRIO @{" Device Unit " Link "MGLOS"} MGLOS @{" disc-at-once " Link "MIDAO"} MIDAO @{" Disclaimer " Link "LDISC"} LDISC @{" Disconnect/Reselect " Link "MIBUF"} MIBUF @{" Euro cheque " Link "FSUPT"} FSUPT @{" Filesystem for CD writer " Link "FWRTP"} FWRTP @{" Filesystems supporting Rock Ridge " Link "MIRRA"} MIRRA @{" Fixation of CD-R " Link "FVRIO"} FVRIO @{" Fixation of CD-Rs " Link "MISCF"} MISCF @{" Fixation of sessions " Link "MISCF"} MISCF @{" Fixing a CD-R " Link "MISCF"} MISCF @{" Fixing a session " Link "MISCF"} MISCF @{" Fixing empty sessions " Link "MISCF"} MISCF @{" Glossary " Link "MGLOS"} MGLOS @{" GUI " Link "F-GUI"} F-GUI @{" Handling CD-Rs " Link "MICDR"} MICDR @{" Hangup " Link "FSCSI"} FSCSI @{" HFS " Link "MIHFS"} MIHFS @{" Hybrid CDs " Link "MIHFS"} MIHFS @{" Installation " Link "MINST"} MINST @{" Installer Script " Link "MGLOS"} MGLOS @{" Instructions " Link "MISTR"} MISTR @{" Introduction " Link "MINTR"} MINTR @{" ISO 9660 <1> " Link "MIRRA"} MIRRA @{" ISO 9660 " Link "MIISO"} MIISO @{" ISO 9660 AMIGA " Link "MIISO"} MIISO @{" ISO 9660 directory level restriction " Link "MIISO"} MIISO @{" ISO 9660 directory levels " Link "FDATA"} FDATA @{" ISO 9660 file name restrictions " Link "MIISO"} MIISO @{" ISO level 1 " Link "MIISO"} MIISO @{" ISO level 2 " Link "MIISO"} MIISO @{" Joliet " Link "MIJOL"} MIJOL @{" JVC problems " Link "FWRTP"} FWRTP @{" Label for CD-R " Link "FVRIO"} FVRIO @{" Labelling CD-Rs " Link "MICDR"} MICDR @{" Legal " Link "MLEGL"} MLEGL @{" Licence Agreement " Link "LLICA"} LLICA @{" MakeCD, cracked " Link "FVRIO"} FVRIO @{" MakeCD, virus infected " Link "FVRIO"} FVRIO @{" Meeting Pearls " Link "MGLOS"} MGLOS @{" Mixed CD-Rs (audio and data) " Link "MICDE"} MICDE @{" Mixed CDs (audio and data) " Link "MIMIM"} MIMIM @{" Mixed Mode " Link "MIMIM"} MIMIM @{" mkisofs " Link "MGLOS"} MGLOS @{" Multisession " Link "MIMUS"} MIMUS @{" MultiSession " Link "MIIOP"} MIIOP @{" Multisession <-> Multivolume " Link "MIMVC"} MIMVC @{" Multivolume " Link "FDATA"} FDATA @{" Multivolume CDs " Link "MIMVC"} MIMVC @{" Multivolume filesystem " Link "MIMVC"} MIMVC @{" Notes for beginners " Link "MBEGN"} MBEGN @{" Online help " Link "F-GUI"} F-GUI @{" Parallel reading/writing " Link "FSETT"} FSETT @{" Pause between tracks <1> " Link "FAUDI"} FAUDI @{" Pause between tracks <2> " Link "MIDAO"} MIDAO @{" Pause between tracks " Link "MITAO"} MITAO @{" Payment of registration fee " Link "FSUPT"} FSUPT @{" PMA " Link "MITUS"} MITUS @{" Postal money order " Link "FSUPT"} FSUPT @{" Problems reading CD-Rs " Link "MICDR"} MICDR @{" Problems reading CD-Rs with several sessions " Link "MITUS"} MITUS @{" Program Icon " Link "MGLOS"} MGLOS @{" Progress Indicator " Link "MGLOS"} MGLOS @{" Public Screen " Link "F-GUI"} F-GUI @{" Questions " Link "MFAQS"} MFAQS @{" Reading unfixed sessions " Link "MITUS"} MITUS @{" Registration <1> " Link "FSUPT"} FSUPT @{" Registration " Link "LREGI"} LREGI @{" Repair CD-R " Link "FVRIO"} FVRIO @{" Reselection " Link "MIBUF"} MIBUF @{" Rock Ridge " Link "MIRRA"} MIRRA @{" Rock Ridge extensions " Link "MGLOS"} MGLOS @{" Romeo " Link "MIROM"} MIROM @{" Saving of the registration number " Link "FSUPT"} FSUPT @{" SCSI hangups " Link "FWRTR"} FWRTR @{" SCSI problems " Link "FSCSI"} FSCSI @{" Selection of driver " Link "MICMP"} MICMP @{" Session " Link "MGLOS"} MGLOS @{" Sessions " Link "MITUS"} MITUS @{" Settings " Link "FSETT"} FSETT @{" Space requirements for Rock Ridge extension " Link "MIRRA"} MIRRA @{" Space requirements for tracks and sessions " Link "MITUS"} MITUS @{" Support " Link "FSUPT"} FSUPT @{" Supported devices " Link "FWRTR"} FWRTR @{" TAO " Link "MITAO"} MITAO @{" Test mode " Link "MITST"} MITST @{" TOC " Link "MITUS"} MITUS @{" Toshiba CD-ROM drives " Link "MICDR"} MICDR @{" Track " Link "MGLOS"} MGLOS @{" Track-at-once " Link "MITAO"} MITAO @{" Tracks " Link "MITUS"} MITUS @{" Trademarks " Link "LTRAD"} LTRAD @{" Unit " Link "MGLOS"} MGLOS @{" VISA card " Link "FSUPT"} FSUPT @{" Volume Name " Link "MGLOS"} MGLOS @{" Window sizes " Link "F-GUI"} F-GUI @{" Write append error <1> " Link "FSCSI"} FSCSI @{" Write append error " Link "FWRTP"} FWRTP @{" Writing on CD-Rs " Link "MICDR"} MICDR @EndNode