Jaws For Windows 6.0
Hi,
Im trying to package Jaws for Windows onto a multi os and multi hardware environment. We use Win2k and Win Xp. The software delivered via radia and is packaged using REFWI.
The only way that i have found to do this is to package this up and leave out all info relating to the JFWVID display driver. When i deliver the software i have created a script that runs and a custom action after all the software has been delivered and runs the following command 'c:\progra~1\freedo~1\jaws\6.0\setjv.exe /jfwvid /y'. Now this script runs and works perfectly on a the windows 2000 platform and asks for no user intervention but when the same script is run on windows xp it halts delivery of the software and waits for a user to press the y key. Im wondering if anyone has packaged this product and could come up with a possible reason why this only happens on XP.
I have mailed Freedom Scientific but the dont rush in replying.
Any help would be grately appreciated.
S
Im trying to package Jaws for Windows onto a multi os and multi hardware environment. We use Win2k and Win Xp. The software delivered via radia and is packaged using REFWI.
The only way that i have found to do this is to package this up and leave out all info relating to the JFWVID display driver. When i deliver the software i have created a script that runs and a custom action after all the software has been delivered and runs the following command 'c:\progra~1\freedo~1\jaws\6.0\setjv.exe /jfwvid /y'. Now this script runs and works perfectly on a the windows 2000 platform and asks for no user intervention but when the same script is run on windows xp it halts delivery of the software and waits for a user to press the y key. Im wondering if anyone has packaged this product and could come up with a possible reason why this only happens on XP.
I have mailed Freedom Scientific but the dont rush in replying.
Any help would be grately appreciated.
S
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
VikingLoki
18 years ago
Sounds like that /y isn't doing its job on XP for some reason. Here's a trick I used to do in the DOS days, it might work if the setjv.exe works entirely in a command session (no GUI).
Create a text file called SETJV.TXT (or whatever name you prefer). It should contain the exact keystrokes that need to be entered into setjv.exe, be it just a y or a y<enter>.
Change your command line to 'c:\progra~1\freedo~1\jaws\6.0\setjv.exe /jfwvid /y < SETJV.TXT'. (use the full path for the text file if necessary) That will inject the contents of the text file into the user input for setjv.exe, which may do the trick for you.
Create a text file called SETJV.TXT (or whatever name you prefer). It should contain the exact keystrokes that need to be entered into setjv.exe, be it just a y or a y<enter>.
Change your command line to 'c:\progra~1\freedo~1\jaws\6.0\setjv.exe /jfwvid /y < SETJV.TXT'. (use the full path for the text file if necessary) That will inject the contents of the text file into the user input for setjv.exe, which may do the trick for you.
Posted by:
Simon1x
18 years ago
That was my thinking. But even that didnt work.
Im now thinking that it might be something to do with XP SP2. With the extra security features that were put in......
This setJV.exe alters the display settings to add something called 'display chaining' Which seems to enable Jaws to take control of the existing display drivers.
Im still waiting for a respone from the vendors.
Im now thinking that it might be something to do with XP SP2. With the extra security features that were put in......
This setJV.exe alters the display settings to add something called 'display chaining' Which seems to enable Jaws to take control of the existing display drivers.
Im still waiting for a respone from the vendors.
Posted by:
VikingLoki
18 years ago
Sounds like you're right. What exactly is the "yes" in response to? Could it be an SP2 security popup?
Posted by:
Simon1x
18 years ago
When you run Setjv /jfwvid this exe prompts you to confirm you wish to make changes to the display device chain. Without doing this the application fails to function correctly.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.