Hullo Brian (or any others who might be able to untangle this problem),
Been off on another project, and only returned to this problem today.
My aim is to replicate how I used Pegasus before I changed my memory chip a few weeks ago, since when my system has gone rather haywire!
My ideal system, as I enjoyed before I changed my chip, was to keep all my mail in folders on my chip. I move my chip between my desktop and my laptop, and in each case, the chip runs as a separate mailbox attached to the the host in the folder hierarchy. In each case, the host copy of Pegasus (on my laptop or my desktop) has NewMail and Copy to Self folders, but no other folders. Once dealt with, all incoming mail is moved from NewMail on the host and filed in the folders on the chip, and from time to time all "Copy to Self" files are moved to the Copy to Self folder on the chip. aturally, Of course, the chip can be run independently, if needed. The setup has run quite happily like this for about two years. (And I would expect this is pretty much the standard operating procedure for those Pegasus users who keep their data on a memory chip.)
However, when I recently copied my files from my old chip to a new one, something went awry. Generally, after transferring all files folders to a new memory chip, I would delete Pmail.cfg on the new chip, rebuild Pegasus as a standalone system from the "Welcome to Pegasus" screen where the three boxes appear (ie the options "..one person using running Pegasus..", "..more than one person..", or "..Network.." options) and then re-attach the chip as a new mailbox to each host, using the "Add Mailbox to List" feature. Not sure if this is the approved means of moving from one media to another, but it has worked fine for me - until now!
After my post a few days ago, and Brian's response of 14 October, I have at least managed to recover the new mail from the laptop host system and separately backed up all folders; so I am not concerned about data recoverability. But I am about the weird semi-inoperable folder muddle that I seem to have created. I am hoping that if I explain the following in detail, the answers will spring to your mind - they certainly don't to mine!
A. Running Pegasus from the chip independent of the host on the desktop machine, I have a "Recent Search Results" filing tray that won't delete, saying it has folders in it to be deleted first, (but there are none there to delete) and apart from the "Recent Search Results" filing tray, there are five other filing trays, all of which faithfully appear as do all other folders (about 70 in all), which are fully accessible. (So, the only problem here is a Recent Search Results tray that can't be deleted.)
B. When I run Pegasus from the desktop's C:\ drive, with the chip attached as a separate mailbox, about 20 of the about 70 folders on the chip appear where I would expect them, as folders of the chip, but the balance of the folders think they belong to the host, and hang directly from the host. Neither the frozen "Recent Search Results" nor the five other "filing trays" put in an appearance. When I close the desktop based copy of Pegasus, I get an error message, with Windows telling me it would like me to let let MS know. (As if they would help - or care!!)
[Later - for some reason, running this configuration later, all the folders - save for the chip's "NewMail" - now appear as folders of the C:\, (perhaps the one group got lonely without its fellow folders!.) The host now shows NewMail, two copies of Copy to Self, all the folders of the chip, and none of the five filing trays. The chip shows "New Mail", and nothing else!]
C. When I run the chip in standalone mode on the laptop, the Pegasus wizard appears and tries to reinstall the internet connection. The new mail folder appears, as does the undeleteable Recent Search Results filing tray as do all the other filing trays, but no other folders appear at all. [But I have also seen today on occasion all the folders appear, but apart from the New Mail, under this situation, all folders report that they are damaged and can't be opened. They also can't be re-indexed. And I am not sure why the damaged folder option comes forward as opposed to the empty filing tray option!]
D. When I run the laptop based Pegasus and attach the chip as a mailbox, three folders appear; the host's NewMail and Copy to Self folders, and the chips Newmail folder appears with its mail readable. No other folders or filing trays appear.
E. If go back to my old chip (sigh) and run it in standalone mode – it works fine! But if I add it to the desktop Pegasus it seems its caught the same lurgy as B. above, and all the folders think they belong to the harddrive of the desktop and have jumped from the chip drive designation to the main drive!
When running the chip from a short cut, I am using the -roam command line option in each case.
Well, that’s as closely as I can define the problem/s. I’m
very much hoping that there is a simple solution, Brian. Failing a simple solution, I would probably methodically create new folders on the desktop and move files from the chip to the new folders and when that process completes, flatten the chip and start with a brand new Pegasus installation. But the curious split folder structure in B above prevents me doing that; so I'd have to find another solution, perhaps copying and pasting all the pmm and pmi folders off the chip and starting again. That option would certainly have saved me many hours wasted today chasing this scarlet pimpernel!
Any help you could provide would be most appreciated.
Johnny
<p>Hullo Brian (or any others who might be able to untangle this problem),
</p><p>Been off on another project, and only returned to this problem today.</p><p>My aim is to replicate how I used Pegasus before I changed my memory chip a few weeks ago, since when my system has gone rather haywire!
</p><p>My ideal system, as I enjoyed before I changed my chip, was to keep all my mail in folders on my chip. I move my chip between my desktop and my laptop, and in each case, the chip runs as a separate mailbox attached to the the host in the folder hierarchy. In each case, the host copy of Pegasus (on my laptop or my desktop) has NewMail and Copy to Self folders, but no other folders. Once dealt with, all incoming mail is moved from NewMail on the host and filed in the folders on the chip, and from time to time all "Copy to Self" files are moved to the Copy to Self folder on the chip. aturally, Of course, the chip can be run independently, if needed. The setup has run quite happily like this for about two years. (And I would expect this is pretty much the standard operating procedure for those Pegasus users who keep their data on a memory chip.) </p><p>However, when I recently copied my files from my old chip to a new one, something went awry. Generally, after transferring all files folders to a new memory chip, I would delete Pmail.cfg on the new chip, rebuild Pegasus as a standalone system from the "Welcome to Pegasus" screen where the three boxes appear (ie the options "..one person using running Pegasus..", "..more than one person..", or "..Network.." options) and then re-attach the chip as a new mailbox to each host, using the "Add Mailbox to List" feature. Not sure if this is the approved means of moving from one media to another, but it has worked fine for me - until now!</p><p>After my post a few days ago, and Brian's response of 14 October, I have at least managed to recover the new mail from the laptop host system and separately backed up all folders; so I am not concerned about data recoverability. But I am about the weird semi-inoperable folder muddle that I seem to have created. I am hoping that if I explain the following in detail, the answers will spring to your mind - they certainly don't to mine!</p><p>A.&nbsp;&nbsp; Running Pegasus from the chip independent of the host <u>on the desktop machine</u>, I have a "Recent Search Results" filing tray that won't delete, saying it has folders in it to be deleted first, (but there are none there to delete) and apart from the "Recent Search Results" filing tray, there are five other filing trays, all of which faithfully appear as do all other folders (about 70 in all), which are fully accessible. (So, the only problem here is a Recent Search Results tray that can't be deleted.)
</p><p>B.&nbsp;&nbsp;&nbsp; When I run Pegasus from the desktop's C:\ drive, with the chip attached as a separate mailbox, about 20 of the about 70 folders on the chip appear where I would expect them, as folders of the chip, but the balance of the folders think they belong to the host, and hang directly from the host. Neither the frozen "Recent Search Results" nor the five other "filing trays" put in an appearance. When I close the desktop based copy of Pegasus, I get an error message, with Windows telling me it would like me to let let MS know. (As if they would help - or care!!)</p><p>[Later - for some reason, running this configuration later, all the folders - save for the chip's "NewMail" - now appear as folders of the C:\, (perhaps the one group got lonely without its fellow folders!.) The host now shows NewMail, two copies of Copy to Self, all the folders of the chip, and none of the five filing trays. The chip shows "New Mail", and nothing else!]
</p><p>C.&nbsp;&nbsp;&nbsp; When I run the chip in standalone mode <u>on the laptop</u>, the Pegasus wizard appears and tries to reinstall the internet connection. The new mail folder appears, as does the undeleteable Recent Search Results filing tray as do all the other filing trays,&nbsp; but no other folders appear at all. [But I have also seen today on occasion all the folders appear,&nbsp; but apart from the New Mail, under this situation, all folders report that they are damaged and can't be opened. They also can't be re-indexed. And I am not sure why the damaged folder option comes forward as opposed to the empty filing tray option!]
</p><p>D.&nbsp;&nbsp;&nbsp; When I run the laptop based Pegasus and attach the chip as a mailbox, three folders appear; the host's NewMail and Copy to Self folders, and the chips Newmail folder appears with its mail readable. No other folders or filing trays appear.
</p><p class="MsoNormal">&nbsp;E.&nbsp;&nbsp; If go back to my old chip (sigh) and run it in standalone mode – it works fine! But if I add it to the desktop Pegasus it seems its caught the same lurgy as B. above, and all the folders think they belong to the harddrive of the desktop and have jumped from the chip drive designation to the main drive!</p><p>&nbsp;When running the chip from a short cut, I am using the -roam command line option in each case.
</p><p class="MsoNormal">&nbsp;</p>
<p class="MsoNormal">Well, that’s as closely as I can define the problem/s. I’m
very much hoping that there is a simple solution, Brian. Failing a simple solution, I would probably methodically create new folders on the desktop and move files from the chip to the new folders and when that process completes, flatten the chip and start with a brand new Pegasus installation. But the curious split folder structure in B above prevents me doing that; so I'd have to find another solution, perhaps copying and pasting all the pmm and pmi folders off the chip and starting again. That option would certainly have saved me many hours wasted today chasing this scarlet pimpernel!
</p><p class="MsoNormal">&nbsp;Any help you could provide would be most appreciated.</p><p class="MsoNormal">Johnny
</p>
<p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p>