ZoomText is unable to communicate with its display driver component.


I'm packaging an application named "ZoomText" version9.18.3(latest one) for visually impared users. For this I'm using .When I install the source on a HP xw6400 model PC and reboot and then relogin to launch the application, it says - "ZoomText is unable to communicate with its display driver component." and the display drivers gets corrupted.

I suspect that the setup of this software has its own logic to interact with the display drivers of the machines.

Has anyone packaged this in past and encountered the same issue & have a solution? Can this be packaged on a specific model machine(in my case, HP xw6400) and deployed to any other models(say, HP xw6200/xw6000 or any other workstations of DELL or IBM, etc).

Can someone help me on this.Thanks in advance.

0 Comments   [ + ] Show comments

Answers (10)

Posted by: anonymous_9363 13 years ago
Red Belt
I'd say that this is definitely a question for the application vendor. Before you bounce it to them, though, bypass all the usual nonsense vendors try to stall you with by ensuring that your OS is up-to-date with all its Service Packs and that your display driver is the most recent. You may also want to install a driver, if available, for your monitor.
Posted by: abking99 13 years ago
Second Degree Blue Belt
see below link:

you will find below topic:

“ZoomText Express are is unable to communicate with its display component”, when launching ZoomText Express

hope this helps!
Posted by: captain_planet 13 years ago
Black Belt
I conquered this little beast last year some time.....for my old workplace. If I recall, it uses Display Chaining so I had to dynamically configure the display driver. And ensure it reverted back on uninstall! What a nightmare. And it's all a bit hazy. I hit soooo many blue screens when getting this to work. Let me see if I can dig anything up.....
Posted by: sandyran 13 years ago
Senior Yellow Belt
Thanks all for your replies.I've dropped an email to the vendor support team though and waiting for the reply.Meanwhile can someone can answer if this can be packaged at all as I suspect this is a hardware specific software that interact with the display drivers of your computer.
Posted by: captain_planet 13 years ago
Black Belt
It *can* be packaged, but it's by no means easy.

Here's a very rough guide of what I had to do - you'll need to conduct your own investigatiuons to support it because things may be different now.

On install, I made a type 38 Custom Action (running just before installFinalize) to do the following:

Rename the following file:
"C:\WINDOWS\system32\dcmc0d0.dll" (rename it to something like 'dcmc0d0.dllbackup')

On install, I got the value from the key:
HKLM\SYSTEM\CurrentControlSet\Control\Class\{4D36E968-E325-11CE-BFC1-08002BE10318}\0000\Settings "InstalledDisplayDrivers"

(Which was 'Ai2Ldr')

I used this to retrieve the name of the ZoomText display driver .dll. Then I renamed the dll from:


Then I set the following value to 'Ai2Ldr':
SYSTEM\CurrentControlSet\Control\DisplayChaining\Display0 "Original Names"

Then i set:
HKLM\SYSTEM\CurrentControlSet\Control\Class\{4D36E968-E325-11CE-BFC1-08002BE10318}\0000\Settings "InstalledDisplayDrivers"
to be 'JAWSVID'

I traced all this using ProcMon and a snapshot tool called InCtrl. This obviously all needs to be reversed on uninstall too, which is HIGHLY important.

Fiddling about like this is not really advised if you're not experienced. It took me a couple of weeks to find all this out and get it working, with the help of an old friend who circles these forums. It needs to be made as robust as possible, because fiddling with display drivers can seriously knacker the machine. Hopefully this will give you a very rough guide about what is happening and what to look out for....

Why do I have a feeling they released a utility (a lightweight exe) with the installation source (after I'd done all this) to configure all this for you? Hmmm. Maybe it was in one of my countless ZoomText dreams/nightmares....
Posted by: stephenejones 13 years ago
Senior Yellow Belt
Looking at some old scribbed notes, I ended up using this command line in SMS to get it to install successfully:


I think I then ran a batch script to do some final registry tidying.

The /NDC switch I believe maintains some compatibility with different display drivers over different hardware.
Posted by: sandyran 13 years ago
Senior Yellow Belt
Thanks captain & stephene for your prompt replies.I'm aware of the silent setup method described on appdeploy package KB but thought of getting it done in the usual manner by capturing it.
Posted by: Francoisracine 13 years ago
Third Degree Blue Belt
I did successfully deployed it with a batch file. My problem was the patch. Sometimes the patch was installing properly and sometimes not. I ended up not installing the fix... :( But the product was working correctly in our environment.
Posted by: Inabus 13 years ago
Second Degree Green Belt
Disable duel graphics cards if you have them turned on, this application hates them and wont work, also ensure that all graphics drivers are up to date. By dual it could mean an onboard and slot based card in a machine.

Posted by: hofsteda 11 years ago
Yellow Belt
HKLM\SYSTEM\CurrentControlSet\Control\Class\{4D36E968-E325-11CE-BFC1-08002BE10318}\0000\Settings "InstalledDisplayDrivers"
Just to expand on this from my understanding from having tangled with jaws\zoomtext on several hundred machines. The value of the above installedDisplaydrivers reg_multi_sz is usually the filename of the displaycard driver minus the .dll . When dcm is active it points to the driver of the first driver in the chain. If no chaining was done there is no dcmc0d0.dl and the HKLM\SYSTEM\CurrentControlSet\Control\Class\displaychaining\display0 is unpopulated. When the first driver is inserted into the chain, it renames the original driver dll to dcmc0d0.dll and copies the original values of InstalledDisplayDrivers to HKLM\SYSTEM\CurrentControlSet\Control\Class\displaychaining\display0 "Original Names".
The filename of the inserted driver, minus the dll, is used for the InstalledDisplayDrivers of the class key above.
The inserted driver is also placed in the First Entry value of the displaychaining\display0 key.
There are reg_multi_sz for each driver in the chain with the next driver listed as the value. The last dcm aware driver points to dcmc0d0, or the renamed display driver dll.

Using my test vm for example:
Originally "InstalledDisplayDrivers" = vboxdisp of the virtualBox Display driver.
after installing zoomtext this became ai2ldr.
after installing jaws the values of the displaychaining\display0 are:
Original Names VBoxDisp
First Entry Ai2Ldr
DCM Copies dcmc0d0
Ai2Ldr JawsVid
JawsVid dcmc0d0

These keys provide enough information to allow inserting and adding displaychain drivers for installers. You can use the dcmutil included with zoomtext to watch those keys being manipulated.

If you mess up the chain, you will be in 4bit vga mode. The easiest fix at that point is to reinstall the display drivers and clear the values of the displaychaining\display0 key.

I'm revisiting this myself as I'm trying to avoid having to launch zoomtext on every machine as an admin on windows 7 after silently installing it.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ