New Btrieve error, this time 20 [Archive] - ForumsHQ

[Psyanide]

after removing all the files and registry input for wgserv, I reinstalled, now I get BTRIEVE OPEN ERROR 20 "wgsmenu2.dat"



what is it, how do I fix it, and can I sue gallacticom for all this trouble??? http://mmb.forumshq.com/iB_html/non-cgi/emoticons/smile2.gif

[syntax53]

btrieve is not working correctly on your machine. error 20 means the microkernel or btrieve requester isn't loaded. so the exe is trying to use breive and it can't.

-syntax

[Psyanide]

ok thank you, now, how do I get the btrieve to run? and which file is it? i need a fix for this problem, please. http://mmb.forumshq.com/iB_html/non-cgi/emoticons/smile2.gif

you can chat with me on AIM: TownDrunk1974



thank you,

Psyanide

[syntax53]

best thing to do would be to uninstall worldgroup. then go into your registry and search for anything "btrieve" or "pervasive" and delete the keys (delete the highest level keys, aka "folders," you can without deleting anything non btrieve related). then reboot and reinstall worlgroup.



good luck,

syntax

[MrBlack]

Fummud and fummap come with btreive.exe, you could prolly just use that to replace instead of reinstalling...if not, then reinstall :rolleyes:

[drcorey]

Error 20: The MKDE or Btrieve Requester is inactive.

In the DOS and NetWare environments, you must load the MicroKernel and, if applicable, the Btrieve Requester before generating any requests. By default in the Windows and Windows NT environments, the Setup utility turns on the Local Engine Usage option. To access a client/server MicroKernel engine but not a workstation engine, turn the Local option off and turn the Server option on. To access both workstation and client/server MicroKernels, turn the Server option on and leave the Local option on. Also, in the Windows environment, be sure that the Btrieve for Windows DLLs and MicroKernel executable are in your PATH or in the top level of your Windows directory. In the Windows NT environment, you must start the MicroKernel before generating any requests. Make sure the Windows NT DLLs are in your path. In the OS/2 environment, be sure that the necessary DLLs are in your LIBPATH directory.