Bug 2567 – ActivePerl path error on virgin xp machine at install time

Bug 2567 - ActivePerl path error on virgin xp machine at install time

Summary:

ActivePerl path error on virgin xp machine at install time

Status:	CLOSED FIXED

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Windows Installer
Version:	6.2.1
Platform:	PC Windows XP

Importance:	P2 major (vote)
Target Milestone:	---
Assigned To:	Wallace Lai

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2005-11-15 13:30 UTC by Blackketter Dean
Modified:	2008-12-18 11:12 UTC (History)
CC List:	2 users (show)

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Blackketter Dean 2005-11-15 13:30:29 UTC

Customer reported:

SlimServer installation on XP SP2 always gives an error (roughly: ActivePerl not in path) the first time you execute it on a virgin XP machine, but seems to work anyway. Second time and subsequent times through the error does not appear. Duplicated this on two different XP systems.

Comment 1 Nicholas Harvey 2005-11-17 10:19:56 UTC

(In reply to comment #0)
> Customer reported:
> 
> SlimServer installation on XP SP2 always gives an error (roughly: ActivePerl
> not in path) the first time you execute it on a virgin XP machine, but seems to
> work anyway. Second time and subsequent times through the error does not
> appear. Duplicated this on two different XP systems.
> 
I can concurr having also seen exactly this problem when installing SlimServer 6.2 on a Windows XP Home SP2 installation.

Comment 2 will 2006-04-11 11:08:20 UTC

(In reply to comment #0)
> Customer reported:
> SlimServer installation on XP SP2 always gives an error (roughly: ActivePerl
> not in path) the first time you execute it on a virgin XP machine, but seems to
> work anyway. Second time and subsequent times through the error does not
> appear. Duplicated this on two different XP systems.

Yet another XP Pro SP2 installation uncovered this bug.  It's on an IBM T42p that's chock full of stuff.

Comment 3 Blackketter Dean 2006-04-11 11:35:07 UTC

chris:  can you reproduce in your vmware setup?

Comment 4 Chris Owens 2006-04-11 14:18:58 UTC

I cannot easily reproduce it.  I have tried on two different xp images with no other software installed, and with a fair selection of other stuff installed.

That said, I have seen it before, (on my home machine before I even started!) so I'll talk to Kevin and see if I can pin down what specs would be more likely to repro it.

Comment 5 Blackketter Dean 2006-08-16 14:55:41 UTC

ActiveState is aware and is looking at this, according to Jan.

Comment 6 Chris Owens 2006-08-16 17:17:38 UTC

Changed severity due to feedback from support team.

Comment 7 Dan Sully 2006-09-02 16:49:18 UTC

Ok, since this isn't really going to be fixed for 6.5 (and is out of our hands), I'm moving it.

Comment 8 Chris Owens 2007-10-15 09:22:47 UTC

Wallace, would your automation fail if this error happens?  Have you ever seen it?  Could you try installing manually several times on clean images and see if you can reproduce this?

Comment 9 Blackketter Dean 2007-11-25 11:27:06 UTC

Wallce/Dan: Is this still an issue with 7.0?

Comment 10 Dan Evans 2007-11-26 11:44:07 UTC

Support has not gotten any report of this in recent history.

Comment 11 Michael Herger 2007-11-29 13:46:46 UTC

Consider this gone.

Comment 12 Wallace Lai 2008-01-17 17:32:04 UTC

Verified the fix with SqueezeCenter Version: 7.0 - 16286 on Windows XP - EN - cp1252.
Bug as written is not seen.  Marking as "VERIFIED".

Comment 13 Wallace Lai 2008-01-17 17:32:40 UTC

Regression tests did not find any bug casued by this fix.  Closing.