Jump to content

Paint.NET install shared out


Recommended Posts

Ok we (My Class Mates) are having a problem with getting Paint.NET to work from a share folder.

Our class is a Windows Server 2003 class with 2 window server 2003 systems setup, and about 8 Windows XP Pro computers. The network is not connected to the internet. All computers have .NET Framework 2.0 installed. We are trying to setup one Windows XP Pro computer with Paint.NET 3.10. The install worked. We then shared the folder out with Full Control. We then used another computer to try and run Paint.NET from the share folder. We got an error.

Any idea why we got an error even though the share folder has read, write, and execute.

PS: It not because of registries as we did a test to make sure.

Link to comment
Share on other sites

It's not trying to make life hard. There are sound security reasons for this. Paint.NET is not designed to run from a network share. If you have administrator privilege on your local system, then just install it locally. If you don't, then copy it locally (a folder on your desktop should even work just fine). I do not understand why you are even trying to do this.

The Paint.NET Blog: https://blog.getpaint.net/

Donations are always appreciated! https://www.getpaint.net/donate.html

forumSig_bmwE60.jpg

Link to comment
Share on other sites

We are all Admins to all systems and to both servers.

Best way to look at it is as a large network.

Lets say we had 50 computers. It be better to install Paint.NET on a server and share it out. Because Paint.NET is so small we wont have to worry about lag on the network. Also because it is shared we can install Effects and File Types right to the server and not have to waste time on installing on all 50 computers. It also means you can do updates with out having to update every computer.

It just makes it better for large networks.

Link to comment
Share on other sites

Try installing Paint.NET on each of the computers and setting the install directory to the shared drive location. Each install would overlap the last but that shouldn't cause any problems.

Probably not a good idea.

Click to play:
j.pngs.pngd.pnga.pngp.png
Download: BoltBait's Plugin Pack | CodeLab | and how about a Computer Dominos Game

Link to comment
Share on other sites

We are all Admins to all systems and to both servers.

Best way to look at it is as a large network.

Lets say we had 50 computers. It be better to install Paint.NET on a server and share it out. Because Paint.NET is so small we wont have to worry about lag on the network. Also because it is shared we can install Effects and File Types right to the server and not have to waste time on installing on all 50 computers. It also means you can do updates with out having to update every computer.

It just makes it better for large networks.

Or you can read up on unattended installation and AD/GPO stuff, which is designed specifically to handle this.

http://www.getpaint.net/doc/latest/en/U ... ation.html

As for the plugins, I'm sure it's trivial to set up replication or even a batch file to maintain folder synchronization.

The Paint.NET Blog: https://blog.getpaint.net/

Donations are always appreciated! https://www.getpaint.net/donate.html

forumSig_bmwE60.jpg

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...