X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f From: "Rod Pemberton" Newsgroups: comp.os.msdos.djgpp References: <43E12016 DOT 2070308 AT mainstreetsoftworks DOT com> <7t88b3-d2q DOT ln1 AT news DOT infowest DOT com> <43E1863D DOT 8080308 AT mainstreetsoftworks DOT com> Subject: Re: TSR issues (with code) Lines: 85 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-IWN-Posted-By: [68.60.59.250] Thu Feb 2 01:46:39 2006 Message-ID: X-Complaints-To: abuse AT eli DOT net X-Trace: 52616e646f6d49564b835516cab6b1f728cd0aaad111e06a2859ca5fe614c2a3fdb4d17c804a296421caf04f2ab9f82156ae24623661bb78902a64656c1b4f8928a0e5db9aa91318699aed1c928502a567e402cb235c7a40cdb390a1f795d8fa5c01c7299d7f8e86a0f0123f06c50219fd7eee27eb68b0a9f729efec5af41eae50bedaea322b5a9746f2034ed9f9a0ed X-Abuse-Info: Please be sure to forward ALL headers so that we may process your complaint properly. NNTP-Posting-Date: Thu, 02 Feb 2006 08:59:36 UTC Date: Thu, 02 Feb 2006 09:02:35 GMT To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com "Brad House" wrote in message news:43E1863D DOT 8080308 AT mainstreetsoftworks DOT com... > Thanks for replying (and testing)! > I've actually not yet tested any DPMI other than cwsdpmi (I was > assuming it was me, totally). On your tests, I assume the Win98 > DosBox test used the Windows DPMI env, and the RM MS-DOS 7.10 > used cwsdpmi? Yes, and yes. DJGPP checks for a compatible installed DPMI host first (Win98SE) before starting up CWSDPMI etc. (i.e., OpenWATCOM hosts won't work.) > One other thought. I'm using DJGPP 2.04 beta with gcc 3.4.4 and > binutils-2.16.1. What versions are you running? If you're running > something other than that, could you send me the testtsr.exe that you > generated so I can verify if maybe it's my development environment? I'm running DJGPP 2.03 with (DJGPP versions of) gcc 3.4.1, binutils 2.15 (plus older versions overinstalled...) Are the versions you're running the most current? I thought gcc was upto 4.0.2 or 4.0.3 perhaps? 2.04 beta? Where is the beta? on www.delorie.com? I've seen a couple people mention it and asked DJ, but he didn't point me in the correct direction. I looked there but didn't see it...(Yes, I know I can be blind.) Getting the exe to you may be a problem. How are you expecting the exe to get to you? I don't have true email, at the moment and I am not planning on correcting that issue soon. I prefer ftp/http. I can outbound email to open newservers, send outbound email to email servers which don't confirm my PC's server identity, i.e., spam-able, (DJ email relay blocks), anonymous ftp, http-put(?), telnet(rz-sz), xx/uuencode and post... I think Winzip/PKZIP, perhaps 7-zip, now handle xx/uuencode. > Oh, and, I really don't plan on using WatcomC, we were just doing some > testing to see if that would be a feasible option if all else fails, > but I think we'd like to stick with DJGPP and GCC if at all possible > (besides DOS/4GW doesn't support protected mode TSRs, so we'd have > to see if DOS/4G is still out there). DOS/4G and CWSDPMI, PMODEDJ(pmodetsr) don't support them either. In fact, I haven't found any DPMI host for any platform which supports the DPMI 1.0 TSR calls, that includes all the DPMI 1.0 hosts. Yes, DOS/4GW, PMODEW, and others come with OW. Most of the OW crowd have switched to Devore's Causeway, Kumar's DOS/32A (not to be confused w/DOS32/A), and Japheth's HXRT. I continue to use DOS/4G and PMODEW... I think PMODEW is faster than DOS/32A. As for DOS/4G, except for one bug, it is very reliable. Most of the more advanced calls can be implement with the simple subset in DOS/4G, but people don't seem to know/care/spend the time. > Are there any suggestions you can make if all else fails? My DOS 6.22 > environment is pretty much a fresh install, I think the only thing 1) beta DJGPP 2) memory 3) DPMI host 3) DOS issue 4) ???? My first thought is to back out beta DJGPP since it is new. However, testing memory, changing the DPMI host, and switches DOS versions are probably much easier. Reentrancy can be an issue. DJGPP uses about 170 DOS, BIOS, DPMI calls. OW 1.3 uses about 100. I don't know about OpenWatcom 1.4. I've been intending to download it, but I suspect not much has been done for DOS. I've written a couple of DJGPP TSR's. They all work well, except int 0x21. When it comes to int 0x21, everything works except one interrupt call. They lockup on DOS exec, int 0x31, ah=4b00. I don't know how to workaround that issue. Hopefully, it is something I forgot or implemented incorrectly with reentrancy or locking... perhaps PSP, perhaps not saving/restoring the SDA... I don't know. I found it easier to just write DOS TSR's in NASM, so I haven't returned to the issue. I boot into DOS clean, and use different batch files for OW, DJGPP, etc. I use a less popular device driver loader, P. Frost's DDL, to get the drivers loaded after I'm at the command prompt. The Freedos crowd uses something similar (asleep, don't recall). Rod Pemberton