Changes between Version 203 and Version 204 of windows_backend_activity_log
- Timestamp:
- 08/20/10 14:54:38 (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
windows_backend_activity_log
v203 v204 285 285 o [wdi] progress bar looks bad on XP / non Aero 7/Vista 286 286 o [wdi] "not a valid assembly or a COM component." when trying to use it in C#/.NET (reported by Ken Abryl Eleazar Salanio) 287 o [wdi] display of debug setupapi.log on 2k is mixed up, since the log is 8859-1 (or any locale)and we expect UTF-8287 o [wdi] display of debug setupapi.log on 2k is mixed up, since the log is current locale and we expect UTF-8 288 288 o [zadig] why do these all these control look SO UGLY compared to what MSVC promises? [FIXED ("ooh, shiny!!"): 2010.05.28] 289 289 o [zadig] the font in device selection still looks 3.1ish... [FIXED: 2010.05.31] … … 316 316 o [zadig] seen "program assertion failed - editable_desc != NULL" on driverless device insert 317 317 o [zadig] log dialog can flash after the progress bar dialog is closed (test this with a MinGW32 zadig on x64) 318 o [zadig] can crash post exit on cygwin ( another LocalFree vs free issue?)318 o [zadig] can crash post exit on cygwin (dump analysis doesn't reveal a direct crash coming from code on exit..) 319 319 o [zadig] 64K of log is not enough for everybody! [FIXED: 2010.08.19] 320 320 o [zadig] bad scrollup on win2k [FIXED: 2010.08.19]