C / C++ / MFC

Eugen Podsypalnikov24-Jul-12 0:06

Eugen Podsypalnikov

24-Jul-12 0:06

It could be a splitter window (2 + 3) in another (1 + (2 + 3)) Smile | :)

They sought it with thimbles, they sought it with care;
They pursued it with forks and hope;
They threatened its life with a railway-share;
They charmed it with smiles and soap. Smile | :)

Eugen Podsypalnikov24-Jul-12 0:17

Eugen Podsypalnikov

24-Jul-12 0:17

May be the solution is also thinkable for you Smile | :)

:
- An MDI app
- The Tabed MDI list-views controlled by the selection in your tree control
- The Tree control is in a pane (CDockablePane) controlled by the selection in your main list control
- The Main list control is in a pane as well
- The layout of the MDI-area and panes is controlled by the Users and remanent for them

They sought it with thimbles, they sought it with care;
They pursued it with forks and hope;
They threatened its life with a railway-share;
They charmed it with smiles and soap. Smile | :)

Mohibur Rashid25-Jul-12 14:45

Mohibur Rashid

25-Jul-12 14:45

create three different custom window-class and create those window on the main window when required

Vaclav_25-Jul-12 16:51

Vaclav_

25-Jul-12 16:51

Unless you absolutely have to have ONLY 3 views why don't you use standard CSplitter CreateStatic and create CSplitter frame with 4 views?
Than let the MFC do the dirty work. No need to customize anything.

ekinnh26-Jul-12 18:13

ekinnh

26-Jul-12 18:13

Thanks. I managed to do the 3 views splitter windows. Smile | :)

Vaclav_27-Jul-12 2:42

Vaclav_

27-Jul-12 2:42

Great, can you share the basic idea / code?
I was thinking 1 column / 3 rows would also work if it is acceptable.

ekinnh31-Jul-12 22:13

ekinnh

31-Jul-12 22:13

I just got the idea from this article:

http://www.codeproject.com/Articles/190/A-Visual-Framework-Views-Tabs-and-Splitters

Basically I just wrote this in the MainFrame:

C++

m_wndSplitterHor.CreateStatic(this, 2, 1)
m_wndSplitterHor.CreateView(0, 0, RUNTIME_CLASS(CSampleCollectList), CSize(280,300), pContext) //View 1
m_wndSplitterHor.SetColumnInfo(0, 200, 0);

m_wndSplitterVer.CreateStatic(&m_wndSplitterHor, 1, 2, WS_CHILD | WS_VISIBLE, m_wndSplitterHor.IdFromRowCol(1, 0))
m_wndSplitterVer.CreateView(0, 0, RUNTIME_CLASS(CSampleTree), CSize(250,0), pContext) //View 2
m_wndSplitterVer.CreateView(0, 1, RUNTIME_CLASS(CSampleCollectList), CSize(250,0), pContext) //View 3

But now im stuck with tab control in View 3. Any idea?

[Hook HW interrupts in flat mode with DOS32/A]

Sunil P V26-Jul-12 2:09

Sunil P V

26-Jul-12 2:09

Inherit your application view class from CFormView. This enables you to have controls on the view just like you would have on a dialog. For your usage I think this is suitable and it saves time. Check for online samples too...

Sunil

liaoo23-Jul-12 16:42

23-Jul-12 16:42

Dear all,
I have a question about how to hook HW interrupt in flat memory mode...Maybe you can give me some directions... Smile | :)

@ about my application...
- created by combining Watcom C and DOS32/A.
- written for running on DOS mode( not on OS mode )
- with DOS32/A now I can access >1M memory and allocate large memory to use...(running in flat memory mode !!!)

@ current issue...
- I want to write an ISR(interrupt service routine) for one PCI card. Thus I need to "hook" the HW interrupt to test...
- For example, the PCI card's interrupt line(0x3C) = 0xE in DOS mode. That means this device will issue interrupt via 8259's IRQ 14.

But... I did not how to achieve my goal to hook this interrupt in "flat mode" ?

@ reference I found...
- in watcom C's library doc, there is one sample using _dos_getvect, _dos_setvect, and _chain_intr to hook INT 0x1C...I tested this code and found OK.

But when I apply it to my case: INT76 ( where IRQ 14 is "INT 0x76" due to (14-8) + 0x70 )then nothing happened...

* I have checked HW interrupt is truly generated but my own ISR did NOT invoked...

Do I lose something ? or are there any functions I can use (in DOS32/A) to achieve my goal ? Confused | :confused:

enhzflep23-Jul-12 19:01

enhzflep

23-Jul-12 19:01

Wow - there's a blast from the past.

With your sample app that hooks INT 0x1C, was that also running in flat-mode?

That is to say - the 80x86 family run in two modes - one that has a flat address-space and the other that has segmented memory space.

When in segmented mode (DOS) there's a table that holds the address of all of the ISRs. To hook an interrupt, you simply grab the table entry you want then overwrite it with the address of your own routine. Inside your routine you do what you need, calling the original routine before, after your code or not at all. When you want to remove the hook, you simply re-write the table entry.

While in protected mode (win,linux,dos4gw/dos32a) memory is arranged quite differently. You don't have a globally accessable place that you can just read and write in quite the same way. You have the beasts known as Interrupt Descriptor Table.

I spent a long time 15 years ago trying to roll-my-own code that would enter protected mode. I've got vague memories of having trouble wrapping my head around the IDT & GDT.

What I'm getting at, is that I can't be sure that the functions you're calling are intended for flat-mode. If the ISR is running in flat-mode, you can't even address it in the 4 bytes that each entry has in a real-mode IDT.
I also don't quite follow the formula you've used to come up with int 0x76

Anyway, here's a page on IDTs and the differences between real/protected mode.
http://en.wikipedia.org/wiki/Interrupt_descriptor_table[^]

You know what I'd probably be doing? Downloading the source-code for some old games that used the dos4g/w extended and looking there for some hints. You should find something in either the timing or the sound code. The one that immediately comes to mind is Doom. Don't remember if Duke Nukem 3d was too I beleive Rise Of The Triad - ROTT used the watcom compiler. A lot of games by iD, Apogee & 3dRealms of the era used the extender.

Good luck & thanks for the read & memories. Thumbs Up | :thumbsup:

liaoo23-Jul-12 19:47

23-Jul-12 19:47

My app runs at "flat memory mode" in DOS(by DOS extender -DOS/32A). I added the sample code to hook INT 0x1C in my app then found OK ! Thus that code should be running in flat mode ^_^

Another example demonstrating if app is in flat mode maybe: if allocating memory on this mode, get the offset address of this pointer then I got 4-byte address ! ( If in real mode, the offset address will be 2byte because real mode is SEG:OFF format...)

As you said memory is arranged quite differently with dos extender BUT I think there must be handy APIs provided by DOS/32A to achieve this goal because it is a common demand...

And 0x76 comes in below statement:
"DOS/32 Advanced will install real mode IRQ callbacks for all 16 hardware interrupts (IRQ 0-7, IRQ 8-15 = INT 08-0Fh, INT 70-77h)"
Because my device use IRQ14 thus (14-8)+0x70 = 0x76 and it is the interrupt number CPU got to calculate the entry of ISR !

enhzflep23-Jul-12 20:23

enhzflep

23-Jul-12 20:23

Okay, do these help -
http://stackoverflow.com/questions/6746321/dos32-irq-handler[^]
http://stackoverflow.com/questions/6771702/dos32-extender-help-needed[^]

liaoo23-Jul-12 22:02

23-Jul-12 22:02

Thanks in advance... I will try it !

But...does it work ? Poke tongue | ;-P

Does anybody successfully use these 2 to hook HW interrupt ? Wink | ;)

Software_Developer23-Jul-12 20:10

Software_Developer

23-Jul-12 20:10

Here's some wonderful reading.

[Interrupt Service Routines]
[he WATCOM C/C++ Programmer's FAQ]
[finding a device on the PCI bus]
[PCI Device access under 32-Bit PM DOS]

there are 2 ways of finding a PCI device on the bus. You can either use the PCI BIOS interface call, or direct hardware I/O.
Here's the BIOS way:

INTEL_VENDOR_ID	EQU	8086h			; intel's unique sig #
INTEL_EXP_NIC	EQU	1227h			; sample PCI device etherexpress 10/100 NIC
.386
	mov	ax, 0b102h                      	; interrupt 1a function b102
	mov	dx, INTEL_VENDOR_ID
	mov	cx, INTEL_EXP_NIC
	xor	si, si				; 0=1st device, 1=2nd etc.
	int	1ah                              
	jc	nope

; once returned from this call, BH=bus number, BL=device/function #
nope:

liaoo23-Jul-12 22:05