[comp.archives] [folklore] Re: BESM-6; hyphenation; turning machines off

DLV@CUNYVMS1.BITNET (09/23/90)

Archive-name: cyrillic-fonts/22-Sep-90
Original-posting-by: DLV@CUNYVMS1.BITNET
Original-subject: Re: BESM-6; hyphenation; turning machines off
Archive-site: listserv@ubvm.cc.buffalo.edu
Reposted-by: emv@math.lsa.umich.edu (Edward Vielmetti)


Ed Vielmetti said:
>>Another related TeX font is the CMCYR set developed by Alexander Samarin and
>>Nana Gonti at the Institute for High Energy Physics in Protvino, USSR. It
>includes only Russian letters (WMCYR has Ukrainain, Serbian, et al letters,
>>as well as yat', fita, and izhitsa), but they look better then WNCYR.
>If you're going to be hip these days, you have to give e-mail addresses
>in Protvino and an FTP site for the fonts.

Sorry! My omission.

Samarin can be reached (not very reliably) at SAMARIN@VXCERN.DECNET.CERN.CH.
There's a leased line between Protvino and CERN. :)

One way to get this stuff (for those of us who can't FTP) is to send e-mail
to LISTSERV@UBVM.CC.BUFFALO.EDU, whose body says: GET CMCYRMF PACKAGE. The
files will be mailed to the address in your From: field. If Internet doesn't
understand what's in your From: field (as is the case with these .SU
addresses), you can say: GIVE CMCYRMF PACKAGE user%domain.SU@RELAY.EU.NET or
some such. Other files of interest are WNCYRMF PACKAGE (U of Washington
fonts, ligature-compatible with the old MCYR), and RUSTEX-L FILELIST (list
of all files, including Russian hyphenation patterns, and mailing list
archives.

Large subsets of this are available for anon FTP from at least 2 sites whose
names I can't recall for the life of me. :) However this information *has*
been posted to comp.archives once, I'm certain. :) :) :)

---

Speaking of turning off computers, I'd like to tell about my experiences
with OS/2. I write a lot of programs for a client on a 386 machine that runs
OS/2 and acts as a network server. Every once in a while the whole system
halts with a messsage similar to "Single step interrupt in system code" and
needs to be rebooted. OS/2's file structure is similar to MS DOS's, so this
procedure typically leaves a few "lost" clusters (i.e., disk clusters that
are marked as allocated, but don't belong to any files). This happens with
DOS too if you reboot while you have open files. Under DOS this is fixed
very easily by issuing CHKDSK/F. Under OS/2 this doesn't work, because C:
disk has open files on it (swap file, harderr.sys, et al). So, I have to
first boot MS DOS from a floppy in drive A: and do DOS's CHKDSK C:/F (this
is Compaq DOS, which supports large partitions), and only then reboot OS/2.

This helps deal with another OS/2 problem---uncontrollable growth of the
swap file. I have 9MB of RAM, and the swap file normally runs about 6MB, but
sometimes, when I load several programs, or edit a huge file, it increases
(say... 20MB), and it never shrinks, and it can't be touched while OS/2 is
running. Once, an erroneous C program died an out-of-bounds error, but
nevertheless caused the swapfile to take up all available disk space. When I
boot DOS, I also erase the swapfile.

I guess there's a moral in this having to keep around a DOS diskette to keep
OS/2 running...

PS/2 --- half a computer
OS/2 --- half an operating system for half a computer

Dimitri Vulis
CUNY GC Math