Is anyone aware of any compatibility issues between VFP6 and Windows 2003?

Does anyone know if they fixed the:

http://support.microsoft.com/default.aspx?scid=kb;en-us;299603

problem they said was "too big to fix" before they edited their "Q"

--
Thank you,
Louis Sorbera

RE: Windows 2003 issues by Leemi

Leemi
Wed Aug 06 14:39:50 CDT 2003

Hi Louis:

This is two separate questions, right?

I know of no problem with VFP 6.0 and Windows 2003 Server.

Your second question about the "Error reading file" Error Message on
Windows 2000 Terminal Services can normally be fixed by following the steps
in this article:

818528 Problems When More Than One User Accesses the Same File Through
Terminal
http://support.microsoft.com/?id=818528

You need to contact Windows product (not VFP product support) to get this
hot fix. Basically, you do the following:

1. Install the hot fix on the Windows 2000 TS Server.
2. Make the registry change on the Windows 2000 TS Server.
3. Reboot the server.

I have seen this fix the problem with the "Error reading file" problem with
VFP on Windows Terminal Services in all the cases where the fix has been
employed.

I hope this helps.

This posting is provided "AS IS" with no warranties, and confers no rights.

Sincerely,
Microsoft FoxPro Technical Support
Lee Mitchell

*-- VFP8 HAS ARRIVED!! --*
Read about all the new features of VFP8 here:
http://www.universalthread.com/VisualFoxPro/News/VFP8Release.asp
Purchase VFP8 here:
http://shop.microsoft.com/Referral/Productinfo.asp?siteID=11518

Keep an eye on the product lifecycle for Visual FoxPro here:
http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodv
- VFP5 Mainstream Support retires June 30th, 2003
- VFP6 Mainstream Support retires Sept. 30th, 2003


>Is anyone aware of any compatibility issues between VFP6 and Windows 2003?
>
>Does anyone know if they fixed the:

>http://support.microsoft.com/default.aspx?scid=kb;en-us;299603

>problem they said was "too big to fix" before they edited their "Q"

>--
>Thank you,
>Louis Sorbera


Re: Windows 2003 issues by Louis

Louis
Sat Aug 09 21:44:57 CDT 2003

And what about this,

http://support.microsoft.com/default.aspx?scid=kb;EN-US;294816

to which Microsoft says:
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products
that are listed at the beginning of this article.
This was determined to be too large of an architectural change to implement
as a hot fix for Windows 2000. There is currently no hot fix available.

And this:
http://support.microsoft.com/default.aspx?scid=kb;en-us;299603

We are instructed to:
Locate the OpLocksDisabled value under the following key in the registry:
HKEY_LOCAL_MACHINE\System\CCS\Services\Mrxsmb\Parameters

It doesn't exist on 2000. Does it on 2003. Should it be added if not?

Finally, I'd be happy to post these on the appropriate newsgroup, but I
can't find one. When will there be a newsgroup for Windows 2003, or is it
labeled differently?

--
Thank you,
Louis Sorbera


"Lee Mitchell" <Leemi@microsoft.com> wrote in message
news:mGP1CKFXDHA.1308@cpmsftngxa06.phx.gbl...
> Hi Louis:
>
> This is two separate questions, right?
>
> I know of no problem with VFP 6.0 and Windows 2003 Server.
>
> Your second question about the "Error reading file" Error Message on
> Windows 2000 Terminal Services can normally be fixed by following the
steps
> in this article:
>
> 818528 Problems When More Than One User Accesses the Same File Through
> Terminal
> http://support.microsoft.com/?id=818528
>
> You need to contact Windows product (not VFP product support) to get this
> hot fix. Basically, you do the following:
>
> 1. Install the hot fix on the Windows 2000 TS Server.
> 2. Make the registry change on the Windows 2000 TS Server.
> 3. Reboot the server.
>
> I have seen this fix the problem with the "Error reading file" problem
with
> VFP on Windows Terminal Services in all the cases where the fix has been
> employed.
>
> I hope this helps.
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> Sincerely,
> Microsoft FoxPro Technical Support
> Lee Mitchell
>
> *-- VFP8 HAS ARRIVED!! --*
> Read about all the new features of VFP8 here:
> http://www.universalthread.com/VisualFoxPro/News/VFP8Release.asp
> Purchase VFP8 here:
> http://shop.microsoft.com/Referral/Productinfo.asp?siteID=11518
>
> Keep an eye on the product lifecycle for Visual FoxPro here:
> http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodv
> - VFP5 Mainstream Support retires June 30th, 2003
> - VFP6 Mainstream Support retires Sept. 30th, 2003
>
>
> >Is anyone aware of any compatibility issues between VFP6 and Windows
2003?
> >
> >Does anyone know if they fixed the:
>
> >http://support.microsoft.com/default.aspx?scid=kb;en-us;299603
>
> >problem they said was "too big to fix" before they edited their "Q"
>
> >--
> >Thank you,
> >Louis Sorbera
>



Re: Windows 2003 issues by Vera

Vera
Sun Aug 10 04:13:26 CDT 2003

"Louis Sorbera" <louis_sorbera@msn.com> wrote in
news:u#YXlluXDHA.212@TK2MSFTNGP12.phx.gbl:

> And this:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;299603
>
> We are instructed to:
> Locate the OpLocksDisabled value under the following key in the
> registry:
> HKEY_LOCAL_MACHINE\System\CCS\Services\Mrxsmb\Parameters
>
> It doesn't exist on 2000. Does it on 2003. Should it be added if
> not?

Have a look at:
296264 - Configuring Opportunistic Locking in Windows
http://support.microsoft.com/default.aspx?scid=kb;en-us;296264

it lists the location of the OpLock parameter for W2K, 2003 and
XP.

Note: in many cases, the *absense* of a parameter in the registry
means that it currently has the default value.
Some parameters are "auto-tuned", i.e. the OS calculates them at
boot time. Such parameters are not found in the registry. When you
add such a parameter to the registry and give it a value, the
parameter becomes "fixed" and can no longer be auto-tuned by the
OS.
I don't think that this is the case with the OpLock parameter, I
just wanted to give a more general explanation why parameters
sometimes are missing from the registry.
For an example of an auto-tuned parameter, check:

128167 - Server Service Configuration and Tuning at
http://support.microsoft.com/default.aspx?scid=kb;en-us;128167

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---