Article View: comp.os.msdos.programmer
Article #3359TD/386 woes...
From: todd j. derr
Date: Fri, 06 Nov 1992 05:03
Date: Fri, 06 Nov 1992 05:03
29 lines
1566 bytes
1566 bytes
I have had NO success trying to use TD/386. Problem was that port 21h was getting changed somewhere and I couldn't figure out where, when it occurred to me, "hey, this is a prefect job for TD386"... So, I put it's driver in CONFIG.SYS, fire it up, set break on out to port 21, run. boom. GP fault. So, I strip down CONFIG and AUTOEXEC, try it again, same thing. So, my (minimal) config is: STACKER 2.0 TDH386.SYS and nothing else... TD386 seems like it could be a very useful tool for problems like this, but it doesn't do me much good the way it is... This hasn't been the first time that TD386 has failed; it also failed me in a similar situation, but last time I wrote it off because I meant for the breakpoint (another port access) to happen within the ROM BIOS, so I figured that that might cause some problems. This time, I have no idea whatsoever why it wouldn't work. I got all the patches to BC++ 3.1 I could find, none of them seem to pertain to TD, so... ideas, anyone? todd "before I get REALLY upset..." derr -- todd j. derr - the c.o.m.a. moderator! infidel+@pitt.edu (412) 363-9027 infidel@pittunix (BIT) work: 648-1247
Technical Details
Message-ID:
<9211@blue.cis.pitt.edu.UUCP>Path:
arc1-ca.pugleaf.net!sparky!uunet!gumby!wupost!zaphod.mps.ohio-state.edu!pitt.edu!infidelShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!gumby!wupost!zaphod.mps.ohio-state.edu!pitt.edu!infidel From: infidel+@pitt.edu (todd j. derr) Newsgroups: comp.os.msdos.programmer Subject: TD/386 woes... Message-ID: <9211@blue.cis.pitt.edu.UUCP> Date: 6 Nov 92 05:03:45 GMT Sender: news+@pitt.edu Organization: university of pittsburgh cis Lines: 29 Originator: infidel@unixd2.cis.pitt.edu