Rick Brewster

Same, although it works if I manually select 32-bit.

Hmm. Well I haven't received any other reports of this ... ghosts?

Are you still using those shortcuts that change around the directory that Paint.NET is running from? (or whatever it was -- I forget exactly) You can also use Process Explorer to spy on the current directory for the PaintDotNet.exe process when that error occurs.

Well, can you please post the contents of the following log files which will be in the %TEMP% directory (e.g., c:\users\User Name\AppData\Local\Temp): * PdnSetupShim.log * PdnMsiInstall.log * PdnSetupNgenInstall.log

Upgrade is not supported with MSI AD/GPO. You must first uninstall.

Uhh no. You're asking me to undo almost everything I just did for this release. SP2 isn't even supported by Microsoft anymore. I announced I'd be doing this months ago on my blog, so no one should really have any claim to surprise. This allows me to cut down my testing by many hours per release, significantly reduce the download size (as BB mentioned), and is a stepping stone to removing XP support completely so that I can use OS components only available in Win7/Vista in Paint.NET v4.0. And given the amount of bandwidth I'm chewing through with Paint.NET, it is worth it. Go talk to your IT admin and have them install SP3, or ask them to let you install it yourself. It's been out for 2 years already -- I refuse to be the one paying for your outdated IT policy when I'm giving this away for free.

No, but since this is a .NET issue I think you'd make more progress by asking on a forum related to .NET itself. Moved to Troubleshooting

Sorry, but this is already answered in the FAQ, Paint.NET will never be ported to Mac, or Linux, or Mono, or iPhone, or _____. On the Mac, however, Parallels is a very good way of running Paint.NET. I've used it myself on my MacBook Pro (2008 model). Closed

Nope. It's a pineapple.

I've filed a bug on this. For Paint.NET v4.0, this EXIF tag simply won't be localized and will always say "Paint.NET v4.0" (or the appropriate version).

In the Paint.NET installation directory, is there a file named PaintDotNet.SystemLayer.Native.x86.dll? In the Windows system directory (C:\Windows\System32) is there both a dwrite.dll and a d2d1.dll?

Uhh ... why? Do you really need to save to C:\Windows and C:\Program Files?

I just fixed it about 10 seconds ago Thanks Bungle. Not in any automatic way. You probably don't want to do this.

Not stupid. Not bad. There are no plans to add Sketchup support to Paint.NET.

Change it from a string to an IntPtr, and remove the [MarshalAs] attribute. I assume VTFImageFormat is an enum, with implicit type of int?

That's because I'm still uploading all the manifest files. Hold your horses.

You're probably stomping memory or stack then. What's the definition in C/C++ for that function you're calling?

As usual, there are two ways to get it: 1. Direct download from the website, http://www.getpaint.net/ . There is no need to uninstall your old version; that will be taken care of automatically. 2. Use the built-in auto-updater. You can either wait a few days for the update to be offered to you, or you can go to the Utilities menu and then click on Check for Updates. What's new since v3.5.4: Fixed the bug where saving as 8-bit PNG/GIF/BMP wasn't always working, usually with larger images. Improved the performance of the Gaussian Blur effect by 30-40%. Improved the performance of all the layer blending modes by 15-30%. Improved the performance of zooming with the mouse wheel on dual-core Intel Atom systems. Updated to support .NET 4.0 if no other version of .NET is installed. Reduced download size from 4.8MB down to 3.5MB. Fixed a small error in the Chinese translation. Please note that Service Pack 3 (SP3) is now required for Windows XP users. Also, Service Pack 1 (SP1) is now required for Windows Vista users. If you do not have these installed, then the Paint.NET installer will open the appropriate download page on Microsoft's site.

Ok you say "This line crashes", but please remember that I am not psychic. I need the exception.

Unless you're implementing a structure that contains a union, you shouldn't have to specify LayoutKind.Explicit. You should only need to specify a special Pack value if the C/C++ struct also does. If you copy/paste the C/C++ definition for that struct, I can tell you if your interop definition is correct.

Yes, file type plugins aren't loaded until they are needed -- which isn't until the user requests an Open or Save dialog. Like I said, use the post that talks about debugging your plugin. You will need to look at the InnerException on that, or tell VS to break on any exception and not just unhandled ones.

That's not a regression from previous versions though. Plus, it could be Windows that's displaying it wrong.

I can't understand anything you're saying.

Oh please. I could ban you, then none of your new links would work! Stop being so selfish and self-entitled.

Have you tried static linking to the runtimes? That would get rid of the installation issue completely.