ghost@aladdin.com (L. Peter Deutsch) (07/17/89)
1) Snoopy is right about the reason for the crash when you type .123.
The fix I prefer is to insert the line
dval = 0;
just before the
goto ff;
in iscan.c at approximately line 351. But I think his fix works too.
2) Snoopy is also right (gawd, it's awful dealing with someone who's right
all the time) about the reason that the DOS executable crashes.
I was in such a hurry to put out the release before I left town that
I accidentally distributed an executable that only runs on 80386 systems.
A revised executable is on its way.
- P. D.
ghost@aladdin.com
...{uunet,parcplace.com}!aladdin!ghost
P. O. box 60264, Palo Alto, CA 94306Leisner.Henr@XEROX.COM (marty) (07/18/89)
Where is there an uncorruped DOS executable available on the net? (the tar file on prep.ai.mit.edu contains one with the wrong size). marty ARPA: leisner.henr@xerox.com GV: leisner.henr NS: leisner:wbst139:xerox UUCP: hplabs!arisia!leisner
rds95@leah.Albany.Edu (Robert Seals) (07/18/89)
In article <whatever> L. Peter Deutsch writes: > 2) Snoopy is also right about the reason that the DOS executable crashes. > I was in such a hurry to put out the release before I left town that > I accidentally distributed an executable that only runs on 80386 systems. Are you sure? I have a 386+387 that the distributed executable don't work on. And another thing (smiley) - thanks for putting together ghostscript!! It's groovy. But I have a complaint. The compiling scheme is just dumb. I have a hard disk named "d:". Yes, I can edit the .bat files (and I do), but I very rarely get a correctly functioning executable. Ever since v1 (the first release wasn't numbered, I don't think), I sometimes get this weird glitch where every file gets warning messages about structure members which don't exist. There MUST be a cleaner way to get gs compiled on a DOS system. And a suggestion: is there a way to isolate the physical device output routines so that I can use my nifty Whizzo graphics board and monitor? If I could just plug in my own "draw a dot" routine, then we wouldn't necessarliy be limited to 640x350x1. I seem to recall a fair amount of device dependence in the code, but I haven't scrutinized it since early versions. And more stuph: I see that ghostscript fonts are on the official gnu "things to make and do" list. I wish I knew more about fonts, cuz this is really a must. I do know a good amount about writing (reasonably portable) C code, so if you'd like my help, I'd be happy to assist. I am, after all, one of those leftist gnu-adherents. rob
snoopy@sopwith.UUCP (Snoopy) (07/20/89)
In article <8907170530.0.UUL1.3#5127@aladdin.com> ghost@aladdin.com (L. Peter Deutsch) writes: |1) Snoopy is right about the reason for the crash when you type .123. |The fix I prefer is to insert the line | dval = 0; |just before the | goto ff; |in iscan.c at approximately line 351. But I think his fix works too. I prefer putting it right before the goto ff also, it is slightly more efficient that way. I was too tired and/or lazy that evening to analyse whether or not there was some case that would slip through doing it the efficient way, so I went for the safe but slightly less efficient fix. |2) Snoopy is also right (gawd, it's awful dealing with someone who's right |all the time) Would it help if I shipped you a copy of my driver for the Ramtek graphics terminal that doesn't work at all? :-) _____ .-----. /_____\ Snoopy ./ RIP \. /_______\ qiclab!sopwith!snoopy | | |___| parsely!sopwith!snoopy | tekecs | |___| sun!nosun!illian!sopwith!snoopy |_________| "But we're only up to the fourth inning."
snoopy@sopwith.UUCP (Snoopy) (07/20/89)
In article <1910@leah.Albany.Edu> rds95@leah.Albany.Edu (Robert Seals) writes: | There MUST be a cleaner way to get gs compiled on a DOS system. So think of one and either post it or mail it to Peter. Building gs under UTek is great fun also, as Peter used some Sun extensions which aren't exactly universal. |And a suggestion: is there a way to isolate the physical device output |routines so that I can use my nifty Whizzo graphics board and monitor? They *are* isolated. There is a set for IBMPC-EGA and a set for X-windows. I have sets for Tek61vp02 and dot-matrix in Beta test, and a couple of others in progress. Someone did a set for SunView. |If I could just plug in my own "draw a dot" routine, then we wouldn't |necessarliy be limited to 640x350x1. I seem to recall a fair amount of |device dependence in the code, but I haven't scrutinized it since early |versions. Any program that creates graphics output is going to be device dependent. Remember what Ghostscript *is*. Its mission is to take device independent (more or less) PostScript code and display it on a particular device. The trick is to isolate it so that new "device-drivers" or "back-ends" or whatever you want to call them can be added. Peter has done a pretty good job of this. You should be able to hack things for your Whizzo graphics board and monitor without too much grief, especially now that Peter has written some documentation for the interface. |And more stuph: I see that ghostscript fonts are on the official gnu |"things to make and do" list. I wish I knew more about fonts, cuz this |is really a must. I do know a good amount about writing (reasonably |portable) C code, so if you'd like my help, I'd be happy to assist. |I am, after all, one of those leftist gnu-adherents. Len is starting up a small mailing list for people working on fonts. If you would like to be on it, send mail to wheaties.ai.mit.edu!tower. _____ .-----. /_____\ Snoopy ./ RIP \. /_______\ qiclab!sopwith!snoopy | | |___| parsely!sopwith!snoopy | tekecs | |___| sun!nosun!illian!sopwith!snoopy |_________| "But we're only up to the fourth inning."