Doug.Geoffray@f8.n369.z1.fidonet.org (Doug Geoffray) (10/23/90)
Index Number: 11225
[This is from the Blink Talk Conference]
TW> well doug let me see I took cocal eyes to work and put the exe
TW> file and prose4000 driver in my route directory then I added a
TW> line in the autoexec that went something like prose4000
TW> ve
TW> I think I also tried prose4000 !c1
TW> couldn't get it to talk to me. I don't know for sure which com
TW> port the prose is going to I am not permitted to open up the
TW> work computer and if I didn't wouldn't know which port it was
TW> going to.
Tandy,
It does not matter which port you assign to the PROSE4.COM driver. The
Prose doesn't really replace the port. The PROSE driver simply intercepts
characters that would have gone to that port. I would suggest you tell
the PROSE4.COM driver to use LPT3. Therefore you should have the
following two lines in your batch file.
PROSE4 /!l3
VE
That is it. However, if you have changed the PROSE-4000 from its default
IRQ of 2 or changed that base address then you must also tell the
PROSE4.COM driver of this. Very few people ever modify the Prose board
but if you do, you must include the information. The PROSE4.COM driver
assumes IRQ 2 and a port address of 300 HEX. You can use the command
line parameter /!Ix where x is the required IRQ. I would bet that you
are using the standard stuff.
Also, don't forget about the leading slash before the !l3. I noticed
on your line above that you did not include the slash. Once you execute
the PROSE4 line the Prose should say 'Prose 4000 device driver version x'.
If it doesn't then you have problems right away and Vocal-Eyes will not
work. Give this a try Tandy and let me know what happens.
Regards,
Doug
--
Uucp: ..!{decvax,oliveb}!bunker!hcap!hnews!369!8!Doug.Geoffray
Internet: Doug.Geoffray@f8.n369.z1.fidonet.org