HITMAN-X- Posted November 2, 2007 Share Posted November 2, 2007 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. Quote DEXTUT.COM Link to comment Share on other sites More sharing options...
Bob Posted November 2, 2007 Share Posted November 2, 2007 Check http://blogs.msdn.com/brada/archive/200 ... share.aspx Quote No. Way. I've just seen Bob. And... *poof!*—just like that—he disappears into the mist again. ~Helio Link to comment Share on other sites More sharing options...
HITMAN-X- Posted November 2, 2007 Author Share Posted November 2, 2007 Ok bob I was reading the page and it says that Windows like to make life hard and that there are work arounds. However I could not see a work around for the problem I am having. Quote DEXTUT.COM Link to comment Share on other sites More sharing options...
Rick Brewster Posted November 2, 2007 Share Posted November 2, 2007 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. 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...
HITMAN-X- Posted November 2, 2007 Author Share Posted November 2, 2007 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. Quote DEXTUT.COM Link to comment Share on other sites More sharing options...
barkbark00 Posted November 2, 2007 Share Posted November 2, 2007 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. Quote Take responsibility for your own intelligence. -Rick Brewster Link to comment Share on other sites More sharing options...
BoltBait Posted November 2, 2007 Share Posted November 2, 2007 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. Quote Click to play: Download: BoltBait's Plugin Pack | CodeLab | and how about a Computer Dominos Game Link to comment Share on other sites More sharing options...
Rick Brewster Posted November 2, 2007 Share Posted November 2, 2007 That's probably the worst thing you could try. 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...
Rick Brewster Posted November 2, 2007 Share Posted November 2, 2007 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. 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...
barkbark00 Posted November 2, 2007 Share Posted November 2, 2007 Probably not a good idea. That's probably the worst thing you could try. I figure you guys would say that... Quote Take responsibility for your own intelligence. -Rick Brewster 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.