We just recently had a customer report an issue with using a Vista machine
sharing DBISAM tables with another Vista machine, and have found out that
there is a problem with using a Vista machine as a host for sharing DBISAM
or ElevateDB tables with other Vista machines due to a bug in the SMB2
protocol in the Vista OS.

For now, we recommend that you do *not* deploy any applications in such an
environment until MS comes up with an official fix.   The indications are
that a fix will be available with the first Vista service pack.  There is an
official hotfix available, but you have to call MS to get it and it isn't
publicly available.

You can find information on the problem here:

http://forums.microsoft.com/msdn/showpost.aspx?postid=1259708&siteid=1&sb=0&d=1&at=7&ft=11&tf=0&pageid=0

The problem only occurs with a Vista <--> Vista setup that can use SMB2.
With any other combination of OS's, such as XP <--> Vista  or Vista <-->
2000, the problem doesn't occur because one of the participating OS's can
only use the SMB file-sharing protocol, not the SMB2 file-sharing protocol.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


Wow! How did that escape into the wild?

Roy Lambert

Roy,

<< Wow! How did that escape into the wild? >>

Well, I suspect that the SMB locking is very much like database locking.
It's very difficult to test *every* situation, so you have to make sure that
the architecture and logic is completely sound or else you'll get a bug like
this.  The SMB protocol has been notoriously a problem for MS in early
revisions.  They had problems in '95 and '98, and also with 2000.

--
Tim Young
Elevate Software
www.elevatesoft.com

> Well, I suspect that the SMB locking is very much like database locking.
> It's very difficult to test *every* situation, so you have to make sure
> that the architecture and logic is completely sound or else you'll get a
> bug like this.  The SMB protocol has been notoriously a problem for MS in
> early revisions.  They had problems in '95 and '98, and also with 2000.

So... now that they finally get SMB right in Windows XP, they ditch it for
SMB2 / vista, where we have to go through another 3 releases of Windows
before they get it right again?  

Adam,

<< So... now that they finally get SMB right in Windows XP, they ditch it
for SMB2 / vista, where we have to go through another 3 releases of Windows
before they get it right again?   >>

Something like that.

--
Tim Young
Elevate Software
www.elevatesoft.com

I wonder if this has been resolved already. Just tried DBISam on 2 Vista machines and it appears to work fine. Both are clean installs of Vista and not an upgrade from XP. Placed the
database folder in the ..Users\Public\.. folder and shared it out. Tried opening the same table and same record on both PC's at the same time and the locking appears to work fine.

regards
gregory

Gregory,

<< I wonder if this has been resolved already. Just tried DBISam on 2 Vista
machines and it appears to work fine. Both are clean installs of Vista and
not an upgrade from XP. Placed the database folder in the ..Users\Public\..
folder and shared it out. Tried opening the same table and same record on
both PC's at the same time and the locking appears to work fine. >>

It's possible.  Are your copies of Vista particularly new ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:

<<It's possible.  Are your copies of Vista particularly new ?>>

1st one was Vista Home Premium purhased around Feb to Mar 07 and installed on a clean harddisk. 2nd one was Vista Ultimate purchased just last week with new hardware. Both are
connected to the internet so they are getting all the latest windows updates. Im using most of the default windows setting on both PC's. I tested on DBISam V3.3 with lpOptimistic locking
enabled.

regards
gregory