XPHome Update woes...

Here's a good one -

I noticed my XPHome machine (at home) had some sizable
windows updates. Wellllll....we are getting calls from our
clients that are running XPHome - our software just flashes
then quits when they click the icon. Only happens on XPHome
after the update. Re-registering our DLL's does not help.
At this point it seems to be only when the program is installed
on a network drive.

Thankyou Microsoft.

--
kpg A+ MCP MCNGP 0x22
If only you and dead people could read hex
how many people can read hex?

kpg
Mon Feb 14 12:51:08 CST 2005

> I noticed my XPHome machine (at home) had some sizable
> windows updates. Wellllll....we are getting calls from our
> clients that are running XPHome - our software just flashes
> then quits when they click the icon. Only happens on XPHome
> after the update. Re-registering our DLL's does not help.
> At this point it seems to be only when the program is installed
> on a network drive.

UPDATE:

XP Home or Pro, same problem.

Get the message:

This applications has failed to start because the application
configuration is incorrect. Reinstalling application may fix the
problem.

(it does not)

If I copy the network folder to the local drive, then change our ini
file to read the data off the network drive it works! So the XP machine
can read the network just fine, but it can't run our exe.

This user has a 98 machine also, it works fine (same network!).

The only time I've seen this is with a .net assembly (which we are not)
where the .net security settings need to be set to allow intranet access.

But it gets better...another user with the same problem has two identical
XP Home workstations - one works one does not.

The servers of the workstations with the problem range from Win95, Win98
to XP Pro. (Q:who would use Win95 as a server? A: My customers!)

kp "I'm getting pi$$ed" g

CrushesBeforeItCuts
Mon Feb 14 13:04:15 CST 2005

(Q:who would use Win95 as a server? A: My
> customers!)
> kp "I'm getting pi$$ed" g

ROFL. sorry man. I feel your pain. I wish I had an answer for you but I
don't. Maybe one of the smart people in the group will.
--
aka
Doom MCNGP #38
"What do you mean I don't support the system?
I go to court when I have to"

fygar
Mon Feb 14 13:12:58 CST 2005

On Mon, 14 Feb 2005 12:51:08 -0600, "kpg" <ipost@thereforeiam.com>
wrote:


Do you have the execute permission on the remote folder turned on?




...butch()

kpg
Mon Feb 14 13:22:02 CST 2005

"CrushesBeforeItCuts" <doom_mcngp38@nospam.com> wrote in message
news:_c2dnerLtPSya43fRVn-1g@prairiewave.com...
>#(2/14/2005 1:13:44 PM) #
> (Q:who would use Win95 as a server? A: My
>> customers!)
>> kp "I'm getting pi$$ed" g
>
> ROFL. sorry man. I feel your pain. I wish I had an answer for you but I
> don't. Maybe one of the smart people in the group will.

Well that was helpful. :-)

I'm getting closer - we use XP styles in our program...not the external
kind but one compiled into the exe as a resource. If there is a problem'
with the manifest file (which is written in XML) this error will occur.

The fact that it only happens on the network drive tells me that is
indeed a .NET permission thing. Problem is I set adjusted the .NET
security for the intranet zone to no trust on my test machine (which was
not having the problem BTW) and every thing still works great.

So I think that the .NET framework 1.1 update that was part of the
windows updates for XP messed up the XML security rights for the
intranet zone on some XP machines - but at this point I don't know how
to fix it - short of removing the manifest file form our software (but then
xp users get those ugly win98 style controls).

Well, CBIC, you keep working on it...

kp "hey Fris, little help here?..." g

kpg
Mon Feb 14 13:24:08 CST 2005

"fygar" <cpudoc10@hotmail.com> wrote in message
news:fvt111d2d4g7tvilgvc3ptkc3i2djhkd43@4ax.com...
>#(2/14/2005 1:22:14 PM) #
> On Mon, 14 Feb 2005 12:51:08 -0600, "kpg" <ipost@thereforeiam.com>
> wrote:
>
>
> Do you have the execute permission on the remote folder turned on?
>
>

My first thoughts...but the server is WIN95, so I am assuming FAT32
Workgroup. No NTFS or AD permissions to mess with.

kp "things were simpler back then" g

billLASTINIT
Mon Feb 14 13:48:35 CST 2005

kpg wrote:
>
> kp "hey Fris, little help here?..." g

Sorry, dude. I have zero experience in .Net

We're using VB Classic.

For what it's worth, the only difference between running an app local and
over the network is permissions, period. You have to be on the right track.
If I were you, I'd google groups (not just plain google) with keywords
pertaining to the specific update you installed to see if anyone else has
experienced the same problem.

--
Fris ".Nyet" bee®, MCNGP #13

The MCNGP Team - We're here to help!
http://www.mcngp.com

Certaholics
http://groups.yahoo.com/group/certaholics

kpg
Mon Feb 14 14:14:54 CST 2005

"Frisbee®" <billLASTINIT@dasi-software.com> wrote in message
news:uOxTt4sEFHA.2828@TK2MSFTNGP09.phx.gbl...
># (2/14/2005 2:11:06 PM) #
> kpg wrote:
>>
>> kp "hey Fris, little help here?..." g
>
> Sorry, dude. I have zero experience in .Net
>
> We're using VB Classic.
>

Yeah, us too. VB6. I use the manifest 'trick' to get XP styles
out of VB6 controls. I knew this would come back to bite me.

The only .NET stuff we do is for web applications which are just
for customer support and the like. .NET is VERY nice, though, I
like it.