![]() |
Frequently Asked Questions | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Summary: FAQ (Frequently Asked Questions) on all aspects of data transfers and file exchanges between Macintosh and PC, using our MacDisk and other utilities. Explanation of some specific aspects of Macintosh files and how to cope with them in MacDisk. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
Using the FAQ
On the other hand, conversion means transforming the contents of a file to allow another program to open it (e.g., conversion of a WordPerfect file to open it in Microsoft Word). If you're transferring files between Word for the Macintosh and Word for Windows, for an example, you don't need any conversion. The word processor manages everything. Anyway, we bundle our programs with a little conversion utility, which can be helpful, mostly with some Macintosh text formats. See our data sheet on MacText.
When the program can't identify the signature in whole or in part, it uses the default "TXT" extension. This option can be canceled in the 'Preferences' item of the 'Options' menu of Macdisk. To get a more useful result, for example, the "QXD" extension for a Macintosh QuarkXpress file (don't bother, this one is already in the table), you will have to edit the internal table of the program. You have to look at the signature of a known good file, on a Macintosh medium (look in the last column of the Display panel, or in the 'Properties' dialog box), and put it in the table with the correct PC extension using our SignEdit utility. It is also possible that the signature file got corrupted or deleted or moved. Please check that the program points to the correct file in the registry. To do that, select the 'Registry' item in the 'Expert' menu and look at the contents of the key stored in the registry. Check that this file exists. You can also click on the 'Browse' button to search for this file. If the file was deleted, you can download a new copy from this site. You can also consult our page on signatures for more information and for a list of the most commonly used signatures.
On the Macintosh A double click doesn't launch the correct application, and you are asked whether you want to open the file in SimpleText. The cause may be that you don't have on this computer the program you need to open a precise data file, say Tiff files. The cause may also be that our programs don't know the MS-DOS extension of the source files and could only put a generic signature on the file (corresponding to a generic file icon [cornered paper sheet]). See our page on our utility SignEdit to see how to correct the behavior of our programs. On the PC (under Windows 95/98/NT/2000) You can almost get the same problems on the PC, even more if you asked Windows not to display the file extensions. If a double click on a file icon doesn't start the correct application, the extension is surely wrong (or you don't have the correct application). The extension can be wrong because our programs don't know the signature of the Macintosh file. In this case, you'll have to use our SignEdit utility to correct the behavior of our programs.
There are also schemes where the file is compressed by a kind of TSR (like DiskDoubler etc. on the PC). Those files have the signature DDAPDDFL. I don't know any way to uncompress them on the PC. You'll have to ask the sender to send you uncompressed files, or files compressed with other utilities (see above).
The names of the color seps are stored in the master EPS file. When you transfer the fileset from the Macintosh to the PC (with our utility MacDisk, the filenames may change (for example, if the filename contains a "/" or some other illegal character). More, most programs used to transfer data between both platforms have features to add an extension according to the file signature. As the color seps are also EPS files, you get filenames like "file.y.eps". Therefore, we added to our programs a new file naming mode, which does nothing and keeps the filename used on the Macintosh. It remains that some characters can't be used on the PC. In this case, we have to do something to be able to create the file on the PC hard disk. Therafter, when you try to open the DCS fileset in PhotoShop, you get the error message: Unable to open DCS color filesObviously, you have to restore the linking between the files. One often recommended solution is to open all color separations in PhotoShop and to merge the channels. The problem is that you loose the contents of the master EPS file, which can contain clipping paths, etc. Therefore, we had the idea to develop a little utility to edit/rebuild the links between the master EPS file and the files containing the color separations. This utility, named DCS-Edit, can be downloaded from this site. The program is very easy to use. Select the master EPS file (and the color seps if the program can't find them itself). You can then edit freely the filenames in the master file and the names of the files on the disk. Just save your changes before exiting. We would like to get your comments and observations on this utility.
The solution is to insert four new items in the signature file: C,EPSF????,DCS - Cyan Channel M,EPSF????,DCS - Magenta Channel Y,EPSF????,DCS - Yellow Channel K,EPSF????,DCS - Black ChannelYou can cut and paste those lines in the signature files, or enter corresponding entries in SignEdit 32.
The driver (HSFLOP.PDR) doesn't bear the same date as the other files of the IOSUBSYS subfolder. If you want to be sure, go into this subfolder and right-click on the file, then choose Properties and the Version tab. You should find an item labelled "ItemName" whose value is "QFE" (Quick Fix Engineering). Please note that this problem only occurs with Windows 95 OSR 2. It was cured with Windows 98. The only cure is to upgrade to Windows 98 or NT, if the hardware configurations allows it.
When such files are transferred to the PC, our program gives them a correct extension, but the destination program refuses to open the files, saying that the format is incorrect, because of the presence of this header at the beginning of the file. One solution is to use a little utility we developped, called MacBinary, to correct (that is strip) the header. The program proposes to options: adding a header and stripping it. The program tries to be prudent while checking the presence of the header, but you surely should work on a copy of the file...
Former versions: Just uninstall the former version (or the demo version) and do a clean install from the distribution floppy disk. It should cure the problem.
To overcome this problem, we developped a free utility, called QT-Flattener (length 841 032 bytes). It can run on MacBinary files and on bundled files (data fork in a MOV file, resource fork in a QTR file). A 32-bit console version (length 97 117 bytes) is also available. It is not so heavy (no installer) and can run in a batch file.
(This file must be converted with BinHex 4.0) in the first line. The Binhex format is a kind of encoding standard (like uuencode, mime, etc.) used frequently to send Macintosh files on the Net. See our page on the Binhex coding standard for more informations and for an utility to decode the files.
We have discovered this behavior quite recently. The explanation is a badly set registry key, that the program should double check. This will be corrected in the next version (6). In the mean time, the solution is to open the registry and to put a zero in the key "HKEY_LOCAL_MACHINE\SOFTWARE\LS_Duhem\program_name\Options". If you don't feel secured when fiddling with the Registry, you can delete the whole LS_Duhem key. Our programs rebuild their keys when they don't find them in the Registry.
The causes may be different under Windows 2000.
The causes may be different under Windows 2000.
Our programs behave normally with Norton version 5, running with all possible settings.
If the diskettes are physically High density disks (letters HD on the right of the sliding piece of metal or plastic), it is nevertheless possible that they were formatted on a very old Macintosh (before the SE 30 and II CI models). In this case, to be able to read them on a newer Macintosh computer, you'll have to hide the second hole (the one without the read protection sliding piece) with a piece of opaque adhesive.
The problem doesn't exist under Windows 98, Windows 2000 or Windows NT 4 (even with version 4.00 of the DLL shell32.dll in this later case). If you don't intend to install any version of Microsoft Internet Explorer on your computer, ask for a corrected version of the package. If you encountered the problem with a demo (trial) version, please download the program again. All demo version were updated on 07/12/2000.
We recommend upgrading if you intend to install this version of Microsoft operating system.
MacDisk cannot access such drives under Windows 95/98/ME. On the other hand, it perfectly opens them under Windows NT/2000/XP. If you don't see in the Drive Selection dialog box a drive which is correctly recognized by the BIOS, please check that this drive is not blacklisted (see this function in the 'Expert' menu).
This service must be installed from an administrator account. The installation is done by the installer, called instserv.exe, stored in the lsdiorw subfolder. Uninstalling the service is done by uninstallserv.exe, stored in the same folder. If you get an error message about lsdiorw, first check that the service is installed and started. Go to Start, Parameters, Control Panel, Administrative Tools and Services. In this console, look at the line lsdiorw. If the service is not started, you can start it in the context-sensitive menu (right click). This will fail if you are a plain user. If you want to download a fresh copy of the service and the installation routines, go to the Downloading Page.
This error happens on computers running Windows 95/98 without the latest DCOM updates. To solve it, you'll have to update the DCOM software, using one of following links: Link for Windows 98 Link for Windows 95. The updater for Windows 95 is also present on the distribution CD-ROM, in a folder labelled DCOM. The updater for Windows 98 is not a freely redistributable component, and we could not include it on the CD-ROM.
See the text on this setting on the page about the service Lsdiorw.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|