Zugg Software :: View topic - zMUD - 7.05

Newbie Joined: 14 Jun 2004 Posts: 6 Location: USA

I installed a 7.0x version a couple of months ago. I started it up today and did the registration process and launched. No matter where I clicked, I got a small popup window that read "zMUD" in the title and contained the word "Uknown." with a "OK" button. It won't let me do anything...not even quit. I have to open up task manager and force the task to end to close it. I uninstalled and downloaded 7.05 and started it up...however I have the same problems. I've also rebooted.

I have confirmed that the LicCtrl service is up and running.

Windows XP Pro OS

I have peeked around the forums, but I found nothing that could help.

Help Please!

-Eric
-Licensed Customer

Posted: Mon Jun 14, 2004 12:30 am

HAve you followed the instructions to refresh your settings file?

It may be corrupt.

Or I may be talking drivel...

Newbie Joined: 14 Jun 2004 Posts: 6 Location: USA

Do you have a reference on how to update settings?

This is what I've done.

Removed Zmud (Uninstall + deletion of any files that were left behind)
Installed to MDAC 2.8 (forced a reboot)
Installed Zmud 7.05

Now, at start up I get...

"in table-level validation express"

If I run it again I get

"Fatal Error: Cannot open databases in directory: C:
zMUD"

I click OK and get

"There are still active COM objects in this application. One or more clients may have references to these objects, so manually closing this application may cause those client application(s) to fail."

If I click yes....it closes the app

If I click no.....I get

"Chars: Cannot perform this operation on a closed dataset"

Posted: Mon Jun 14, 2004 1:05 am

Ok - I've read about this somewhere on this site.

My first suggestion really was drivel. I'll get back to you if I find the article

Newbie Joined: 14 Jun 2004 Posts: 6 Location: USA

I've found this thread...

http://zuggsoft.com/forum/topic.asp?TOPIC_ID=15350

After digging some more, I reallized that I updated MDAC but NOT Jet (I missed step #2 as described in http://zuggsoft.com/data for Windows XP). I'm in the process of doing step #2 now, so hopefully that works! I'll respond when I'm done.

Eric

Newbie Joined: 14 Jun 2004 Posts: 6 Location: USA

That didn't help. Ugh.

I'll play with it some more. In the meantime, is there a version available that I can use my license with that does not rely on JET?

Eric

Newbie Joined: 14 Jun 2004 Posts: 6 Location: USA

*bump*

Anybody have any insight on this issue?

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

There are currently two versions available, 7.05 and 3.62. Version 3.62 does not require either MDAC or JET, but it seldom works at all with Windows XP.

I have no idea what your underlying problem is. If you've already read all the sticky topics in the General Forum, and taken any actions they suggested, I'd suggest corresponding with support@zuggsoft.com.

NOTE: The sticky topics won't show up in Active Topics unless they have recent posts.

Newbie Joined: 14 Jun 2004 Posts: 6 Location: USA

I'm still having the issue. It does appear to be a JET issue. I updated MDAC/JET per http://zuggsoft.com/data and not only does zMUD not work, but MS Access '02 doesn't work anymore either. I've researched the issue, but I have not been able to resolve it. I'll most likely get a refund on my zmud license if a solution doesn't turn up within 2 weeks.

Posted: Wed Jun 30, 2004 7:01 pm

If Access doesn't work either than your MDAC/JET is still messed up. There is an MDAC Checker program on the www.zuggsoft.com/data page that can be used to check your MDAC installation to see what is messed up. You should probably run Windows Updater to see if it detects any other files that need to be updated. Other than that, search the Microsoft site to see how else you might fix your MDAC installation. You might need to reinstall Windows XP and then apply the patches properly using Windows updater.

Unfortunately, MDAC is notorious for not installing properly if not done in exactly the right way, and once it's messed up it will not fix itself because it thinks it is already installed. This is a Microsoft problem and not much I can do about it though.