Back to home page

DOS ain't dead

Forum index page

Log in | Register

Back to index page

Rugxulo

Usono,
05.05.2008, 18:38
(edited by Rugxulo, 05.05.2008, 21:17)

BIEW bug?? (GPF in RMCB under JEMMEX) (DOSX)

Okay, first of all, I'll admit to using "old" JEMMEX 5.71 (since supposedly 5.72 is no different, just assembled via different tools). And it works fine. However, on my old P166 I have the latest BIEW (DJGPP) installed (which is cool although I seldom really use it), and it had a small crash:

General Protection Fault in RMCB at eip=110f ; flags=3302
eax=01510001 ebx=000010C0 ecx=00000000 edx=00086300
esi=00001788 edi=0000234C ebp=00000000 esp=00002338

That's all I was able to manuallys scribble down before the screen blanked (Eric's IDLEDPMS), and unfortunately, whatever this was (I feel pretty confident it's something in BIEW, actually), it messed up IDLEDPMS where I couldn't unblank the screen (doh). So, this is the only "clue" I have. (The game is afoot, Watson!) :-P

Japheth, I doubt you could diagnose this, but I present it here to you for laughs, for completeness' sake, etc. Don't agonize too much over it! ;-)

rr

Berlin, Germany,
05.05.2008, 21:06

@ Rugxulo

BIEW bug?? (GPF in RMCB under JEMMEX)

> General Protection Fault in RMCB at eip=110f ; flags=3302

What is RMCB? Some memory control block?

EDIT: RMCB = real-mode callback

> (Eric's IDLEDPMS), and unfortunately, whatever this was (I feel pretty
> confident it's something in BIEW, actually), it messed up IDLEDPMS where I

Some people think BIEW is full of bugs. So I'm not surprised.

---
Forum admin

Rugxulo Usono, 05.05.2008, 21:21 @ rr	BIEW bug?? (GPF in RMCB under JEMMEX) Post reply
	> Some people think BIEW is full of bugs. So I'm not surprised. But it uses DJGPP (and hence DPMI), so what could it be doing (outside of inline asm) that would cause such an error? (Granted, I did run the Shift-F6 "CPU performance" option, maybe that's why??)

rr

Berlin, Germany,
05.05.2008, 21:35

@ Rugxulo

BIEW bug?? (GPF in RMCB under JEMMEX)

> > Some people think BIEW is full of bugs. So I'm not surprised.
>
> But it uses DJGPP (and hence DPMI), so what could it be doing (outside of
> inline asm) that would cause such an error? (Granted, I did run the
> Shift-F6 "CPU performance" option, maybe that's why??)

From "release.txt":
- Sometime, when biew-Win32 is running under WinNT-4.0 (SP4-5) and
system perform swapping after quitting of biew You may receive GPF.
- If you have selected 'Use MMF' option in biew-Win32 and are viewing
file biew.ini, that after leaving biew you get GPF.
- 'CPU performance' of biew-DOS32 (aka djgpp) doesn't work under Win98
and may crash such systems.

---
Forum admin

Japheth

Germany (South),
06.05.2008, 07:45

@ Rugxulo

BIEW bug?? (GPF in RMCB under JEMMEX)

> General Protection Fault in RMCB at eip=110f ; flags=3302
> eax=01510001 ebx=000010C0 ecx=00000000 edx=00086300
> esi=00001788 edi=0000234C ebp=00000000 esp=00002338
>
>
> Japheth, I doubt you could diagnose this, but I present it here to
> you for laughs, for completeness' sake, etc. Don't agonize too much over
> it! ;-)

Thanks! However, it's not a Jemm dump. A RMCB is code running in protected-mode, it runs in the DPMI host's context.

RMCBs are rarely used. One of the most popular uses is a mouse event proc. Did you use the mouse?

---
MS-DOS forever!

Rugxulo

Usono,
06.05.2008, 22:56
(edited by Rugxulo, 06.05.2008, 23:32)

@ Japheth

BIEW bug?? (GPF in RMCB under JEMMEX)

> Thanks! However, it's not a Jemm dump. A RMCB is code running in
> protected-mode, it runs in the DPMI host's context.
>
> RMCBs are rarely used. One of the most popular uses is a mouse event proc.
> Did you use the mouse?

Nope, no mouse (or mouse driver) installed.

EDIT: Only stuff like IDLEDPMS and HXLDR32 and UIDES. BTW, I'm looking at BIEW's src, but I don't see anything strange that would cause any huge issues. Oh well.

Japheth

Germany (South),
11.05.2008, 20:19

@ Rugxulo

BIEW bug?? (GPF in RMCB under JEMMEX)

> EDIT: Only stuff like IDLEDPMS and HXLDR32 and UIDES. BTW, I'm looking at
> BIEW's src, but I don't see anything strange that would cause any huge
> issues. Oh well.

What does "Oh well" mean? That your interest has waned to some other piece of soft? Or, if no, did you try Dos386's suggestion to remove JemmEx? If yes - what were the results?

---
MS-DOS forever!

Rugxulo

Usono,
12.05.2008, 21:57

@ Japheth

BIEW bug?? (GPF in RMCB under JEMMEX)

> > EDIT: Only stuff like IDLEDPMS and HXLDR32 and UIDES. BTW, I'm looking
> at
> > BIEW's src, but I don't see anything strange that would cause any huge
> > issues. Oh well.
>
> What does "Oh well" mean? That your interest has waned to some other piece
> of soft? Or, if no, did you try Dos386's suggestion to remove JemmEx? If
> yes - what were the results?

I can't even be sure what caused the problem. All I can do (if you want) is retry with DR-DOS' EMM386 (or maybe only HIMEM): BIEW -> Shift+F6 (SysInf) -> CPU Performance. But even retrying here on WinXP, if I try more than once, it seems to stall (probably "hang", but I'm not gonna wait for hours just to be sure).

In short, it's too small an issue to worry about (assuming it's a BIEW bug).

Japheth

Germany (South),
13.05.2008, 10:36

@ Rugxulo

BIEW bug?? (GPF in RMCB under JEMMEX)

> I can't even be sure what caused the problem. All I can do (if you want)

No thanks! I'm just irritated by your habit of reporting "bugs" and then quickly "move away" from the issue. As for me, I'm either interested in something and then also care about it or I'm not interested and consequently will neither care nor talk about that thing.

---
MS-DOS forever!

Rugxulo

Usono,
13.05.2008, 22:10

@ Japheth

BIEW bug?? (GPF in RMCB under JEMMEX)

> > I can't even be sure what caused the problem. All I can do (if you want)
>
> No thanks! I'm just irritated by your habit of reporting "bugs" and then
> quickly "move away" from the issue. As for me, I'm either interested in
> something and then also care about it or I'm not interested and
> consequently will neither care nor talk about that thing.

Sorry, I'm a bit of a spazz, easily distracted. And in this case, I expected you to know what it meant (since I have no clue).

Rugxulo

Usono,
14.05.2008, 02:13

@ Rugxulo

BIEW bug?? (GPF in RMCB under JEMMEX)

> > > I can't even be sure what caused the problem. All I can do (if you
> want)
> >
> > No thanks! I'm just irritated by your habit of reporting "bugs" and
> then
> > quickly "move away" from the issue. As for me, I'm either interested in
> > something and then also care about it or I'm not interested and
> > consequently will neither care nor talk about that thing.
>
> Sorry, I'm a bit of a spazz, easily distracted. And in this case, I
> expected you to know what it meant (since I have no clue).

Well, I tested it a bit without any TSRs, even under only plain XMS (DR-DOS'), so it must be something either in BIEW or CWSDPMI (as DOS386 suggested). Meh.

DOS386

08.05.2008, 17:58

@ Rugxulo

CWSDPMI bug

> General Protection Fault in RMCB at eip=110f ; flags=3302
> eax=01510001 ebx=000010C0 ecx=00000000 edx=00086300
> esi=00001788 edi=0000234C ebp=00000000 esp=00002338

NOT new

It's CWSDPMI ... it always "redirects" GPF's in Ring 0 to "RCMB" :lol3:

Hints:

- Remove JEMMEX
- HDPMI32

> Some people think BIEW is full of bugs. So I'm not surprised.

There are a few ... but it's still very use for me :-)

> One of the most popular uses is a mouse event proc.

See above, old INFOPAD also triggered this bug without any mouse involved at all :-D

---
This is a LOGITECH mouse driver, but some software expect here
the following string:*** This is Copyright 1983 Microsoft ***

Japheth

Germany (South),
08.05.2008, 18:08

@ DOS386

CWSDPMI bug

> It's CWSDPMI ... it always "redirects" GPF's in Ring 0 to "RCMB" :lol3:

Is this common knowledge? Then please reveal details! "GPFs in Ring 0" shouldn't happen in a raw DPMI host without built-in extender.

> - Remove JEMMEX

Why should this change behavior?

---
MS-DOS forever!

DOS386

09.05.2008, 07:24

@ Japheth

CWSDPMI bug

> > It's CWSDPMI ... it always "redirects" GPF's in Ring 0 to "RCMB" :lol3:
>
> Is this common knowledge? Then please reveal details!

That's probably why CWSDPMI unconditionally whines about RCMB even if no rat callbacks or even no driver is present.

> "GPFs in Ring 0" shouldn't happen in a raw DPMI host without built-in extender.

Yeah ... many things shouldn't happen. But if a "very rarely used" callback is present (HX GUI, Blocek, FreeBASIC, DUGL, ...) and the application crashes and you touch the mouse :crying:

---
This is a LOGITECH mouse driver, but some software expect here
the following string:*** This is Copyright 1983 Microsoft ***

Steve

US,
09.05.2008, 08:19

@ DOS386

CWSDPMI bug

> > > It's CWSDPMI ... it always "redirects" GPF's in Ring 0 to "RCMB"
> :lol3:
> >
> > Is this common knowledge? Then please reveal details!
>
> That's probably why CWSDPMI unconditionally whines about RCMB even if no
> rat callbacks or even no driver is present.
>
> > "GPFs in Ring 0" shouldn't happen in a raw DPMI host without built-in
> extender.
>
> Yeah ... many things shouldn't happen. But if a "very rarely used"
> callback is present (HX GUI, Blocek, FreeBASIC, DUGL, ...) and the
> application crashes and you touch the mouse :crying:

I'm having trouble understanding your logic. How does 'always "redirects"' follow from 'probably' and 'if a "very rarely used" callback is present...and the application crashes and you touch the mouse'

But I have a solution (maybe) to that last problem: Don't play with your mouse when a prog is crashing.

DOS386

09.05.2008, 08:30

@ Steve

CWSDPMI bug

1. You did bottom-post
2. Your "answer" is off-topic and useless

> But I have a solution (maybe) to that last problem: Don't play with your
> mouse when a prog is crashing.

Please go away and play with your cat instead of brewing further posts like this one. :hungry:

PS: DOSferatu has just been registered ... welcome :-)

---
This is a LOGITECH mouse driver, but some software expect here
the following string:*** This is Copyright 1983 Microsoft ***

Steve

US,
09.05.2008, 08:52

@ DOS386

CWSDPMI bug

> 1. You did bottom-post

It was a single question based on related quotes. The position of the question therefore seemed logical in this case.

BTW, you have now top-posted.

> 2. Your "answer" is off-topic and useless

OK, what would be a useful solution?

> > But I have a solution (maybe) to that last problem: Don't play with your
> > mouse when a prog is crashing.
>
> Please go away and play with your cat instead of brewing further posts
> like this one.

You still haven't answered my question.

> PS: DOSferatu has just been registered

Your new name?

DOS386

11.05.2008, 13:01

@ Steve

CWSDPMI bug

> BTW, you have now top-posted.

NO.

> You still haven't answered my question.

I don't see any. Possibly there is none :clap:

> > PS: DOSferatu has just been registered
>
> Your new name?

NO.

---
This is a LOGITECH mouse driver, but some software expect here
the following string:*** This is Copyright 1983 Microsoft ***

rr

Berlin, Germany,
13.05.2008, 10:58

@ Steve

CWSDPMI bug

> > PS: DOSferatu has just been registered
>
> Your new name?

DOSferatu is "just another" TP coder. He'll probably introduce himself soon. But be warned, he writes very lengthy posts. ;-)

---
Forum admin

Laaca

Czech republic,
14.05.2008, 09:13

@ rr

CWSDPMI bug

> DOSferatu is "just another" TP coder.

Great! Another brother in arms.

---
DOS-u-akbar!

Back to index page

22632 Postings in 2109 Threads, 402 registered users, 371 users online (0 registered, 371 guests)
DOS ain't dead | Admin contact

powered by my little forum