Thank you,

I'll give it a shot..

Ed Sullivan/EPS

Hello,

We're migrating our last Netware (6.5) file server to Windows, and time has come to move our last Pegasus user (me) from Netware Mode to Standalone.  'Problem is, Pegasus is so dependable and it's been so long since I've had to do any real technical support of my own account that I'm not sure the best way to do this.  I started by moving the home mailbox location from the old network drive to my local hard drive, but that leaves the pmail.ini and white and black lists, etc. still on the about-to-be-retired Netware file server (\\BRKFILESEA0V).  I still have the Netware 32bit client on my XP Pro workstation and can (for the time being) flip back and forth from the Netware side to the Windows side - 'tried using pconfig.exe, but of course when I'm logged in as a Netware user I have the correct context but pconfig 'sees' the Netware environment and doesn't offer standalone, and when I'm logged in on the Windows side Pegasus can't find the pmail.ini, etc.   I'd like to migrate the existing setup rather than do a clean install, because I have a number of IMAP and POP profiles set up to pull email from a variety of legacy accounts (AOL, etc.) that still need to be monitored on a regular basis.   

Here's a dump from the About/Info window my Pegasus (v 4.61).   Any advice (including the "just go to {link} and read carefully" kind)  would be most appreciated. 

Thank you,

Ed Sullivan

WinPMail version: Version 4.61 (Win32), Feb  5 2011
Language resources: Standard UK English resource set
Extension Manager version: 1.13
Operating mode: Network
User name and ID: speedy.EPSBERKELEY.EPS, 0
Windows version: 5.1
Windows flag word: 0
WINPMAIL.EXE directory: C:\PMAIL\Programs
Home mailbox location: C:\EMAIL\SPEEDY\PMAIL
New mailbox location: \\BRKFILESEA0V\DATA\users\speedy\PMAIL
TMP environment variable: C:\DOCUME~1\egads\LOCALS~1\Temp
TEMP environment variable: C:\DOCUME~1\egads\LOCALS~1\Temp
LAN-based SMTP support: Y, Y, N
NetWare MHS support: Y, N, N
  - MHS path is L:\
Built-in TCP/IP support: Enabled
  - WINSOCK version: WinSock 2.0
  - WINSOCK path: C:\WINDOWS\system32\WSOCK32.DLL
Commandline: -roam
Active -Z options: 32768
PMR variable: F:\PMAIL
PML variable: F:\PMAIL
MAI variable: (None)
NB variable: L:\MHS\NB
Autofiltering folders: 0 (0 active, 0 inactive)
Last new mail count: 13

NICA module: Novell NetWare NDS Mode
NICA module version: 1.2 release 0, Jul 13 1999
Configuration context: EPSBERKELEY.EPS
Default server version: 5.70 rev 6, 127 user
Connections: Highest, 20; Current, 2
Shell/Requester version: 4.91.4
Mercury spool directory: \\BRKFILESEA0V\SYS\Pmail\queue
New mailbox location algorithm: 0
 

> WINPMAIL.EXE directory: C:\PMAIL\Programs
> Home mailbox location: C:\EMAIL\SPEEDY\PMAIL
> New mailbox location: \\BRKFILESEA0V\DATA\users\speedy\PMAIL

The program pconfig.exe can be run in the standalone mode when the Novell client is loaded using the -s commandline option.  Make sure you are running the program from the C:\PMAIL\Programs directory.  

I'm no too sure Pegasus Mail can handle the home and new mail directory you have specified though.  Pconfig.exe would need to be specified as c:\email\~n\pmail and according to David this is not supported.  I'd set the home mail directory to c:\email\~n and then put the mail in c:\email\speedy.  This means that there needs to be a pmail.usr file in c:\email as well.

Once this is done you can move the \\BRKFILESEA0V\DATA\users\speedy\PMAIL files to the c:\email\speedy directory as well.