T-Stick exception EOLEException in module DLL_NETcard

Forums › Spark New Zealand (including Skinny and BigPipe) › T-Stick exception EOLEException in module DLL_NETcard_R.dll install error

Zigg

437 posts

Ultimate Geek
+1 received by user: 307

#54430 17-Dec-2009 15:30

I've been trying to get the T-Stick (MF626) software installed for someone, but keep getting the above error. Googling doesn't turn up much info - it mainly seems to happen on Eee / Netbooks or nLite cutdown XP installs. This is a Dell desktop with XP / SP3. I figure some XP component is either corrupt or not installed, but I have no idea what. Out of desperation I installed the .Net framework and Java, but no dice. They were basically fobbed off when they rang support and were told something on their PC was blocking it -the obligatory “disable your firewall and AV software” response. Any ideas? The software installed fine on my XP tester box, and was able to connect.

ResponseMediaNZ

518 posts

Ultimate Geek
+1 received by user: 196

ID Verified

Trusted

#283476 17-Dec-2009 16:09

Have you tried the updated software @
http://www.zte.co.nz/main/Product_Downloads/MF626_downloads.htm

Also maker sure there is no other connection manager software installed i.e. a later verson of the software.

Zigg

437 posts

Ultimate Geek
+1 received by user: 307

#283505 17-Dec-2009 18:57

I've grabbed the latest software and will try it tomorrow. No other connection manager software installed.

There was a problem with their Device Manager, it had the following error:

Snap-in failed to initialize.
Name:Device Manager
CLSID:{74246BFC-4C96-11D0-ABEF-0020AF6B0B7A}

Fixed that with regsvr32 devmgr.dll. Not sure if it somehow relates to the T-Stick problem.

Zigg

437 posts

Ultimate Geek
+1 received by user: 307

#283537 17-Dec-2009 21:19

Update. I noticed the PC in question had no "Compatibility" tab in the file properties, Googling found that some installs of the software resulted in "Run this prg in compat. mode for Win NT 4 / SP5" being the default. I've changed the setting to that on my tester box, and the same error pops up. So hopefully I can restore the tab or run the Compatibility Wizard and change the setting.