> Next problem: I tried to get printer support via USB (currently they
> use classic LPT, but those printers get very rare).
Indeed they are. And many modern printers use protocols that aren't compatible
with old DOS programs.
> But as soon as I load the basic USBUHCI driver, the USB-stick is
> Because I felt that the world needed another DOS text editor, I have
> spent past month's evenings on a new project named SVED.
> SVED (short for "the SvarDOS editor") is designed for basic editing
> of configuration files and such. It is NOT meant to be a full-
> featured text editor. On the
> is it possible in DOS (using BIOS?) to implement a tsr or so which allows the
> following:
>
> holding a key longer to return a SHIFT-key on screen?
>
> Example:
>
> press key »a« and HOLD the key for e.g. 500 milliseconds,
> => print shift-a = »A« on screen.
You might be able to do
> It has been a very long time. But, if I recall correctly, I’m fairly sure
> you
> can programmatically change the LEDs as well. But, I don’t recall the
> details. But, I might have code sitting around somewhere that has that
> functionality.
The LED status is contained in the BIOS Data
FYI, in MS-DOS divided the Internationalization aspect into four different
subcategories: Keyboard Layout, Code Page, Country, and Language (which also
includes dialects). While they all overlap and inter-relate to some degree,
they are distinct and are all handled separately. The more
> I'm thinking about doing a video that shows how to do real work on
> DOS. I sometimes see comments on YouTube with people asking "could
> you really do *work* with DOS?" And the answer is of course you can,
> that happened every day.
>
> So I'm collecting a list of things you'd do in the 80s
> I did not catch how to do LPT interrupt, real and protected mode. It
> would be a great help if there is an example.
> I work with watcom and realized it, but only once, then the ISR is
> never called again.
> May be LPT is not very often used.
It would help to know exactly what you're trying
My understanding is that there are two major differences between POP and IMAP.
The first is that POP only allows one-way communication (downloading from the
server to the client) so there is no synchronization mechanism. If you
download the same e-mail to multiple devices, each one can be set
> The driver providing an issue is one called vide_cdd
I found this reference to the file:
https://www.vogonswiki.com/index.php/VIDE-CDD.SYS
It doesn't mention any compatibility issues, but does say it's very small
compared to most other drivers which may be why it has problems (there might
> The comparability issue is not in vied_cdd.sys
> It is in the dectalk drivers itself.
> I have the hardware driver for my cd and DVD rom drives, when
> vide_cdd.sys is run, it references the hardware drive in its command.
I looked up a little bit about DECtalk. It looks like the earlier
Karen:
Do you know which of the two CD-ROM drivers you are having trouble with?
It takes two drivers to install a CD in DOS. One is the hardware-specific
driver that may come with the CD hardware itself, but there are also several of
them (like OAKCDROM.SYS) that will work with different
> What I'm wondering is if the following (piping into a .BAT) is
> considered acceptable or "standard" for DOS.
>
> "prog1.exe | %COMSPEC% /c work.bat | %COMSPEC% /c fixups.bat
> some.txt"
>
> Does that work like I'd expect? (Seems to ... barely.) Is it rare?
> Is it buggy? Is there a better way?
I don't know of a DOS program to do specifically what you're asking. But this
reminds me of the old commercial DOS program called SIDEWAYS that was designed
to take text-based printer output from Lotus 123 and print it sideways
(commonly called Landscape mode nowadays). I think it also worked
13 matches
Mail list logo
