This is from the setupapi.app.log
[DIF_SELECTBESTCOMPATDRV -
USB\VID_04F9&PID_0146&MI_01\6&1B69BAE3&0&0001]
Section start 2006/06/18 22:25:24.593
cmd: winpeshl.exe
dvi: No class installer for 'Unknown driver software package'
dvi: No CoInstallers found
dvi: Default installer: Enter
dvi: {Select Best Driver}
! dvi: Selecting driver failed(0xe0000228)
dvi: {Select Best Driver - exit(0xe0000228)}
! dvi: Default installer: failed!
! dvi: Error 0xe0000228: There are no compatible drivers for this
device.
<<< Section end 2006/06/18 22:25:24.609
<<< [Exit status: FAILURE(0xe0000228)]
[DIF_DESTROYPRIVATEDATA - ACPI\PNP0401\4&7443DCA&0]
Section start 2006/06/18 22:25:24.609
cmd: winpeshl.exe
dvi: Class installer: Enter
dvi: Class installer: Exit
dvi: Default installer: Enter
dvi: Default installer: Exit
<<< Section end 2006/06/18 22:25:24.609
<<< [Exit status: FAILURE(0xe000020e)]
This is from the end of the setupapi.dev.log
dvi: {FULL Install}
dvi: Device Instance =
'USBSTOR\DISK&VEN_GENERIC&PROD_USB_MS_READER&REV_1.03\9205291&3'
dvi: {Install FILES}
inf: Loaded PNF for
'x:\$windows.~bt\windows\system32\driverstore\filerepository\disk.inf_429b591d\disk.inf'
(Language = 0409).
dvi: DI_NOFILECOPY is set
dvi: Install section is disk_install.NT
dvi: Appending INFs...
dvi: Skipping file copy...
dvi: {Install FILES exit 00000000}
dvi: {Install DEVICE}
dvi: Creating Driver Key...
inf: Loaded PNF for
'x:\$windows.~bt\windows\system32\driverstore\filerepository\disk.inf_429b591d\disk.inf'
(Language = 0409).
dvi: Install section is disk_install.NT
dvi: Appending INFs...
dvi: Processing Registry directives...
inf: {Install Inf Section [disk_install.NT]}
inf: {Install Inf Section [disk_install.NT] exit
(0x00000000)}
dvi: Processing Property directives...
inf: {Install Inf Section [disk_install.NT]}
inf: {Install Inf Section [disk_install.NT] exit
(0x00000000)}
dvi: Processing HW sections...
dvi: Writing common device property settings.
dvi: Provider name=Microsoft
dvi: DriverDate (FILETIME) 1c694c5.a38c8000
dvi: DriverVersion=6.0.5384.4
dvi: Class name=DiskDrive
dvi: Manufacturer=(Standard disk drives)
dvi: Matching DeviceID=gendisk
dvi: Strong
Name=disk.inf:disk_device.NTx86:disk_install:6.0.5384.4:gendisk
dvi: Writing common device property settings
complete.
dvi: Installing services...
inf: {Install Service Section
[disk_install.NT.Services]}
inf: DelService: none
inf:
AddService=disk,2,disk_ServiceInstallSection,disk_EventLog_InstallSection
(disk.inf line 123)
dvi: Add Service: Modified existing service
'disk'.
inf: AddReg=autorun_addreg (disk.inf line
131)
inf:
HKLM,System\CurrentControlSet\Services\disk,AutoRunAlwaysDisable,0x00010008,"Brother
RemovableDisk(U)" (disk.inf line 32)
inf: AddReg=disk_EventLog_AddReg (disk.inf
line 134)
inf:
HKR,,EventMessageFile,0x00020000,%SystemRoot%\System32\IoLogMsg.dll
(disk.inf line 137)
inf: HKR,,TypesSupported,0x00010001,7
(disk.inf line 138)
inf: {Install Service Section
[disk_install.NT.Services] exit(0x00000000)}
dvi: Installing WMI section...
dvi: {Install DEVICE exit 00000000}
dvi: Writing common driver property settings.
dvi: DriverDescription=Disk drive
dvi: DeviceDisplayName=Disk drive
dvi: Install Device: Restarting device. 22:13:56.390
<ins>
ààËÛ'×9W Û¤
Hope this helps
droid said:
Here's something you can do if nothing else helps. I would pay attention
to the last paragraph since you say it is continually rebooting. When you
go through the procedures try to avoid the rebooting so the log files
won't get messed by the reboot, do this by hitting F8 fast after the
first crash/early reboot.
Finding setup logs, reporting and attaching logs to report, figuring out
what device or driver causes hangs or crash during setup:
1. google -> beta client
click the first link. It needs .NET but I think it will be installed if
you try to run it without it..
2. finding and identifying the correct logs
setupapi.app.log
setupapi.dev.log <<-- last 20 lines here may indicate hanging driver
These are the primary setup logs, there are others but these are the
major.
Hint: Before searching logs try Folder Options and enable viewing of
hidden folders and files. Also try Run diskmgmt.msc -> assign drive
letters for partitions with no drive letters.
A:
There can be multiple logs with the same name, but they are different!
First look at the drive you tried to install Vista to, if it has Vista
Windows\INF\ directory and the mentioned logs files.
B: early setup failure
If you can't find Windows VISTA directory (if setup did not get so far)
then look all volumes/partitions in the drives that were on the machine
during the install for directories starting with $. There are 2-4 of them
(possibly in different partitions) depending on when the setup failed.
Search for .log under all the *:\$WINDOWS.. and again look at the
date/minute timestamp to see which of the logs was changed just before
the failure occured.
Also see that the date and Minute timestamp of the log files are around
the time when the setup failed, sometimes a setup/install failure causes
the computer to automatically reboot and the setup will run again but
failing in different way than the first time (making the bug report less
useful). For best bug report it's better to catch the failure when it
first happens. Yes it means starting the install all over again and
keeping eye on it. But this will guarantee that the last line in the log
will be around the time of the failure. If it is a driver crash then you
can figure out the offending driver yourself just by looking at the last
twenty or so lines of setupapi.dev.log.
