Jump to content

aworkerb

Members
  • Posts

    12
  • Joined

  • Last visited

Everything posted by aworkerb

  1. Well, I guess a picture's worth at least a couple of words. Here's where I installed the files. But see my forehead-smacking realization bolded farther down... I'm not sure what the "Shop" version is, unless you mean the Microsoft Store? I've only ever had the standalone version. HOWEVER, your post made me poke around and finally notice that there were NO OTHER FILES in the parent folder of my FileTypes folder, only a handful of other folders (Effects, Shapes, Staging). That's because everything else is where the program actually lives, Program Files (x86), not plain old Program Files. I moved the filetype libraries to the correct folder, and now I can save out ZIP files. Too bad the reason I went down the path in the first place has come and gone. But I'll be ready for next time. Thanks for the help and motivating me to look more carefully.
  2. Good idea. Unfortunately, "there were no errors encountered while loading plugins".
  3. Ugh. Even removing everything else from FileTypes didn't help. Well, thanks for the reply.
  4. I just installed the files into the FileTypes folder but ZIP doesn't appear in the Open or Save As options. I'm on 4.2.15 -- anyone using it successfully with the latest version?
  5. Did something change since the instructions at the start of this thread were last updated? I downloaded the filetype plugin from the github link, not anything from the dropbox link, and just put it into the filetypes folder. Now I get a dialog asking for resolution when I try to open an SVG image. Is it that simple now, and we can ignore the rest of the instructions? Or am I missing out on some functionality?
  6. Update: I installed Paint.net 4.2.11 beta build 7433 and... so far so good. When I run it with disableNtfsTx applied, and save a file into a OneDrive synced folder, the sync remains stable and things appear to work as they should! Thank you! Now to figure out how to ensure that paintdotnet.exe always runs with that switch, even when I double-click a pdn file or right-click and pick Edit for an image file. edit: figured it out, with surgical registry edits to values within Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\paint.net.1
  7. FWIW, the problem remains (for me) for the latest version of OneDrive, 20.052.0311.0011
  8. This is great -- looking forward to trying it, and will report back. Thanks!
  9. I won't pretend to know this by any means, but from extremely quick research it seems that regular OneDrive ONLY support NTFS, and I imagine that would necessitate supporting NTFS transactions, and I'd speculate OneDrive for Business is pretty much the same, but who knows. More significantly, I didn't notice this problem up until sometime in the past month or so, and I was definitely using Paint.NET to save into OneDrive sync'd folders for a while before that (months, at least). ... and since Paint.NET was last updated in mid-Feb, but OneDrive was updated in early April, I'm leaning toward that version of OneDrive being the culprit. I'm trying to get the go-ahead from my corp help desk to install a late April update. For my situation, everything works normally, with the OneDrive folders acting just like local ones, up until the point where I save from Paint.NET into one of them.
  10. Recently, whenever I use Paint.net to save an image file into a OneDrive for Business synced folder, it causes file synchronization to stop, and I have to reboot in order to properly restart the sync. A coworker confirmed getting the same problem. Has anyone else who uses OneDrive for Business (and synchronizes their folders so they can be accessed through File Explorer) seen this problem? Or if you haven't tried saving to a synced folder, mind trying? (Not sure if data points for the consumer version of OneDrive are relevant or not.) I'm running paint.net 4.2.10 (Final 4.2.10.7348.40816) and OneDrive version 2020 (Build 19.232.1124.0012). I've made the sync fail several times upon saving a file in Paint.net. I do not currently know if saving files using other applications causes the same problem.
×
×
  • Create New...