Excellent instructions. One question: Is there any adverse effect to
loading DTPC850.EXE if you're going to be operating in a
mostly-Windows-but-sometimes-shell-to-DOS environment? In other
words, should I put some detection in my batch file as to whether I'm
booting DOS 6.22 or Windows 95? What exactly does DTPC850 do, why do
I need it, or why don't I?
On Wed, 20 Oct 1999 11:22:27 -0500, you wrote:
>Her it is again
>
>The first place you have to go is to the
>DECtalk WEB Site at the following URL address:
>http://www.digital.com/oem/products/dectalk/dtalk.htm
><http://www.digital.com/oem/products/dectalk/dtalk.htm>
>Once you are in this site, go to the "Support" section, and then go
to the
>"download" section. In the download section, there is a section for
the
>DECtalk PC1. Please make sure you are in the PC1 area, not the PC2
or the
>DECtalk Express areas.
>
>1) Then, following the instructions, download the file called 4.2.cc
and
>install it on your PC.
>2) Then, download the file called 4.2.cd and place these files in the
same
>directory where you installed the 4.2.cc file. The 4.2.cd file will
>overwrite certain pieces of the 4.2.cc file with bug fixes. Please
note
>that the 4.2.cd file is not an installation file; it is simply a
bug-fix
>file that overwrites certain sections of the 4.2.cc file, so don't
use the
>install routine for 4.2.cd.
>3) If you are in the Windows environment, you are now finished and
>should be able to use DECtalk with JAWS with no problems with the
accented
>characters.
>
>4) If you are in DOS, there is one additional step you need to do:
go
>into the DECtalk directory where you installed 4.2.cc and 4.2.cd and
scan
>through the dt.bat files until you find the dt_load statement that
should
>look like this:
> dt_load kernel.sys dtpcdic.dic lts.exe ph.exe cmd.exe usa.exe
> ADD at the end of this line the following argument: dtpc_850.exe
>
> When you are finished, the command line should read like this:
> dt_load kernel.sys dtpcdic.dic lts.exe ph.exe cmd.exe usa.exe
>dtpc_850.exe > NUL
>5) You are now ready to use DECtalk in the DOS environment.
>
>PLEASE NOTE: this should be used in a 'pure' DOS environment, that
is, you
>should not be running DOS in a Windows window.
>
>I hope this resolves the issue for you..
>
>At 11:49 PM 10/19/99 -0700, you wrote:
>>Hi Walter,
>>
>>At 03:51 PM 10/19/99 -0500, you wrote:
>>>Tom, which dectalk card are you using.
>>
>>It's a PC1. Didn't I mention that? Hmmm.
>>
>>This problem is definitely a
>>>dectalk problem.
>>
>>Oh, really? Perhaps, but why can I read accented characters using a
>>different screen reader with its particular Dectalk driver with no
ill
>>effects?
>>
>> I use to have the same problem, and I wrote to dectalk
>>>about it, and a nice lady over there gave me the fix for my dectalk
pc 1
>>>card. She did remind me that the pc 1 was an old card, which I
already
>>>knew, but her fix worked. I have not had any crashes from those
foreign
>>>accented characters since.
>>
>>Well, whom did you contact and what was the solution? I'm sure a
number of
>>us on the list might benefit from this information. How about it?
>> Cheers!
>>Tom
>>-
>>Visit the jfw ml web page: http://jfw.cjb.net
>>
>>
>Walter
>-
>Visit the jfw ml web page: http://jfw.cjb.net
-
Visit the jfw ml web page: http://jfw.cjb.net
