How do I record the image file to a CD?
CDEveryWhere does not record directly to a CDR or CDRW. It creates a special file called an "ISO image" that contains the actual data that should exist on the CD. Your CD recording software must support recording an ISO image (not raw image) to the CD, most software can do this. An ISO image is not the same as a raw image, although they are sometimes called the same. A raw image contains special error detection and correction codes that the CDR software will generate as it is writing the ISO image to the CD. The software will have a special command for this. You cannot simply add the image file to the CD layout as you would when recording normal files off your hard drive. For example, Adaptec's Easy CD Creator 3.0 uses the menu command "File | Create CD from Disc Image..." to record image files. Please see your software's manual or help file on recording images to a CD.
Do I need a Macintosh computer or hard drive to create a "hybrid" ISO/Macintosh CD-ROM ?
No. CDEveryWhere creates the Macintosh volume without the need for a Macintosh computer or hard drive. Some packages that create hybrid CDs require you to create your Macintosh volume on a Macintosh and then move the hard drive to your PC. The volume is read from the hard drive and added to the end of your ISO/Windows volume.
CDEveryWhere creates the Macintosh volume itself, on top of the other platforms. There are two benefits to this approach. First, you don't need a Macintosh and second, all platforms share the files to reduce overhead. Macintosh attributes are preserved through use of MacBinary and BinHex files. CDEveryWherecan decode these files as described in the help document. Please look at the Hints for writing Macintosh files on Windows or Unix.
How do I preserve Macintosh resource forks on Unix or Windows?
Macintosh files are stored on non-Macintosh drives in several ways. The most popular formats are MacBinary and BinHex. CDEveryWhere can decode these formats while writing the image. Typically MacBinary files have a ".bin" extension and BinHex files have ".hqx". By default, CDEveryWhere will decode these when included in the image. In the image preview, the Macintosh filename will appear instead of the ".bin" or ".hqx" filename. You can also see the file type and creator for each file in the "Macintosh" tab.
Non-Macintosh users can include Macintosh applications and files in their images. If the application is available from a web or FTP site, download the .bin or .hqx file to your hard drive. Include the file in the image and it will be decoded for you. The application will run from the CD on a Macintosh.
Please also read the manual's Create Layout section.
Why does CDEveryWhererun slowly on Windows NT when writing the image?
Microsoft Windows NT does not handle writing large files efficiently. One test showed that a 500MB image took 3 hours to write on the local hard drive. It took only 20 minutes when writing to a shared (network) drive. It is suggested that if two machines are available, use one for running CDEveryWhereand the other to store the image. This problem does not occur with Windows 95.
Why does Adaptec's Easy CD Creator say that it doesn't recognize my image format?
Easy CD Creator has its own image file format. CDEveryWhere creates an ISO image, a byte-for-byte file of the data that should be written to the CDR. You may need to upgrade Easy CD Creator to be able to use the ISO image. This upgrade can be downloaded from http://www.adaptec.com. After you have the newest version, select the "ISO Image Files (*.iso)" option from the "Select Image File" dialog.
You also may experience problems if you create a pure Macintosh CD. Easy CD Creator attempts to detect if the file you select is in ISO format. Recreate the image with the "Standard CD-ROM" option enabled.
Why does Norton Utilities for Macintosh find errors on a CD that I made with CDEveryWhere?
The "errors" are not really errors at all. The reason these results appear is due to how the hybrid CD is created. Some parameters of the volume are not the expected values on a normal Macintosh volume. These differences still conform to the volume specification published by Apple Computer, Inc.
If you do a disk scan using either Norton Utilities, Disk First Aid, or some other utility, you will get volume bit map errors. The volume bit map records which areas of the disk are used. The cause is data that are used by non-Macintosh platforms. Those areas of the disk are marked used but no Macintosh file uses them. It is correct to report the error, but it will not affect using the CD.
Does CDEveryWhere support multisession?
Currently, the image created by CDEveryWheremust be written in the first session. There is an exception for Macintosh, which can read images off multisession CDs.
How do I get the "right-click" menu on a Mac?
Use Command-Click (a.k.a Open Apple-Click).
How do I get my Mac custom icons to display in the Finder?
You need CDEveryWhere v1.2 build 46 or later. You can get the latest version at upgrade
You must archive a Mac directory that has the custom icons you want. Archive your Macintosh directory using the instructions in the Hints page in the section "Copying Files from a Macintosh to Windows". Custom icons for directories and files will be preserved when they are drag and dropped into the layout. You must use the AUXZip utility to preserve directory icons. An "Icon" file will display in the layout but will not be seen by the Mac user. For volume icons, include an "Icon" file (created by setting a custom directory icon) in the root of the CD layout.
How do I get my Mac CD to open a window when the CD is inserted?
As of CDEveryWhere v1.2 build 46, we do not support opening a window when a Mac CD is inserted. We do plan to support this feature in the future.
How do I preserve Macintosh file and directory names with special characters (TM, (C), etc)?
You can preserve these characters using one of the following methods:
Macintosh files archived with AUXZip (see Hints) and opened with CDEveryWherev1.2.1 and later by selecting "Get From" menu option.
CDEveryWhere v1.2.2 and later support Windows NT "Services for Macintosh" volumes. All filename characters are preserved.
CDEveryWhere v1.2 build 46 and later preserves the characters for MacBinary and BinHex encoded files.
Run CDEveryWhere on a Macintosh.
We have had several reports of Aladdin Expander 5.0 creating corrupted MacBinary files. We have provided a utility for the Mactinosh called AUXZip to archive Macintosh files and directories while preserving all attributes. It is easier to use than StuffIt and is free to use. Please see the instructions for using AUXZip on the Hints page.
Why doesn't CDEveryWherework with my FTP server?
CDEveryWhere supports most major FTP servers. Most Unix (and clones), Microsoft Internet Information Server and AS/400 are supported. If your server is not supported, please send email to support@cdeverywhere.com with the following information:
Why doesn't HP-UX recognize long filenames?
In order for HP-UX to recognize RockRidge extensions, you need to mount the CD using the pfs_mount command instead of mount_cdfs. pfs_mount is licensed from Young Minds, Inc. and included for free in all HP-UX versions from 10.0 and above. If you are using automounter, you cannot set it up to automount RockRidge (as of version 11.0). Later versions of HP-UX may let you do this or have RockRidge built into cdfs.
CDEveryWhere does not record CD audio tracks. It will record audio files from your computer onto the CD as a file. For example, you can record a WAV or MP3 file to a CD that can be read by other platforms. You cannot record a WAV file to the CD that can be played by a CD player. CDEveryWhere only creates data CDs. You cannot add an audio track to the end of the ISO image file using CDEveryWhere.
What is the different between demo version and the full version of CDEveryWhere?
The demo version has all the features of the full version except that it only allows you to create up to 50MB of the image and it will generate a demoonly.txt file in the image to indicate that it is the demo version.
Why does the demoonly.txt is on the CD image I created?
The demoonly.txt will only appear on the demo version of the CDEveryWhere. If you are using the full version and the demoonly.txt still appear, please contact the customer support at support@cdeverywhere.com.
I can't browse my hard drive (C:). My OS is Windows ME. What Should I do?
Remove "WinAPI.dll" files from the installation directory of CDEveryWhere.
What is the difference between Standard and Professinal Editions?
Please see Edition Comparison Page at versionCompare.shtml
Why does my CD has readme.txt file?
When you are using the CDEveryWhere Personal Edition, a "readme.txt" file will be automatically written to the root of every CD created, this file will overwriting any existing "readme.txt" file and explains that the CD was created using the personal edition and details the restrictions placed on use and distribution.
After upgrading Windows, CDEveryWhere says 'License Key is expired'.
Please uninstall and reinstall the latest version of CDEveryWhere from our website. If This doesn't solve your problem, please contact us at support@cdeverywhere.com.
AutoStart for Macintosh doesn't work on my Macintosh computer.
The AutoStart file must be in the root directory of the CD image/layout. Please follow the instruction in the on-line manual.
Note: CDEveryWhere set up the feature called QuickTime AutoStart. Mac OS quietly discontinued this feature due to the security problem. There is no way to auto start a file on a data CD on Mac OS X anymore. In fact, there is no standard way to open a particular file on a CD, such as autorun.inf file on Windows, when a CD is inserted into Mac OS X. How a Mac OS X behaves is highly depending on the user specific settings. In a sense, Mac OS X works similar to Linux systems. The rsultant CD still auto start on Mac OS 9 or 8.
How to copy files from Macintosh to Windows.
If you have a CDR drive for your PC and you want to record files from a Macintosh, you don't need to record the CD from the Macintosh. You can copy files from the Macintosh to the PC using either StuffIt (TM by Aladdin Systems) or the AUXZip utility provided by Interative Information R&D. AUXZip preserves more information than StuffIt and there is no charge to use it.
AUXZip
AUXZip is available at AUXZip.bin. It is a Java application encoded with MacBinary. You will need the MRJ 2.1 or higher available at http://www.apple.com/java. AUXZip is a single application, just download and execute. If you are using StuffIt to decode the MacBinary, you need to set the preferences to turn off the "Continue to Expand" option. This utility is freely available for anyone to use.
- Execute the AUXZip application
- Find the folder(s) and file(s) you want to copy in the left side of the window. Select one or more items and click the "Add" button. If you add a folder, AUXZip will archive all the folders inside of it. You may add as many items as you like. If you make a mistake, select the file or folder and click "Remove".
- Enter the name of the ZIP file to create.
- Click the "Zip" button. Each file will be displayed as it is being added to the archive. The "Zip" button will be disabled until the archive is finished. You may click "Cancel" to cancel the operation.
- Copy the file to the PC.
- If you have the professional version of CDEveryWhere, you can open the zip file using the "Get From | Zip Archive" command in the main menu. This is the only way to preserve special characters (such as the trademark character) that appear in file or directory names. Otherwise, you can unzip the files using your favorite unzip utility and add them as usual. You will lose any special characters that are in file or directory names when unzipping.
- If you are using the professional version, you can drag and drop any combination of directories and files from the opened archive. You will notice that CDEveryWhere displays the type and creator information in the top window along side each file. If you have an older version of CDEveryWhere, you will see ".resource" and ".finderinfo" directories. Please get an updated version of CDEveryWhere from the web site at http://www.cdeverywhere.com/updates.shtml.
- If you have unzipped the archive, you must use the "Get From -> Apple/Unix Volume" menu command to access the Macintosh portion of the files.
StuffIt
The archiver is shareware but the expander is freeware. They are both available at http://www.aladdinsys.com. Follow these instructions to write your Macintosh files to a CD image on your PC:
- Use StuffIt to create a .SIT archive of your files
- Copy the archive to your PC.
- Set the "Cross-Platform" options in Aladdin Expander 5.0 (or later) to:
- Never convert text files to Windows format
- Always save Macintosh files in MacBinary format
- Always (add or replace) file extensions
- Expand the archive using Aladdin Expander. The filenames that Aladdin Expander creates from your archive are not what will appear in the image. CDEveryWhere will extract the Macintosh filename from the MacBinary file.
- Add the ".MacBin" files to your image layout. The filenames should reflect the original Macintosh filename. In the "Macintosh" tab you will see the file type and creator.
AutoStart CD on Mac OS X in Classic Environment.
AutoStart CD on Macintosh Computers is available through Mac OS's QuickTime Autostart. This is available on HFS filesystem, which CDEveryWhere creates on the CD. In order to AutoStart the CD, you need to start up the Classic Environment on Mac OS X.
Apple's FAQ is available at http://devworld.apple.com/qa/qtpc/qtpc12.html
Please also read the manual at manual/en/autorun.shtml
Writing Macromedia Director and Authorware files
Please read the manual's Tips section for this topic.</>
Working with Macromedia Flash MX.
Mactmedia Flash MX can export your Flash presentation into two executable formats. One is the *.exe file for Windows PCs. Another is the *.bin/*.hqx file for Macintosh Computers.
With CDEveryWhere, you can auto-play these files at the insertion of the CD. In order to make this work, you need the Stardard or Professional edition of CDEveryWhere.
Writing Adobe Acrobat files and readers.
Adobe Acrobat files are cross-platform documents that require a reader ("Acrobat Reader") application to view and print them on the user's computer. It is simple to create a CD to enable most platforms to read your Acrobat files.
Installing and Starting CDEveryWhere on Mac OS X
After successfully installing CDEveryWhere, several alsiases (icons) will be created under your desktop. There are several issues reported that these aliases won't start CDEveryWhere. In order to start CDEveryWhere, please click on cdewc.command script file under the installation directory, which is typically /Application/CDEveryWhere.
Quick steps to set up HFS attributes (file association on Macintosh)
This feature is only available with the Professional Edition and the demo version.
1. Select Platform tab.
2. Click on Advanced Option button for Macintosh (HFS). The new window "Mac HFS Options" will pop up.
3. In the new window, select the File TYpes tab.
4. Click on the Add button. The new window "Add Type Definition" will pop up.
5. Enter the name of file type in the Name field, the HFS file type code in the Type field and the HFS file creator code in the Creator field. (You can leave the Creator field blank if you don't care which application will be used to open the file.).
6. Now enter the file name in File Pattern field and press the enter key on your key board.
7. Click on the OK button to close the window. Click on the OK button to close the window "Mac HFS Options".
8. Drag and drop the files and create an image.
Can I use CDEveryWhere to create an image for DVD?
CDEveryWhere doesn't support the DVD image creation, officialy. However, CDEveryWhere doesn't set any limitation on the size of the image file. We had conducted some research and non-extensive testing and concluded that CDEveryWhere can create about 3.7 GB of the image file. When the size approaches 4.0 GB, the image file starts to have a problem. This is probably because of the over head data for HFS filesystem support which has a limitation of 4.0 GB. So, if you don't need to support HFS, you may try disabling the support for HFS under the Platform tab.