Skip to main content

[archive] Windows Vista file sharing

  • September 2, 2008
  • 4 replies
  • 0 views

[Migrated content. Thread originally posted on 02 September 2008]

Anyone had problems with file sharing when using Windows Vista?

Acucobol RTS version 8.00 for WIN-32, two-user license (same problem with Acucobol RTS 5.2.1.
Data file use Vision version 4.

They previously had two PCs with Windows XP.
The programmes and data are in a partition on one of these PCs and the partition is shared and accessed by the other PC.
This worked fine.

Then they bought two new PCs, both with Windows Vista, and the problems began.
If they run on one PC at a time (any one) then it works fine.
When they try to run on both at the same time, as they always did previously under XP, they get unpredictable "hangs".
It looks as if the one locks the data (entire file maybe?... could it be that under Vista it locks the whole file and not just the record?) for the other.

They are too small to install Acuserve.

Any experiences?

4 replies

[Migrated content. Thread originally posted on 02 September 2008]

Anyone had problems with file sharing when using Windows Vista?

Acucobol RTS version 8.00 for WIN-32, two-user license (same problem with Acucobol RTS 5.2.1.
Data file use Vision version 4.

They previously had two PCs with Windows XP.
The programmes and data are in a partition on one of these PCs and the partition is shared and accessed by the other PC.
This worked fine.

Then they bought two new PCs, both with Windows Vista, and the problems began.
If they run on one PC at a time (any one) then it works fine.
When they try to run on both at the same time, as they always did previously under XP, they get unpredictable "hangs".
It looks as if the one locks the data (entire file maybe?... could it be that under Vista it locks the whole file and not just the record?) for the other.

They are too small to install Acuserve.

Any experiences?
Vista uses the new SMB 2 protocol when working with mapped drives to other Vista machines and Windows 2008 servers. This could be playing into the difference in behavior. If that is the protocol being used then there is no way to turn off opportunistic locking. A work-around would be to use a non-Vista machine (an old XP) as the host for the files which would then force Vista to communicate using the old SMB protocol.

[Migrated content. Thread originally posted on 02 September 2008]

Anyone had problems with file sharing when using Windows Vista?

Acucobol RTS version 8.00 for WIN-32, two-user license (same problem with Acucobol RTS 5.2.1.
Data file use Vision version 4.

They previously had two PCs with Windows XP.
The programmes and data are in a partition on one of these PCs and the partition is shared and accessed by the other PC.
This worked fine.

Then they bought two new PCs, both with Windows Vista, and the problems began.
If they run on one PC at a time (any one) then it works fine.
When they try to run on both at the same time, as they always did previously under XP, they get unpredictable "hangs".
It looks as if the one locks the data (entire file maybe?... could it be that under Vista it locks the whole file and not just the record?) for the other.

They are too small to install Acuserve.

Any experiences?
Vista uses the new SMB 2 protocol when working with mapped drives to other Vista machines and Windows 2008 servers. This could be playing into the difference in behavior. If that is the protocol being used then there is no way to turn off opportunistic locking. A work-around would be to use a non-Vista machine (an old XP) as the host for the files which would then force Vista to communicate using the old SMB protocol.

[Migrated content. Thread originally posted on 02 September 2008]

Anyone had problems with file sharing when using Windows Vista?

Acucobol RTS version 8.00 for WIN-32, two-user license (same problem with Acucobol RTS 5.2.1.
Data file use Vision version 4.

They previously had two PCs with Windows XP.
The programmes and data are in a partition on one of these PCs and the partition is shared and accessed by the other PC.
This worked fine.

Then they bought two new PCs, both with Windows Vista, and the problems began.
If they run on one PC at a time (any one) then it works fine.
When they try to run on both at the same time, as they always did previously under XP, they get unpredictable "hangs".
It looks as if the one locks the data (entire file maybe?... could it be that under Vista it locks the whole file and not just the record?) for the other.

They are too small to install Acuserve.

Any experiences?
Vista uses the new SMB 2 protocol when working with mapped drives to other Vista machines and Windows 2008 servers. This could be playing into the difference in behavior. If that is the protocol being used then there is no way to turn off opportunistic locking. A work-around would be to use a non-Vista machine (an old XP) as the host for the files which would then force Vista to communicate using the old SMB protocol.

[Migrated content. Thread originally posted on 02 September 2008]

Anyone had problems with file sharing when using Windows Vista?

Acucobol RTS version 8.00 for WIN-32, two-user license (same problem with Acucobol RTS 5.2.1.
Data file use Vision version 4.

They previously had two PCs with Windows XP.
The programmes and data are in a partition on one of these PCs and the partition is shared and accessed by the other PC.
This worked fine.

Then they bought two new PCs, both with Windows Vista, and the problems began.
If they run on one PC at a time (any one) then it works fine.
When they try to run on both at the same time, as they always did previously under XP, they get unpredictable "hangs".
It looks as if the one locks the data (entire file maybe?... could it be that under Vista it locks the whole file and not just the record?) for the other.

They are too small to install Acuserve.

Any experiences?
It seems that we Acucobol users are not alone.

See this link:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1259708&SiteID=1

Has anyone found any other way to get around this?