Mike Hearn wrote:
On Sat, 25 Oct 2003 17:07:56 +0200, Sir Marcus Meissner scribed thus:
[EMAIL PROTECTED]@@[EMAIL PROTECTED]@@[EMAIL PROTECTED]
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 name
On Sun, Oct 26, 2003 at 12:34:13AM +0100, Martin Fuchs wrote:
> On 25.10.2003 22:52:30 Mike Hearn wrote:
> > On Sat, 25 Oct 2003 17:07:56 +0200, Sir Marcus Meissner scribed thus:
> > >
> > [EMAIL PROTECTED]@@[EMAIL PROTECTED]@@[EMAIL PROTECTED]
> > >
> > > It is accessing offsets 0x15, 0x16, 0x17
On 25.10.2003 22:52:30 Mike Hearn wrote:
> On Sat, 25 Oct 2003 17:07:56 +0200, Sir Marcus Meissner scribed thus:
> >
> [EMAIL PROTECTED]@@[EMAIL PROTECTED]@@[EMAIL PROTECTED]
> >
> > It is accessing offsets 0x15, 0x16, 0x17, 0x18.
> >
> > (base memory size and extended memory size?)
>
> Do we h
On Sat, 25 Oct 2003 17:07:56 +0200, Sir Marcus Meissner scribed thus:
> [EMAIL PROTECTED]@@[EMAIL PROTECTED]@@[EMAIL PROTECTED]
>
> 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
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.
T
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
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
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