pbelb Posted December 8, 2009 Share Posted December 8, 2009 I understand PDN 3.5.1 needs .NET framework 3.5 sp 1 (which is already supposed to be on the machine since it's a new Windows 7 installation). note: I'm running x64 version of Windows 7 Ultimate. anyhow, I get the nasty message saying: "Paint.NET Setup Front End has stopped working" I'm pretty sure the problem is not due to the installation of Windows 7, so I'm looking for an update to the installer. please get in touch with me and let me know what info you need so that you can figure out what the problem is. Quote Link to comment Share on other sites More sharing options...
pbelb Posted December 9, 2009 Author Share Posted December 9, 2009 and, for those that are wondering, I checked the HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5\SP value, and it's already at 0x01. so that is not the cause of the issue. Quote Link to comment Share on other sites More sharing options...
pbelb Posted December 9, 2009 Author Share Posted December 9, 2009 note that the 'Version' number for .NET 3.5 (sp1) here on this computer is shown as: 3.5.30729.4926 Quote Link to comment Share on other sites More sharing options...
pbelb Posted December 10, 2009 Author Share Posted December 10, 2009 Ok, I also tried 3.5, but got exactly the same error message. I also tried 3.36, and it did install fine!!! so there is something that's been introduced with 3.5 that's causing issues on Windows 7 x64. Quote Link to comment Share on other sites More sharing options...
Sarkut Posted December 10, 2009 Share Posted December 10, 2009 pbelb: Another possibility is a glitch in the in-built NET Framework 3.5 SP1. PdN v.3.36 actually requires only NET 2.0 although 3.5 SP1 was recommended. That could explain 3.36 working while 3.51 won't. If that is the case, then running sfc /scannow from an elevated command prompt might correct things. Quote Link to comment Share on other sites More sharing options...
pbelb Posted December 16, 2009 Author Share Posted December 16, 2009 Ok, I tried the command suggested, and then tried reinstalling, but it still fails in exactly the same way. any other ideas on how to diagnose the problem? Quote Link to comment Share on other sites More sharing options...
pyrochild Posted December 16, 2009 Share Posted December 16, 2009 Shot in the dark: try changing the installation directory. Quote ambigram signature by Kemaru [i write plugins and stuff] If you like a post, upvote it! Link to comment Share on other sites More sharing options...
pbelb Posted December 19, 2009 Author Share Posted December 19, 2009 no, that does not make any difference. I tried that, and it makes no impact at all. exactly the same error shows up. are there any other people that are seeing this issue, or is it just me? Hard to imagine it's just me - fresh install of windows 7 and all. anyone else seeing this issue? if so, did you solve it, and if so, how? Quote Link to comment Share on other sites More sharing options...
Rick Brewster Posted December 19, 2009 Share Posted December 19, 2009 What language do you have Windows set to? Quote The Paint.NET Blog: https://blog.getpaint.net/ Donations are always appreciated! https://www.getpaint.net/donate.html Link to comment Share on other sites More sharing options...
pbelb Posted December 19, 2009 Author Share Posted December 19, 2009 english (US). interestingly, I tried some other info that says that I should be able to create an MSI set, and got a result that says that the files are not to be found in the temporary directory. look at the attached image, from top to bottom. ie: the command prompt, then the display of the setup dialog and where it got to, then the error dialog, then the window showing the contents of the directory it's complaining about. perhaps it's a red herring and the files have already been cleaned up? Quote Link to comment Share on other sites More sharing options...
pbelb Posted December 19, 2009 Author Share Posted December 19, 2009 note: I also tried the idea of grabbing a static copy of the PdnSetup folder while the initial dialog window is up, copying that to another location, then aborting the setup. then, go to the static copy of the PdnSetup folder and run the SetupShim.exe from there. I'm not seeing anything else that is more helpful at this stage, but I did notice that the SetupFrontEnd.config shows it's saying it's compatible with .net v2.0.50727 while the app itself needs 3.5 sp1. this seems a bit odd to me. I would have thought that everything should be saying it wants 3.5 sp1 for consistency. further, I went into my system registry and see that there is a key at HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v2.0.50727 which shows that the 'Version' sub value has 2.0.50727.4927 so it does appear that I have a compatible 2.0 .net framework installed also. Quote Link to comment Share on other sites More sharing options...
pbelb Posted December 19, 2009 Author Share Posted December 19, 2009 Rick, I can probably organise for the remote desktop support option to be turned on and get that to work so that you can see the issue first hand if you really want to see the issue first hand. I would think that there must be other win7 x64 new installs that are suffering the same sort of issue. either PM me or email me at pbelb@hotmail.com if you are wanting to do this. Quote Link to comment Share on other sites More sharing options...
pbelb Posted December 19, 2009 Author Share Posted December 19, 2009 note that with the attempt to create the .msi packages, I hit 'retry' and ended (fairly quickly) getting an error dialog with more complaints about missing files. I suspect the .msi creation functionality is broken. here is the content of the details box: See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.IO.FileNotFoundException: Could not find file 'PaintDotNet.msi'. File name: 'PaintDotNet.msi' at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite) at PaintDotNet.Setup.CreateMsiPage.PrepMsi(String msiPath, String dstDir, ProcessorArchitecture platform, Hashtable msiProperties) in D:\src\pdn\paintdotnet\src\SetupFrontEnd\CreateMsiPage.cs:line 45 at PaintDotNet.Setup.CreateMsiPage.CreateMSIs() in D:\src\pdn\paintdotnet\src\SetupFrontEnd\CreateMsiPage.cs:line 81 ************** Loaded Assemblies ************** mscorlib Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900) CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll ---------------------------------------- SetupFrontEnd Assembly Version: 3.51.3610.35031 Win32 Version: 3.51.3610.35031 CodeBase: file:///C:/Users/pbelb/AppData/Local/Temp/PdnSetup/SetupFrontEnd.exe ---------------------------------------- PaintDotNet.Core Assembly Version: 3.51.3610.35022 Win32 Version: 3.51.3610.35022 CodeBase: file:///C:/Users/pbelb/AppData/Local/Temp/PdnSetup/PaintDotNet.Core.DLL ---------------------------------------- System.Windows.Forms Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Drawing Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- PaintDotNet.Base Assembly Version: 3.51.3610.35016 Win32 Version: 3.51.3610.35016 CodeBase: file:///C:/Users/pbelb/AppData/Local/Temp/PdnSetup/PaintDotNet.Base.DLL ---------------------------------------- PaintDotNet.SystemLayer Assembly Version: 3.51.3610.35021 Win32 Version: 3.51.3610.35021 CodeBase: file:///C:/Users/pbelb/AppData/Local/Temp/PdnSetup/PaintDotNet.SystemLayer.DLL ---------------------------------------- System.Core Assembly Version: 3.5.0.0 Win32 Version: 3.5.30729.4926 built by: NetFXw7 CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- PaintDotNet.Resources Assembly Version: 3.51.3610.35022 Win32 Version: 3.51.3610.35022 CodeBase: file:///C:/Users/pbelb/AppData/Local/Temp/PdnSetup/PaintDotNet.Resources.DLL ---------------------------------------- WindowsBase Assembly Version: 3.0.0.0 Win32 Version: 3.0.6920.4902 built by: NetFXw7 CodeBase: file:///C:/Windows/assembly/GAC_MSIL/WindowsBase/3.0.0.0__31bf3856ad364e35/WindowsBase.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. Quote Link to comment Share on other sites More sharing options...
pbelb Posted December 19, 2009 Author Share Posted December 19, 2009 After hitting the cancel button on the error message dialog, I'm now presented with the attached screenshot, and it seems that I'll have to kill it off via the task manager.... it's off in la-la land. Quote Link to comment Share on other sites More sharing options...
pbelb Posted December 19, 2009 Author Share Posted December 19, 2009 ok, I take it back. sort of. Ok, so I noticed that after the last attempt at creating the MSI packages, that there was a PdnSetup folder left behind with nothing in it. so I deleted the folder, and tried the msi creation command again. this time, it did actually create the .msi packages. I tried installing the package, and it created the desktop icon for me, but, when I go and try to start the app, it now pops up a dialog box saying that Paint.net has stopped working, and that it's checking for a solution. curiously, the task manager shows that PaintDotNet.exe is still running, even though there are not any visible windows on-screen... after about 30 seconds the process disappears from the task manager list. either way, I'm still up the creek without a paddle. Quote Link to comment Share on other sites More sharing options...
pbelb Posted December 19, 2009 Author Share Posted December 19, 2009 On the off chance that the setup process is doing something with printers, I will mention that I have installed version 5.0.0.19 of the PrimoPDF software, which installs a print driver thing that generates PDF files rather than printed output. I also have installed the Samsung CLP-310 series print drivers. Quote Link to comment Share on other sites More sharing options...
Rick Brewster Posted December 19, 2009 Share Posted December 19, 2009 Nope nothing with printers. Honestly I have no idea what's going on with your system. I've had Paint.NET working great on Win7 almost all year and don't see others reporting the exact same issue. There are some who've reported being block from install on a fresh Win7, but a registry key ends up being the fix. If you've already got it installed (via the MSI), then that shouldn't be the issue. Quote The Paint.NET Blog: https://blog.getpaint.net/ Donations are always appreciated! https://www.getpaint.net/donate.html Link to comment Share on other sites More sharing options...
pbelb Posted December 19, 2009 Author Share Posted December 19, 2009 Hi Rick, thank you for replying. Would you mind being more explicit in some details about the registry key to which you refer? Quote Link to comment Share on other sites More sharing options...
Sarkut Posted December 19, 2009 Share Posted December 19, 2009 pbelb, The only Win7 registry problems I've noticed concern the NET Framework key that you have already checked. Since Paint.NET seems to have installed, sort of, I wonder whether running PdnRepair.exe might sort things out. Quote Link to comment Share on other sites More sharing options...
Rick Brewster Posted December 20, 2009 Share Posted December 20, 2009 Hi Rick, thank you for replying.Would you mind being more explicit in some details about the registry key to which you refer? This is the one I found, http://sineshift.wordpress.com/2009/12/ ... windows-7/ Quote The Paint.NET Blog: https://blog.getpaint.net/ Donations are always appreciated! https://www.getpaint.net/donate.html Link to comment Share on other sites More sharing options...
pbelb Posted December 26, 2009 Author Share Posted December 26, 2009 ok, I ended up trying installing pdn on a virtualbox hosted win7x64 instance (freshly installed) and found that it installed there without any problems at all. so, I ended up rebuilding my win7x64 install (the one I boot to) and found that I am able to install pdn 3.5.1 without any trouble at all. I still have no idea as to why the .net install was hosed up on the earlier install, but, in any case, it does now install just fine. thank you for all the help offered. all the best, peter. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.