MantisBT - DriverPacks BASE
View Issue Details
0000399DriverPacks BASEDPs BASE misc.public2007-09-25 14:302008-05-22 00:15
vcc 
Siginet 
noneminoralways
closedsuspended 
7.04 
 
wnt5_x86-32 (Windows XP)
disc (CD/DVD)
not applicable
not applicable
not applicable
0000399: XP version recognition incorrect
Forgive me if this has been adressed verbally in some way as not something you wish to work on. I was just suprised to find this is still an issue as I have not been in touch for some time and I am eager to start testing again since I have some new machines to test the Driverpacks on.
When selecting my Corporate version of XP SP2 it tells me it is the Retail version. Neither RyanVM Integrator nor Powerpacker notices it as such, they are correct in finding it is the Corporate version.
No tags attached.
Issue History
2007-09-25 14:30vccNew Issue
2007-09-25 14:30vccStatusnew => assigned
2007-09-25 14:30vccAssigned To => ruudboek
2007-09-25 14:30vccDestination OS Platform => wnt5_x86-32 (Windows XP)
2007-09-25 14:30vccInstallation Platform => disc (CD/DVD)
2007-09-25 14:30vccDriverPacks => not applicable
2007-09-25 14:30vccDriverPacks Method => not applicable
2007-09-25 14:30vccDriverPacks Finisher Method => not applicable
2007-09-25 17:13vccNote Added: 0000685
2007-10-04 11:48vccNote Added: 0000686
2007-10-04 11:53vccNote Edited: 0000686
2007-10-11 17:41BashratTheSneakyAssigned Toruudboek => Siginet
2007-10-11 17:41BashratTheSneakyCategoryDPs Finisher => DPs BASE misc.
2007-10-11 17:41BashratTheSneakySummaryActually version 7.05.2 - XP versioning => XP version recognition incorrect
2007-10-11 17:43BashratTheSneakyNote Added: 0000693
2007-10-11 17:43BashratTheSneakyAssigned ToSiginet => BashratTheSneaky
2007-10-11 17:43BashratTheSneakyAssigned ToBashratTheSneaky => Siginet
2007-10-11 17:43BashratTheSneakyStatusassigned => acknowledged
2007-10-11 17:44BashratTheSneakyPrioritynormal => none
2007-10-11 17:44BashratTheSneakyResolutionopen => suspended
2007-10-11 23:07vccNote Added: 0000702
2007-10-31 10:23vccNote Edited: 0000702
2008-05-22 00:05OverFlowNote Added: 0000774
2008-05-22 00:14OverFlowStatusacknowledged => closed

Notes
(0000685)
vcc   
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   
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   
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   
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   
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