I've used Pegasus mail for, well, forever it seems - always on one machine. Now I have a network of 3 machines, and due to hardware failures it seems I'm constantly moving from one to another. I'd like to set up one network home, which would allow me to get to my incoming email from any of my machines. I think right now all of my machines are Windows 7 Ultimate. The other issue is that I want to make sure my current, single-user mailbox isn't destroyed in the process, but rather migrates nicely to a networked environment.
My first attempt, which almost worked, was to create one shared, mountable drive on one machine, which I refer to (somewhat randomly) as H: on every machine. Since I'm the only one reading email, and I only do it from one machine at a time, I naively thought I could move (that is, specify, within Pegasus) my mailbox (both new and regular) to H:, and set this H: up on every one of my machines - the (self-imposed) protocol being that I only would use one machine at a time, and that machine would (universally, that is this is the same on every machine) use a mailbox "H:\users\Bryan\Pmail\". It really did seem to work - (pardon my machine names) :the real disk was on Mycenae, and my Plataea machine could reach over, download mail, etc. Then I found I could also read email on Mycenae; *but*, when I went back to Plataea, I got messages that the mailbox location didn't exist - though before I had read email on Mycenae - the directory was accessible and had the same path. However, having read email from Plataea, it seemed (perhaps due to file permissions/ownership, but I've checked that closely), that Mycenae could not read it. My other machine is Tiryns; haven't tried access from there yet, as these two should work first, I would think.
Stepping back, I want to do this because I've got some hardware problems, and I want to be somewhat independent of specific machines. I may end up reinstalling the OS on one or more machines, and even moving the physical location of my shared, master disk. I'd like to abstract away from the real, physical location of that disk, and make it universally available (as well as something that I can move easily if I need to).
So: to be specific, should I get into the network installations of Pegasus? When I started to do that, I had dialog boxes that said things like "Do you want to create a mailbox", or "The username isn't recognized" (though my login name in the Windows workgroup is the same - I have no server to support a domain). If I do install Pegasus with the shared access network options, *what do I do with my current mailbox*? I've got thousands of emails there, carefully categorized, and I want to be able to port them to whatever network identity mailbox Pegasus sets up. I've been very nervous about 'creating a new mailbox' and specifying an existing pmail directory, thinking that maybe things would be overwritten. When I specified my username ("Bryan") I was told it didn't exist - though I was logged in under that name. If Pegasus network sharing works to some degree independently of Windows, I couldn't figure it out.
I went off on a tagent trying to figure out why Windows 7 uses a "roaming" directory for settings, thinking that maybe there was some mechanism in Windows that would get me where I want to go trivially (ha!). All of my machines are Windows 7 - none is a 'server', so I can't set up a 'domain' and share settings across machines using that mechanism. I'm also hoping that Pegasus doesn't depend on this underlying Windows domain mechanism, but I'm not sure - the verbiage is often the same, though that could be coincidental. All I've got is a set of computers (some XP, come to think of it) that I'd like to work together without having to buy something from Microsoft. Though I probably would, if the cost were OK and I didn't have to change the OS on one of my machines.
Finally, I should say I've searched and read through the fora, and have some idea of how I would set things up if I were starting afresh; but I'm not. My pegasus email directory, when examined by hand, has a pmail.ini that has lots of detailed info, including paths to mailboxes. I think I want to *migrate* my single-user world to one that is networked - I haven't found any messages forae that address that. I'm still afraid of 'creating' a directory and specifying a path to my existing directory, as critical files might be overwritten; *but*, when I create a *new* directory and then copy in my old files, things fail. I've tried that, though maybe without specifying that the Pegasus install should be networked. The number of permutations (kind of Pegasus install, mailbox location (local/networked)) have grown such that I'm sure I haven't completely searched that space.
I've tried to directly edit the pmail.ini file(s), and registry entries that reference the mailbox. Oh, and, incidentally, sometimes when I try to change mailbox location within Pegasus, nothing happens - even clicking the right button, Peg doesn't exit and restart, just ignores me. And if I quit and come back, the old setting is there - it's as if Pegasus actively resists changing to a location that is a network mount. But there is no error or warning - just obtuseness. That's why I thought I should see what might be hiding in the Registry. I had no luck with any of this.
Any advice would be most appreciated. I can't help but think that this must be a problem that others have faced, or will face.
Bryan
<p>I've used Pegasus mail for, well, forever it seems - always on one machine.&nbsp; Now I have a network of 3 machines, and due to hardware failures it seems I'm constantly moving from one to another.&nbsp; I'd like to set up one network home,&nbsp;which would&nbsp;allow me to get to my incoming email from any of my machines. I think right now all of my machines are Windows 7 Ultimate.&nbsp; The other issue is that I want to make sure my current, single-user mailbox isn't destroyed in the process, but rather migrates nicely to a networked environment.</p><p>My first attempt, which almost worked, was to create one shared, mountable drive on one machine, which I refer to (somewhat randomly) as H: on every machine. Since I'm the only one reading email, and I only do it from one machine at a time, I naively thought I could move (that is, specify, within Pegasus) my mailbox (both new and regular) to H:, and set this H: up on every one of my machines - the (self-imposed) protocol being that I only would use one machine at a time, and that machine would (universally, that is this is the same on every machine) use a mailbox "H:\users\Bryan\Pmail\". It really did seem to work -&nbsp;(pardon my machine names) :the real disk was on&nbsp;Mycenae, and my Plataea machine could reach over, download mail, etc.&nbsp;&nbsp;Then I found I could also read email on Mycenae;&nbsp;*but*, when I went back to Plataea, I got messages that the mailbox location didn't exist - though before I had read email on Mycenae -&nbsp; the directory was accessible and had the same path. However, having read email from Plataea, it seemed (perhaps due to file permissions/ownership, but I've checked that closely), that Mycenae could not read it. My other machine is Tiryns; haven't tried access from there yet, as these two should work first, I would think.</p><p>Stepping back, I want to do this because I've got some hardware problems, and I want to be&nbsp;somewhat independent of specific machines. I may end up reinstalling the&nbsp;OS on one or more&nbsp;machines, and even moving the physical location of my shared, master disk. I'd like to abstract away from the real, physical location of that disk, and make it universally available (as well as something that I can move easily if I need to).</p><p>So: to be specific, should I get into the network installations of Pegasus? When I started to&nbsp;do that, I had dialog boxes that said things like "Do you want to create a mailbox", or "The username isn't recognized" (though my login name&nbsp;in the Windows workgroup is the same - I have no server to support a domain). If I do install&nbsp;Pegasus with the shared access network options, *what do I do with my current mailbox*? I've got thousands of emails there, carefully categorized, and I want to be able to port them to whatever network identity mailbox Pegasus sets up. I've been very nervous about 'creating a new mailbox' and specifying an existing pmail directory, thinking that maybe things would be overwritten. When I specified my username ("Bryan") I was told it didn't exist - though I was logged in under that name. If Pegasus network sharing works to some degree independently of Windows, I couldn't figure it out.</p><p>I went off on a tagent trying to figure out why Windows 7 uses a "roaming" directory for settings, thinking that maybe there was some mechanism in Windows that would get me where I want to go trivially (ha!). All of my machines are Windows 7 - none is a 'server', so I can't set up a 'domain' and share settings across machines using that mechanism. I'm also hoping that Pegasus doesn't depend on this underlying Windows domain mechanism, but I'm not sure - the verbiage is often the same, though that could be coincidental. All I've got is a set of computers (some XP, come to think of it) that I'd like to work together without having to buy something from Microsoft.&nbsp; Though I probably would, if the cost were OK and I didn't have to change the OS on one of my machines.</p><p>Finally, I should say I've searched and read through the fora, and have some idea of how I would set things up if I were starting afresh; but I'm not. My pegasus email directory, when examined by hand, has a pmail.ini that has lots of detailed info, including paths to mailboxes. I think I want to *migrate* my single-user world to one that is networked - I haven't found any messages forae that address that.&nbsp; I'm still afraid of 'creating' a directory and specifying a path to my existing directory, as critical files might be overwritten; *but*, when I create a *new* directory and then copy in my old files, things fail.&nbsp; I've tried that, though maybe without specifying that the Pegasus install should be networked. The number of permutations (kind of Pegasus install, mailbox location (local/networked)) have grown such that I'm sure I haven't completely searched that space.</p><p>I've tried to directly edit the pmail.ini file(s), and registry entries that reference the mailbox. Oh, and, incidentally, sometimes when I try to change mailbox location within Pegasus, nothing happens - even clicking the right button, Peg doesn't exit and restart, just ignores me. And if I quit and come back, the old setting is there - it's as if Pegasus actively resists changing to a location that is a network mount. But there is no error or warning - just obtuseness. That's why I thought I should see what might be hiding in the Registry. I had no luck with any of this.</p><p>&nbsp;Any advice would be most appreciated.&nbsp; I can't help but think that this must be a problem that others have faced, or will face. </p><p>&nbsp;Bryan</p>
