baslinux AT lists.ibiblio.org
Subject: Baslinux mailing list
List archive
- From: keesan AT cyberspace.org
- To: baslinux AT lists.ibiblio.org
- Subject: [BL] xterm and -fn; WORD for DOS
- Date: Sat, 20 Dec 2003 13:11:09 -0500
>> I fixed this problem by changing from -fn 10x20 to -fn fixed or -fn
>> linux8x16. These are smaller, however, and do not fill the whole window
>> (even when I run at 640). What other fonts should I try? There is no
>> linux10x20. What I have is usable, no big deal. 10x20 might not be a
>> good default for bl2.
>>
>fonts are a huge and complex issue under Linux. I think there are some
>font how to's that might help. I'm still sorting these things out myself,
>so can't be of much help. I do know that there is a 9x18 fixed font: have
>you tried that one? (i.e., -fn 9x18 -fb 9x18bold) 100 dpi as opposed to
>75 dpi fonts might be an issue here as well: I understand the system uses
>whichever it finds first in the font path specified in XF86Config.
Do you also have to specify the bold font used? Steven's setup does not.
I will try adding -fb10x20 and see if that helps. The links (that show up
double) are in bold. Thanks. I sort of doubt that just changing 10x20 to
9x18 would fix anything. In the meantime linux8x16 does work. And I
could even set it to show more lines than 25.
>>
>> I tried to set up WORD 5.5 for DOS and the printer driver installation
>> does not work. Setup is supposed to produce drivers ending in .prd from
>> the files in .pr$ (created when you run the downloaded .exe) and does not.
>> How do I convert these myself? We were going to give a disk to the friend
>> with the broken Windows and ended up giving her Works instead today.
>>
>The .exe file just inflates the contents. To install things, you have to
>run setup.exe within the folder where stuff was inflated. Then, the dir
>"word" is created and all contents further inflated and installed, with
>legitimate extensions. Sounds like maybe you didn't run the setup.exe,
>but only the wd55_ben.exe executable.
>
I ran setup. Setup complained and would not install the printer drivers,
said it could not find them. I was installing to floppy disk. Running
the .exe creates 700K of *.pr$ files. WORD itself wants *.prd files.
How would .pr$ normally be converted to *.prd? Simply renaming did not
help. There is a PRD to TXT conversion program that did not help as it
could not find any PRD files.
I don't need to print WORD files but my friend does. Did MS deliberately
cripple the program? I also note that it expected to find the drivers in
\PRINT2\ but everything unpacked into a single directory and a few things
overwrote other things.
>James
>_______________________________________________
>BasLinux mailing list
>[27]BasLinux AT lists.ibiblio.org
>[28]http://lists.ibiblio.org/mailman/listinfo/baslinux
>
> Delete & Prev | [29]Delete & Next
> Move to: [30][(1)__INBOX.......] [31]Move
>
> [32]Take Address
-
[BL] xterm and -fn; WORD for DOS,
keesan, 12/20/2003
-
Re: [BL] xterm and -fn; WORD for DOS,
James Miller, 12/20/2003
-
Re: [BL] xterm and -fn; WORD for DOS,
3aoo-cvfd, 12/20/2003
-
Re: [BL] xterm and -fn; WORD for DOS,
keesan, 12/20/2003
-
Re: [BL] xterm and -fn; WORD for DOS,
3aoo-cvfd, 12/20/2003
- Re: [BL] xterm and -fn; WORD for DOS, James Miller, 12/20/2003
-
Re: [BL] xterm and -fn; WORD for DOS,
3aoo-cvfd, 12/20/2003
-
Re: [BL] xterm and -fn; WORD for DOS,
keesan, 12/20/2003
-
Re: [BL] xterm and -fn; WORD for DOS,
3aoo-cvfd, 12/20/2003
-
Re: [BL] xterm and -fn; WORD for DOS,
James Miller, 12/20/2003
Archive powered by MHonArc 2.6.24.