home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os2.apps
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!ames!agate!spool.mu.edu!yale.edu!ira.uka.de!math.fu-berlin.de!informatik.tu-muenchen.de!rommel
- From: rommel@Informatik.TU-Muenchen.DE (Kai-Uwe Rommel)
- Subject: Re: IOPL=NO locks system
- References: <Bxv7wD.4Jv@helios.physics.utoronto.ca> <17NOV199211325491@cl2.cl.uh.edu>
- Sender: news@Informatik.TU-Muenchen.DE (USENET Newssystem)
- Organization: Technische Universitaet Muenchen, Germany
- Date: Wed, 18 Nov 1992 08:33:10 GMT
- Message-ID: <1992Nov18.083310.25504@Informatik.TU-Muenchen.DE>
- Lines: 29
-
- In article <17NOV199211325491@cl2.cl.uh.edu> CSCI19DC@cl.uh.edu writes:
- >In article <Bxv7wD.4Jv@helios.physics.utoronto.ca>, karls@aurora.physics.utoronto.ca (Karl Schroeder) writes...
- >>Do the new ET4000 drivers bundled with the SP require IOPL=YES? It would
- >>seem so from my experience. The system locks on load of PM if I change
- >>IOPL to no.
- >> This is the only oddity I've found with the full SP installation. My
- >>problems with lockup of dos and os2 windows may have been due to the fact
- >>that after first installing the SP, I continued using the Trident 16-bit
- >>driver. Maybe the hardware couldn't cope; but with an ET4000 card, the
- >>graphics fly.
- >> My system: 486/33, 8 meg, 120 meg IDE.
- >
- >Sorry I cant give you some kind of answer, Karl.
- >
- >I just wanted to post and say that this also occurs with the WIN31-32BIT GRE
- >Beta, at least on my PC Clone.
-
- I have reported this here (rather in comp.os.os2.misc) before: the IOPL
- line needs at least to contain the name of the display driver, which is
- no longer DISPLAY.DLL. In case of a 8514/A it is IBM8514, in case of VGA
- it is IBMVGA32, in case of ET-4000 32-bit drivers it is IBMDEV32.
-
- Kai Uwe Rommel
-
- /* Kai Uwe Rommel --- rommel@informatik.tu-muenchen.de */
-
- DOS ... is still a real mode only non-reentrant interrupt
- handler, and always will be. -Russell Williams
-
-