Changes between Version 203 and Version 204 of windows_backend_activity_log


Ignore:
Timestamp:
08/20/10 14:54:38 (3 years ago)
Author:
pbatard
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • windows_backend_activity_log

    v203 v204  
    285285o [wdi] progress bar looks bad on XP / non Aero 7/Vista 
    286286o [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-8 
     287o [wdi] display of debug setupapi.log on 2k is mixed up, since the log is current locale and we expect UTF-8 
    288288o [zadig] why do these all these control look SO UGLY compared to what MSVC promises? [FIXED ("ooh, shiny!!"): 2010.05.28] 
    289289o [zadig] the font in device selection still looks 3.1ish... [FIXED: 2010.05.31] 
     
    316316o [zadig] seen "program assertion failed - editable_desc != NULL" on driverless device insert 
    317317o [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?) 
     318o [zadig] can crash post exit on cygwin (dump analysis doesn't reveal a direct crash coming from code on exit..) 
    319319o [zadig] 64K of log is not enough for everybody! [FIXED: 2010.08.19] 
    320320o [zadig] bad scrollup on win2k [FIXED: 2010.08.19]