wang@ai.toronto.edu (Huaiqing Wang) (02/05/90)
Hi, everybody:
My last news about help with DOSTEX received many replies which
helped me a great deal, the most virtual replies are from:
Frank C. Robey (frc@saturn.wustl.edu)
Neil Weisenfield (weisen@eniac.seas.upenn.edu)
Although I already got DOSTEX working, now I am having a hard
time with DVIEPS. It always give me a error message like this:
"FATAL--loadchar(): Could not allocate xxxx words of raster space
--used xxxx words so far"
What is this? I defined the FONTDIR and INPUTDIR correctly.
I also got DVIVGA working as well.
Did anybody got it working? (Again!)
Any hints would be appreciated.
___________________________________________________________________________
wang@ai.toronto.edu
wang@csri.utoronto.ca
___________________________________________________________________________sbnicol@rose.waterloo.edu (Scott Nicol) (02/05/90)
In article <90Feb4.120923est.4589@neat.cs.toronto.edu> wang@ai.toronto.edu (Huaiqing Wang) writes: >Hi, everybody: > > Although I already got DOSTEX working, now I am having a hard >time with DVIEPS. It always give me a error message like this: > > "FATAL--loadchar(): Could not allocate xxxx words of raster space >--used xxxx words so far" I, too, get an error message like this on occasion. It seems to be a feeble "out-of-memory" error message. Instead of gracefully exitting, this program just crashes. I obtained (from somewhere, can't remember exactly) another version of this program that was compiled in Microsoft C, but it can't find my font directories. Oh well, off to the laser printer... - Scott Email: sbnicol@rose.waterloo.edu -or- ...!uunet!watmath!rose!sbnicol SlowMail: 546 FallingBrook Dr., Waterloo, Ont., Canada, N2L 4N4. Phone: (519) 725-1980
sekoppenhoef@rose.waterloo.edu (Shawn E. Koppenhoefer) (02/05/90)
<20528@watdragon.waterloo.edu> sbnicol@rose.waterloo.edu (Scott Nicol) writes: ><90Feb4.120923est.4589@neat.cs.toronto.edu> (Huaiqing Wang) writes: >>Hi, everybody: >> Although I already got DOSTEX working, now I am having a hard >>time with DVIEPS. It always give me a error message like this: >> "FATAL--loadchar(): Could not allocate xxxx words of raster space > I, too, get an error message like this on occasion. It seems to be >a feeble "out-of-memory" error message. Instead of gracefully exitting, I used to have exactly this problem... there is a new DVIEPS executable on simtel... maybe that one doesn't have this problem. I have a 24pin printer and when i used DVIPAN on the .dvi files it worked without a problem whatsoever (dvipan is supposed to have been a modification of dvieps i think). I'm not sure what happens if you send 24pin output to a 9 pin printer but it's worth a try i guess. Also... when i was trying to get dvieps working i cut down my environment size a *LOT* and played around with files= and buffers= in the config.sys file. Oh.. and don't do font caching.... it uses memory! (you sound like you need all you can get ...don't we all though) Why are you using DOSTEX? I'm using SBTeX and it works great! It's much newer (faster?? smaller??) than DOSTEX too! Anyway.. hope some of this helps ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| _ _ KLEIN BOTTLE for sale... Shawn E. Koppenhoefer | | enquire within. ...watmath!rose!sekoppenhoef | - ~~~~~~~~~~~~~~~~~sekoppenhoef@rose.uwaterloo.ca sekoppenhoef@rose.uwaterloo.edu
scole@sim.uucp (Steven Curtis Cole) (02/12/90)
Noticing a few messages about DVIEPS here, I'd though I'd tell you all what I've managed to accomplish with it. I got the binary in the DOSTEX distribution, and noticed memory problems as well as a few other bugs having to do with stray dots over the page. Disatisfied with its performance, I grabbed the source for the DVI drivers and recompiled with my own changes. What happens in my version: To keep memory use down, I scan each page three times, storing and printing one third of the page on each pass. The old DVIEPS I had used only two passes. Unfortunately, this increases execution time by 50%. The new version is also written for a generic IBM graphics printer, not whatever printer it was originally written for. Whatever the noise problem was disappeared in the new version. Unfortunately, the changes aren't ifdef'd very well, and I didn't feel that my changes should be submitted to the people who worry about the source for TeX. I'd be happy to contribute the source to someone who can fix it up and get it to the right people; I don't have the time now to properly take care of it. (Such is the life of a graduate student...) Note that this thing is monsterously slow. It's faster for me to upload my dvi files, and then drive to campus to use a laser printer to produce output than it is to use my poor EPSON... If you've got capability like this, spend your time getting that to work and just forget about DVIEPS... (Of course, I'm also running an old 4.77 MHz XT...) Steve Cole scole@sim.berkeley.edu