Miscellaneous Technical Notes Volume 3
This page contains miscellaneous short technical notes for various products.
- Contents
- Mac OS X 10.3 and FireWire 800 Drive Corruption
- Is There Any Way to Retrieve Data From Damaged PCMCIA Memory Media Cards?
- XP CardBus Drivers Information
- Issues with Certain Host Systems not Providing USB Specification Power
- Installing Windows drivers for Interfirm HS-DMX32/HS-DMX32R/HS-CF32
- Optional Power Supply for External OmniDrives
- IPI/CSM Product Compatibility with The Windows
- Removing Elan's PSeries Drivers from The Windows Installations
Mac OS X 10.3 and FireWire 800 Drive Corruption
We are aware of the issues announced by Apple regarding Mac OS X 10.3 and Oxford Semiconductor's OXFW922 bridge based FireWire 800 drives with firmware versions earlier than v1.05. Any Synchrotech UltiFire800 drives sold after 11/01/2003 will have v1.05 firmware pre-installed. Our bridgeboard manufacturer has supplied us with a firmware updater for customers with drives purchased before that date. There is no need to update FireWire 400 drives, this update is designed only for the OXFW922 chipset.
- 922_updater_Mac.sit
- Firmware updater for use with Mac OS X 10.2.8 or later, instructions included with download
Is There Any Way to Retrieve Data From Damaged PCMCIA Memory Media Cards?
Several drive recovery services can attempt to do this. We can't maintain a comprehensive list, but the following companies have been reported by our customers as having helped them. We provide this list as a service to customers looking for some of these items, it does not constitute an endorsement of any of these products, services or vendors.
Sandisk an Lexar include photo recovery software with their highest end cards. These packages might be available in a stand alone form. Contact them for more information.
- Lexar's ImageRescue 2.0
- Sandisk's RescuePRO
An end user suggested this software package for the Macintosh: CardRaider
XP/Vista CardBus Drivers Information
The PCM-CR-PC1IC3 uses the Ricoh R5C485, the PCM-CR-PC2IC3 uses the Ricoh R5C486, the PCM-CR-PC1IF32R uses the Ricoh R5C843, the PCM-CR-PC1IF32 uses the Texas Instruments PCI1510, and the PCM-CR-PC2IF32-B uses the Texas Instruments PCI1520 drivers supplied with Windows XP/Vista/7. These drivers are automatically installed by the Windows when it recognizes a PC Card slot at installation, but often not installed if it doesn't. Typically these drivers are not present on a desktop system since most customers add a PCI to PC Card drive reader well after Windows software is installed on a system.
If you have a retail CD-ROM of the Windows XP/Vista/7 installation disk, then this isn't an issue since simply inserting the CD-ROM during the new hardware found routine will allow Windows to find and install the correct drivers. However, many end users purchase computers from large vendors with Windows XP/Vista/7 pre-installed and the CD-ROM they get with their system isn't a full copy of Windows (a restore disk) although they paid in full for Windows. In this case the end users needs to contact their system vendor and tell them that they need the "signed Microsoft Windows XP/Vista/7 drivers for the R5C485, R5C486, R5C843, PCI1510, or PCI1520" depending on which controller their PC Card drive reader uses. The drivers may already be on a system in "C:\\WINDOWS\system32\DRIVERS\pcmcia.sys", and instructing the installation routine to that file may help.
Issues with Certain Host Systems not Providing USB Specification Power
The USB specification calls for host systems (ie. computers) to provide +5VDC @ 500mA. Peripheral devices are allowed to provide +5VDC at either 500mA or 300mA. USB peripherals often can run under USB bus powered mode, which means they draw their operational electricity off the USB and don't require a separate power adapter of their own. Unfortunately, certain vendors are beginning to sell systems with USB ports that do not provide the required power. USB devices that normally function off of USB bus power will either not operate, or exhibit strange behavior with these systems. This situation is solely the fault and responsibility of the systems manufacturer and not peripheral manufacturers.
A work around to this is to purchase a power adapter for USB devices that can utilize them, or to purchase a powered USB hub that can provide the necessary USB bus power. However, in the case of laptops and portable devices this is problematic as it requires access to a power outlet. In other words, the work around defeats the whole notion of portability.
This issue is of important interest to PCM-CR-U1323G and PCM-CR-U111-530 owners and prospective buyers with certain laptop models. Elan Digital Systems details this issue for a specific laptop in one of their FAQ Entries, and Synchrotech suspects certain other models from the same vendor have the same problem.
Installing Windows drivers for Interfirm HS-DMX32/HS-DMX32R/HS-CF32
- Download HSCF32DRV20.zip from the Synchrotech site https://www.synchrotech.com/support-download/HSCF32DRV20.zip
- After downloading the files from the internet, unzip the package and open the HSCF32DRV20 directory
- Place a media card into the adapter and insert into the PC Card slot
- Windows will go through the 'new hardware found routine,' Choose 'Install from a specific location,' and on the following screen use the 'Browse' button to guide it to the HSCF32DRV20 directory
- Windows will balk with its signed driver extortion 'logo' warning, ignore it by clicking 'Continue Anyway'
- Windows will identify the adapter as an 'Interfirm Technology High Speed CardBus Adapter'
- This will be visible under IDE ATA/ATAPI controllers in the 'device manager'
Optional Power Supply for External OmniDrives
The USB specification calls for host systems (ie. computers) to provide +5VDC @ 500mA. Peripheral devices are allowed to provide +5VDC at either 500mA or 300mA. USB peripherals often can run under USB bus powered mode, which means they draw their operational electricity off the USB and don't require a separate power adapter of their own. Unfortunately, certain vendors are beginning to sell systems with USB ports that do not provide the required power. USB devices that normally function off of USB bus power will either not operate, or exhibit strange behavior with these systems. This situation is solely the fault and responsibility of the systems manufacturer and not peripheral manufacturers.
IPI's External OmniDrives will work on USB bus power alone on any host providing +5VDC @ 500mA, even when Linear Flash cards requiring 12V writes and erases are needed. In cases that a host system doesn't provide enough power, an optional power supply, the PCM-CR-U1EPS, is indicated. However an off the shelf 5VDC at ≥ 500mA, standard polarity (inner pin positive, outer ring negative) will work as well. Again, in almost every case, a power supply is not needed with OmniDrives.
IPI/CSM Product Compatibility with The Windows
This table is intended to make it easier to determine if a specific IPI/CSM product we carry works with a specific The Windows operating system. The first column contains the IPI/CSM products. The second column lists the types of PCMCIA PC Card memory devices supported by the device. The subsequent columns list various The Windows version support, and it also lists support for 64-bit and 32-bit version support. The last column lists the older versions of The Windows the devices.
PC Card Memory | Works with The Windows versions | ||||
---|---|---|---|---|---|
7 | Vista | XP | Others (16/32-bit) | ||
USB 2.0 to PC Card Read-Writer 1-Slot for ATA Flash + SRAM + Linear Flash (OMNIDriveUSB2 LF) (ART0020711) | ATA Flash | 64-bit 32-bit |
64-bit 32-bit |
64-bit 32-bit |
NT 4, 98, 98SE, ME, 2000, Server 2003 |
SRAM | |||||
Linear Flash | |||||
OMNIDriveUSB2 Pro USB 2.0 to PC Card Read-Writer 1 Slot ATA Flash/SRAM | ATA Flash | 64-bit 32-bit |
64-bit 32-bit |
64-bit 32-bit |
NT 4, 98, 98SE, ME, 2000, Server 2003 |
SRAM | |||||
EasyReader USB 2.0 to PC Card Read-Writer 1 Slot ATA Flash Cards | ATA Flash | 64-bit 32-bit |
64-bit 32-bit |
64-bit 32-bit |
NT 4, 98, 98SE, ME, 2000, Server 2003 |
SoftDrive Professional PC Card Storage Device Software | ATA Flash | 32-bit | 32-bit | 32-bit | NT 4, 98, 98SE, ME, 2000, Server 2003 |
SRAM | |||||
Linear Flash | |||||
USB 2.0 to PC Card Read-Writer 1 Slot Linear/ATA Flash/SRAM Internal LF | |||||
ATA Flash | 64-bit 32-bit |
64-bit 32-bit |
64-bit 32-bit |
NT 4, 98, 98SE, ME, 2000, Server 2003 | |
SRAM | |||||
Linear Flash | |||||
OmniDrive Pro Parallel Port to PC Card Read-Writer 1 Slot + SRAM/Linear | ATA Flash | 32-bit | 32-bit | 32-bit | MS-DOS 3.3+, 3.11, 95, NT 4, 98, 98SE, ME, 2000, Server 2003 |
SRAM | |||||
Linear Flash | |||||
OmniDrive Parallel Port to PC Card Read-Writer 1 Slot + SRAM | ATA Flash | 32-bit | 32-bit | 32-bit | MS-DOS 3.3+, 3.11, 95, NT 4, 98, 98SE, ME, 2000, Server 2003 |
SRAM |
Removing Elan's PSeries Drivers from The Windows Installations
Typically manufacturers provide a mechanism for removing drivers from the system. Elan, however, never wrote an uninstall routine. They did provide instructions for manually removing the drivers in the readme.txt file on the PSeries installation CD-ROM. Those instructions are reproduced here. These 5.07.07 release notes are for operating systems that PSeries readers were approved to run on. If you have inadvertently installed the PSeries drivers on systems newer than The Windows Server 2003 (eg. The Vista, 7, 8, etc.), you may have to account for changes in these procedures based on changes to The Windows. This applies to systems that had existing PSeries drives installed and were upgraded to systems newer than The Windows Server 2003.
In the case that these instructions don't work, or that changes in later Windows systems render these instructions entirely obsolete, the best course of action to permanently remove PSeries drivers is to back up all your data, reformat your system disk, and reinstall The Windows from scratch as per the instruction come from Microsoft when you purchase your copy of Windows. This assures that the PSeries drivers are entirely removed from a system.
----------oOo---------- ************************************************ 6 Uninstalling the PSeries drivers ************************************************ The PSeries drivers are fully plug and play in that they will detect the PCMCIA hardware will no load if the PCMCIA hardware is not present in the PC. Usually it is not necessary and not recommended to completely uninstall the PSeries drivers. If the drivers are to be completely removed, the following sections explain how to remove the drivers for the particular operating system. DON'T FORGET!!! THE PCMCIA HARDWARE WILL FAIL TO OPERATE CORRECTLY WITHOUT THE PSERIES DRIVERS INSTALLED! 6.1 Uninstalling the PSeries drivers in Windows 9x/Me ================================================== To uninstall the PSeries drivers, go to the "Control Panel", run "Add/Remove Programs", select the PSeries Drivers and click "Change/Remove". Re-boot the computer into "Safe Mode" (by pressing "F8" during boot). Double click the "System" icon in the control panel, select "Device Manager" and expand the "PCMCIA socket" entry highlight each entry for the PCMCIA socket and click "Remove". From Windows Explorer delete the files: c:\windows\inf\pseries.inf c:\windows\inf\pseries.pnf c:\windows\system\pseries.vxd From Windows Explorer, go to the c:\windows\system\oldpcmcia folder and move the "PCMCIA.INF" file to the c:\windows\inf folder. Run the registry editor (regedit.exe) an delete the key: "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet \Services\VxD\PSeries" Shut down the PC and remove the PC-Card adapter hardware. Re-boot the PC and the driver is no longer installed. ----------oOo---------- 6.2 Uninstalling the PSeries drivers in Windows NT ================================================== To uninstall the PSeries drivers: 1) Shut down the PC and remove the PC-Card adapter hardware. 2) re-boot the PC and go to the "Control Panel", run "Add/Remove Programs", select the PSeries Drivers and click "Change/Remove". 3) Run the registry editor (regedit.exe) an delete the key: "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PSeries" 4) From Windows Explorer delete the file: c:\winnt\system32\drivers\pseries.sys The PSeries driver is now no longer installed. ----------oOo---------- 6.3 Uninstalling the PSeries drivers in Windows 2000/XP & Server 2003 ===================================================================== Version 5.06 of the PSeries driver introduced more integrated operation with the Windows 2000 driver model. So there are differences in the way previous and later releases are uninstalled. ---------------------------------------------------------- To uninstall the PSeries 5.05 and earlier release drivers: ---------------------------------------------------------- 1) Shut down the PC and remove the PC-Card adapter hardware. 2) re-boot the PC and go to the "Control Panel", run "Add/Remove Programs", select the PSeries Drivers and click "Change/Remove". 3) Run the registry editor (regedit.exe) an delete the key: "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PSeries" 4) From Windows Explorer delete the file: c:\winnt\system32\drivers\pseries.sys The PSeries driver is now no longer installed. ------------------------------------------------- To uninstall the PSeries 5.06 to 5.07.02 drivers: ------------------------------------------------- 1) go to the "Control Panel", run "Add/Remove Programs", select the PSeries Drivers and click "Change/Remove". 2) From Windows Explorer delete the file: c:\winnt\inf\pcmcia.inf then rename the c:\winnt\inf\pcmcia.old file to c:\winnt\inf\pcmcia.inf To successfully remove all traces of the PSeries driver, you must NOT remove the PCMCIA adapter hardware from the PCI slot until you have performed the following step. IF you have moved the adapter from another PCI slot at any time, then you will need to re-do this step with the hardware in every slot that was previously used. (Windows 2000 preserves the setup independently for each PCI slot in the PC). 3) Open the "Device Manager" and expand the "PCMCIA socket" entry, highlight each entry for the PCMCIA socket, right-click and select "Uninstall...". Finally, when you have completed the above step for each PCI slot the PCMCIA adapter has been in, you can do the following steps... 4) Run the registry editor (regedit.exe) an delete the key: "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PSeries" 5) From Windows Explorer delete the file: c:\winnt\system32\drivers\pseries.sys 6) Shut down the PC and remove the PC-Card adapter hardware. When you Re-boot the PC and the driver is no longer installed. ----------oOo---------- ----------------------------------------------------- To uninstall the PSeries 5.07.03 (and later) drivers: ----------------------------------------------------- 1) go to the "Control Panel", run "Add/Remove Programs", select the PSeries Drivers and click "Change/Remove". 2) From Windows Explorer delete the file: c:\winnt\inf\pseries.inf then rename the c:\winnt\inf\pcmcia.old file to c:\winnt\inf\pcmcia.inf To successfully remove all traces of the PSeries driver, you must NOT remove the PCMCIA adapter hardware from the PCI slot until you have performed the following step. IF you have moved the adapter from another PCI slot at any time, then you will need to re-do this step with the hardware in every slot that was previously used. (Windows 2000/XP preserves the setup independently for each PCI slot in the PC). 3) Open the "Device Manager" and expand the "PCMCIA socket" entry, highlight each entry for the PCMCIA socket, right-click and select "Uninstall...". 4) Finally, when you have completed the above step for each PCI slot the PCMCIA adapter has been in, you can shut down the PC and remove the PC-Card adapter hardware. When you Re-boot the PC and the driver is no longer installed. ----------oOo----------