FoxPro Setup - Starting exe from XP on W98 machine

Author

Starting exe from XP on W98 machine

Agis

2005-04-07, 8:05 pm

Starting an exe from another machine worked just fine until recently. The
machine starting the exe is a XP machine and the machine serving the exe is a
W98 machine. The problem first appeared when the application that starts the
exe was upgraded from VFP6 to VFP8. This problem can be solved by
uninstalling the security patch KB885250 on the XP machine. I'm worried that
a future SP from XP might include the security patch and therefore break this
again. My questions are:

Why does this only appear since the app was upgraded to VFP8
What has this to do with the security patch
How do I make sure this keeps working with future SP's?

Lee Mitchell

2005-04-07, 8:05 pm

Hi Agis:

What error message do you get when the patch is installed? Since the patch
blocks remote code execution, have you tried running a Filemon log
(www.sysinternals.com) to see what files might be accessed to cause the
problem?

I have not heard of a problem with VFP and this security patch. Do you know
what the application does when it starts?

I hope this helps.

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

Sincerely,
Microsoft FoxPro Technical Support
Lee Mitchell

*-- VFP9 HAS ARRIVED!! --*
Read about all the new features of VFP9 here:
http://msdn.microsoft.com/vfoxpro/

*--Purchase VFP 9.0 here:
http://www.microsoft.com/PRODUCTS/i...cid=54787e64-52
69-4500-8bf2-3f06689f4ab3&type=ovr

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

>Starting an exe from another machine worked just fine until recently. The
>machine starting the exe is a XP machine and the machine serving the exe
is a
>W98 machine. The problem first appeared when the application that starts
the
>exe was upgraded from VFP6 to VFP8. This problem can be solved by
>uninstalling the security patch KB885250 on the XP machine. I'm worried
that
>a future SP from XP might include the security patch and therefore break
this
>again. My questions are:

>Why does this only appear since the app was upgraded to VFP8
>What has this to do with the security patch
>How do I make sure this keeps working with future SP's?

Agis

2005-04-11, 7:26 am

The error states: "this application has failed to start because
the configuration is wrong - reinstalling the application may fix the
problem"

If you search www.universalthread.com for "KB885250", you will find that
others have reported this aswell. It definitly is a problem that occurs in
VFP8 and higher and to my knowledge only when starting an exe on a XP machine
while the exe is hosted on the W98 machine.

"Lee Mitchell" wrote:

> Hi Agis:
>
> What error message do you get when the patch is installed? Since the patch
> blocks remote code execution, have you tried running a Filemon log
> (www.sysinternals.com) to see what files might be accessed to cause the
> problem?
>
> I have not heard of a problem with VFP and this security patch. Do you know
> what the application does when it starts?
>
> I hope this helps.
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> Sincerely,
> Microsoft FoxPro Technical Support
> Lee Mitchell
>
> *-- VFP9 HAS ARRIVED!! --*
> Read about all the new features of VFP9 here:
> http://msdn.microsoft.com/vfoxpro/
>
> *--Purchase VFP 9.0 here:
> http://www.microsoft.com/PRODUCTS/i...cid=54787e64-52
> 69-4500-8bf2-3f06689f4ab3&type=ovr
>
> Keep an eye on the product lifecycle for Visual FoxPro here:
> http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodv
> - VFP5 Mainstream Support retired June 30th, 2003
> - VFP6 Mainstream Support retired Sept. 30th, 2003
>
> is a
> the
> that
> this
>
>
>

Agis

2005-04-12, 7:24 am

The same application compiled in VFP6 still works fine.
The same application works fine without the patch installed.
I haven't tried Filemon, but besides the exe I think only the runtime and
the runtime support files will be opened.

"Lee Mitchell" wrote:

> Hi Agis:
>
> What error message do you get when the patch is installed? Since the patch
> blocks remote code execution, have you tried running a Filemon log
> (www.sysinternals.com) to see what files might be accessed to cause the
> problem?
>
> I have not heard of a problem with VFP and this security patch. Do you know
> what the application does when it starts?
>
> I hope this helps.
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> Sincerely,
> Microsoft FoxPro Technical Support
> Lee Mitchell
>
> *-- VFP9 HAS ARRIVED!! --*
> Read about all the new features of VFP9 here:
> http://msdn.microsoft.com/vfoxpro/
>
> *--Purchase VFP 9.0 here:
> http://www.microsoft.com/PRODUCTS/i...cid=54787e64-52
> 69-4500-8bf2-3f06689f4ab3&type=ovr
>
> Keep an eye on the product lifecycle for Visual FoxPro here:
> http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodv
> - VFP5 Mainstream Support retired June 30th, 2003
> - VFP6 Mainstream Support retired Sept. 30th, 2003
>
> is a
> the
> that
> this
>
>
>

Agis

2005-04-12, 9:24 am

Hi Lee,

I just ran FileMon with and without the patch installed on the XP machine
(same machine on wich I deinstalled the patch). The start of the FileMon log
is exactly the same. If you want the complete logs I can mail them to you if
you give me a e-mail address to mail to. With the patch the last lines in the
log are:

101 15:42:23 KERNEL3
2:FFEFC579 FindOpen
C:\AGIS\NL-NL NOTFOUND
102 15:42:23 KERNEL3
2:FFEFC579 Close C:\
AGIS\AVW. EXE SUCCESS CLOSE_FI
NAL

Up until this point not even the runtime is called upon. Only the AvW.exe is
checked and with it the avw.exe.manifest and avw.exe.config wich are not
found.

Without the patch installed, everything is exactly the same until line 101.
From 102 on things go different and like the way I want it to. The runtime is
loaded and the application starts. Here are line 101 (the same) and some of
the following lines until the runtime is queried:

101 15:42:23 KERNEL3
2:FFEFC579 FindOpen
C:\AGIS\NL-NL NOTFOUND
102 15:42:23 KERNEL3
2:FFEFC579 FindOpen
C:\AGIS\NL NOTFOUND
103 15:42:24 MSGSRV3
2:FFFF8E05 Attribute
s C:\WINDOWS\USER. DAT SUCCESS SetAttri
butes
104 15:42:24 MSGSRV3
2:FFFF8E05 Open C:\W
INDOWS\USER. DAT SUCCESS OPENEXIS
TING
WRITEONLY COMPATIBILITY
105 15:42:24 MSGSRV3
2:FFFF8E05 Write C:\
WINDOWS\USER.DAT SUCCESS Offset: 0
Length: 32
106 15:42:24 MSGSRV3
2:FFFF8E05 Commit C:
\WINDOWS\USER. DAT SUCCESS NOACCESS
UPDATE
107 15:42:24 MSGSRV3
2:FFFF8E05 Seek C:\W
INDOWS\USER. DAT SUCCESS Beginnin
g
Offset: 327712 / New offset: 327712
108 15:42:24 MSGSRV3
2:FFFF8E05 Write C:\
WINDOWS\USER.DAT SUCCESS Offset:
327712 Length: 36864
109 15:42:24 MSGSRV3
2:FFFF8E05 Commit C:
\WINDOWS\USER. DAT SUCCESS NOACCESS
UPDATE
110 15:42:24 MSGSRV3
2:FFFF8E05 Seek C:\W
INDOWS\USER. DAT SUCCESS Beginnin
g
Offset: 0 / New offset: 0
111 15:42:24 MSGSRV3
2:FFFF8E05 Write C:\
WINDOWS\USER.DAT SUCCESS Offset: 0
Length: 32
112 15:42:24 MSGSRV3
2:FFFF8E05 Close C:\
WINDOWS\USER. DAT SUCCESS CLOSE_FI
NAL
113 15:42:24 MSGSRV3
2:FFFF8E05 Attribute
s C:\WINDOWS\USER. DAT SUCCESS SetAttri
butes
114 15:42:24 KERNEL3
2:FFEFC579 Seek C:\A
GIS\AVW. EXE SUCCESS Beginnin
g
Offset: 4096 / New offset: 4096
115 15:42:24 KERNEL3
2:FFEFC579 Read C:\A
GIS\AVW.EXE SUCCESS Offset: 4096
Length: 1536
116 15:42:24 KERNEL3
2:FFEFC579 FindOpen
C:\AGIS\MSVCR70.DLL NOTFOUND
117 15:42:24 KERNEL3
2:FFEFC579 FindOpen
C:\AGIS\AVW.EXE SUCCESS AvW.exe
118 15:42:24 KERNEL3
2:FFEFC579 FindClose
C:\AGIS\AVW.EXE SUCCESS
119 15:42:24 KERNEL3
2:FFEFC579 Open C:\A
GIS\AVW. EXE SUCCESS OPENEXIS
TING
READONLY DENYWRITE
120 15:42:24 KERNEL3
2:FFEFC579 Seek C:\A
GIS\AVW. EXE SUCCESS Beginnin
g
Offset: 33803 / New offset: 33803
121 15:42:24 KERNEL3
2:FFEFC579 Read C:\A
GIS\AVW.EXE SUCCESS Offset: 33803
Length: 4
122 15:42:24 KERNEL3
2:FFEFC579 Seek C:\A
GIS\AVW. EXE SUCCESS Beginnin
g
Offset: 7926 / New offset: 7926
123 15:42:24 KERNEL3
2:FFEFC579 Read C:\A
GIS\AVW.EXE SUCCESS Offset: 7926
Length: 8
124 15:42:24 KERNEL3
2:FFEFC579 Seek C:\A
GIS\AVW. EXE SUCCESS Beginnin
g
Offset: -1 / New offset: -1
125 15:42:24 KERNEL3
2:FFEFC579 Read C:\A
GIS\AVW.EXE SUCCESS Offset: -1
Length: 4
126 15:42:24 KERNEL3
2:FFEFC579 Close C:\
AGIS\AVW. EXE SUCCESS CLOSE_FI
NAL
127 15:42:24 KERNEL3
2:FFEFC579 Seek C:\A
GIS\AVW. EXE SUCCESS Beginnin
g
Offset: 1024 / New offset: 1024
128 15:42:24 KERNEL3
2:FFEFC579 Read C:\A
GIS\AVW.EXE SUCCESS Offset: 1024
Length: 2856
129 15:42:24 KERNEL3
2:FFEFC579 Seek C:\A
GIS\AVW. EXE SUCCESS Beginnin
g
Offset: 3880 / New offset: 3880
130 15:42:24 KERNEL3
2:FFEFC579 Read C:\A
GIS\AVW.EXE SUCCESS Offset: 3880
Length: 216
131 15:42:24 KERNEL3
2:FFEFC579 Seek C:\A
GIS\AVW. EXE SUCCESS Beginnin
g
Offset: 5632 / New offset: 5632
132 15:42:24 KERNEL3
2:FFEFC579 Read C:\A
GIS\AVW.EXE SUCCESS Offset: 5632
Length: 512
133 15:42:24 KERNEL3
2:FFEFC579 FindOpen
C:\AGIS\AVW.EXE SUCCESS AvW.exe
134 15:42:24 KERNEL3
2:FFEFC579 FindClose
C:\AGIS\AVW.EXE SUCCESS
135 15:42:24 KERNEL3
2:FFEFC579 Open C:\A
GIS\AVW. EXE SUCCESS OPENEXIS
TING
READONLY DENYNONE
136 15:42:24 KERNEL3
2:FFEFC579 Attribute
s C:\AGIS\AVW. EXE SUCCESS GetAttri
butes
137 15:42:24 KERNEL3
2:FFEFC579 Attribute
s C:\AGIS\AVW.EXE SUCCESS Get Modify
138 15:42:24 KERNEL3
2:FFEFC579 Seek C:\A
GIS\AVW.EXE SUCCESS End Offset: 0 /
New offset: 0
139 15:42:24 KERNEL3
2:FFEFC579 Seek C:\A
GIS\AVW. EXE SUCCESS Beginnin
g
Offset: 0 / New offset: 0
140 15:42:24 KERNEL3
2:FFEFC579 Read C:\A
GIS\AVW.EXE SUCCESS Offset: 0
Length: 64
141 15:42:24 KERNEL3
2:FFEFC579 Seek C:\A
GIS\AVW. EXE SUCCESS Beginnin
g
Offset: 240 / New offset: 240
142 15:42:24 KERNEL3
2:FFEFC579 Read C:\A
GIS\AVW.EXE SUCCESS Offset: 240
Length: 248
143 15:42:24 KERNEL3
2:FFEFC579 Seek C:\A
GIS\AVW. EXE SUCCESS Beginnin
g
Offset: 33793 / New offset: 33793
144 15:42:24 KERNEL3
2:FFEFC579 Read C:\A
GIS\AVW.EXE SUCCESS Offset: 33793
Length: 14
145 15:42:24 KERNEL3
2:FFEFC579 Seek C:\A
GIS\AVW. EXE SUCCESS Beginnin
g
Offset: 25879 / New offset: 25879
146 15:42:24 KERNEL3
2:FFEFC579 Read C:\A
GIS\AVW.EXE SUCCESS Offset: 25879
Length: 2
147 15:42:24 KERNEL3
2:FFEFC579 Close C:\
AGIS\AVW. EXE SUCCESS CLOSE_FI
NAL
148 15:42:24 KERNEL3
2:FFEFC579 FindOpen
C:\AGIS\VFP8R.DLL NOTFOUND

"Lee Mitchell" wrote:

> Hi Agis:
>
> What error message do you get when the patch is installed? Since the patch
> blocks remote code execution, have you tried running a Filemon log
> (www.sysinternals.com) to see what files might be accessed to cause the
> problem?
>
> I have not heard of a problem with VFP and this security patch. Do you know
> what the application does when it starts?
>
> I hope this helps.
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> Sincerely,
> Microsoft FoxPro Technical Support
> Lee Mitchell
>
> *-- VFP9 HAS ARRIVED!! --*
> Read about all the new features of VFP9 here:
> http://msdn.microsoft.com/vfoxpro/
>
> *--Purchase VFP 9.0 here:
> http://www.microsoft.com/PRODUCTS/i...cid=54787e64-52
> 69-4500-8bf2-3f06689f4ab3&type=ovr
>
> Keep an eye on the product lifecycle for Visual FoxPro here:
> http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodv
> - VFP5 Mainstream Support retired June 30th, 2003
> - VFP6 Mainstream Support retired Sept. 30th, 2003
>
> is a
> the
> that
> this
>
>
>

Sponsored Links