FAQ: GDOS drivers 1.9

Gerd Castan

unread,

Mar 30, 1994, 2:57:34 AM3/30/94

to

Perhaps I posted version 1.8 with the title:
"Everything you wanted to know about GDOS".
I didn't want tu use the same title as Douglas N. Wheeler. Sorry.

#################### cut here ########################

Everything you wanted to know about GDOS drivers

(but were afraid to ask)*

Version 1.9

Gerd Castan **

3.3.1994

________________________________
* (c) by Woody Allen ;-)
** English translation by Stefan Damerau (stefan_...@sl.maus.de)

German version posted in de.comp.sys.st und maus.gui.gem.
English version posten in comp.sys.atari.st

Contents

1 Technical Info
2 Introduction
3 Motivation
4 Changes
5 VDI Drivers
5.1 Ink Printers
5.2 9pin drivers
5.3 24pin drivers
5.4 Laser drivers
5.5 Atari laser drivers
5.6 Screen drivers
5.6.1 LineA
5.6.2 Setscreen & Getscreen
5.6.3 NVDI and WARP 9
5.7 Other drivers
5.7.1 Memory drivers
5.7.2 Plotter drivers
5.8 What's missing
6 Errors
7 Fonts
7.1 General
7.2 Bitmap fonts
7.3 Vector fonts
8 printer
8.1 List of availability
9 Programs
10 Utilities
10.1 fontfix
10.2 Outline Fonts
10.3 Printer Driver
10.4 ASSIGN
10.5 FONTCHK
10.6 FONTCNV
10.7 GEMFont
10.8 FontMonger
10.9 Font ID
11 Distribution
11.1 Atari
11.2 BELA
11.3 FontGDOS
11.4 Language
11.5 Internet
11.6 Working Title
11.7 Speedo drivers
11.8 Speedo 4.2
11.9 COMPO
11.10 IMG-0300
11.11 Others
11.12 FTP
12 Source
13 Tips'n Tricks
13.1 Pixeltrash at printing, advice for users
13.2 NEC P6+
14 Tips'n Tricks for coders
14.1 Fontsize and Pixelsize
15 Addresses
16 Miscellaneous
16.1 Critics
16.1.1 Critics to the author
16.1.2 Critics to the translator
16.2 Praise
16.3 For my support
16.4 Trademarks
17 Appendix
17.1 Literature

1 Technical Info

My email address will change more than once next time. Due to this reason I
have an alias, forwarding my mail to my actual location - and if it's in
the MAUS Net: G.Ca...@physik.uni-stuttgart.de

For easy location of this document at servers and mailboxes, I ask for
using the following name(s) and saving the ascii AND TeX versions:
FILENAME=
gdosi19e (english version)
gdosinf19e (when using UNIX) CR+LF should be used when saving at
UNIX-Fileservers too, not just LF

2 Introduction

Actually I'm writing a program, that makes his print out via GDOS. Looking
for printer drivers I faced the problem, that many times no documentation is
included to the drivers.

Otherwise it may happen that there are different drivers with the same name.

Here I have briefly collected my experiences with printer drivers.

This collection doesn't generally want to describe coders how to use
printer drivers (except to problems not mentioned in literature). And you
wont find information about the concept or how to install printer drivers.
To get this refer to the list at the end of this FAQ.

What I want to exclaim here is more information about the several drivers:

o Where are the drivers available?
o How to distinguish them?
o What are the problem with them?
o Which drivers can be used for certain printers?

If anybody has more experience or questions, please write me. I will face
the work to update this FAQ.

Credits:
Kay Prisille (MIGRAPH-Products, Calligrapher lite)
Julian Reschke (IMG-0???)
Volker Ritzhaupt
Jürgen Voorgang (Working Title - Products)
Herwig Schelauske (Installation of GDOS, Name-conventions)
Normen Kowalewski (Font-GDOS)
Erik Dick (SpeedoGDOS)
Patrick Dubbrow
Ulrich Rossgoderer (WYSIWYG)
Stefan Hintz (CHARLY IMAGE)
Ulli 'Huhu' Ramps, Christian Nieber (Speedo 4.2)
Mickey Boyd (reviewing parts of the translation)

Gerd Castan.

3 Motivation

With GDOS it took me 2 hours of coding, to get the screen-output to the
printer in maximum quality. And (almost) with no extra work I get output to
printers I even don't know.

If there's anybody who wants to write a program with printing options, he
should better care of the main job of the programm.

Nobody wants to pay for printer drivers if there's another program that
didn't take the coder extra work with such stuff making this program less
expensive (and surely better).

The User has - besides the lower price - another advantage. If he uses
several programs he needs place for the driver and the fonts only one time on
the disc.

SpeedoGDOS is available from Atari shops (Atari Competence Center in Germany)
now.

The (qualified) feedback to my FAQ has - compared to last autumn - raised
remarkable. Due to Speedo the interest in GDOS coming from the coders seems
to be bigger.

4 Changes

New chapters/infos are marked with '+', changed ones with '*'. Smaller
changes aren't marked.

+ Pegasus, Riemann II, CHARLY IMAGE, rho-Analyse
+ SLM_HS.SYS
+ Speedo 4.2 (Drivers)
+ Font-ID
* Phonenumbers in ISO style
* Screendrivers: bitmap-fonts
* WARP 9
* Monoklin
* Bitmap fonts
* Note to ink printers

5 VDI-Drivers

In this table I have listed distributor, errors and useable fonts.

5.1 Ink Printers

________________________________________________________________________
| Name |Date |Length |Distributor |Errors | Others | Fonts |
|___________|_________|_______|____________|_1_|_2_|________|__________|
| BJ10E |20.11.90 | 45917 | WT | | | |NC |
| BJ10 |20.11.85 | 45919 | CL | | | |NC |
| BJ10 |28.08.91 | 45660 | BELA | | | |NC |
| BJ10 |27.01.92 | 59715 | FontGDOS,I | | n | |NC, OTL |
| BJ10 |28.01.93 | 61428 | Speedo | | n | |NC, SPD |
| BJ10 |02.07.93 | 63496 | Speedo 4.2 | | n | |NC, SPD |
| HP_LJET |22.02.89 | 45512 | BELA | | | p.g. | LS |
| HP_LASER |25.09.89 | 36928 | Atari,I | | | |LS |
| LASERJET |06.03.91 | 54517 | Atari | | | |LS |
| LASERJET |27.01.92 | 60194 | FontGDOS,I | | n | |LS, OTL |
| LASERJET |28.01.93 | 61907 | Speedo | | n | |LS, SPD |
| LASERJET |02.07.93 | 64408 | Speedo 4.2 | | n | |LS, SPD |
| HPL150 |12.04.86 | 51541 | wt | | |150dpi | LL |
| HPL300 |24.04.86 | 51541 | CL,wt | | | |LS |
| DESKJET |13.05.92 | 45637 | BELA | | | p. |LS? |
| DESKJET |14.05.91 | 46040 | CL,WT | | | p. |300x600 |
| DESKJET |06.03.91 | 54285 | Atari,I | | | |LS? |
| DESKJET5 |14.05.91 | 46040 | CL,WT | | | delta |LS |
| DJ5 |27.01.92 | 60600 | FontGDOS,I | | n | |OTL |
| DJ5 |28.01.93 | 62251 | Speedo | | n | |SPD |
| DJ5 |02.07.93 | 64319 | Speedo 4.2 | | n | |SPD |
| MT90 |21.12.90 | 44881 | BELA | | |180dpi | SP |
| PAINTJET |27.01.92 | 60005 | FontGDOS | | n | |SP, OTL |
| PAINTJET |28.01.93 | 61648 | Speedo | | n | |SP, SPD |
| PAINTJET |02.07.93 | 63642 | Speedo 4.2 | | n | |SP, SPD |
| PAINTJET |14.08.92 | 60173 | I | | | |SP, OTL |
|_PAINTJET__|13.10.91_|_45934_|_WT_________|___|___|________|SP________|

Note: The drivers named HP_LJET and DESKJET can be used for (HP-compatible)
ink and laser printers. The difference is in the transfer to the printer:
Packed (p.) or not packed (n.p.). 'Delta' means that the data is delta
packed.

PAINTJET is a color driver with 8 colors.

MT90 is made by Patrick Dubbrow.

Using ink drivers produces a problem with bitmap fonts. Using 300dpi all is ok.
But 360dpi fonts are optimised for best efforts with pin printers having thick
pins. Using ink printers makes the fonts look much too thin.

Solution: either use 300 [ 600, 1200 :-) ] or exclusively use vectorfonts

5.2 9pin-drivers

________________________________________________________________________
| Name |Date |Lenght |Distributor |Errors | Others | Fonts |
|___________|_________|_______|____________|_1_|_2_|________|__________|
| FX240DPI |22.12.89 | 45396 | BELA | y | | |SR |
| FX80 |22.12.89 | 45396 | BELA,wt | n | | |EP |
| FX80_2 |12.06.91 | 45396 | I | | | |EP |
| FX80 |24.09.91 | 45525 | CL | | | |EP |
| FX80 |16.12.87 | 45396 | Atari | n | | |EP |
| FX80 |27.01.92 | 59236 | FontGDOS,I | n | n | |EP, OTL |
| FX80 |28.01.93 | 61111 | Speedo | | n | |EP, SPD |
| FX80 |02.07.93 | 63177 | Speedo 4.2 | | n | |EP, SPD |
| FX80HIGH |22.01.89 | 44730 | Atari,I | n | | |SR |
| FX80_QD |24.09.91 | 45525 | WT | | | |EP |
| NX1000 |27.01.92 | 58719 | FontGDOS | n | n | |EP, OTL |
| NX1000 |28.01.93 | 60723 | Speedo | | n | |EP, SPD |
| NX1000 |02.07.93 | 62717 | Speedo 4.2 | | n | |EP, SPD |
| NX1000 |14.08.92 | 58887 | I | | | |EP, OTL |
| OKI20 |27.01.92 | 58491 | FontGDOS | n | n | |EP, OTL |
| OKI20 |28.01.93 | 60495 | Speedo | | n | |EP, SPD |
| OKI20 |17.03.93 | 60511 | Speedo 4.2 | | n | |EP, SPD |
| OKI20 |14.08.92 | 58659 | I | | | |EP, OTL |
| SMM804 |16.12.87 | 44801 | Atari | | | |LB |
| SMM804_2 |16.06.91 | 44801 | I | | | |LB |
| SMM804 |27.01.92 | 59201 | FontGDOS,I | | n | |LB, OTL |
| SMM804 |28.01.93 | 61076 | Speedo | | n | |LB, SPD |
|_SMM804____|02.07.93_|_63142_|_Speedo_4.2_|___|_n_|________|LB,_SPD___|

Note: FX80HIGH prints normal text twice, FX240DPI once, FX80_QD printer in
quad density.

NX1000 and OKI20 are color drivers with 8 colors

5.3 24pin drivers

________________________________________________________________________
| Name |Date |Lenght |Distributor |Errors | Others | Fonts |
|___________|_________|_______|____________|_1_|_2_|________|__________|
| EPSON360 |04.04.90 | 45619 | BELA | y | | |NC |
| EPSON360 |16.09.92 | 45547 | WT | | |180x360 | |
| EPSLQPAR |14.02.91 | 44939 | I | | | | |
| LQ570 |28.01.93 | 62051 | Speedo | | n | |SPD |
| LQ570 |02.07.93 | 64228 | Speedo 4.2 | | n | |SPD |
| NB15 |22.12.89 | 44881 | BELA,wt | n | | |SP |
| NB15 |16.12.87 | 44881 | Atari,CL | n | | |SP |
| NB15_2 |12.06.91 | 44881 | I | | | |SP |
| NB15 |27.01.92 | 59121 | FontGDOS,I | n | n | |SP, OTL |
| NB15 |28.01.93 | 60989 | Speedo | n | n | |SP, SPD |
| NB15 |02.07.93 | 63055 | Speedo 4.2 | n | n | |SP, SPD |
| NECP6 |12.04.80 | 45199 | wt | | | |NC |
| NECP6 |10.04.91 | 45619 | BELA | y | | |NC |
| NECP6 |06.02.86 | 44906 | Atari,I | y | | |NC |
| NECP6_2 |28.06.91 | 46557 | I | | | |NC |
| NECP |27.01.92 | 59516 | FontGDOS | y | n | |NC, OTL |
| NECP |28.01.93 | 61229 | Speedo | | n | |NC, SPD |
| NECP |02.07.93 | 63297 | Speedo 4.2 | | n | |NC, SPD |
| NEC_P |14.08.92 | 59516 | I | | | |NC, OTL |
| P24M |08.04.89 | 47104 | I | | | | |
| P24ML |08.04.89 | 47104 | I | | | | |
| P24MWID |08.04.89 | 47104 | I | | | | |
|_P24MWIDL__|08.04.89_|_47104_|_I__________|___|___|________|__________|

5.4 Laser drivers

________________________________________________________________________
| Name |Date |Lenght |Distributor |Errors | Others | Fonts |
|___________|_________|_______|____________|_1_|_2_|________|__________|
| RICOH12 |23.06.92 | 45438 | WT | | |400dpi | |
| HP_LJET |22.02.89 | 45512 | BELA | | | n.p. |LS |
| HP_LASER |25.09.89 | 36928 | Atari,I | | | |LS |
| LASERJET |06.03.91 | 54517 | Atari | | | |LS |
| LASERJET |27.01.92 | 60194 | FontGDOS,I | | n | |LS, OTL |
| LASERJET |28.01.93 | 61907 | Speedo | | n | |LS, SPD |
| LASERJET |02.07.93 | 64408 | Speedo 4.2 | | n | |LS, SPD |
| HPL150 |12.04.86 | 51541 | wt | | |150dpi | LL |
| HPL300 |24.04.86 | 51541 | CL,wt | | | |LS |
| DESKJET |13.05.92 | 45637 | BELA | | | p. |LS |
| DESKJET |14.05.91 | 46040 | CL | | | |LS |
| DESKJET |06.03.91 | 54285 | Atari,I | | | |LS |
| CANONLBP |26.09.89 | 36980 | Atari,I | | | |LS |
| LBP |13.01.92 | 45453 | WT | | | |LS |
| SLM804 |12.04.91 | 47496 | BELA | | n | |LS |
| SLM804 |16.12.87 | 45788 |Atari,I,CL,wt| | y | |LS |
| SLM |12.12.90 | 48399 | Language | | | |LS |
| SLM |27.01.92 | 60036 | FontGDOS,I | | n | |LS, OTL |
|_SLM_______|28.01.93_|_61911_|_Speedo_____|___|_n_|________|LS,_SPD___|

5.5 ATARI laserdrivers

________________________________________________________________________
| Name |Date |Lenght |Distributor |Errors | Others | Fonts |
|___________|_________|_______|____________|_1_|_2_|________|__________|
| SLM804 |12.04.91 | 47496 |BELA | | n | |LS |
| SLM804 |16.12.87 | 45788 |Atari,I,CL,wt| | y | |LS |
| SLM |12.12.90 | 48399 |Language | | | |LS |
| SLM |27.01.92 | 60036 |FontGDOS,I | | n | |LS, OTL |
| SLM |28.01.93 | 61911 |Speedo | | n | |LS, SPD |
| SLM |02.07.93 | 63987 |Speedo 4.2 | | n | |LS, SPD |
|_SLM_HS____|_________|_______|ROM_________|___|_n_|________|LS,_SPD___|

SLM_HS is a SLM driver for Falcon.

5.6 Screen drivers

The screen is (if VDI functions are used) seen as an output device just
like printer, plotter etc. That's why fonts for the screen can be installed
in ASSIGN.SYS just like for printers.

Normally this isn't remarked because the drivers are in ROM. But they can be
used like printer drivers.

Note: For Systemfonts only (like the original ones) non proportional fonts
with a 8*8 or 8*16 matrix can be used. That's limited by the AES not VDI.

With newer AES (from 4.0?) it's no problem to use fonts of free choice
(Variable AE_FONTID and AE_FONTSIZE in GEM.CNF, see [15]). Coders should
make sure their programs can take that. (even like scrollbars of free width)

Bitmap fonts not assigned for screen driver 1 are not available for other
screen drivers.

5.6.1 LineA

The so called LineA-routines are subprograms of the screen drivers from the
ST series, to be treated as undocumented. This is the hardware depending part of
the drivers.

The attentive readers discovers it: Exchanging the drivers removes the
LinaA-routines too. As happened with the TT for example.

So never use them!

Reading access can be taken to the LineA variables. But Why?

5.6.2 Setscreen & Getscreen

These XBIOS-Functions (mostly Setscreen) shouldn't be used.

But what am I talking. For those using them or those being tortured
because someone else did:

The Videohardware of 1040STE and Mega STE has a hardware bug. When defining
a new physbase with Setscreen (and if it's the same gotten with Getscreen),
it may happen that the screen is 'folded'. This happens due to the movement
of a register at a special moment, which is only allowed to be moved at
special phases of the screen output.

What has to be done?

Users: The programs NVDI and FALT_OFF stop this error. Or give this FAQ to
coder.

Coders: Either even don't use Setscreen.
If you use it though: If physbase isn't changed, the value taken
with Getscreen may not be used. Use the
value -1 than physbase!

5.6.3 NVDI and WARP 9

There are two often used programs exchanging the ROM drivers: NVDI and WARP
9 (earlier QuickST). TurboST was distributed by BELA but isn't updated no
more.

If these are used once, one will never want to miss them: the Desktop seems
to be terribly slow. I will never want to work without NVDI on my Atari.
Others say the same about WARP 9.

NVDI uses strongly optimised drivers for the ST and TT resolutions. Sadly I
don't know which drivers are used by WARP 9.

NVDI is available from Behne & Behne and contains not only the drivers but a
GDOS and a manual describing exactly all VDI calls.

WARP 9 is available from CodeHead.

Due to this NVDI is spread in Germany and WARP 9 in the US

Different to NVDI WARP 9 only speeds up the text output. Grafics stay slow as
before. AND the newest version does'nt work with MultiTOS.

5.7 Other drivers

________________________________________________________________________
| Name |Date |Length | Distributor|Errors | Others | Fonts |
|___________|_________|_______|____________|_1_|_2_|________|__________|
| META |11.04.89 | 5644 | I | | | |MF |
| META |08.10.88 | 9325 | BELA | | | |MF |
| META |16.12.87 | 9325 | Atari | | | |MF |
| META_2 |14.06.91 | 9325 | I | | | |MF |
| META |27.01.92 | 9718 | FontGDOS | | n | |MF, OTL |
| META |28.01.93 | 9733 | Speedo | | n | |MF, SPD |
| META |02.07.93 | 11174 | Speedo 4.2 | | n | |MF, SPD |
| MEMORY |27.01.92 | 58397 | FontGDOS | | n | |LS, OTL |
| MEMORY |28.01.93 | 60265 | Speedo | | n | |LS, SPD |
| MEMORY |02.07.93 | 62331 | Speedo 4.2 | | n | |LS, SPD |
| PSCRIPT |14.10.92 | 33016 | WT | | | | |
| HPGL |08.07.91 | 48885 | ST458 | | | | |
| ZEBRA |07.12.91 | 45746 | WT | | | | |
| T_OFFICE | | | wt | | |98/196dpi| |
| T_OFFICE | | | wt | | |98/196dpi| SPD |
|_IMG-0300__|_________|_______|_Reschke,wt_|_n_|___|________|LS________|

ING-0300 can be copied (non commercial). The other IMG-0??? drivers are by
SciLab. ZEBRA is for the Zebra Labelprinter.

5.7.1 Memory drivers

A memory driver doesn't do anything else than a screen driver (see [14] and
[12]). The output simply goes to another area of memory.

The normal v_openwk binding doesn't have all parameters needed to open this
driver. If not included to the language this binding must be made by
yourself. A listing is found at [14].

The memory driver listed above can produce b/w output only and has a logical
resolution of 300dpi. The (Matrix) drivers tested by me have no problems
with fonts installed that are for other other drivers. The memory driver
should take screen-fonts - due to the 300dpi.

Problem could appear because of the aspect ratio (relation of pixelwidth to
height) - normally not similar to the screen resolution.
Due to this circles can be displayed as ellipses.

With NVDI version 2.5 the output can be redirected to offscreen bitmaps.
You can make any GDOS outputs to this bitmaps and copy the result in windows
on the screen.

5.7.2 Plotter drivers

A HPGL driver seems to be distributed with the program DATA. On PD-Disk ST
458 (German PD series) is one too. If I get more about it I'll include this
info here.

5.8 What's missing

I don't know drivers using the abilities of the following printers:

o Epson 360dpi Needleprinters
o DeskJet 500C
o DeskJet 550C
o LaserJet IV

6 Errors

Errors in the printer drivers - that I know - are the following:

1 These drivers display fonts with the attribute 'light'
2 Doesn't work on TT
3 The EXTENDED ENQUIRE FUNCTION (VDI 102, vq_extnd) doesn't give back the
parameters as listed in the german 'Profibuch' (Jankowski, Rabich,
Reschke - Sybex)
4 Using the attributes 'italic' and 'outlined' the letters of bitmap fonts
are cut off on the right side. This error appears independent from other
attributes being used.
This error was in the Libraries of the driver sources from Atari and
seems to be included in all drivers except to NVDI and SpeedoGDOS.

If theres nothing written about an error I don't know if this error appears
or not.

Seems it's no accident, that Xact only uses the attributes 'fat', 'italic'
and 'underlined'. (See [14])

Another reason against using 'outlined' is the following:
If you make a driver calculate an outlined font from a normal one it get's
'wider' by two pixels. Due to the reason that a pixel has a width depen-
ding to the resolution (other than a fitted font) a text gets different
widthes in each resolution. But who wants to have different textformat on
different printers? The only way to stop this is letterspacing -
typographic 'bullshit'.

7 Fonts

7.1 General

There are many fonts on the Internet only for the screen and maybe useable
for one printer. Everybody using these fonts should know that he can't print
documents in an acceptable quality via GDOS.

But in the Atari and former BELA package there are contained the fonts for
all printer drivers in this package (the 360*360dpi fonts are missing in the
Atari package). If you have a useable program you can print every document
with every driver.

Speedo removes this problem.

7.2 Bitmap-fonts

The fonts used are Bitmap fonts in the DR standard format. (See [1] and
appendix)

GDOS bitmap fonts have their width information defined in both, screen font and
printerfonts. Sadly the designers were a bit too zealous and fitted the width
of
the sreen fonts to make them look very beautiful. That are they, but they're
not
similar to the printer donts and don't allow WYSIWYG.
No problem with Speedo fonts

7.3 Vector fonts

The vector fonts with the old FSM-GDOS format are named with OTL.

These fonts and drivers should'nt be used no more and are listed to only for
completion of this FAQ.

The vector fonts in SpeedoGDOS format are named with SPD.

8 Printer

_______________________________________________________________________
|_Producer____________Printer___________________|Drivers Fitting______|
| NEC |P6+,P7+, |NECP... |
|___________________|P60,P70____________________|NB15_(FX:_:,:NX1000)_|
|_HP________________|LaserJet_II________________|HP_LJET______________|
|_HP________________|DeskJet,_LaserJet_III,IV___|DESKJET_(HP_LJET)____|
|_CANON_____________|BJ10E______________________|BJ10_________________|
|_CANON_____________|LBP_4/8____________________|CANONLBP,_LBP________|
|_Mannesmann-Tally__|MT_90______________________|MT90_________________|

Drivers in brackets work but don't use the ability of the printer totally.
This means - for 24pin printers - that these are used in 9pin mode. At
HP compatible laser and ink printers this means that the data isn't packed
though being supported by the printers.

Some Deskjet drivers are told to make problems. In this case try the Laser-
jet driver. The printing takes longer than (due to more data) but the
problems should be removed then.

The meaning of compatible normally is made by the producers of the
compatible printers.

Notes:

o If you don't find your printer in the list and knows a fitting driver,
please inform me.
o Try other drivers even if you have found one fitting to your printer.
o Of course the FontGDOS drivers have strong problems with the memory. But
the speed of them is faster than the other (Speedo not considered).

8.1 List of availability

In the German TOS-Magazin July '92 page 24 contains a list.
If you know about list available europe/worldwide inform me.

9 Programs

Nowadays it's obvious (but not usual) to use GDOS in every program.

The following list is limited to those using GDOS to print too.

This list is no commercial. I'll include every program I get to know.
(Comment by the Translator: Sorry for mentioning Atari Works three times,
but I wanted to keep the 'Text/DTP' and 'Spreadsheet' Chapters')

Notes:

o Programs listed in the Speedo column with yes* support Speedo but don't
use it - don't output text too.
o Xact can print without Speedo too.
o FSM-GDOS is included in the Wordflair II-package.
o Platon only outputs Metafiles via GDOS.
o I didn't make it to print via GDOS in OPUS.
o Programs only printing via Device 21 are out!

Kandinsky Version 1.57 and TreeView are available together in:
ftp.e-technik.tu-muenchen.de pub/comp/platforms/atari/incoming

10 Utiliies

10.1 fontfix

Problem: The font height is included incorrectly in some fonts. fontfix
discovers this error and corrects it.

On the Internet fontfix can be found here:

ftp.uni-muenster.de /pub/atari/Applications/Dtp/Fonts/Gdos

ftp.cs.tu-berlin.de /pub/atari/utils

10.2 Outline Fonts

This utility edits the EXTEND.SYS for SpeedoGDOS. This file contains a
description of the volume from the Speedo-Caches, the fonts and the
font sizes. The Caches can be saved to disc an be loaded again, too.
A well done program, except that the offered cache sized are fitted to
FSF-GDOS, not Speedo

Filename: OUTLINE.PRG alias OUTLINE.ACC, 67644 Bytes

Included with SpeedoGDOS.

Why doesn't Atari make programs that include a display of the version?

10.3 Printer driver

To edit the ASSIGN.SYS

Filename: DRIVERS.PRG alias DRIVERS.ACC, 64878 Bytes

Before starting this program it's better to create a backup of the
ASSIGN.SYS!
The two reasons are the following:

1. The informations about the Bitmapfonts are removed without comment.
2. ASSIGN.SYS is replaced by a new one if 'Benutzereigen'-'Hinzufügen' (in
the German release) is selected wihtout any chance to get it back.
(The English Version should have a Dialog like 'Own drivers' 'Add' or
similar). To all coders: Don't copy that style!

If this utility should sometimes display no drivers, simply start
ASSIGN.PRG (see 10.4 ASSIGN)

DRIVERS.PRG/ACC only displays the speedo drivers of my collection. Does
anybody know, how it does this? It doesn't even display the filename but a
name being included as string in the driver. How does one get it?

10.4 ASSIGN

ASSIGN 1.0a is by Dirk Sabiwalsky (PD).

It tests three things:

o Are there several fonts using the same ID and have different Names
(typefaces)?
o Are there several fonts using the same ID and the same pixel height?
o Are there several fonts with the same name (typeface) and different
IDs?

10.5 FONTCHK

FONTCHK tests GDOS fonts if they have possible errors.

It's included with ProList, for example.

10.6 FONTCNV

Converts GDOS-fonts from Motorola to Intel format.

Comes with ProList too.

10.7 GEMFont

Font editor able to read Signum and PK (TeX) Fonts too.

Internet: ftp.tu-clausthal.de:pub/atari/systools/gdos/gemfo120.lzh
Use the chance to get a new unlzh or lhxarc.

10.8 FontMonger

Converter and editor for different vector formats including Speedo. Only works on
IBMs or MAC though.

10.9 Font-ID

Font-ID is a little Freeware tool made by Frank Schneider. In a window it
displays the fonts installed with GDOS or SpeedoGDOS including the Font-ID in
different sizes. So you can get an overview when you don't have a program with
font selector/ID display function at the moment.
11 Distribution

11.1 Atari

The drivers with the name Atari are available from Atari. Send three disks,
Money for shipping and a friendly letter to them and you'll get them with
printer drivers and fonts.

This Package is available at Atari-shops too.

No docs but for this price ...
(That's the way in Germany - other countrys may differ!)

11.2 BELA

The fonts with the name BELA were available from BELA

There were two discs with packed Printer-drivers and fonts for them

The fonts DO have the same IDs as ones from Atari, but the internal
font NAME is different. Due to this these fonts are not correctly accepted
by some programs if used with Atari fonts.

There's almost no documentation. Not even a hint about who owns the copyright
for the drivers or about the author(s)

One last thing about BELA: R.I.P. ;-)

11.3 FontGDOS

The drivers from this package are really much faster than the former ones.
(Only bitmap fonts and graphics are comparable of course)

I didn't have any problem using these with other GDOS ersions but you must
limit use to the old Fonts.

FontGDOS is the successor to Atari GDOS. Mainly, it differs in the
Bezier functions, and had faster (and colorable) drivers. It has no
relation to FSMGDOS or SpeedoGDOS.

FontGDOS is available from several firms which use it for their programs.

11.4 Language

The driver named Language is spread on the language disc for the MegSTe

11.5 Internet

The drivers signed with "I" can be found on the Internet.
For example: ftp.cs.tu-berlin.de

11.6 Working Title

The WT drivers are spread with Calligrapher. They are (c) Working Title, the
wt-driver are licensed by Working Title.

No drivers are on the Calligrapher DEMO-disc. The drivers coming with
Calligrapher-lite (15DM) are signed with CL in the tables.

Screenfonts are on both discs.

11.7 Speedo-drivers

SpeedoGDOS is available for everyone now (in Germany 99.-DM)

Contents:

o Installation program
o Speedo font engine
o 2 programs to edit ASSIGN.SYS and EXTEND.SYS
o 14 Fonts in Speedo format by Bitstream
The Falcon Speedo (in Germany) comes with 18 Fonts now
o 14 Printer drivers
o An installation manual

Outrageous features are:

o Speed
o Not the whole font file has to be read (memory saving)
o 16bit-Fonts (no 256 character limit)

See [4]

The information if it's a Speedo or bitmap font can be found in byte 33 of
the Fontname (vqt_name, INQUIRE FACE NAME AND INDEX, VDI 130). Zero means
bitmap font and one means FSM or Speedo font.

Some Problems are inportant to be mentioned:

A coder can't find out if a driver can handle Speedo fonts (see last
question in 10.3)

Some font IDs are used by bitmap AND Speedo fonts, though different fonts
with similar IDs may never be installed the same time.

If you don't take care of this you'll get bombs.

Speedo depends on the user to install the right drivers and fonts. The
coder cannot do anything to stop errors.

The best way is only to install bitmap fonts with the right drivers or to
use a Speedo only system.

The monospace font coming with Speedo has no 'umlaute'

Don't Trust [14] about saying that SpeedoGDOS is not updated.

For Installation and coding best is to refer to [5-7]
Remember to start NVDI before SpeedoGDOS in the AUTO-Folder!

The ones that bought Speedo got 4.0, the Falcon-buyers got 4.1

Now Version 4.2 (beta) is available with remarkable bugfixes. Speedo 4.2
is (in Germany) available as bundle or update (40.-DM) from R.O.M.
Only COMPO is selling it single.

Speedo 4.2 get's the font ID by adding 5000 to the internal one. NOW the
problems with same IDs in bitmap and vector fonts are history.

11.8 Speedo 4.2

SpeedoGDOS Release Notes
Version 4.2 Beta

The following is a list of changes made to SpeedoGDOS.

1) Line-A - Due to many requests from developers, SpeedoGDOS is now no longer
Line-A dependent. All output is done through VDI calls. This was done to make
Speedo compatible with various graphics cards, and to make it more multi-tas-
king-friendly. In addition, users should be able to use various VDI replace-
ments with GDOS.

Another benefit from removing the Line-A dependency is that we no longer have to
worry about the scratch buffer used for algorithmic special effects. We have
implemented the special effects inside of SpeedoGDOS and the drivers, so that
the user/program does not have to worry about the memory needed to accomodate
arbitrary sized characters. Unfortunately, this means that old drivers need to
be relinked with the new independent library (found in the new driver kit).

There are plusses and minuses of the new implementation of special effects. In
many cases, the special effects will be slower. With all previous incarnations
of GDOS, you could not use 'bolding' or 'skewing' at non-90 degree rotations;
now both of these work at all rotations. On the other hand, 'lightening' used
to work at all angles and combinations of effects; now 'bold' mixed with 'ligh-
ten' only work at 90 degree rotation angles.

Miscellaneous Note - When using special effects, many applications have a hard
time placing the cursor. In both the v_gtext() call and the v_ftext() call, the
only cursor compensation to be made is for bolding. Bolding adds the thicken
value to the number of pixels of each character. For rotated characters, note
that the extra pixels can be considered a vector along the positive x-axis which
is rotated at the same angle as the text and added to the advance vector;
therefore, the length of the text string should remain the same at any angle.
This is true even when SpeedoGDOS generates characters on a scan-line basis
(when the character does not fit in the character cache), although it does not
implement the special effects. Also, applications should watch for the case
when they keep track of the cursor position with vqt_advance() or vqt_width(),
instead of vqt_extent() or vqt_f_extent(). In versions prior to 4.2, the appli-
cation could accurately place the cursor by adding two pixels for every outline
character and by adding left and right skew offsets for a skewed string. Now
these effects are generated by the outline font engine, so the application must
either rely on the extent calls or it must inquire for the advance vectors for
characters that are skewed and/or outlined separately. For compatibility pur-
poses, it is recommended that the version number of SpeedoGDOS is checked so
that programs can handle both old and new characteristics.

2) Font ID's - Speedo font id's have been promoted to a higher range of ID num-
bers. This was introduced to avoid conflicts with bitmap fonts and more impor-
tantly, with the system font (which conflicted with a variation of Swiss 721).
For those applications which use the usual interface with Speedo (i.e. use
vqt_name() to find out what the font ID's are), there should be no problem, ex-
cept if documents have font ID's embedded into formatting information. Of cour-
se, all the user has to do is substitute the font. If the application actually
goes into the font file header to read the ID, note that we are adding 5000(de-
cimal) to all Speedo font ID's.

3) Printer Driver Incompatibilities - Speedo will now check the printer driver
it is trying to load for the '_FSM_HDR' cookie embedded in the driver header
information. If GDOS does not find the cookie, it will not allow the loading of
any fonts; therefore, you can still use your driver for non-text applications.
For future reference, please be sure that the driver header begins on a word
boundary for all drivers to be used with this version and any future versions of
GDOS.

4) Vst_load_fonts() - We have made two optimizations to the loading of fonts.
The first is when a load_font call is made, GDOS checks the date of the ex-
tend.sys file to see if it was modified since the last load. A reload used to
be mandatory because a bigger scratch buffer might have been required. Since we
no longer need a scratch buffer, GDOS only checks to see if a change has been
made to the list.

The second change is that GDOS no longer deallocates the global list of fonts if
there are no more workstations using GDOS fonts. Therefore, application laun-
ches will be faster. On the other hand, the miscellaneous cache never gets
cleared of font header information, unless a reboot happens.

5) Memory.sys - The memory driver used to mistakenly open a printer handle.

6) vst_height() - Vst_height used to have a bug in which a maximum point size is
reached and then the size begins to shrink. This is fixed.

7) Postscript table - The Postscript table has been fixed (i.e. the indexes were
off by 32 for certain Postscript files).

8) Fixed vrt_copyfm() in the drivers.

9) When in 'bicsmode', character 0 was not passed through to the font engine.

10) Negative point and set sizes - The handling of negative point and set sizes
has been made consistent with the original handling in FSMGDOS.

11) The handling of fractional setsizes was incorrect in the drivers, and is now
fixed.

12) V_ftext() in the drivers can now handle the offsets passed into the ptsin
array.

13) Screen drivers can now safely load as device 10.

14) The memory driver can be loaded residently.

15) vqt_devinfo() - Vqt_devinfo() now returns information, whether or not the
device has been opened. Furthermore, the device drivers name, found in the dri-
ver header, is copied into the ptsout array; the name is 26 bytes long. Note:
if the driver is not SpeedoGDOS-compatible, a null string is returned, and if
there is an error, a -1 is returned in ptsout[1].

16) vst_width() - A new call has been added to Speedo. The call is similar to
vst_height() except that it sets the width. The bindings are identical except
that the opcode is 231. Note: As with vst_arbpt() and vst_setsize(), you must
call the general call (i.e. vst_arbpt() or vst_height()) before using the width
calls (i.e. vst_setsize() and vst_width()). In addition, the general calls al-
ways reset the widths.

Miscellaneous Note: Although these have been published before, many requests
have come in for the SpeedoGDOS error codes. Here they are:
Code 1 Out of memory
2 File open
3 File read
4 File write
5 Speedo engine error
6 Character too large (not used, defaults to line output)
7 No room for scratch buffer
8 Character cache error
255 Miscellaneous
These errors are placed in the error code address that applications should pro-
vide. Note that if you have MultiTOS installed, GDOS will report the error to
Salert, the system alert box. A revision of the error handling is overdue, sin-
ce some of the errors are no longer relevant (e.g. code 6), and error code 5 is
returned for the lack of availability for pair and track kerning (in addition to
the serious errors).

11.9 COMPO

Compo offers a package of 40 Fontcuts in Bitstream Speedo-format (99.-DM,
price may change): 4 Cuts of Bitstream Amerigo, 1 of Blippo, 1 Broadway,
1 Brush Script, 1 Caslon Openface, 1 Dom, 2 Kaufmann, 2 Ribbon, 14 of Swiss
(Helvetica), 14 of Zurich (Univers)

11.10 IMG-0300

On the Internet:

ftp.uni-muenster.de /pub/atari/Gdos

11.11 Others

I am not choosing drivers to list here. I'll list them all! The authors
and users of the programs should email me information about drivers they
would like to see in the list. Please include code length, date, and
known bugs.

11.11 FTP

Many students can get software worldwide via ftp (comment by s.d.: lucky
boy'n girls ...). Prices for steady connections are constant, but
connections between America and Europe have to be paid depending to the
volume of data transferred.

Please try not to ftp over the Atlantic and use short ways.
Do your tranfers during off hours of the server (not 9am - 5pm).

Files with known names can be found by Archie.

In Germany:
telnet archie.th-darmstadt.de
login: archie
help

In the US e.g.:
archie.ans.net

The Archie databases ask about once each month one ftp server after the
other for freely available files

12 Source

Being a developer it's possible to get an almost complete printer driver in
object code. This one should only be fitted to a special printer.

This package is available for GDOS and SpeedoGDOS.

13 Tips'n tricks

13.1 Pixeltrash at printing, advice for users

Printing graphics on a NEC P6+ (maybe other printers too) including a lot of
black in a line I often had the problem that one line was left out (Speedo
drivers NB15, NECP) or two lines were printed displaced in one line (Speedo
drivers FX80, NX1000).

This happens when printing directly and via CENSPEED. When using VARSPOOL this
effect no longer occurs.

VARSPOOL can be found on the driver disk of the NEC-printers.

13.2 NEC P6+

Once in a while a NEC P6+ will get noisy (rrrrrrrrrrraattatatattaa).
When you open the front you'll see a round stick (about 1cm thick).
Put two drops of sewing-machine-oil on it each year (you'll get it from Mom)

14 Tips'n tricks for coders

Fontsize and Pixelsize

Here are my experiences with GDOS and WYSIWYG. Credits to Ulrich Rossgoderer
for confirming these.

It's about the output of vector graphics and text on screen and printer.

The size of text is defined in point and is always the same - independent from
the resolution of the output device.
Different are vector graphics: they have to be recalculated in pixels before
the output. This should be no problem because when opening a virtual/physical
workstation you get the pixel size in micrometers in devParm[3] and devParm[4].

Let's assume the vector graphic is saved internally in micrometers, then the
definition points at the output simply have to be divided by devParm[3] or
devParm[4] to get the position in pixels. When doing the output in windows an
offset has to be added. But thats not relevant here.

So far for the theory being quite simple (see [3]).
Now for the practice.

As described above we output a text and a border - saved internally as vector
graphic. It doesn't matter here if the text is a Speedo or a bitmap font.
To have a better chance to compare the border exactly surrounds the text.

Doing this I got the following experineces: The text exactly filling the border
on the screen (ST-high) is - when printed - much too small compared to the
border.

An error in the recalculation of the pixelsize can't be the problem, because I
made the printing with the drivers NB15, NECP, FX80, NX1000 and the results are
the same.

I have only one explanation for this: The screen driver supposes a different
resolution for the pixelsize than for the font size.

Two solutions I can offer:

First you can use another pixelsize on the screen than the one given from the
operating system. After opening the virtual workstation (and ONLY this one!) I
claculated
devParm[3] := 282
devParm[4] := 282
and with this parameter I made the recalculation from micrometers in pixels.
Now the relation from graphic to text on screen and print-out is exactly the
same. But now a DIN A4-page doesn't fit on the screen in it's width.
The numbers are found by me the experimental way and possibly can be optimized

Another solution may be this: Use a smaller font size for the screen (and ONLY
there!) by multiplicating the size with 72/96. This is simple with Speedo fonts
because the size in points can be defined by almost endless values behind the
point. Using bitmap fonts this won't work due to not having a font in a
72/96 times size for every printer font. (Different to translate this, sorry - SD)

This method surely is to be modified for ST-Mid and other resolutions.

From Wilfried Behne (Half NVDI ...): SpeedoGDOS ignores the devParm[3]
and [4] - values of the screen drivers. The values of physical workstations
ARE taken.

15 Addresses

( Lot's of stuff is available from the friendly Atari-dealer 'around the
corner ;-/ )

(Note: All addresses are German ones - except when marked!)

Application Systems Heidelberg (ASH)
Postfach 102646 * 69016 Heidelberg
Tel.: +49 6221 300002

ATARI Computer GmbH
Am Kronberger Hang 2 * 65824 Schwalbach /Ts.
Tel.: +49 6196 801-0; Fax.: +49 6196 801 180
Entwicklersupport-Mailbox: +49 6196 81041

Behne & Behne Systemsoftware GbR
Lindenkamp 2 * 31515 Wunstorf
Tel./Fax.: +49 5031 8629

BELA Computer GmbH: R.I.P.

ByTech GbR
Detlef Kuhl, Frank Hieronymi
Bismarckstrasse 88 * 10627 Berlin
Tel.: +49 30 3134258

COMPO Software GmbH
Ritzstrasse 13 * Postfach 1051 * 54591 Pruem
Tel.: +49 6551 6067

Digital Systems & Consulting
Soester Str. 306 * 59071 Hamm
Tel.: +49 2381 889413; Fax.: +49 2381 889812

Stephan Gerle
Ruthstrasse 8 * 44149 Dortmund

H3 Systems
Häusserstrasse 44 * 69115 Heidelberg
Tel.: +49 6221 164031; Fax.: +49 6221 184541

Harald und Martin Hansen
Weserstrasse 82 * 12059 Berlin

Hard & Soft
Obere Münsterstr. 33-35 * 44575 Castrop-Rauxel
Tel.: +49 2305 18014; Fax.: +49 2305 32463

ICP GmbH & Co.KG
Leserservice TOS * Innere-Cramer-Klett-Strasse 6 * 90403 Nürnberg 1

MAXON Computer GmbH
Schwalbacher Strae 52 * 65734 Eschborn
Tel.: +49 6196 481811

Migraph Inc.
32700 Pacific Highway S.
Suite 12, Federal Way
WA 98003, USA USA!!!
Tel.: 0012068384677

OMIKRON Soft+Hardware GmbH
Sponheimerstr. 12a * 75117 Pforzheim
Tel.: +49 7231 356033

Pergamon Software * Lehmann & Herzog
Wegscheidestr. 29 * 60435 Frankfurt/Main
Tel.: +49 69 5488279

rhotron GmbH
Entenmuehlstrasse 57 * 66424 Homburg/Saar
Tel.: +49 6841 64067; Fax.: +49 6841 2467

Richstein & Dick GbR (Kaktus)
Konrad-Adenauer Strasse 19 * 67663 Kaiserslautern
Tel.: +49 631 22253

Richter Distributor
Hagener Str. 65 * 58285 Gevelsberg
Te.: +49 2332 2706

R.O.M. Software (New Address!)
Christian Nieber & Ullrich Ramps
Raschdorffstr. 99 * 13409 Berlin
Tel.: +49 30 4924127

SciLab GmbH
Isestrasse 57 * 20149 Hamburg
Tel.: +49 40 4603702

SHIFT Computer + Werbung GmbH (quit!!)
Kompagniestr. 13 * W-2390 Flensburg
Tel.: +49 461 22828

SILICON Technology & Promotion
Wilhelmshöher Allee 124 * 34119 Kassel
Tel.: +49 561 711924

Softbaer GbR
Richardstr. 60 * 12055 Baerlin ;-)
Tel.: +49 30 6226884

SPIRIT WARE
Bible Church 15211
15th Avenue NE Seattle, WA 98155 (USA) USA!!!

TKR
Stadtparkweg 2 * 24106 Kiel
Tel.: +49 431 337881; Fax.: +49 431 35984

Trade-iT
Arheiligerweg 6 * 64380 Rossdorf
Tel.: +49 6154 9037

Dipl.-Phys.-Ing. Ralf Wirtz
Kasterstr. 30 * 52428 Juelich
Tel.: +49 2461 1255

Wilhelm Mikroelektronik
Luenen

Working Title GbR
Lilienweg 12 * 53123 Bonn
Tel.: +49 228 647020

3K Computerbild
Wevelinghoven 26 * 41334 Nettetal
Tel.: +49 2153 91860

16 Miscellaneous

16.1 Critics

16.1.1 Critics to the author

Critics are greatly welcomed. To get more info, send email to:

G.CA...@physik.uni-stuttgart.de

Possibly one writing me has already tested two or three drivers.
Please write me if the errors listed above occured or not.

Anybody knwoing different driver support addresses, please write me an email.

16.1.2 Critics to the translator

Hi, this is Stefan writing :-)
The reason why I wrote this translation I can't find in my head ...
Guess it's because Atarians should work together and support each other!
Well, if you wonder about some errors of spelling or syntax remind this:
I learnt English at school for 4 years an after that I kept my knowledge
actual by playing some textadventures and now by reading
comp.sys.atari.st and comp.sys.atari.st.tech :-)
If you find some errors in this translation, please don't send them to Gerd but
to me:

stefan_...@sl.maus.de

But take care of the gateway-rules:
No mails bigger than 16kB and please no big UUE-stuff :-)

Thank you and have fun and lot's of experience with this FAQ.

Bye
Stefan

16.2 Praise

If this FAQ helped you out of a problem, please write me a postcard in your
next holidays.

Postcard received yet: not even one :-(

16.3 For my support

Due to actual experiences I ask the distributors to switch on verify when
copying update disks.

I only know two distributors not making any problem with this.

Could One of the readers try to write a Speedo fonte ditor? We (Gerd & Stefan)
offer our time to beta test it ;-)
[I remember that this sentence was slightly different before Stefan
translated it - Gerd]

16.4 Trademarks

This document is full of trademarks, no to be used free|y.

16.5 Guarantee

I'll offer no guarantee.

17 Appendix

17.1 Literature

[1] Douglas N. Wheeler, EVERYTHING YOU EVER WANTED TO
KNOW ABOUT GDOS (AND MORE), (Internet, Filename:
GDOS.ARC oder GDOS.TXT)
Here's written all what's important to know about GDOS drivers.
(AND MORE)

[2] Jankowski, Rabich, Reschke, Atari Profibuch Professionals book],10.
Auflage,
SYBEX, Düsseldorf (1992)
The Standard. For Coders: In the VDI part you'll find how to use
screen and printer drivers correctly.

[3] Marc Rene Gardeya, VDI für jedermann [VDI for everyone], ST-Computer 10/93
Introduction in correct programming of screen and printer outputs.

[4] Julian Reschke, Herbstgedanken, ST-Magazin 11/92
Autumn-thoughts about SpeedoGDOS and Font-GDOS.

[5] Erik Dick, Schön und schnell? [Pretty and Fast?] , ST-Computer 7/93
Common info about GDOS and installation of Speedo. Almost the same
standing in the installation manual, but more information about special
problems

[6] Erik Dick, SPEEDO-Gonzales, ST-Computer 8/93
Important stuff about programming Speedo. Description of the new
bindings tips for coders for standard uses.

[7] Erik Dick, SPEEDO-Gonzales, ST-Computer 9/93
Meaning of the Speedo-Errormessages and bindings of the Bezier and
cache routines

[8] Raymond Schröder, Atari-Hotline, ST-Magazin 7/92
Whats GDOS for? Which programs supports it? How to install it?

[9] Sven Behne, Wilfried Behne, NVDI-Dokumentation, BELA
VDI-description. But no description of the differences between screen
and printer drivers.

[10] Wilfried Behne, Andreas Kromke, Traps in the Atari ST's VDI
and how to get around them, c't 1991, Nr. 3
Much about errors in the screen drivers.

[11] Laurenz Prüssner, : es ist alles so schön Bunt hier [Oh, take a look at
these colors], ST-Magazines 5/92, 7/92, 9/92
How to handle more than 256 colors with device depending formats

[12] Laurenz Prüssner, Sekt oder Selters [Champaign or mineral water],
ST-Magazin 4/93
MEMORY.SYS: Binding, Way to handle color resolutions, fontoutput
with and without SpeedoGDOS.

[14] Laurenz Prüssner, Summertime Blues, ST-Magazin 6/93
Listing to open the MEMORY driver.

[15] Laurenz Prüssner, Mehr Schub!, ST-Computer 2/94
Printing with GDOS - espacially it's about printing of bitmap raster
- color too.

[16] Oliver Scheel, Erste Hilfe für [1st aid for] MultiTOS, ST-Magazin 6/93
Common information to install MultiTOS.

[17] Günter Born, Referenzhandbuch Dateiformate [Reference Dataformats],
2. Edition, Addison-Wesley, Bonn (1992)
With the right drivers it's quite simple to make output in .IMG- and
in .GEM- Format In this book is a description how to read these formats
again (and more).

[18] Günter Born, Dateiformate [Dataformats] Programmierhandbuch [Coders
manual], Addison-Wesley, Bonn (1993)
Sources (TurboC, TurboPascal) for loading and saving the formats
to use the datas [16] is recommended.

[19] Tim Oren, Professional GEM, (Internet, Filename: PROGEM)
Tim Oren almost only describes the programming of the AES but without
him this list would not be complete.

[20] Teflon Fonfara, Frau Kächele & Frau Peters - Die fanatischen
Zwei [The two fanatics], TUCAN Records (1992)
the ultimate Hefezopf-FAQ

CAS...@cip.physik.uni-stuttgart.de; alias: G.Ca...@physik.uni-stuttgart.de
Gerd Castan * Hoehbergstr. 16 * D-70327 Stuttgart

stefan_...@sl.maus.de (MausNet: Stefan Damerau @ SL)
Stefan Damerau * Bergholm 31 * D-24857 Fahrdorf)

CAS...@cip.physik.uni-stuttgart.de; alias: G.Ca...@physik.uni-stuttgart.de
Gerd Castan * Hoehbergstr. 16 * D-70327 Stuttgart

Marc BOURLON

unread,

Mar 30, 1994, 9:37:09 AM3/30/94

to

Great ! I haven't read it yet, but it sounds very good. Thanks a lot.

MB.

Stefan Damerau

unread,

Apr 1, 1994, 5:35:00 PM4/1/94

to

In article CAS...@cip.physik.uni-stuttgart.de (Gerd Castan) writes (reffering
to my posting):

Oh shit. I'll fix that in the next release ...

Bye
Stefan
______________________Important note follows______________________________
Stefan_...@sl.maus.de
User of German MausNet
!!No Mail >16kB please!!

Gerd Castan

unread,

Apr 5, 1994, 6:34:30 AM4/5/94

to

In <A64...@SL.maus.de> Stefan_...@sl.maus.de writes:

> In article CAS...@cip.physik.uni-stuttgart.de (Gerd Castan) writes (reffering
> to my posting):
> GC> | |

I fixed that before I posted it.

Where did this line break happen?
From me -> Internet News or on the way from Internet -> MausNet?

>
> Bye
> Stefan
Gerd

Stefan Damerau

unread,

Apr 7, 1994, 5:04:00 PM4/7/94

to

In article CAS...@cip.physik.uni-stuttgart.de (Gerd Castan) writes:

Hi Gerd!

GC>From me -> Internet News or on the way from Internet -> MausNet?
I guess this has happened because I've set a limit to line length in my Maus
(SL). There I've set it to 80characters, because I don't want to shock other
Mausers with lines longer than this standard.
In German:
(In meiner Heimatmaus habe ich 80Zeichen/Zeile eingestellt, damit ich nicht
andere Mauser mit Texten, die breiter als dieser Standard sind, schocke)

Did you - and the others in the InterNet - get the table as it should be?
(Sind die Tabellen bei Dir - und anderswo im InterNet - korrekt angekommen?)