http://msdn2.microsoft.com/en-us/vbrun/ms788708.aspx

"The Visual Basic 6.0 IDE has never been offered in a native 64-bit version, nor has the 32-bit IDE been supported on 64-bit Windows. VB6 development on 64-bit Windows is not and will not be supported."

I'll check if i find all of the files you listed on my system.


Edit: TabCtl32.ocx is missing, but this is no problem. When I start SETUP.EXE from DISK1 in my temp dir, I receive a message that this program was incompatible with my 64-Bit-Edition of windows and I am advised to call the manufacturer... the message occurs even before the exe itself is being started, before any depending DLL is loaded.

The problem occurs with many old installers (so with TAW's), maybe it would work if I could copy the program files manually? (With TAW, it did.)

Chris

Thanks for checking, Stoepsel.

I'll look more closely at your link later, and thanks for posting it. But I believe your quote above is regarding the IDE and that's ok, I don't plan to install and program in VB6 on a 64-bit OS.

It's runtime support that matters, if the VB6 runtime is supported (and it looks like it should be for another 10 years, unless I read it wrong), my VB6 program should work I would think.

Or is it the installation that's the problem? I use an older version of InstallShield, same one as TAW I believe. I do check the OS on install as one file (Scrrun.dll, I believe) has a unique version for NT4.0 (not that anyone is still using Win NT but if the other verion of this file gets installed in NT it kills the OS).
--


Mark

I posted during your edit.

Looks to be the install, I can probably fix it if you're willing to give it a try. Might take a day, and I have no way of testing it first. If that makes you nervous I wouldn't try it.
--


Mark

I'm a geek, so I'm always looking forward to new betas I can test
Thx for your efford!

Ok, I'll whip something up.

The good news is that according to that link all the system files I use are supported (no surprise there as I'm not using anything exotic).

The bad news is that on first glance my version of InstallShield won't install to 64-bit. In my installation I'm telling it to install to all Windows OS's except NT4.0, “all” being what was supported by InstallShield v2.12 (Win95, 98, NT3.51, NT4.0, 2000). This was before XP but apparently that doesn’t matter as it installs fine in XP. I forgot to test in Vista, I need to load it back on my laptop and try it.

Anyway, I own a newer version of InstallShield (not very new anymore) and that may support 64-bit, although the install size (thus download size) would be larger and I like the consistency with TAW in the old version. But I won't rule it out as an option.

I think I'm going to try something else, like you said just copying the files over. You'll still need the system files installed and registered though (i.e. without TabCtl32.ocx the tabs won't work! ). I'm going to first try and use VB6.0's built-in installer (keeping it all Microsoft) to install the required system files, and then you can just unzip the TAWC program folder wherever (i.e. ...\Program Files\TAW Configurator). I know Vista changes the rules regarding "Program Files", not sure how that'll work out yet.

Anyway, the TAWC executable is self-contained (no DLLs) and no Registry settings are set until it’s run, so as long as the system files are properly installed it should run fine. I can check this all on a clean partition, except of course for the 64-bit test. I'll get back to you.
--


Thanks,
Mark

Last update on the Help...
http://198.65.10.229/DID/TAWC_HT1.pdf

Pure torture.

I'll finish it tonight (~2 pages left plus a thorough proofreading and side bookmarks), the program itself is ready, and tomorrow I'll collect whatever mods together and release. Then I'll make a setup for 64-bit before starting a new project.

It's going to be a productive TAW weekend, I hope everyone check in.
--


Mark

Man,
I briefly previewed and browsed through this documentation pdf. Very elegant work. Big thanks. This proves that in order to get it something right , more work than forum is required. I need to take my time to get some items out on my end.
When ready ....

Thanks, Polak. I just wanted to post something to show I'm still on it. I realized I hadn't yet even spellchecked the last couple of pages, oh well...it's just a progress update.

No rush on anything (if you have anything to share), I've just added another day or two until release with a new (optional) mod distribution method I’m working on. The current method is to provide mods in a zipped folder, you unzip and put the TCM files and accompanying folders in your "mods folder". That still works and you get the same end result.

The new method is to provide a single Mods.dat file that you simply overwrite in your TAWC folder (regardless where your mods are). Works like a TAW patch, just copy over the newest DAT file. Every time you start TAWC it looks at this file and knows if it needs to update your mods, add new mods, etc (all contained in the DAT file). And this puts us one step away from a future auto-update option, but even with a manual download and copy it just makes adding mods easier, IMO.

I may not be around too much this weekend but I'm still "here".
--


Mark

It's nice to see someone actually taking the trouble to complete something. Well done.

So many little things added...

For example, per jureidini's post above, TAWC now checks that your game is extracted before doing anything which requires extraction and tells you so versus saying only, "Target file not found".

Choosing Update on HUD Options, the process takes a few seconds, so what's going on? Is it done (so asked my wife, bless her for beta testing)? Now when you choose Update your mouse pointer becomes an hourglass to indicate activity and then you get a simple confirmation message that your game has been updated. Lots of little things like this have been added.

Simplification in the Help Instructions...

i.e. Dialog box as shown above...
http://198.65.10.229/DID/CSH_EXP1.jpg
=========================
"Buttons:"
"Apply: Copies files into your TAW game folder as defined by the TCM file."
...to...
"Apply: Copy files into your TAW game folder."

The first message is too much info, that stuff is covered in detail in the reference part of the manual, instructions should be as simple and straightforward as possible (my project today, especially with the last several pages of the PDF which explain setup and extraction).

BTW, the Mods.DAT method for updating mods is finished and works great!

Ok, I'm back to work...
--


Mark