Frequently asked questions ========================== Please read these questions and answers carefully, before asking any questions. Maybe your question is answered in this list. Q: The online help of MakeCD causes trouble with CycleToMenu and MagicCX. What can I do against this? A: 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. Q: I want to save the window sizes or open the windows on a public screen. Is this possible? A: Since the windows are from triton.library, you can use the Triton preferences editor to achieve both. Feel free to register Triton. Q: Are there any mailing lists for MakeCD? A: Yes, there are. Refer to "english/MakeCD.txt". Q: When will you add support for my CD writer XYZ? A: 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. Q: 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? A: 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. Q: I have written a CD, but it seems to be damaged. My CD-ROM drive cannot access it. :-( A: You have to fix the session or the CD-R in order to access the CD in your CD-ROM drive. Q: When will MakeCD be able to write multisession _datatracks_? A: Multisession datatracks are planned for version 2.0 of MakeCD. Q: How can I set the length of the pauses between the tracks? A: 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. Q: Is there a possibility to copy a CD with multiple tracks without pauses despite of the fact that writing will add pauses? A: 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. Q: 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? A: You need a filesystem that supports Amiga Protection Bits. The freely distributable AmiCDFS2 supports them since version 2.30. AsimCDFS will support them starting with version 3.7. The author of CacheCDFS has promised to follow soon and has a working beta version. Q: I have entered and saved my registration number and address. Nevertheless, the next time the MakeCD registration requesters pops again. What's wrong? A: 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. Q: What is the difference between sequential and parallel reading/writing? Which one should I use? A: 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. Q: 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? A: I 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. Q: Reading and writing of data tracks works fine even with disconnect, but I get into trouble when using other track types. Why that? A: 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.