Member Avatar for aliashoori

I am working on a Wincor ATM model 2150xe. The OS of the Wincor is NT 4.0 and Procash NDC is installed on it. Its connection to host was X.25, and Eicon C91 Card was installed on it. I made necessary modifications on it to change it to TCP/IP, but after I install Ethernet card on it, I encounter the following error message:
__________
Service Control Manager
At least one service or driver faied during system startup. Use Event Viewer to examine the event log for details.
__________

The card I install is Intel® PRO/1000 MT Desktop Adapter, and is a normal Ethernet card, but I don’t know why this message is displayed?

Do you know how I can solve this problem?

If it is not solved, can I disable the Alert, so that it does not pop up, or when it pops up, it is avoided so that the ATM does not remain stopped?

Service-Control-Manager-S.jpg 14.63 KB
  • 3 Contributors
  • 2 Replies
  • 326 Views
  • 8 Hours Discussion Span
  • Latest Post Latest Post by Bob_180_Bob

Dani AI

Generated

Short summary and practical next steps (builds on and ): that Service Control Manager dialog on NT4 means a kernel-mode driver or a service failed while the system was starting. The first, decisive action is to read the System log in Event Viewer (look for Service Control Manager errors / Event ID 7000/7009/7023 or similar) so you know exactly which service or driver failed and why. (learn.microsoft.com)

Locate the failing service/driver and remove or disable it so the machine can boot unattended. Typical workflow on NT4:

  • Acknowledge the SCM dialog, log on, open Event Viewer -> System, double-click the red error to get the service name or driver filename.
  • Open Registry Editor (RegEdit), go to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\<ServiceOrDriverName>
  Start  = DWORD value

Set Start = 4 to disable the entry (or remove/uninstall the driver via Device Manager in Safe Mode). Back up the registry before editing. This prevents NT from trying to load the bad driver each boot without suppressing the underlying problem. (learn.microsoft.com)

If the NIC is the offender (likely with a newer PRO/1000 MT driver), use Intel’s NT4 driver package rather than modern Win2k/XP drivers — Intel historically supplied a Windows NT 4.0 Network Adapter Driver Set (PRONT4) for older adapters; extract the NT4-specific INF/SYS and install that instead of a newer package. Also confirm the NT4 installation has the latest official updates (SP6a / post-SP6a rollup was the final NT4 update). Using a card with explicit NT4 support is often the simplest fix. (downloadcenter.intel.com)

Do not attempt to “hide” the SCM dialog as a permanent solution — it only masks a faulty driver and can leave the ATM in an unsupported, unstable state. The correct approach is to identify the failing driver (Event Viewer), disable or replace it (registry/Device Manager), and install a driver package built for NT4. For unattended deployments, slipstreaming the right NT4 drivers or using a vendor‑supported NIC avoids the startup stop altogether. (ibm.com)

Recommended Answers

All 2 Replies

Member Avatar for Laser

The most likely cause would be that you have the incorrect driver loaded. It may also be that the driver requires a service pack to be previously installed. If memory serves SP 6 was the final released.

Perhaps you'll find a better driver or some help at Intel's web site.

Edited by Laser because: n/a
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.