Weird problem when installing dictionary

[Fokke Nauta]

Hi all,

Using W7-64b.
I have 3 dictionaries, which installed and worked well in XP-32b.
In W7-64b I can install them using the XP compatibility mode. Two of
them, the Germman and French one, installed OK and work well. The 3rd
one, the English one, stalls during installing, at the moment that a
file is being copied to c:\Windows\fonts. It concerns the font ENGELS-U.TTF.

I have to cancel the installation with the result the English dictionary
is not installed.

On a W7-64b installation in VMWare all 3 dictionaries installed well
using the XP compatibility mode, no problem there. All 3 worked well.

But not in my system. And in the fonts folder I can't see the actual
files, but it shows only the name of the fonts. So there is nothing I
can do here.

Anyone has a suggestion?

Fokke

 

[Gene E. Bloch]

Hi all,

Using W7-64b.
I have 3 dictionaries, which installed and worked well in XP-32b.
In W7-64b I can install them using the XP compatibility mode. Two of
them, the Germman and French one, installed OK and work well. The 3rd
one, the English one, stalls during installing, at the moment that a
file is being copied to c:\Windows\fonts. It concerns the font ENGELS-U.TTF.

I have to cancel the installation with the result the English dictionary
is not installed.

On a W7-64b installation in VMWare all 3 dictionaries installed well
using the XP compatibility mode, no problem there. All 3 worked well.

But not in my system. And in the fonts folder I can't see the actual
files, but it shows only the name of the fonts. So there is nothing I
can do here.

Anyone has a suggestion?

Fokke

I have suggestion, but I don't know if it will work.

Run the dictionary installation program in Administrator mode, i.e.,
right click on the program file or a shortcut to it, and choose "Run as
Administrator".

 

[Ed Cryer]

I have suggestion, but I don't know if it will work.

Run the dictionary installation program in Administrator mode, i.e.,
right click on the program file or a shortcut to it, and choose "Run as
Administrator".

It might also be a good idea to install it in XP compatibility mode.

Ed

 

[Gene E. Bloch]

It might also be a good idea to install it in XP compatibility mode.

Ed

Good idea - thanks.

You also led me to think that it might work if the installer is run in
XP compatibility mode.

 

[jbm]

Hi all,

Using W7-64b.
I have 3 dictionaries, which installed and worked well in XP-32b.
In W7-64b I can install them using the XP compatibility mode. Two of
them, the Germman and French one, installed OK and work well. The 3rd
one, the English one, stalls during installing, at the moment that a
file is being copied to c:\Windows\fonts. It concerns the font
ENGELS-U.TTF.

I have to cancel the installation with the result the English dictionary
is not installed.

On a W7-64b installation in VMWare all 3 dictionaries installed well
using the XP compatibility mode, no problem there. All 3 worked well.

But not in my system. And in the fonts folder I can't see the actual
files, but it shows only the name of the fonts. So there is nothing I
can do here.

Anyone has a suggestion?

Fokke

You don't say what dictionaries they are (publishers).

I've got a (very old) copy of LiRiS' Chambers Dictionary, which started
life in Win3.1. Progressed to Win3.11 with no trouble. Win2000 wouldn't
touch it, even the installer. WinXP ran it perfectly. Win7-64 lets it
install, but refuses to run it because it can't find some of the files
it needs (DLL's I think). In XP I found it ran better from the C:\
directory rather than the Programs directory, where it tended to crash
occasionally.

jim

 

[Fokke Nauta]

I have suggestion, but I don't know if it will work.

Run the dictionary installation program in Administrator mode, i.e.,
right click on the program file or a shortcut to it, and choose "Run as
Administrator".

Thanks, but I tried. I should have mentioned.
Didn't work.

Fokke

 

[Fokke Nauta]

It might also be a good idea to install it in XP compatibility mode.

Ed

I did.
Funny enough the other 2 dictionaries installed well.
The English didn't.

Fokke

Fokke

 

[Fokke Nauta]

Good idea - thanks.

You also led me to think that it might work if the installer is run in
XP compatibility mode.

The good thing of W7 is having these compatibility modes. I used the XP
SP2 mode to install it. Worked well for 2 dictionaries only.

Fokke

 

[Fokke Nauta]

You don't say what dictionaries they are (publishers).

I've got a (very old) copy of LiRiS' Chambers Dictionary, which started
life in Win3.1. Progressed to Win3.11 with no trouble. Win2000 wouldn't
touch it, even the installer. WinXP ran it perfectly. Win7-64 lets it
install, but refuses to run it because it can't find some of the files
it needs (DLL's I think). In XP I found it ran better from the C:\
directory rather than the Programs directory, where it tended to crash
occasionally.

jim

They are - kind of - obsolete and stem from the XP time. The publisher
is Prisma, but it is based upon Ifinger. In XP they worked well, it was
a pleasure to use them.
It is weird that in a W7 64b virtual machine it all installs well (in XP
mode) and works well. In the host machine however, the other 2
dictioaries install well and work OK, but only the English doesn't.

I wonder why the installer halts when copying a font to the fonts directory.

Fokke

Fokke

 

[Dave-UK]

They are - kind of - obsolete and stem from the XP time. The publisher
is Prisma, but it is based upon Ifinger. In XP they worked well, it was
a pleasure to use them.
It is weird that in a W7 64b virtual machine it all installs well (in XP
mode) and works well. In the host machine however, the other 2
dictioaries install well and work OK, but only the English doesn't.

I wonder why the installer halts when copying a font to the fonts directory.

Fokke

Fokke

Is there anything in the Event Viewer or Reliability Monitor?
(Action Center > Maintenance > View reliability history.)

 

[Fokke Nauta]

Is there anything in the Event Viewer or Reliability Monitor?
(Action Center > Maintenance > View reliability history.)

OK, the Reliability Monitor is great. It shows the following:

-----------------------
Description
A problem caused this program to stop interacting with Windows.

Problem signature
Problem Event Name: AppHangXProcB1
Application Name: GLBFB.tmp
Application Version: 2.0.7.194
Application Timestamp: 3905ad98
Hang Signature: df08
Hang Type: 32
Waiting on Application Name: Adobe3DAndVideoServer.exe
Waiting on Application Version: 0.0.0.0
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 2057
Additional Hang Signature 1: df08d8a7e128aa6018d3c38c4cd9d568
Additional Hang Signature 2: 76fa
Additional Hang Signature 3: 76fa30649ffc9f2bcec8c76b9e7e2857
Additional Hang Signature 4: df08
Additional Hang Signature 5: df08d8a7e128aa6018d3c38c4cd9d568
Additional Hang Signature 6: 76fa
Additional Hang Signature 7: 76fa30649ffc9f2bcec8c76b9e7e2857
-----------------------

The Event viewer shows:

-----------------------
The program GLBFB.tmp version 2.0.7.194 stopped interacting with Windows
and was closed. To see if more information about the problem is
available, check the problem history in the Action Center control panel.

Event Data:
GLBFB.tmp
2.0.7.194
157c
01cd9588327bef25
1
A:\GLBFB.tmp
7b41e30a-017b-11e2-bb5e-005056c00008
430072006F00730073002D00700072006F00630065007300730000000000

 

[Dave-UK]

OK, the Reliability Monitor is great. It shows the following:

-----------------------
Description
A problem caused this program to stop interacting with Windows.

Problem signature
Problem Event Name: AppHangXProcB1
Application Name: GLBFB.tmp
Application Version: 2.0.7.194
Application Timestamp: 3905ad98
Hang Signature: df08
Hang Type: 32
Waiting on Application Name: Adobe3DAndVideoServer.exe
Waiting on Application Version: 0.0.0.0
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 2057
Additional Hang Signature 1: df08d8a7e128aa6018d3c38c4cd9d568
Additional Hang Signature 2: 76fa
Additional Hang Signature 3: 76fa30649ffc9f2bcec8c76b9e7e2857
Additional Hang Signature 4: df08
Additional Hang Signature 5: df08d8a7e128aa6018d3c38c4cd9d568
Additional Hang Signature 6: 76fa
Additional Hang Signature 7: 76fa30649ffc9f2bcec8c76b9e7e2857
-----------------------

The Event viewer shows:

-----------------------
The program GLBFB.tmp version 2.0.7.194 stopped interacting with Windows
and was closed. To see if more information about the problem is
available, check the problem history in the Action Center control panel.

Event Data:
GLBFB.tmp
2.0.7.194
157c
01cd9588327bef25
1
A:\GLBFB.tmp
7b41e30a-017b-11e2-bb5e-005056c00008
430072006F00730073002D00700072006F00630065007300730000000000
-----------------------

Is this useful to you?

Fokke

No, it doesn't mean much to me. The problem seems to be something
to do with Adobe3DAndVideoServer.exe.
It's interesting to me to see that an Adobe file may be causing problems.
I use the Oxford Talking Dictionary which is a really old program and
although it installs ok in Win7 there was a noticeable delay in starting
the dictionary.

I traced the delay to the dictionary getting involved with a file called
atmfd.dll. It's an Adobe Type Manager, something to do with fonts and is
an Adobe file bundled with Win7.
I renamed the atmfd.dll and the dictionary works properly now.
I don't know what the dll does but I haven't had any problems without it.

Googling Adobe3DAndVideoServer.exe will tell you more about it, what it
is supposed to do and whether you need it or not.
Perhaps as a test stop the Adobe3DAndVideoServer.exe file from running
and then try to install your dictionary.

 

[Fokke Nauta]

No, it doesn't mean much to me. The problem seems to be something to do
with Adobe3DAndVideoServer.exe.

I first thought this was an application that my dictionary tried to
install.

It's interesting to me to see that an Adobe file may be causing problems.
I use the Oxford Talking Dictionary which is a really old program and
although it installs ok in Win7 there was a noticeable delay in starting
the dictionary.

I traced the delay to the dictionary getting involved with a file called
atmfd.dll. It's an Adobe Type Manager, something to do with fonts and is
an Adobe file bundled with Win7.
I renamed the atmfd.dll and the dictionary works properly now.
I don't know what the dll does but I haven't had any problems without it.

Googling Adobe3DAndVideoServer.exe will tell you more about it, what it
is supposed to do and whether you need it or not.
Perhaps as a test stop the Adobe3DAndVideoServer.exe file from running
and then try to install your dictionary.

Thanks! You put me in the right direction. I renamed atmfd.dll (first
had to take ownership and change the rights) and stopped
Adobe3DAndVideoServer.exe in the Task Manager.

Installation went smoothly and I can now use the English dictionary as well!

Once again, many thanks!

Fokke

 

[Dave-UK]

Thanks! You put me in the right direction. I renamed atmfd.dll (first
had to take ownership and change the rights) and stopped
Adobe3DAndVideoServer.exe in the Task Manager.

Installation went smoothly and I can now use the English dictionary as well!

Once again, many thanks!

Fokke

That's good!
One thing to remember if you ever run the System File Checker, (sfc /scannow) it will replace the renamed dll.

 

[Fokke Nauta]

That's good! One thing to remember if you ever run the System File
Checker, (sfc /scannow) it will replace the renamed dll.

I never ran the System File Checker before. Something special from W7?

Fokke

 

[Gene E. Bloch]

The good thing of W7 is having these compatibility modes. I used the XP
SP2 mode to install it. Worked well for 2 dictionaries only.

OK, it seemed to be worth a try :-(

Another thought (if not already expressed in this thread). Can you
install it to another folder outside of the Program files or Program
Files (x86) set? I use Programs Other for some anomalies in Vista and 7.
Of course, some installers don't have that option...

 

[Gene E. Bloch]

Thanks, but I tried. I should have mentioned.
Didn't work.

Well, I just posted another idea in this thread. If that fails, it's
three strikes against me and I'm out

 

[Gene E. Bloch]

I never ran the System File Checker before. Something special from W7?

Fokke

It's been around for many versions, too many for me to remember the
first.

It's called sfc.exe. You can run sfc or sfc.exe at the command prompt.
Use /? or /help as an argument to learn more about it.

Its job is to discover corrupted or missing system files and replace
them from a reservoir of originals that it keeps somewhere on disk.

 

[Fokke Nauta]

It's been around for many versions, too many for me to remember the
first.

It's called sfc.exe. You can run sfc or sfc.exe at the command prompt.
Use /? or /help as an argument to learn more about it.

Its job is to discover corrupted or missing system files and replace
them from a reservoir of originals that it keeps somewhere on disk.

If this is your 3rd strike, you're still in

Never knew this one. I thought I knew something about Windows ...
Never tried before.

Fokke

 

[R. C. White]

Hi, Fokke.

The System File Checker, as its name suggests, checks system files. It
was/is a part of Windows XP and later versions of Windows; I don't recall if
it existed in Win9x or Win2K. For an official - but brief - description,
see:
http://support.microsoft.com/kb/929833
Use the System File Checker tool to troubleshoot missing or corrupted system
files on Windows Vista or on Windows 7

An unofficial but more complete description is here:
http://www.updatexp.com/scannow-sfc.html

The short answer is, "The System File Checker tool (SFC.exe) scans for
missing or corrupted system files and repairs them." For what I call a
"mini-Help" screen for its usage, open a Command Prompt window and type:
sfc /?

The most common use of the command is with sfc /scannow. This will scan all
the installed operating system files in your Windows installation and
compare them to a "known good" copy of the file kept in its on-disk cache.
If it cannot find the good copy on your disk, it may ask for you to insert
the DVD, but this is not usually necessary. If a required file is missing,
it will replace it; if the file is corrupted (and fails the CRC or other
test), SFC will replace it from the cache. This might take some time...

SFC is a seldom-needed tool that is a life-saver in the rare times when we
do need it.

RC
--
R. C. White, CPA
San Marcos, TX
(e-mail address removed)
Microsoft Windows MVP (2002-2010)
Windows Live Mail 2012 (Build 16.4.3503.0728)) in Win8 (RTM Ent Eval)


"Fokke Nauta" wrote in message

That's good! One thing to remember if you ever run the System File
Checker, (sfc /scannow) it will replace the renamed dll.

I never ran the System File Checker before. Something special from W7?

Fokke