c++ - dmc, interrupts, TCP/IP and memorymodel
- kvleonhardt (18/18) May 29 2012 Hi
- Walter Bright (3/21) Jun 15 2012 What you could do is get the full DMC package, which includes the comple...
Hi I am writing an application where I need following features: * Running on DOS with DOS extender (Right now testing with HX Dos extender) * A lot of memory. > 1 MB * TCP/IP stack * Writing own ISR I have some troubles combining all this. If I want to use the TCP/IP stack comming with DMC (Winsock) I need Win32 memory model. But that excludes the use of dos_getvect and dos_setvect :-( I tried to compile WaterlooTCP with DMC, but I have the same problems with the interrupt vector functions, as I need "flat" memory model which is the Waterloo TCP's name for Win32 memory model. This was my original favorite, to avoid winsock. Waterloo TCP: http://home.broadpark.no/~gvanem/ Before I try to write my own get_vect and set_vect functions, I would like to hear if I am on the wrong track. BR kvleonhardt
May 29 2012
On 5/29/2012 11:33 PM, kvleonhardt wrote:Hi I am writing an application where I need following features: * Running on DOS with DOS extender (Right now testing with HX Dos extender) * A lot of memory.> 1 MB * TCP/IP stack * Writing own ISR I have some troubles combining all this. If I want to use the TCP/IP stack comming with DMC (Winsock) I need Win32 memory model. But that excludes the use of dos_getvect and dos_setvect :-( I tried to compile WaterlooTCP with DMC, but I have the same problems with the interrupt vector functions, as I need "flat" memory model which is the Waterloo TCP's name for Win32 memory model. This was my original favorite, to avoid winsock. Waterloo TCP: http://home.broadpark.no/~gvanem/ Before I try to write my own get_vect and set_vect functions, I would like to hear if I am on the wrong track. BR kvleonhardtWhat you could do is get the full DMC package, which includes the complete library source. Then, you could modify it to suit.
Jun 15 2012