Can't extract KotB or Co8 mod

I have tried several times to extract both of these mods and can't get either to extract. I've tried opening with WinRAR and WinZip, neither extract them. I've also tried with front end x. I've put them into the ToEE and tried, also tried from other places. I would love to play KotB as that was the module that introduced me to dnd. I had Co8 installed years ago on another computer, now it won't work. Also my wife tried it on her computer with the same results. Front end installed properly, but never detects any addons.

 

Hello, Zmeck! Let's see if we can get you sorted out.

Starting with the basics, did you follow the installation instructions found here?

If so, does ToEE launch at all, either through the vanilla desktop icon or through the front-end?

 

I followed all the instructions, and yes it launches through both of them. I have GOG edition. I tried installing there, also from base drive.

 

OK, so if you downloaded and installed the Co8 mod and it set up the frontend, when you start the front end does it show the Co8 mod as well as vanilla ToEE? It sounds like you've attempted to activate the Co8 mod through TFE, correct? The instructions point it out, but it bears repeating that mod activation in TFE does take a while and may seem like nothing is happening. Make sure to let it run until it completes.

 

I downloaded the front end separate from the modules. So the only thing in the front end is Temple. There is no option for Co8 or KotB. As I said those don't extract.

 

That's what I've been trying to get to extract. And it isn't extracting. They are supposed to self extract, but they aren't.

 

OS is windows 8.1, tried with Norton auto-protect off, and admin. Also my wife tried to extract it on her laptop, although she didn't have the game installed.
Operating System: Windows 8.1 64-bit (6.3, Build 9600) (9600.winblue_ltsb.170427-1704)
Language: English (Regional Setting: English)
System Manufacturer: ASUSTeK COMPUTER INC.
System Model: K30BF_M32BF_A_F_K31BF
BIOS: 0406
Processor: AMD A10-6700 APU with Radeon(tm) HD Graphics (4 CPUs), ~3.7GHz
Memory: 8192MB RAM
Available OS Memory: 8132MB RAM
Page File: 4841MB used, 11482MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.03.9600.17415 64bit Unicode

 

This is the text when I double click on KotB from the game folder.
May 19, 2017 3:31:48 PM org.co8.jtfe.logging.TFELogger log
INFO: Starting ToEE Front-End X logging service...
May 19, 2017 3:31:48 PM org.co8.jtfe.logging.TFELogger log
INFO: This is ToEE Front-End X v4.0 running on Maywind Engine on JRE-1.8.0_131-Windows 8.1-x86
May 19, 2017 3:31:48 PM org.co8.jtfe.logging.TFELogger log
INFO: Building the portable ToEE directory file list...
May 19, 2017 3:31:49 PM org.co8.jtfe.logging.TFELogger log
INFO: Trying to set up native look and feel: choosing com.sun.java.swing.plaf.windows.WindowsLookAndFeel...
May 19, 2017 3:31:49 PM org.co8.jtfe.logging.TFELogger log
INFO: Checking if the game patch level is compatible with the front-end...
May 19, 2017 3:31:49 PM org.co8.jtfe.logging.TFELogger log
INFO: Looks like patch 2 or better [should work].
May 19, 2017 3:31:53 PM org.co8.jtfe.logging.TFELogger log
INFO: Changing module table selection to -1...
May 19, 2017 3:31:53 PM org.co8.jtfe.logging.TFELogger log
INFO: Detecting the status of intro movies...
May 19, 2017 3:31:53 PM org.co8.jtfe.logging.TFELogger log
INFO: Intro movies detected to be enabled.
May 19, 2017 3:31:53 PM org.co8.jtfe.logging.TFELogger log
INFO: Ensuring portable game file names...
May 19, 2017 3:31:53 PM org.co8.jtfe.logging.TFELogger log
INFO: Reading TFE-X initialization parameters...
May 19, 2017 3:31:53 PM org.co8.jtfe.logging.TFELogger log
INFO: Reading ToEE Front-End X initialization settings from TFE-X.ini...
May 19, 2017 3:31:53 PM org.co8.jtfe.logging.TFELogger log
INFO: Done reading ToEE Front-End X initialization settings from TFE-X.ini.
May 19, 2017 3:31:53 PM org.co8.jtfe.logging.TFELogger log
INFO: Writing ToEE Front-End X initialization settings to TFE-X.ini...
May 19, 2017 3:31:53 PM org.co8.jtfe.logging.TFELogger log
INFO: Done writing ToEE Front-End X initialization settings to TFE-X.ini.
May 19, 2017 3:31:53 PM org.co8.jtfe.logging.TFELogger log
INFO: Writing ToEE Front-End X initialization settings to TFE-X.ini...
May 19, 2017 3:31:53 PM org.co8.jtfe.logging.TFELogger log
INFO: Done writing ToEE Front-End X initialization settings to TFE-X.ini.
May 19, 2017 3:31:53 PM org.co8.jtfe.logging.TFELogger log
INFO: Writing ToEE Front-End X initialization settings to TFE-X.ini...
May 19, 2017 3:31:53 PM org.co8.jtfe.logging.TFELogger log
INFO: Done writing ToEE Front-End X initialization settings to TFE-X.ini.
May 19, 2017 3:31:53 PM org.co8.jtfe.logging.TFELogger log
INFO: Detecting game resolution...
May 19, 2017 3:31:53 PM org.co8.jtfe.logging.TFELogger log
INFO: Done reading 46 elements from toee.cfg.
May 19, 2017 3:31:53 PM org.co8.jtfe.logging.TFELogger log
INFO: Detected resolution 800x600 in toee.cfg.
May 19, 2017 3:31:53 PM org.co8.jtfe.logging.TFELogger log
INFO: Enforcing disabled autosaves (corrupt ToEE functionality)...
May 19, 2017 3:31:53 PM org.co8.jtfe.logging.TFELogger log
INFO: Done writing 46 elements to toee.cfg.
May 19, 2017 3:31:53 PM org.co8.jtfe.logging.TFELogger log
INFO: Populating the module list...
May 19, 2017 3:31:53 PM org.co8.jtfe.logging.TFELogger log
INFO: Scanning the directory for TFM packages...
May 19, 2017 3:31:53 PM org.co8.jtfe.logging.TFELogger log
INFO: Adding module: Temple of Elemental Evil.tfm...
May 19, 2017 3:31:53 PM org.co8.jtfe.logging.TFELogger log
INFO: Determining the currently active module...
May 19, 2017 3:31:53 PM org.co8.jtfe.logging.TFELogger log
INFO: Changing module table selection to 0...
May 19, 2017 3:31:53 PM org.co8.jtfe.logging.TFELogger log
INFO: Detecting the status of intro movies...
May 19, 2017 3:31:53 PM org.co8.jtfe.logging.TFELogger log
INFO: Intro movies detected to be enabled.
May 19, 2017 3:31:53 PM org.co8.jtfe.logging.TFELogger log
INFO: Detecting the status of intro movies...
May 19, 2017 3:31:53 PM org.co8.jtfe.logging.TFELogger log
INFO: Intro movies detected to be enabled.
May 19, 2017 3:31:53 PM org.co8.jtfe.logging.TFELogger log
INFO: Checking for duplicates and removing them if found...
May 19, 2017 3:31:53 PM org.co8.jtfe.logging.TFELogger log
INFO: Trying to read the module-wide lockout file...
May 19, 2017 3:31:53 PM org.co8.jtfe.logging.TFELogger log
INFO: No lockout file detected, phase skipped.
May 19, 2017 3:31:57 PM org.co8.jtfe.logging.TFELogger log
INFO: ToEE Front-End X is closing...
May 19, 2017 3:31:57 PM org.co8.jtfe.logging.TFELogger log
INFO: Shutting down log handlers...

And when Front End opens, Keep isn't there. I'm hoping that helps, I have no idea what any of that is. Also the same happens when I try to load Co8.

 

I'm not positive exactly what all that means either but from what I see there and what you're describing, it seems like the front end is having trouble installing the modules after it is installed itself as a separate previous function. That being the case, have you tried uninstalling TFE-X and then installing the Co8 or KotB package from the self-extractors? It might be some sort of conflict that can be resolved by installing clean without the front-end already set up.

 

Where are you Installing to? That looks like a problem I had the first time I tried. It went away when I changed the Installation from the default windows location to C:\Games\TOEE

Make sure you set Run as administer under properties as opposed to just right-clicking on the shortcut and choosing run as administer

 

I put it on the C: drive directly and tried opening it without front end. It won't open at all by itself. It asks for a program to open it. That's why I originally downloaded front end separate, thinking that I needed that to open up the file.

 

The modules will not work unless you "activate" them via the front end. The reason it is asking you for a program to extract it with is because it doesn't recognize the format of the compressed file, (module).

I recommend following the installation instructions step by step for a smooth installation.