first off all ensure you have no leftover stray memory breakpoints ollydbg will blink only if it is processing some debug events
running with with f9 should not make it process any event at all
you can disable auto analysis of all modules and opt for manual analysis as and when needed
again it is in alt+o
you can disable Debugging data loading (or stop all the pdb symbols requests sent to from ms symbol server )
these all could speed up the startup of a large binary
i have an 82 mb udd file of microsoft excel.exe and ollydbg doesnt stall loading or analysing it
i just loaded it before replying
loaded excel in a jiffy set a bp on mso#3087 and clicked a cell in excel to break all under a minute max
Code:
Call stack of main thread
Stack Data Procedure Called from Frame
0013F828 3036DAAD EXCEL.3013F050 EXCEL.3036DAA8
0013F85C 30799651 EXCEL.3036DA72 EXCEL.3079964C
0013F9D4 303A68AF EXCEL.30797EA4 EXCEL.303A68AA
0013FA94 30016869 ??? EXCEL.30016866
0013FB7C 30016767 EXCEL.30016796 EXCEL.30016762
0013FB9C 7E418734 ??? USER32.InternalCallWinProc+25
0013FBC8 7E418816 USER32.InternalCallWinProc USER32.UserCallWinProcCheckWow+0B2
0013FC30 7E42A013 USER32.UserCallWinProcCheckWow USER32.CallWindowProcAorW+4C
0013FC60 7E42A039 USER32.CallWindowProcAorW USER32.CallWindowProcW+16
0013FC80 32650ACD USER32.CallWindowProcW mso.32650AC7
0013FCB8 7E418734 ??? USER32.InternalCallWinProc+25
0013FCE4 7E418816 USER32.InternalCallWinProc USER32.UserCallWinProcCheckWow+0B2
0013FD4C 7E4189CD USER32.UserCallWinProcCheckWow USER32.DispatchMessageWorker+0D7
0013FDAC 7E418A10 USER32.DispatchMessageWorker USER32.DispatchMessageW+0A
0013FDBC 30027AF5 USER32.DispatchMessageW EXCEL.30027AEF
0013FDE0 3002771F EXCEL.30027A6A EXCEL.3002771A
0013FEC4 30003AD8 EXCEL.30026B30 EXCEL.30003AD3
0013FF34 300037EC EXCEL.30003802 EXCEL.300037E7
0013FFC4 7C817077 ??? kernel32.BaseProcessStart+20
Code:
C:\Documents and Settings\Admin\My Documents\ollydbg2beta\odbg201\odbg201>ls -lah EXCEL.udd
-rw-rw-rw- 1 Admin 0 81M 2014-03-25 12:56 EXCEL.udd