so, it wouldn't be too hard for cf to put a dmg rappper around an
installer
script to do this instead of an .exe.
----- Original Message -----
From: "Scott Howell" <[EMAIL PROTECTED]>
To: "General discussions on all topics relating to the use of Mac
OS X by
theblind" <[email protected]>
Sent: Friday, September 05, 2008 4:34 AM
Subject: Re: Another Cell Phone and Synching question
Well, let me share a little info. First if you had access to a
windows
box, I was told by Code Factory you could capture the cab files
during
a portion of the installation.
Here is what I was told.
"If you have a Windows PC, run the EXE installer up to the point when
the Remote Activation Wizard starts. You can then exit this wizard
and
end RemoteRegistration.exe through the Windows Task Manager (opened
with Ctrl+Shift+Escape or Ctrl+Alt+Del), under the Processes tab of
this multipage dialog box. Note that you may also need to end
ConfigureRemote.exe and then CABInstall.exe after terminating
RemoteRegistration.exe to completely stop the installer. The CAB
files
will be extracted to C:\Program Files\Mobile Speak Pocket [TTS name],
where TTS name is the text-to-speech voice that the EXE installer you
ran would be installing with Mobile Speak Pocket.
The files you need to copy and run on your device are named
MobileSpeakPocket.CAB, RemoteServer.arm.CAB, and
MSP_[TTSName_Platform].CAB where [TTSName_Platform] may be in the
form
Fonix_USEnglish_Multivoice_PocketPC, for example. If you wish to
install the Magnification and Braille components, then the files you
need to copy to the device are named
PPC_Magnification_Component_English.arm.CAB if you installed with an
English TTS or PPC_Magnification_Component_NoLanguage.arm.CAB if you
installed without speech output, and Braille_Component.arm.CAB.
There are different ways of transferring files to your Windows Mobile
device from your Mac or Linux machine, but the following are most
recommended:
Using a card reader for the type of card used on your device. Card
readers cost anywhere from 10 to 30 US dollars and can also be used
to
share files between the mobile device and computer. Note that if your
device is using miniSD or microSD cards, an adapter for inserting
such
cards into an SD card slot will usually come with the card when
purchased. Thus, you can buy an inexpensive SD card reader and just
use the adapter for the type of card supported by your device.
Using Bluetooth file transfer. Please refer to the user's manual of
your computer or Bluetooth dongle for more information.
To install the CAB files, you will need sighted assistance since
there
is no speech output on the mobile device yet. Launch the file system
browser application on your device. This will be called File
Explorer.
Navigate to the CAB files and press Enter to run each. Note that you
may be prompted that the files are unsigned or from an untrusted
publisher, and asked if you wish to continue with the installation.
Press the Left softkey to proceed with installation. The next prompt
will be about the install location for the contents of the CAB file.
Except for RemoteServer.cab, we strongly advise that you choose the
storage card of your device as the install location for all MSP
components in order to have as much free space as possible in the
device memory for running programs and storing data that cannot be
moved to the storage card.
Remember that the CAB files must be installed in the following order:
1. RemoteServer.arm.CAB (install to device's main memory)
2. MSP_[TTSName_Platform].CAB (we recommend installing to the
storage card)
3. MobileSpeakPocket.CAB (we recommend installing to the
storage
card)
4. Either PPC_Magnification_Component_English.arm.CAB or
PPC_Magnification_Component_NoLanguage.arm.CAB, and
Braille_Component.arm.CAB, in any order (we recommend installing to
the storage card)
When you are done installing all CAB files, soft reset the device.
Note that you will need to use the Activation Manager on the device
to
activate the installed products with a full or trial license. Please
refer to Section 2.4.2 for more information."
And there you have it, direct from the CF folks. Now I will tell you
that I've tried like hell using file jucer to extract the cab files
with no success. From what the author of File Jucer told me, it would
not extract the cab files for some reason of which I've now
forgotten.
So, if anyone figures out how to get the damned cab files out of the
archive, then please let me know.