Hi, On Sat, Oct 25, 2003 at 02:23:17PM +0200, Marcus Meissner wrote:
Hi,
Make Winword 2000 work again.
I do not know, why it does outb $al,0x70, inb 0x71, $al ...
And I am _afraid_ to ask. Why, that's perfectly ok... Just imagine your feeling if it also did: outb $al,0x70, outb al, 0x71
;-)) That only goes to show what a crappy piece of !@#$@$% Winword 2000 is...
+ if (INSTR_EmulateInstruction( epointers->ExceptionRecord, epointers->ContextRecord) == ExceptionContinueExecution) + return EXCEPTION_CONTINUE_EXECUTION;
BTW: Thanks!! This will most certainly fix my JTAG parallel port flashing tool (I already reported it, but nobody fixed it, and the result of "time * need" was too low...). -- Wir kommen alle als Original zur Welt, aber die meisten von uns sterben als Kopien (Autor unbekannt)
David D Hagood wrote:
Andreas Mohr wrote:
I do not know, why it does outb $al,0x70, inb 0x71, $al ...
That looks like a "read realtime clock/CMOS" function. Now WHY an application would be directly reading the RTC....
Incase your faking the system clock ? Tom
On Sat, Oct 25, 2003 at 09:24:19AM -0500, David D. Hagood wrote:
Andreas Mohr wrote:
I do not know, why it does outb $al,0x70, inb 0x71, $al ...
That looks like a "read realtime clock/CMOS" function. Now WHY an application would be directly reading the RTC....
Its office suckage. The function is somewhere around: MSO9.DLL.?AccessGet(a)CFileFolder@@QBE?AW4ACCESSQCFSObj(a)PAviIntterruptQ@@PAH(a)Z It is accessing offsets 0x15, 0x16, 0x17, 0x18. (base memory size and extended memory size?) Ciao, Marcus
On Sat, 25 Oct 2003 17:07:56 +0200, Sir Marcus Meissner scribed thus:
MSO9.DLL.?AccessGet(a)CFileFolder@@QBE?AW4ACCESSQCFSObj(a)PAviIntterruptQ@@PAH(a)Z
It is accessing offsets 0x15, 0x16, 0x17, 0x18.
(base memory size and extended memory size?)
Do we have any tools that can demangle MSVC++ symbol names? c++filt won't do it unfortunately.
Mike Hearn wrote:
On Sat, 25 Oct 2003 17:07:56 +0200, Sir Marcus Meissner scribed thus:
MSO9.DLL.?AccessGet(a)CFileFolder@@QBE?AW4ACCESSQCFSObj(a)PAviIntterruptQ@@PAH(a)Z
It is accessing offsets 0x15, 0x16, 0x17, 0x18.
(base memory size and extended memory size?)
Do we have any tools that can demangle MSVC++ symbol names? c++filt won't do it unfortunately.
winedump does to some extend (even if it fails on this one) A+ -- Eric Pouech
participants (6)
-
Andreas Mohr -
David D. Hagood -
Eric Pouech -
Marcus Meissner -
Mike Hearn -
Tom