MantisBT - DriverPacks BASE
View Issue Details
0000110DriverPacks BASEDPs Finisherpublic2006-07-31 14:122006-08-01 08:04
RogueSpear 
BashratTheSneaky 
normalmajoralways
closedno change required 
6.07 rc2 
 
wnt5_x86-32 (applies to all OSes of this platform)
not applicable
not applicable
not applicable
RunOnceEx
0000110: Custom RunOnceEx ID is ignored.
I manually corrected the issue of too many quotes in cmdlines.txt and entered a custom ID of 80, but the default value was used anyway.
No tags attached.
Issue History
2006-07-31 14:12RogueSpearNew Issue
2006-07-31 14:12RogueSpearStatusnew => assigned
2006-07-31 14:12RogueSpearAssigned To => BashratTheSneaky
2006-07-31 14:12RogueSpearDestination OS Platform => not applicable
2006-07-31 14:12RogueSpearInstallation Platform => not applicable
2006-07-31 14:12RogueSpearDriverPacks => not applicable
2006-07-31 14:12RogueSpearDriverPacks Method => not applicable
2006-07-31 14:12RogueSpearDriverPacks Finisher Method => RunOnceEx
2006-08-01 00:54BashratTheSneakyDestination OS Platformnot applicable => wnt5_x86-32 (applies to all OSes of this platform)
2006-08-01 00:54BashratTheSneakyNote Added: 0000277
2006-08-01 00:54BashratTheSneakyStatusassigned => feedback
2006-08-01 07:57RogueSpearNote Added: 0000278
2006-08-01 08:04BashratTheSneakyStatusfeedback => closed
2006-08-01 08:04BashratTheSneakyNote Added: 0000279
2006-08-01 08:04BashratTheSneakyResolutionopen => no change required

Notes
(0000277)
BashratTheSneaky   
2006-08-01 00:54   
If you execute the following command:

ROE.exe 80

And then check in HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnceEx, you should find the key 80. Tried here and it always works...
(0000278)
RogueSpear   
2006-08-01 07:57   
I think I found the issue. The remainder of my RunOnceEx entries were entered in a series as such: 030, 040, 050, and so on. In BASE I entered a custom ID of 80. I think if I had entered in a custom ID of 080 it would have worked. The leading zero (0) always took precedence over the eight (8).
(0000279)
BashratTheSneaky   
2006-08-01 08:04   
Aha, so it wasn't a bug after all :)

No problem :)

Issue closed.