(04-04-2014, 02:45 AM)Scarlet.Crush Wrote: [ -> ]Can you enable the service to start automatically, reboot, when everything has finally started, stop the service, copy ScpService.log to ScpService_1.log.
Start the service manually, wait 10 seconds, copy ScpService.log to ScpService_2.log
Zip up ScpService_1.log and ScpService_2.log and post as an attachment.
Done; attached. I should note I took the liberty of upgrading to 1.2.2.175 before I began any of this. This should catch your attention, taken from ScpService_1.log:
Code:
2014-04-03 23:21:29.312 ++ C:\Program Files\Scarlet.Crush Productions\ScpService.exe 1.2.2.175
2014-04-03 23:21:29.328 ++ C:\Program Files\Scarlet.Crush Productions\ScpControl.dll 1.2.2.175
2014-04-03 23:22:29.390 ++
2014-04-03 23:22:29.390 -- Bus Open : Offset 0
2014-04-03 23:22:29.390 -- Bus Open : Path \\?\ROOT#SYSTEM#0003#{F679F562-3164-42CE-A4DB-E7DDBE723909}
2014-04-03 23:22:29.453 ## Mapper.Initialize() - Profiles [5] Active [Default] Mappings [0]
I see no OS identification string (maybe that's helpful to you?), but you can clearly see an almost-exact 60 second duration. I estimated 15-30, but turns out its a lot longer. This seems to correlate with your below concern, re: if I see long delays between the 2nd and 3rd lines...
Now from ScpService_2.log:
Code:
2014-04-03 23:23:36.328 ++ C:\Program Files\Scarlet.Crush Productions\ScpService.exe 1.2.2.175
2014-04-03 23:23:36.343 ++ C:\Program Files\Scarlet.Crush Productions\ScpControl.dll 1.2.2.175
2014-04-03 23:23:36.390 ++ Microsoft Windows XP Professional Service Pack 3 (5.1.2600.196608 x86)
2014-04-03 23:23:36.390 -- Bus Open : Offset 0
2014-04-03 23:23:36.406 -- Bus Open : Path \\?\ROOT#SYSTEM#0003#{F679F562-3164-42CE-A4DB-E7DDBE723909}
2014-04-03 23:23:36.421 ## Mapper.Initialize() - Profiles [5] Active [Default] Mappings [0]
Happens nice and fast, as I'd expect. Likewise, the OS identification string is there. So it sounds like WMI isn't available immediately upon logging in, at least on XP. I have no idea how to debug this, but this is the only service behaving this way. :/
Scarlet.Crush Wrote:Check your Windows Event Log for any error / informational messages regarding WMI. I suspect that it may be having some issue when initially loading.
This was one of the first things I did, actually. My apologies for not disclosing that up front. I've gone through the Event Log (it's a lot less verbose in XP as I'm sure you know), under Application, Security, and System, but there's absolutely no indication of any errors or warnings or anything -- just purely informational messages about services starting up. There's nothing about WMI/Windows Management Instrumentation mentioned.
Scarlet.Crush Wrote:I've attached a version of ScpControl.dll with the OS Version Info call commented out, if you are seeing long delays between the 2nd & 3rd lines of the log try it out.
I'll give this a try and report back in a follow-up post.
Scarlet.Crush Wrote:Edit: There is no difference between XP, Vista, 7, 8, 8.1 with how the drivers/service are installed and operate. The ScpDriver.exe installer only registers that it has selected a configuration as a legacy from when it installed an OS specific filter driver.
Ah okay, I made the assumption that on Windows Vista and above you had the service set to "Automatic (delayed)". Apologies for assuming that.