0000041: WINNT.SIF: MsDosInitiated double entries

Notes
(0000140) Denney (reporter) 2006-05-28 20:22 edited on: 2006-05-28 20:23	Already fixed in bug 36.

(0000141) razormoon (reporter) 2006-05-29 01:08 edited on: 2006-05-29 01:15	Uh. no. It's not fixed. What I mean is that the first bug, as found, was 1) dpbase base slipstreaming and then a second slipstream (on top of previous) was adding a second entry. 2) If there was an existing entry (such as a manual entry) 3) nlite entry of MsDosInitiated=0 or No or "No" (again, such as my manual entry). Point is, dpbase is now supposed to remove any existing entry of MsDosInitiated regardless of value.

(0000142) Denney (reporter) 2006-05-29 02:38	Hm... well, with 6.05 final, I cannot reproduce this issue.

(0000143) razormoon (reporter) 2006-05-29 11:29	Hmmm... Ok. Here's excerpt pre slipstream. (It's nlited already) ; Generated by nLite 1.0 RC7 [Data] Autopartition = 0 MsDosInitiated = 0 UnattendedInstall = "Yes"

(0000144) razormoon (reporter) 2006-05-29 11:48 edited on: 2006-05-29 11:51	After dpbase: ; Generated by nLite 1.0 RC7 [Data] Autopartition = 0 MsDosInitiated = 0 UnattendedInstall = "Yes" MsDosInitiated= No M2, CUSTOM, NO KTD

(0000145) BashratTheSneaky (administrator) 2006-05-29 12:52	It will now remove ANY line that contains the string "msdosinitiated" (case insensitive).

Relationships