TalAloni

Sorry for being late to the party, The OP is right to suggest that the THG's fix should have been cleaner. take dmio.sys for example: in the original file: ProductType is first checked against 'WINNT', if equal, the value 1 is stored for later use. and if not, it is checked against 'SERVERNT', if it is equal, the value 2 is stored for later use. Note: For the fix to work, we want the value of 2 to be stored for later use. After the suggested THG change: ProductType is first checked against 'SERVERNTWINNT' (because we removed the null terminator), if equal, the value 1 is stored for later use. and if not, it is checked against 'WINNT', if it is equal, the value 2 is stored for later use. This works well of course (because our ProductType is 'WINNT', but we could achieve the same result by changing a single byte (storing the value 2 for later use for 'WINNT'), and updating the checksum. For the files with the cleaner approach, visit here: http://iknowu.dnsalias.com/files/public/Windows-RAID/KB827913-WindowsXP.htm

Hi, I've recently had the same problem, and did an extensive research into the issue: short answer: use [Keyboard.Load] long answer: some of the [xxxx.Load] groups including [sCSI.Load] are sticky, which means any service added to them will create its own Services\serviceName key and values which will stick to GUI-mode setup and final Windows (and will run over hivesys.inf entries), the good news is that you don't have to use those groups, setupreg.hiv has precedence when it comes to services initialization order. if the service has no group specified in setupreg.hiv, it will be initialized according to it's load order, which is determined by txtsetup.sif according to the following order: [bootBusExtenders.Load] // sticky! (any entry added to here will create its own Services\serviceName key and values, which will run over hivesys.inf entries) [busExtenders.Load] // sticky! [inputDevicesSupport.Load] // partially sticky!, group name won't be created / ran-over, service "Start" entry will be set to 3! [Keyboard.Load] [sCSI.Load] // sticky! + has it's own unavoidable file copy mechanism. [DiskDrivers.Load] [scsiClass.Load] [FileSystems.Load] [CdRomDrivers.Load] Regards, Tal Aloni