X

Troubleshooting CD burning: FAXstf conflicts; Authoring Support; CDs for Windows

Troubleshooting CD burning: FAXstf conflicts; Authoring Support; CDs for Windows

CNET staff
3 min read
Disc Burner and FAXstf Regarding the previously mentioned conflict (see one and two) between FAXstf and Disc Burner, Michael Atteson writes: "Smith-Micro offered the following work-around (and it indeed worked!): 'Unplug any USB devices, including CD burners, that you might have connected to the computer, then restart. If the error message does not occur, then this is the problem. If you have more than one USB device, reconnect each one at a time, then restart until you get the error message. The workaround is to connect the device after startup, then you should be able to send faxes with the device connected."

Toast and FAXstf This also relates to another problem with FAXstf and CD burning software: Joshua Rafofsky writes: "With Toast FireWire Support 1.0.8 and FAXstf Pro 6.0.5 installed, I can crash my Power Mac G4 every time by simply hitting the Eject key on the keyboard. I can avoid this crash by disabling Toast FireWire Support, but of course Toast then no longer recognizes my burner."

Authoring Support update prevents CD burning for some

    Brian Wente writes: "Authoring Support 1.1.2 prevented Toast 4.1.2 from seeing my Que! Fire CD-R. I removed the FireWire Authoring Support extension and it works fine now."

    Corky Brown had a similar problem: "I could no longer burn CDs on my iBook Dual USB after installing Authoring Support 1.1.2. After reverting to Authoring Support 1.1, everything was fine.

These sound related to a previously reported problem between Authoring Support and third-party CD burning software (also see this TIL article).

CDs for Windows Larry MacDonald writes: "I have a Sony CRX 1600L CD-RW. Sony tells me that there is no way for me to burn a CD that a Windows machine can read that has long file names. Example: I want to copy a web site with long, mac, file names to a CD that a Windows machine can read. However, it cuts all the files names to ISO ssssssss.xxx format, so no links work."

    Updates:

    Thomas Ferrell suggests: "To make a CD for Windows in which the files have long names, put the files in a folder that has a short name and zip it. Burn this in ISO format. Transfer to the PC and then unzip."

    Joshua Ochs adds: "I know you can burn CD's that preserve long file names on both platforms. You need to make it a hybrid CD, and use Joliet extensions to ISO (the setting< varies depending on the version of Toast). I believe Toast 5's defaults do just this."

    Jason Bartlett replies: Try this with Toast 5: Select ISO 9660, click on Data and select the Settings tab.Change format to CD-Rom XA and Naming to Allow Macintosh names. This has always worked for me. It does require that a person have a modern CD drive that can read the CD-ROM XA format, and Windows 9x or 2000."

    Daniel Levy writes: "In Toast, choose either ISO 9660 or Hybrid CD (if you want the disk to be native for the Mac as well) format and then click the 'Data...' button for the ISO section. Under the settings tab just choose 'Allow Macintosh Names' and burn the disc. The format doesn't have to be CD-ROM XA to work. I've been doing this for years. Just remember is that filenames that are illegal on the PC will cause the file to be unreadable when you try to open it in Windows."

    Kelly Davies similarly adds: "You can create a Windows CD that keeps the long Mac file names with Toast 4.x/5.x. When creating an ISO disk, you can select a option for the Joliet file names which allows Windows file names up to 31 characters. Note, though, that the Mac will only display the 8.3 names of an ISO disk because the Mac does not support the Joliet convention.