0000399: XP version recognition incorrect

Notes
(0000685) vcc (reporter) 2007-09-25 17:13	Appears I made a mistake when creating this bug report (a bug in the bug report :) ) It is not the Base Finisher. Just the Base. I should have selected Base Misc.

(0000686) vcc (reporter) 2007-10-04 11:48 edited on: 2007-10-04 11:53	I'm wondering about ruudboek and the bug report being assigned to this account. Seems ruudboek hasn't had any real activity in the system since last year. I guess my report has gone into the black hole. - Hey, I also want to say that I realize Sneaky is probably really busy. I want to pass on my appreciation for all the work done with the DriverPacks. This is one of THE BEST projects out. A huge thanks goes to all who make the Driverpacks what they are. -

(0000693) BashratTheSneaky (administrator) 2007-10-11 17:43	That's why it was assigned to ruudboek, he agreed to maintain the Finisher but hasn't been doing that really... The version detection code is provided by Siginet and he told me this was an edge case so didn't really feel like solving it. You have a very, very special copy of XP somehow ;) I'm not willing to solve this extremely minor problem, the XP detection code is super ugly ;) (and not even written by me, as I just mentioned).

(0000702) vcc (reporter) 2007-10-11 23:07 edited on: 2007-10-31 10:23	Yeah, I thought Siginet did the version detection, I remember him telling me that. - I know, it's not an important thing. I just wasn't naming my directories very well, so didn't know what version was in a directory. But the one I do know is Win XP Pro w/SP2 Corporate Ed. and it shows as Home ver. The weird thing is that the version detection works fine in the integrator and Powerpacker. But I know Siginet has been pretty busy lately with coding. Just something I thought I'd mention, a bug to be fixed in the future sometime.

(0000774) OverFlow (administrator) 2008-05-22 00:05	fixing this would require one of the coders to have a rare copy of the OS most corporate disks are detected correctly. Since none of us has the damaged disk to test with it will not be feasable to reproduce and therefore not feasable to update the detection code. Since this issue has not been reported by anyone else in almost a year i would tend to agree with everyone else that this issue is an isolated one. (it only affects one user, to our knowledge of course.) I am going to close this issue unless it is reported again by someone else

Issue History
Date Modified	Username	Field	Change
2007-09-25 14:30	vcc	New Issue
2007-09-25 14:30	vcc	Status	new => assigned
2007-09-25 14:30	vcc	Assigned To	=> ruudboek
2007-09-25 14:30	vcc	Destination OS Platform	=> wnt5_x86-32 (Windows XP)
2007-09-25 14:30	vcc	Installation Platform	=> disc (CD/DVD)
2007-09-25 14:30	vcc	DriverPacks	=> not applicable
2007-09-25 14:30	vcc	DriverPacks Method	=> not applicable
2007-09-25 14:30	vcc	DriverPacks Finisher Method	=> not applicable
2007-09-25 17:13	vcc	Note Added: 0000685
2007-10-04 11:48	vcc	Note Added: 0000686
2007-10-04 11:53	vcc	Note Edited: 0000686
2007-10-11 17:41	BashratTheSneaky	Assigned To	ruudboek => Siginet
2007-10-11 17:41	BashratTheSneaky	Category	DPs Finisher => DPs BASE misc.
2007-10-11 17:41	BashratTheSneaky	Summary	Actually version 7.05.2 - XP versioning => XP version recognition incorrect
2007-10-11 17:43	BashratTheSneaky	Note Added: 0000693
2007-10-11 17:43	BashratTheSneaky	Assigned To	Siginet => BashratTheSneaky
2007-10-11 17:43	BashratTheSneaky	Assigned To	BashratTheSneaky => Siginet
2007-10-11 17:43	BashratTheSneaky	Status	assigned => acknowledged
2007-10-11 17:44	BashratTheSneaky	Priority	normal => none
2007-10-11 17:44	BashratTheSneaky	Resolution	open => suspended
2007-10-11 23:07	vcc	Note Added: 0000702
2007-10-31 10:23	vcc	Note Edited: 0000702
2008-05-22 00:05	OverFlow	Note Added: 0000774
2008-05-22 00:14	OverFlow	Status	acknowledged => closed

Relationships