Transfer to new computer problem

Jerry Wise

posted Sep 23 '11 at 3:17 am

[quote user="fdavis"]

The old machine ran XP and the new one is Windows 7. The hard drive crashed on the old one, so I don't have access to it. A friend was able to salvage just the PMAIL files, so I was able to access those to get the info. Both the old computer and new one are single user machines. I don't remember which version of Pegasus I was using before the crash. Following is the information you asked me to copy in.

Pegasus Mail for Microsoft Windows
Copyright (C) 1992-2010, David Harris, all rights reserved
Electronic mail to support@pmail.gen.nz.

WinPMail version: Version 4.52 (Win32), Jan 13 2010
Language resources: Standard UK English resource set
Extension Manager version: 1.13
Operating mode: Standalone
User name and ID: Admin, 0
Windows version: 6.1
Windows flag word: 0
WINPMAIL.EXE directory: C:\PMAIL\Programs
Home mailbox location: C:\PMAIL\MAIL\Admin
New mailbox location: C:\PMAIL\MAIL\Admin
TMP environment variable: C:\Users\Freddy\AppData\Local\Temp
TEMP environment variable: C:\Users\Freddy\AppData\Local\Temp
LAN-based SMTP support: N, N, N
NetWare MHS support: N, N, N
Built-in TCP/IP support: Enabled
- WINSOCK version: WinSock 2.0
- WINSOCK path: C:\Windows\system32\WSOCK32.DLL
Commandline: -roam -A
Active -Z options: 32768
PMR variable: (None)
PML variable: (None)
MAI variable: (None)
NB variable: (None)
Autofiltering folders: 0 (0 active, 0 inactive)
Last new mail count: 1

One last note: This issue doesn't seem to be causing any particular problems that I can tell. It is just annoying to have those extra lines in the directory structure.

Thanks,

Freddy

[/quote]

You have installed an older version of winpm-32 and the oldest that can work with win7 successfully. I had thought you were installing 4.62 which is the current version but I see differently. However 4.52 should work ok for now and you can then update again soon only it should be easy and routine update.

Can you do any screen shot or any directory listing so we could see what those extra lines look like and what they might be?

If necessary we might need to exchange some information via private message with attachment. Are you and old school user who might be familiar with o9erating via Command prompt and how to do directory and file listings and how to copy and save to a win7 text program like Notepad? Have you discovered Clip yet? It sure comes in handy at times like this and I use it a lot to run commands and have it saved automatically to windows clipboard where it can then be pasted into any Windows applications.

[quote user="fdavis"]The old machine ran XP and the new one is Windows 7. The hard drive crashed on the old one, so I don't have access to it. A friend was able to salvage just the PMAIL files, so I was able to access those to get the info. Both the old computer and new one are single user machines. I don't remember which version of Pegasus I was using before the crash. Following is the information you asked me to copy in.&nbsp;Pegasus Mail for Microsoft Windows Copyright (C) 1992-2010, David Harris, all rights reserved Electronic mail to support@pmail.gen.nz. WinPMail version: Version 4.52 (Win32), Jan 13 2010 Language resources: Standard UK English resource set Extension Manager version: 1.13 Operating mode: Standalone User name and ID: Admin, 0 Windows version: 6.1 Windows flag word: 0 WINPMAIL.EXE directory: C:\PMAIL\Programs Home mailbox location: C:\PMAIL\MAIL\Admin New mailbox location: C:\PMAIL\MAIL\Admin TMP environment variable: C:\Users\Freddy\AppData\Local\Temp TEMP environment variable: C:\Users\Freddy\AppData\Local\Temp LAN-based SMTP support: N, N, N NetWare MHS support: N, N, N Built-in TCP/IP support: Enabled &nbsp; - WINSOCK version: WinSock 2.0 &nbsp; - WINSOCK path: C:\Windows\system32\WSOCK32.DLL Commandline: -roam -A Active -Z options: 32768 PMR variable: (None) PML variable: (None) MAI variable: (None) NB variable: (None) Autofiltering folders: 0 (0 active, 0 inactive) Last new mail count: 1 &nbsp; One last note: This issue doesn't seem to be causing any particular problems that I can tell. It is just annoying to have those extra lines in the directory structure.&nbsp;Thanks,Freddy &nbsp;[/quote]You have installed an older version of winpm-32 and the oldest that can work with win7 successfully. I had thought you were installing 4.62 which is the current version but I see differently. However 4.52 should work ok for now and you can then update again soon only it should be easy and routine update.Can you do any screen shot or any directory listing so we could see what those extra lines look like and what they might be?If necessary we might need to exchange some information via private message with attachment. Are you and old school user who might be familiar with o9erating via Command prompt and how to do directory and file listings and how to copy and save to a win7 text program like Notepad?&nbsp; Have you discovered Clip yet? It sure comes in handy at times like this and I use it a lot to run commands and have it saved automatically to windows clipboard where it can then be pasted into any Windows applications.

fdavis

posted Sep 23 '11 at 1:25 am

I was able to transfer my old directory structure to my new computer, but now in the "Folders" window there are several lines which read <html dir='ltr'><head>meta http-equiv="PICS-La. Then, over on the right side there is a number ( -28251:4).

Every time I open this window a new line is generated, but goes back to 3 lines when I reboot.

Any idea what this is and how can I get rid of them.

I was able to transfer my old directory structure to my new computer, but now in the "Folders" window there are several lines which read &lt;html dir='ltr'&gt;&lt;head&gt;meta http-equiv="PICS-La. Then, over on the right side there is a number ( -28251:4).&nbsp;Every time I open this window a new line is generated, but goes back to 3 lines when I reboot. Any idea what this is and how can I get rid of them.

Jerry Wise

posted Sep 23 '11 at 1:44 am

Age old often repeated problems. Do not try to copy anything from old machine to new that contains any configuration or settings or has paths contained in it. You can transfer message files .cnm and message folder pairs and address book pairs and d lists .pml but do no let any .ini file from the old machine near the new machine. The only time an old setup can be copied is when, and it is rare, both machines are configured the same and installs on both were at default installer values and locations. In any other situation it is far better to install to the new machine accepting the default location and configure it to receive and send mail successfully and only after that test then proceed to copy in old data from other machine and making sure to right location and also that all transferred files are not marked read only by the OS or any backup program or via use of any cdrom for transfer.

Age old often repeated &nbsp;problems. Do not try to copy anything from old machine to new that contains any configuration or settings or has paths contained in it. You can transfer message files .cnm and message folder pairs and address book pairs and d lists .pml but do no let any .ini file from the old machine near the new machine. The only time an old setup can be copied is when, and it is rare, both machines are configured the same and installs on both were at default installer values and locations. In any other situation it is far better to install to the new machine accepting the default location and configure it to receive and send mail successfully and only after that test then proceed to copy in old data from other machine and making sure to right location and also that all transferred files are not marked read &nbsp;only by the OS or any backup program or via use of any cdrom for transfer.

fdavis

posted Sep 23 '11 at 2:05 am

I thought I only got the appropriate files. Obviously I picked up something wrong. So, what can I do about it?

caisson

posted Sep 23 '11 at 2:24 am

[quote user="fdavis"]I thought I only got the appropriate files. Obviously I picked up something wrong. So, what can I do about it?
[/quote]

Probably starting again is your only real option.

If you didn't backup your mail directory you need to do it now, uninstal the existing setup and then reinstal Pmail as a new installation.

Get it working and then selectively transfer files from the backup.

[quote user="fdavis"]I thought I only got the appropriate files. Obviously I picked up something wrong. So, what can I do about it? [/quote]Probably starting again is your only real option.If you didn't backup your mail directory you need to do it now, uninstal the existing setup and then reinstal Pmail as a new installation.Get it working and then selectively transfer files from the backup.&nbsp; &nbsp;&nbsp;

fdavis

posted Sep 23 '11 at 2:27 am

Thanks for your help.

Blessings!

Thanks for your help.Blessings!

Jerry Wise

posted Sep 23 '11 at 2:37 am

[quote user="fdavis"]I thought I only got the appropriate files. Obviously I picked up something wrong. So, what can I do about it?
[/quote]

What OS version is the new machine? On the new machine install can you do Help, About, Info button and copy that display and paste it. If the old machine is also available and runnable do the same and save a copy.

Drastic method used as last resort: Study http://www.vandenbogaerde.net/pegasusmail/pf_pmfiles.htm

What has worked before to solve some "problem cases" is to capture any PMail related file on the new machine and compress them into an archive file like .zip or other and verify that. Then delete the uncompressed files from system. Then run the 4.62 installer .exe and with all blocks checked and accepting the default c:\pmail location it offers. Then proceed to set up and configure including all menus until you can receive and send mail ok. Then you can proceed to work your way through all settings in and under Tools, options and also Tools, Internet options too. When that all check out ok then you can begin to copy just the data needed from the old machine if available and just the messages, messages folders, address books and distribution files. Don't worry about any other files until that all checks out ok and all old mail is now seen and all old folders are intact. Leave any and all files on old machine that are not a part of 4.62 installer archive that may remain or have been stored in and under c:\pmail and below. User files added or stored there don't really belong there and may and often do cause trouble. Any messages and any attachments are already within the files already discussed just as they were received.

What exact version were you using before and on exactly which OS version? Was it an old single user install or a multi user install?

[quote user="fdavis"]I thought I only got the appropriate files. Obviously I picked up something wrong. So, what can I do about it? [/quote]What OS version is the new machine? On the new machine install can you do Help, About, Info button and copy that display and paste it. If the old machine is also available and runnable do the same and save a copy.&nbsp;Drastic method used as last resort: Study http://www.vandenbogaerde.net/pegasusmail/pf_pmfiles.htm What has worked before to solve some "problem cases" is to capture any PMail related file on the new machine and compress them into an archive file like .zip or other and verify that. Then delete the&nbsp; uncompressed files from system. Then run the 4.62 installer .exe and with all blocks checked and accepting the default c:\pmail location it offers. Then proceed to set up and configure including all menus until you can receive and send mail ok. Then you can proceed to work your way through all settings in and under Tools, options and also Tools, Internet options too. When that all check out ok then you can begin to copy just the data needed from the old machine if available and just the messages, messages folders, address books and distribution files. Don't worry about any other files until that all checks out ok and all old mail is now seen and all old folders are intact. Leave any and all files on old machine that are not a part of 4.62 installer archive that may remain or have been stored in and under c:\pmail and below. User files added or stored there don't really belong there and may and often do cause trouble.&nbsp; Any messages and any attachments are already within the files already discussed just as they were received.What exact version were you using before and on exactly which OS version? Was it an old single user install or a multi user install? &nbsp;&nbsp;

fdavis

posted Sep 23 '11 at 2:51 am

The old machine ran XP and the new one is Windows 7. The hard drive crashed on the old one, so I don't have access to it. A friend was able to salvage just the PMAIL files, so I was able to access those to get the info. Both the old computer and new one are single user machines. I don't remember which version of Pegasus I was using before the crash. Following is the information you asked me to copy in.

Pegasus Mail for Microsoft Windows
Copyright (C) 1992-2010, David Harris, all rights reserved
Electronic mail to support@pmail.gen.nz.

WinPMail version: Version 4.52 (Win32), Jan 13 2010
Language resources: Standard UK English resource set
Extension Manager version: 1.13
Operating mode: Standalone
User name and ID: Admin, 0
Windows version: 6.1
Windows flag word: 0
WINPMAIL.EXE directory: C:\PMAIL\Programs
Home mailbox location: C:\PMAIL\MAIL\Admin
New mailbox location: C:\PMAIL\MAIL\Admin
TMP environment variable: C:\Users\Freddy\AppData\Local\Temp
TEMP environment variable: C:\Users\Freddy\AppData\Local\Temp
LAN-based SMTP support: N, N, N
NetWare MHS support: N, N, N
Built-in TCP/IP support: Enabled
- WINSOCK version: WinSock 2.0
- WINSOCK path: C:\Windows\system32\WSOCK32.DLL
Commandline: -roam -A
Active -Z options: 32768
PMR variable: (None)
PML variable: (None)
MAI variable: (None)
NB variable: (None)
Autofiltering folders: 0 (0 active, 0 inactive)
Last new mail count: 1

One last note: This issue doesn't seem to be causing any particular problems that I can tell. It is just annoying to have those extra lines in the directory structure.

Thanks,

Freddy

The old machine ran XP and the new one is Windows 7. The hard drive crashed on the old one, so I don't have access to it. A friend was able to salvage just the PMAIL files, so I was able to access those to get the info. Both the old computer and new one are single user machines. I don't remember which version of Pegasus I was using before the crash. Following is the information you asked me to copy in.&nbsp;Pegasus Mail for Microsoft Windows Copyright (C) 1992-2010, David Harris, all rights reserved Electronic mail to support@pmail.gen.nz. WinPMail version: Version 4.52 (Win32), Jan 13 2010 Language resources: Standard UK English resource set Extension Manager version: 1.13 Operating mode: Standalone User name and ID: Admin, 0 Windows version: 6.1 Windows flag word: 0 WINPMAIL.EXE directory: C:\PMAIL\Programs Home mailbox location: C:\PMAIL\MAIL\Admin New mailbox location: C:\PMAIL\MAIL\Admin TMP environment variable: C:\Users\Freddy\AppData\Local\Temp TEMP environment variable: C:\Users\Freddy\AppData\Local\Temp LAN-based SMTP support: N, N, N NetWare MHS support: N, N, N Built-in TCP/IP support: Enabled &nbsp; - WINSOCK version: WinSock 2.0 &nbsp; - WINSOCK path: C:\Windows\system32\WSOCK32.DLL Commandline: -roam -A Active -Z options: 32768 PMR variable: (None) PML variable: (None) MAI variable: (None) NB variable: (None) Autofiltering folders: 0 (0 active, 0 inactive) Last new mail count: 1 &nbsp; One last note: This issue doesn't seem to be causing any particular problems that I can tell. It is just annoying to have those extra lines in the directory structure.&nbsp;Thanks,Freddy &nbsp;

Related Topics

Pending draft

Confirm move posts

Insufficient permissions

Select a different topic

Edit history