New answers tagged


To get your mouse working under DOS, you can try Bret Johnson’s USB programs — you’ll need one of the USBUHCI drivers, USBMOUSE, and CuteMouse. Given how USBMOUSE works, it might also allow Windows 98 to use it, but I haven’t tried that.


Several of the approaches listed in the answers to Why did MS-DOS applications built using Turbo Pascal fail to start with a division by zero error on faster systems? should work; in particular, c’t’s patch, which includes a working Delay routine, or one of the Pascal fix TSRs.


Surprisingly, googling "Runtime error 200" yields this, which still refers to the defunct Altavista: Borland: Runtime Error 200 - 'Divide by 0' Applications that use the CRT unit may generate this error message when running on very fast machines (i.e. Pentium Pro 180 and above). The cause of this error is a timing loop that occurs as part of the ...


If you could use Java on Windows 3.1 there is a SSH client written in pure Java that would work. I use one on a desktop Java system that has been running for 12 years on Windows to avoid having an SSH tunnel. If it works on an old version of Java that still runs on 3.1 is another question.


When the Sound Blaster was first introduced, the documented way to use the digitized audio features was to make use of a supplied blob of code which was supplied by Creative Labs. If memory serves, using this blob of code required reading it into RAM at a multiple-of-16 address, and invoke it with a normalized form of that address (offset zero of whatever ...


Summary: Real Sound Blasters don't need a driver to initialise or support them. Clones may need one-time initialisation. Exotic cards may need memory-resident translation layers. Games use a collection of per-card drivers to 'talk' to the appropriate hardware interfaces. These can be hard-coded into the game, or a collection of external files like in HMI ...


Most PCI soundcards do not have hardware support for games and other applications that expect a SoundBlaster or AdLib to be present. Older cards made a special effort to provide what's known as "register level compatibility", so they could be used with a wide range of existing games. By the time PCI arrived, Windows had become the PC operating ...


Like any hardware, the hardware of a sound card needs to be “prepared for operation” after having powered up in an unconfigured state. Usually this consists of writing certain values to certain hardware ports and/or memory addresses (after testing for the presence of said sound card). After this, the sound card is ready for operation. In Windows or any other ...


The typical way to provide "driver" services to other programs in DOS is to run a TSR (Terminate and Stay Resident) program installing a software interrupt vector such that running DOS programs could invoke this INT for services (see Ralph Brown's Interrupt List). In the sound context, however, programs would typically do the device I/O directly by ...

Top 50 recent answers are included