Don't get your hopes up - I haven't figured this out, just posting this here in hopes that someone does.
Knowledge Base 64-bit Windows Vista Ultimate Edition Microsoft Mechwarrior IV Mercenaries - MekTek3.02b Microsoft Micwarrior Clan Mech Pack Microsoft Micwarrior Inner Sphere Mech Pack
Problem: When running Mercs on Vista 64-bit, Clan and IS Meck Packs cause Mercs to close immediately after first splash screen.
Symptoms: When Mech Packs are installed, they do NOT display the final splash-screen after install - indicating that C-dilla installation was unsuccessful.
Running the safe-disc repair utility does not work.
Event Viewer: Security Log: Audit Failure: Code integrity determined that the image hash of a file is not valid. The file could be corrupt due to unauthorized modification or the invalid hash could indicate a potential disk device error. File Name: \Device\HarddiskVolume1\Windows\SysWOW64\drivers\CDAC15BA.SYS
Event Viewer: System: Error: Application Popup: \??\C:\Windows\sysWOW64\drivers\CDAC15BA.SYS has been blocked from loading due to incompatibility with this system. Please contact your software vendor for a compatible version of the driver.
Installation of the Mech Packs on a Vista 32 system worked fine without any major events. It installed files in: C:\Program Files\Microsoft Games\Mechwarrior Mercenaries\mw4 It creates hidden directory C:\C_DILLA\SafeCast Product Licences and installs files: C:\C_DILLA\SafeCast Product Licences\9F3025A9.DAT (Clan) and: C:\C_DILLA\SafeCast Product Licences\96740EDE.DAT (Inner Sphere).
It installs the file CDAC15BA.SYS in C:\Windows\system32\drivers\, and on first run, installs the file CDAC11BA.EXE in the same location.
It creates a system service called C-Dilla RTS Service, referencing CDAC11BA.EXE. There are multiple registry entries, including the ones for the C-Dilla RTS Service.
The major differences in Vista 64 are that the files are installed in C:\Windows\sysWOW64\drivers\ rather than in C:\Windows\system32\drivers\. However, the registry entries are still all pointing at C:\Windows\system32\drivers\. (note: I thought I was onto something there...but editing all registry entries to point to the right directory did not work...game still dies).
The hidden directory C:\C_DILLA is also not written, and the license files not installed either. I thought this was the answer, but copying them there from a good install also does not work.
The WOW64 UI is for backwards compatibility of legacy drivers, however, apparently C-Dilla is too backwards. Running in various compatibility modes had no effect.
Hopefully all this information will be of use to someone...
ALL YOU NEED IS A PURE GENETIC CODE AND BLOODLUST!!!
Group: Members
Posts: 1,193
Joined: 22-September 02
From: Coconut Creek, FL
Member No.: 3,391
I am glad to see someone else busting thier head about the mechs paks/vista x64 ordeal. Microsoft products not working with microsoft products.
This is just like one of the machine shop vendors my company uses. We had custom bolts and nuts made by the same machine shop but thier thread manufacturing is so poor that the pitch was off so much that the nuts did not screw onto the bolts.
I am glad to see someone else busting thier head about the mechs paks/vista x64 ordeal. Microsoft products not working with microsoft products.
This is just like one of the machine shop vendors my company uses. We had custom bolts and nuts made by the same machine shop but thier thread manufacturing is so poor that the pitch was off so much that the nuts did not screw onto the bolts.
they specifically said they are dropping backward-compatibility with Vista. deal with it. i got a red light on this anyway.
--------------------
Up Up Down Down Left Right Left Right B A Start *** Junior Admin cheat activated ***
Ah hah. You know, when I was posting, it hung for a long time. I believe I got frustrated...and perhaps I clicked the post button a few more times than usual.
I'll add a bit more to this that may help those trying to work this problem out.
I am running Vista Home Premium.
C-Dilla appears to be alive and well. The system recognizes it as a legacy driver and in my task manager it is running as a service C-DillaCdaC11BA.
Messing with the programs on the IS Pak disk, it is worth noting that \goodies\Machine.exe will not run in Vista, even in NT compatability mode. It may be that this program is at the heart of the problem rather than C-Dilla.
I'll add a bit more to this that may help those trying to work this problem out.
I am running Vista Home Premium.
C-Dilla appears to be alive and well. The system recognizes it as a legacy driver and in my task manager it is running as a service C-DillaCdaC11BA.
Messing with the programs on the IS Pak disk, it is worth noting that \goodies\Machine.exe will not run in Vista, even in NT compatability mode. It may be that this program is at the heart of the problem rather than C-Dilla.
I don't think it has to do with the stuff in the goodies folder. That stuff is on all of the MW4 CD's and does not get installed anywhere as far as I know.
I did some poking around as well looking at directories in my Win7 64 install vs XP and Vista installs. Your correct on the fact that the C-Dilla service is running in the 64 bit environment. I noticed (in win7 64) that some of the other dll's installed with the mechpaks are in the systemwow64 directory instead of system32. Also noted that some of the drivers are installed to systemwow64/drivers.
I tried to copy all of the drivers to the directories they are installed to in XP or vista 32 hoping it was just a problem of the files being in the wrong directories but no dice.
One thing I should have tried is running the safecast repair after the file copy... instead I got frustrated and uninstalled the mechpaks. I'm gonna try that later.
Also need to mention that I tried all this while turning driver integrity off while booting. (allows for un-signed drivers.)
I just recently got my USB to serial (rs232) adapter working in vista64 by doing the same sort of thing. (moving files into the system32 folder) Was also able to get a servo drive programing app to fire up and communicate with a drive the same way. The servo app was released for windows 98... These are two separate programs that worked together under a 64 bit environment....
I also have read that people have enabled gameports in win7 64 and vista 64 the same way.
I'm not convinced this is a lost cause. I don't think it would be a crime of any sort to find a work around for legitimate owners of the mechpaks.
ALL YOU NEED IS A PURE GENETIC CODE AND BLOODLUST!!!
Group: Members
Posts: 1,193
Joined: 22-September 02
From: Coconut Creek, FL
Member No.: 3,391
I am glad this post is still alive and people are still trying. At this point I really dont think microsoft would care, the paks have been discontinued for so long, as well as mercs. Why cant someone crack it already?
This post has been edited by Firehawk_Osis: Feb 28 2009, 01:14
ALL YOU NEED IS A PURE GENETIC CODE AND BLOODLUST!!!
Group: Members
Posts: 1,193
Joined: 22-September 02
From: Coconut Creek, FL
Member No.: 3,391
Apparently NBT Hardcore has the mech paks unlocked. Does anyone know if they have it working with vista 64 bit? How come they were able to get the packs unlocked?
Apparently NBT Hardcore has the mech paks unlocked. Does anyone know if they have it working with vista 64 bit? How come they were able to get the packs unlocked?
I also do play with NetMechIV and NBT Hardcore using Windows Vista 64-Bit Home Premium and the M$ Paks work fine.
Apparently NBT Hardcore has the mech paks unlocked. Does anyone know if they have it working with vista 64 bit? How come they were able to get the packs unlocked?
Simple. You don't need the Microsoft Mech Packs to have access to those mechs with those mods.
MekTek will not unlock them.
--------------------
Up Up Down Down Left Right Left Right B A Start *** Junior Admin cheat activated ***
ALL YOU NEED IS A PURE GENETIC CODE AND BLOODLUST!!!
Group: Members
Posts: 1,193
Joined: 22-September 02
From: Coconut Creek, FL
Member No.: 3,391
QUOTE (RkShaRkz @ Mar 1 2009, 17:29)
Simple. You don't need the Microsoft Mech Packs to have access to those mechs with those mods.
MekTek will not unlock them.
I understand Mektek will not unlock them but is there a chance that Mektek will make a fix so that people who legally own the paks can play them on 64-bit vista?
I understand Mektek will not unlock them but is there a chance that Mektek will make a fix so that people who legally own the paks can play them on 64-bit vista?
Mech Packs on Vista 64, no I didn't fix it...but:
Nov 8 2008, 22:36
