i just tried building and installing it on win7 vm seems to work
without problems
here is an output of the trial
C:\WinDDK\7600.16385.1\src\general\toaster>winmergeu /r %cd% …\toasterorig
C:\WinDDK\7600.16385.1\src\general\toaster>type toasterdiff.txt
Compare C:\WinDDK\7600.16385.1\src\general\toaster with
C:\WinDDK\7600.16385.1\src\general\toasterorig
16/04/2012 03:47:17
Filename, Short Result
remdir.bat, Left Only
showosandbuild.bat, Left Only
toasterdiff.txt, Left Only
C:\WinDDK\7600.16385.1\src\general\toaster>makedirs %cd%
Starting dirs creation…Completed.
C:\WinDDK\7600.16385.1\src\general\toaster>build -ceZg
BUILD: Compile and Link for x86
BUILD: Start time: Mon Apr 16 03:48:03 2012
BUILD: Finish time: Mon Apr 16 03:49:08 2012
BUILD: Done
154 files compiled - 3 Warnings
5 libraries built
30 executables built
C:\WinDDK\7600.16385.1\src\general\toaster> dir /s /b *.exe *sys *.dll
*.lib >> binaries.txt
cutoff the toastcd directory from the list it is duplicate
use sed on binaries.txt to make it binaries.bat
sed commands are
-
prepend copy before path
-
append %cd%\Binaries. after path
C:\WinDDK\7600.16385.1\src\general\toaster\binaries>sed
s/$/\x20%cd%\binaries\./g binaries.txt >binaries.bat
everyline in binaries.bat will look like this
copy C:\WinDDK\7600.16385.1\src\general\toaster\wdm\toastmon\objchk_win7_x86\i386\toastmon.sys
%cd%\binaries.
make the binaries directory copy wont make directory
md binaries
run binaries.bat it will copy all 35 built components to that folder
copy bus.inf , toastco,inf toaster.cat to binaries folder
run buildiso.bat (uses imgburn to build an iso)
C:\WinDDK\7600.16385.1\src\general\toaster\binaries>type BuildIso.bat
“c:\Program Files\ImgBurn\ImgBurn.exe” /mode build /buildoutputmode imagefile /s
rc %CD% /dest %1.iso /FILESYSTEM “UDF” /UDFREVISION “2.01” /VOLUMELABEL %1 /roo
tfolder yes /noimagedetails /start /close
C:\WinDDK\7600.16385.1\src\general\toaster\binaries>BuildIso.bat ToasterCD
mount the iso in vm using capture iso feature
use devcon install :\bus.inf “root\busenum”
a warning will popup do you want to blah blah click yes if you are on
x64 you probably also need to boot in test signing mode
and devcon suceeded and i can do
enum -p 1
here is an output
C:>devcon install d:\bus.inf “root\busenum”
Device node created. Install is complete when drivers are installed…
Updating drivers for root\busenum from d:\bus.inf.
Drivers installed successfully.
C:>d:\Enum.exe -p 1
Opening \?\root#system#0001#{d35f7840-6a0c-11d2-b841-00c04fad5171}
Bus interface opened!!!
SerialNo. of the device to be enumerated: 1
Success!!!
C:>d:\Enum.exe -p 1
Opening \?\root#system#0001#{d35f7840-6a0c-11d2-b841-00c04fad5171}
Bus interface opened!!!
SerialNo. of the device to be enumerated: 1
PlugIn failed:0x57
C:>d:\Enum.exe -u 1
Opening \?\root#system#0001#{d35f7840-6a0c-11d2-b841-00c04fad5171}
Bus interface opened!!!
Unplugging device(s)…
Success!!!
C:>d:\Enum.exe -p 1
Opening \?\root#system#0001#{d35f7840-6a0c-11d2-b841-00c04fad5171}
Bus interface opened!!!
SerialNo. of the device to be enumerated: 1
Success!!!
C:>d:\Enum.exe -e 1
Opening \?\root#system#0001#{d35f7840-6a0c-11d2-b841-00c04fad5171}
Bus interface opened!!!
Ejecting Device(s)
Success!!!
C:>d:\Enum.exe -p 1
Opening \?\root#system#0001#{d35f7840-6a0c-11d2-b841-00c04fad5171}
Bus interface opened!!!
SerialNo. of the device to be enumerated: 1
Success!!!
C:>
On 4/15/12, xxxxx@gmail.com wrote:
> Hello.
>
> As the title may have suggested, I am a windows noob trying to learn the ins
> and outs of windows device drivers. Coming from the Linux world, I am
> initially finding the learning curve a little steeper than I expected,
> especially driver installation.
>
> Now I am using the toaster driver provided within the DDK v7600.16385.1 as a
> sample. I was able to build the drivers using x64 checked build environment.
> My target machine is a VM running Windows server 2008 R2. I boot with the
> ‘disable driver checking for signature’ switch on so I am able to load
> unsigned drivers as well.
>
> By doing this I was able to install the bus driver (busenum.sys), although
> it did tell me that the driver is unsigned (despite placing the toaster.cat
> catalog file in the same directory). Anyhow, as suggested by the toaster
> documentation
> (http://msdn.microsoft.com/en-us/library/windows/hardware/ff558716(v=vs.85).aspx),
> I am supposed to ‘simulate’ the plugging of a toaster using the enumerate
> exe (enum.exe -p 1).
>
> In the words of the documentation 'these applications(enum.exe and
> devcon.exe) send an I/O control (IOCTL) to the bus driver with the
> user-provided globally unique serial number and hardware ID of the device
> and trigger the entire enumeration process. The PnP manager takes the ID
> information that the bus driver provides and searches the system INF
> directory to find a matching INF file. If the PnP manager does not find a
> suitable INF file (for example, when you install for the first time), it
> prompts the user to specify an INF file. At this point, you can pick one of
> the three INF files (Toaster.inf, Toastco.inf, or Toasterf.inf) to be the
> device INF file. If you are testing this sample for the first time, you
> should choose Toastco.inf. '. Regarding the above lines, I was NOT prompted
> to specify the inf file for the toaster function driver. It started
> searching for the driver. And since it couldn’t find the driver file and the
> inf for the toaster function driver, it merely said it failed to install the
> device. I had to manually open the device manager. There in the others
> category, I saw a device named “microsoft_eliyas_toaster_01”. I tried to
> update the driver software for this new device by pointing it to the
> toaster.inf file to which the installer says that ‘windows found driver
> software for your device but encountered an error while attempting to
> install it’. And it further added ‘the system cannot find the file
> specified’.
>
> These two seem mutually exclusive to my untrained eye. Ive searched on this
> all I could on google and ive mostly found threads helping people resolve
> their driver installation issues for printers, scanners and its mostly
> written with en end user perspective. Ive yet to find something written from
> a developer perspective…
>
> Now luckily Ive found this as one of the few active forums where like minded
> windows developers gather…so pls folks…Id be grateful if I could get
> started somewhere…
>
> Regards
> Aijaz
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>