MantisBT - DriverPacks BASE
View Issue Details
0000434DriverPacks BASEDPs BASE misc.public2008-05-15 12:082008-07-16 21:33
DeTard 
OverFlow 
normalminoralways
resolvedfixed 
7.04 
 
wnt5_x86-32 (Windows XP)
other (not natively supported)
CPU
2
custom
0000434: DevPath not able to scan all paths
(Version 8.05 of DPs Base) Found a problem with trying to scan a path that was inside the Windows directory. Putting the CPU directory in Windows, and running the command DevPath C:\Windows\CPU didn't result in the registry being updated at DevicePath. It being a single directory, I updated DevicePath manually.
No tags attached.
Issue History
2008-05-15 12:08DeTardNew Issue
2008-05-15 12:08DeTardStatusnew => assigned
2008-05-15 12:08DeTardAssigned To => BashratTheSneaky
2008-05-15 12:08DeTardDestination OS Platform => wnt5_x86-32 (Windows XP)
2008-05-15 12:08DeTardInstallation Platform => not applicable
2008-05-15 12:08DeTardDriverPacks => not applicable
2008-05-15 12:08DeTardDriverPacks Method => 2
2008-05-15 12:08DeTardDriverPacks Finisher Method => not applicable
2008-05-21 23:13OverFlowAssigned ToBashratTheSneaky => OverFlow
2008-05-21 23:31OverFlowInstallation Platformnot applicable => other (not natively supported)
2008-05-21 23:31OverFlowDriverPacksnot applicable => CPU
2008-05-21 23:31OverFlowDriverPacks Finisher Methodnot applicable => custom
2008-05-21 23:31OverFlowNote Added: 0000773
2008-05-21 23:31OverFlowStatusassigned => acknowledged
2008-06-02 20:31OverFlowNote Added: 0000777
2008-06-02 20:33OverFlowStatusacknowledged => confirmed
2008-06-16 21:52OverFlowNote Added: 0000780
2008-06-16 21:52OverFlowStatusconfirmed => feedback
2008-06-17 11:17DeTardNote Added: 0000786
2008-06-17 12:26OverFlowNote Added: 0000787
2008-06-17 12:29DeTardNote Added: 0000788
2008-06-17 12:32OverFlowNote Added: 0000789
2008-06-17 12:52DeTardNote Added: 0000790
2008-06-17 17:08OverFlowStatusfeedback => closed
2008-06-17 17:08OverFlowResolutionopen => fixed
2008-07-16 21:33OverFlowStatusclosed => resolved

Notes
(0000773)
OverFlow   
2008-05-21 23:31   
i have been looking for other issues...
I was haveing trouble with the code for bartpe too...
i think the easy fix is to create a subfolder to move them to.
i wrote a routine for the bartpe platform to detect the zero subfolders exist path (like in cpu)

I am certain this is not checked for on the disk platform but i could use the same routine for both modules

Ultimately i belive this to be an error in the packs layout.
although it has been this way since version 6.19 at least, and never reported.

i suggest we take a two fold approach to solve

1 make this pack compliant with the other packs.
  a) create at least one subfolder
  b) a single alphanumeric character name ( IE D\CPU\A\ )

2 harden the base code against such user error;
  a) add folder check code to disk platform module


(0000777)
OverFlow   
2008-06-02 20:31   
the layout of cpu folder was altered in the nightlies for testing
the pack is now compliant with the other packs
(0000780)
OverFlow   
2008-06-16 21:52   
did the test version solve this issue?
(0000786)
DeTard   
2008-06-17 11:17   
Well it works so long as you make the pathing include the D directory. So if I have C:\Windows\D\CPU, yeah it works. If I just tell it to look in C:\Windows\CPU, no it does not. Apparently it's hardcoded to look in a path with D?
(0000787)
OverFlow   
2008-06-17 12:26   
i havent used ktd in a long time

i belive it is supposed to look in c:\windows\driverpacks\

by default
(0000788)
DeTard   
2008-06-17 12:29   
This wasn't KTD. I manually had placed the drivers for CPU there at the time I was working with the network driver repository.
(0000789)
OverFlow   
2008-06-17 12:32   
I will have to look at that part of the code more closely ;)
(0000790)
DeTard   
2008-06-17 12:52   
Well to be totally honest, to me this isn't very important any longer, but possibly someone else will have a reason to place drivers in custom paths. As suggested by someone on the forum, I started using Sysprep Driver Scanner, and I'm fairly confident in it's useage now that I can see in verbose detail what directories are being added to the registry prior to commiting the change.