Sorry did not realize that FOIP = FIPS.
Use RegEdit to set HKLM\System\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy\Enabled to 0
http://support.microsoft.com/kb/811833
Sorry did not realize that FOIP = FIPS.
Use RegEdit to set HKLM\System\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy\Enabled to 0
http://support.microsoft.com/kb/811833
[quote=lordbok]
JaxFirehart if you read my first paragraph I stated that I cannot change my group policy due to me having Windows 7 Home Premium and I also stated I already went through that topic looking for answers.
[/quote]
As you say "Due to me having Widows 7 Home Premium" You can't do as Jax suggested! This means you know the issue is on your end not the fault of TTW.
The TTW team is not Windows tech support and we are not here to sort out your computer issues. We will always try our best to help anyone having trouble but, when you know it is on your end it really is up to you to figure out.
Jax has already went out of his way to try to help you, You sound like your asking for more then should be expected of him.
I really hope you figure out the issue but it's on your end and not the teams problem.
The issue is on all windows home premium users then. The installer should be compatible with it. Nearly every other installer is. I also tried removing .NET 4.0 and only installing .NET 4.5 but I still get the Unhandled Exception. I get the error when the TTW installer says;
Installing Tale of Two Wastelands...
TaleOfTwoWastelands - Main.bsa needs to be built...
Extracting Fallout - Misc.bsa...
Extracting Fallout -Meshes.bsa...
Extracting Fallout - Textures.bsa...
Cleaning up duplicate resources...
Building TaleOfTwoWastelands - Main.bsa...
Building complete, checking for patches...
Thats is when I get the Unhandled exception.
[collapsed title=Exception] See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms. at System.Security.Cryptography.MD5CryptoServiceProvider..ctor() --- End of inner exception stack trace --- at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at System.Security.Cryptography.CryptoConfig.CreateFromName(String name, Object[] args) at System.Security.Cryptography.MD5.Create() at WindowsApplication1.TTW_Util.GetChecksum(String fileIn) at WindowsApplication1.TTW_Util.PatchFile(String sourceFile, String destFile, String CHK_New) at WindowsApplication1.Form1.Button1_Click_1(Object sender, EventArgs e) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.17929 built by: FX45RTMREL CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll ---------------------------------------- TTW Patcher Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Users/Gaming/Desktop/Fallout%20NV%20TTW/TTW%20Patcher.exe ---------------------------------------- Microsoft.VisualBasic Assembly Version: 10.0.0.0 Win32 Version: 11.0.50709.17929 built by: FX45RTMREL CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.17929 built by: FX45RTMREL CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.17929 built by: FX45RTMREL CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.17929 built by: FX45RTMREL CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.17929 built by: FX45RTMREL CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System.Runtime.Remoting Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.17929 built by: FX45RTMREL CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box. [/collapsed]
I would gladly love to contribute to helping getting the installer to work on Windows 7 Home Premium for other users as well as me. so if you would like to TV it or something let me know. Though I hope it is not because of the OS and is something small I am missing.
First off, saying "windows is a piece, fix it and make your game work with it" is way off base. Secondly, Jax has offered another solution. If you can open Regedit you should be able to try. Give that a shot and post back.
My project Dash is on Kickstarter!
[quote=JaxFirehart]
Use RegEdit to set HKLM\System\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy\Enabled to 0
[/quote]
My project Dash is on Kickstarter!
To clarify, many people with "Window 7 Home Premium" have ben able to install TTW! AGAIN! THE ISSUE IS ON YOUR END! NOT OURS!
tjmidnight420 Ok well good news and bad news. After the reg change I was able to do most of the process however now there is a new problem. now it says "TaleOfTwoWastelands - Main.bsa failed to patch properly. Please Report this bug" it said this after it said on the installer "Building complete, checking for patches..."
I am unsure of anymore information after that as there is no other windows or error messages just that.
EDIT: I found the installer log so I will upload it. seems like it just cant find a patch file.
EDIT EDIT: Or I can just post what the Installer.log says so you do not have to download it.
[collapsed title=Installer.log] Determining system architecture
[/collapsed]
OK stuff is getting a little heated here.
Lordbok: You need to remember that we answer a lot of questions and 90% of them are questions that could be answered by searching whether it be Google or our own forum. I don't mind helping you get TTW running on your rig, even if Windows is your main hurdle, so long as you put in some leg work as well. That failed to patch properly bug implies to me that your Fallout3 assets are bad somehow. TTW only supports english at the moment, so make sure you are using a legal, fully patched, english copy of FO3. If you are, I would try a clean install of FO3 to make sure. If it still throws errors, I'm at a loss, I will have to program the installer to be more specific, if it can, about which BSAs are up to date.
alright cheers I believe I might know what the problem is. let me give it a try.
Alright I uninstalled and reinstalled Fallout 3 GOTY so it was a fresh installation. I got the exact same error message saying it couldn't patch again, so now I very lost. Is there a manual way to do this? like renaming the Fallout 3 .bsa's etc like with RFCW?