After doing some additional investigation, I decided to try Novell Client 2 SP1 for Windows 7 (IR1) with caching enabled on the client late yesterday. It's still disabled on the server. At the end of the day today, I have not yet found any evidence of database corruption and I haven't seen any issues with Pegasus 4.52 using the latest client.

 Thanks again.

Tony

Since the Novell client is required for Pegasus to work correctly in a Netware environment, and the Novell Client for Windows 7 doesn't work correctly with Pegasus, is it reasonable to assume that Pegasus is not being supported with Netware and Windows 7?

> Since the Novell client is required for Pegasus to work correctly in a Netware environment, and the Novell Client for Windows 7 doesn't work
> correctly with Pegasus, is it reasonable to assume that Pegasus is not being supported with Netware and Windows 7?

It's being used with Netware by some of the testers but there is a problem in the my v3.x server since Win7 no longer supports IPX.  The Novell Client problem is really a Netware problem and not Pegasus Mail though and I expect it will be fixed shortly.  I am going to have a NW v6 server up as soon as I get the time to install the server.

 This problem between Pegasus, Novell Client, and Windows 7 Pro is

causing me some grief with other programs but after using Pegasus on my

Novell network for so long, I'm reluctant to abandon it.

Any progress with getting NW6 setup there?  I'm still having a hard time believing that nobody else has a similar configuration and similar problems.

>  Any progress with getting NW6 setup there?  I'm still having a hard time

believing that nobody else has a similar configuration and similar

problems.

Here's some info from the beta testers Daniel Cates and Tom Ansley.  I can't get NW v6.0 installed so I can test this out.  The NDA means on disclosure agreement. HTH

> On 27 Apr 2010 at 9:47, Daniel Cates <winpmail-beta@pmail.gen.nz>
> wrote:
>
> >
> > From my point of view, go with the latest client, "version 2 SP1" and make  sure file caching is enabled within the client.  This is also a default.
> >
> > With these settings, pegasus mail and netware 6.5 seem fairly stable.  The  interaction between Windows 7 and the latest client seems much better
> > than with the original vista 1.0 client.
> >
> > daniel
> >
> >
> > On 27 Apr 2010 at 17:40, Tom Anstey wrote:
> >
> > > Yes. Bug in Novell client gives problem. The vista 1.0 client works.
> > > T
> > >
[snip]
Be aware that that's fine for most things - however programs such as ConsoleOne (yuk!) want client-side caching disabled under Windows 7, and
BSODs have been reported unless the cache is disabled.

There is a field test fix available from Novell Support it's got a bug number, and also has effects on some financial software packages.

I'm under an NDA, so I can't really say more, but it's a bug in the Novell client, that has been fixed but is due for the next Novell client
SP.  It's both 32 and 64-bit.

I applied the fix to a Vista W/S this morning, and all the automatic copyself and moving messages between folders is now fixed.

Tom

 

Tom,

Thanks for the info.  Unfortunately, enabling caching on the client has caused database corruption in the past even though it is disabled on the server.  So I guess I'm left to limp along a bit longer until Novell decides to release the next update.

 Tony