| > 1. Customer installed the DMI junk on an old Venturis 466 -all the
> pieces seem to be in the right place. When he runs livelink from an NT
> and tries to browse that PC, he gets:
> error: 0x211, dmi service layer notinstalled or not active.
> Any idea why? All TSRs are running on the client.
TSR's??? Only ClientWORKS 1.0 used TSR's for the DMI bits and remote
access was not supported with that version. Only a local Windows
program. You need ClientWORKS 2.0 and Windows 95 or NT to get the
remote DMI feature.
We had a prototype remote-DMI that worked with the 16-bit Windows
DMI service layer but it was never ment to ship.
> 2. I have a new celebris gl 6200. Came with clientworks - at least a CW
> directory. I thought all the newer machines had dmi built into the
> bios, so i just fired up livelink - saw my node - double clicked on it
> and it gave me the same error. Do I have to install the
> DMI/clientworks stuff on my machine (NT 4.0)? Confusing!
Go into the control pannel and click on the "Services" icon. Do you
see a service called "Digital DMI Service Layer" and another called
"Digital DMI Remote Access"? If not, then ClientWORKS is not installed
correctly on this PC.
Saying that a system has DMI in the BIOS only means that the BIOS has
hooks in it for DMI. The hooks allow a system manufacturer to write
code that can extract data that only the motherboard chip-set knowns
about and use it to populate the DMI System MIF.
The remote access to DMI data is not part of the DMI standard (before
version 2.0, ClientWORKS is DMI 1.0). Digital added remote access to
DMI data as part of the ClientWORKS 2.0 product. You must have
ClientWORKS 2.0 or newer installed on a system in order to see it's
data in the LiveLINK browser. LiveLINK shows all the systems that
it can find on the network. It has no way of knowing which of the
systems have ClientWORKS installed on them. We never implemented
the agent discovery we had planned for LiveLINK.
|