HDTenEightyP/NetNews huggingface dataset:
From: annius@nanna.research.ptt.nl (Annius Groenink)
Subject: Re: Questions about colors and the vdi.
Organization: PTT Research
Date: Thu, 15 Oct 1992 16:13:34 GMT

timg@ccwf.cc.utexas.edu (Tim Gallivan) writes:

>Hi,

>For 2 and 4 bit color on a regular ST, I can just set up an array which
>maps color registers to color indices, but I think that this is not
>practical for larger palettes (especially since I don't know what the
>mapping is for the TT and Falcon modes).

ST Magazine (if I remember well) proposed to get the mapping by executing
v_trnfm() on a small raster that contains one pixel of each colour.
Unfortunately, because of speed, v_trnfm() is not an appropriate function when
using color modes (bit planes are seperated). The mapping itself is probably
some un-re-traceable combination of a couple of shifts and adds or sth. (Or is
it a table somewhere in the ROM? Atari why are you doing this to us?)

Anyway the number of colours in false-color modes (forgive the term) will
probably not exceed 256 so you'll be fine with a 256 pixel raster. What I mean
is that the 16 bit modes are mostly 5:5:6 rgb coded so this whole hassle
is irrelevant. A table for 65536 24 bit colours would get a bit big.

-- 
Annius Victor Groenink      Universiteit Utrecht      PTT Research Leidschendam
Mathematics/Comp. Sc.        avgroeni@cs.ruu.nl       +31 70 3325445 (weekdays)
Atari ST/Music          A.V.Groenink@research.ptt.nl  +31 70 3464732 (evenings)
_____________My opinions are my opinions____________  +31 5700 29396 (weekends)
From: an938@cleveland.Freenet.Edu (George II Lenzer)
Newsgroups: comp.sys.atari.st.tech
Subject: D.I.Y. 4 Meg upgrade???
Date: 9 Oct 1992 04:07:40 GMT
Organization: Case Western Reserve University, Cleveland, Ohio (USA)
NNTP-Posting-Host: slc4.ins.cwru.edu


	Has anyone come up with a way to upgrade ST's with a 
homebrew board?  If so, I would be interested in hearing about it.
Please E-mail me if you can.

						Thanx,
						George II Lenzer

-- 
"I'll let you in on a little secret.
	The whole universe is totally INSANE!!!!"
						Mr. Natural
Newsgroups: comp.sys.atari.st.tech
From: apelled@cix.compulink.co.uk (Adam Pelled)
Subject: Re: HD-trouble, DMA-IC?
Reply-To: apelled@cix.compulink.co.uk
Date: Fri, 16 Oct 1992 17:39:16 +0000


In article <1bj75uINN2uc@golem.wcc.govt.nz>, sheppard_r@kosmos.wcc.govt.nz writes:

>For one thing Please get a copy of AHDI 3.1, your version is very badly stuffed
>ans should be never used...
>
>If your STE has this IC C025913-38, then you have the bad DMA chip, 40 pin
>chip under the disk drive..
>
>The good IC is C398739-001A, also the AHDI 3.0 can cause the same kind of
>problems..
>
>The New replacment IC C398739-001A is free, but there could be a charge
>in fitting it ..

    Unless you are in the UK. Then it is 10ukp. However, the fitting is
free :-)

>Roger................              sheppard_r@kosmos.wcc.govt.nz
From: an938@cleveland.Freenet.Edu (George II Lenzer)
Newsgroups: comp.sys.atari.st.tech
Subject: I'm looking for...
Date: 13 Oct 1992 01:51:40 GMT
Organization: Case Western Reserve University, Cleveland, Ohio (USA)
NNTP-Posting-Host: slc10.ins.cwru.edu


...anyone with a developer's package for the ST that they want to 
get rid of.  Also, looking for a monochrome monitor. Cheap!
Please E-mail me if you have either.

						Thanx,
						George II Lenzer
-- 
"I'll let you in on a little secret.
	The whole universe is totally INSANE!!!!"
						Mr. Natural

Newsgroups: comp.sys.atari.st.tech
From: seimet@rhrk.uni-kl.de (Uwe Seimet)
Subject: Re: XHDI (5.0)
Organization: University of Kaiserslautern, Germany
Distribution: eunet
Date: Tue, 13 Oct 1992 11:13:44 GMT

hrs@aber.ac.uk (Herbert Martin Sauro) writes:

>I was under the impression that the 'new' atari disk software 5.00 supported
>the XHDI protocol and I also thought that it deposited a cookie called
>'XHDI'. Trouble is when I boot with version 5.0 no cookie is installed
>and I can't get hold of the routines pointed to by the supposed cookie.
>Am I doing something very worng, perhaps wrong program?
Yes, wrong program. At the moment there are two drivers which support XHDI.
Both are from german developers. These drivers are HuSHI (included with the
SCSITOOL hard disk software from Hard & Soft Herberg) and HDDRIVER (included
with the disktool DISKUS from Creative Computer Design CCD or together with
the virtual memory manager OUTSIDE from Maxon Computer GmbH).
There are no other drivers that support XHDI at the moment.

***************************************
*        Uwe Seimet                   *
*        seimet@rhrk.uni-kl.de        *
*        seimet@chemie.uni-kl.de      *
*-------------------------------------*
* I really hate this damned machine,  *
*     I wish that they would sell it. *
* It never does that what I mean      *
*     but only what I tell it.        *
***************************************
Newsgroups: comp.sys.atari.st.tech
From: bpat@cs.mcgill.ca (Patrick BETREMIEUX)
Subject: Re: VT52 variables? (was: What makes the Screen Scroll *UP* ?)
Organization: McGill University, Montreal, Canada
Date: Mon, 12 Oct 1992 17:46:26 GMT

In article <7akisB1w165w@ersys.edmonton.ab.ca> mforget@ersys.edmonton.ab.ca (Michel Forget) writes:
>
>I received the information from a user on the Forem Net in the Programmer's
>Conference.  I cannot remember the name of the user, but I do remember how he
>did it.  He disassembled the Bconout() function and traced it to see what it
>was doing.  I know nothing about assembly, though, so I really cannot tell you
>more.  There should be a variable for the number of columns, though, if there
>isone for the number of rows.
>
><<  ------------------------------------------  >>
><<        mforget@ersys.edmonton.ab.ca          >>
><<  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~  >>
><<               Michel Forget                  >>
><<   The Key:  Spirit over mind over matter.    >>
><<  ------------------------------------------  >>
>

On TOS 1.2, I have:

$2910 = maximum cursor line
$291E = current cursor column
$2920 = current cursor line

and some others like color and cursor visibility ...

					Patrick BETREMIEUX
					bpat@binkley.cs.mcgill.ca

PS. I still think the best way is what I posted first. Use vt52 ESC codes
to scroll around !!!

Xref: sparky comp.sys.atari.st.tech:5183 comp.sys.atari.st:15174
From: timg@ccwf.cc.utexas.edu (Tim Gallivan)
Newsgroups: comp.sys.atari.st.tech,comp.sys.atari.st
Subject: Questions about colors and the vdi.
Date: 14 Oct 92 21:47:27 GMT
Followup-To: comp.sys.atari.st.tech
Organization: University of Texas Center for Relativity

Hi,

In trying to fix the color in the Ghostscript screen driver, I have come
upon the following problem: I want to use the vdi so that the code I
write will work on all machines, but Ghostscript wants me to tell it
which COLOR REGISTER a given color is in. The problem is that the vdi
color indices (which all the vdi routines seem to use) to not correspond
to the ST color registers.

Is it possible to use the vdi to either:

1) Set and read the palette using the value of the COLOR REGISTER
	and NOT the vdi color index?

2) Use the vdi to find the mapping between color registers and vdi
	color indices?

3) Get around this some other way?

For 2 and 4 bit color on a regular ST, I can just set up an array which
maps color registers to color indices, but I think that this is not
practical for larger palettes (especially since I don't know what the
mapping is for the TT and Falcon modes).

Please do not send me information about XBIOS calls, since I am
insisting on using the vdi.  My GEM documentation is incomplete, and
says nothing about any functions to manipulate the color.

Thanks,

-Tim Gallivan
timg@landau.ph.utexas.edu
Newsgroups: comp.sys.atari.st.tech
From: comeau@csanta.attmail.com (Greg Comeau)
Subject: Re: Trouble with templates in GNU C++
Originator: comeau@well.sf.ca.us
Reply-To: comeau@csanta.attmail.com (Greg Comeau)
Organization: Comeau Computing
Date: Thu, 15 Oct 1992 14:45:29 GMT

In article <CMY7YZP@mailgzrz.tu-berlin.de> pareis@cs.tu-berlin.de writes:
>template<class T> class A
>{
>private:
>	T a;
>public:
>	A( T aa ): a(aa) {}
>	T Get( void );
>};
>int main( void )
>{
>	A<int>	a1(2):
>	return a1.Get();
>}
>template<class T> T A<T>::Get( void )
>{
>	return a;
>}
>The [g++] compiler works fine, but the linker aborts with a message like:
>template.o: A<int>::Get  - symbol not found     ( or the like )
>
>But, if I put the definition of Get directly below the class A
>declaration, it works. I want to know: Is it a problem of the C++
>language or the compiler or the linker (which is PL31)?

Your code works fine with Comeau C++ 3.0 With Templates.
Further, I am not aware of any strange scoping rules or anything that
should prohibit this.  OTOH compilers are using differing mechanisms
to address ATI (automatic template instantiation) and hence you may
be caught in a g++ idiosyncrasy on this although it could equally be a bug.
Perhaps it might change things as well to make A(T aa) an out of line
generic description as you have done with Get rather than in in-line?

- Greg
-- 
         Comeau Computing, 91-34 120th Street, Richmond Hill, NY, 11418
                   Producers of Comeau C++ 3.0 With Templates
          Here:attmail.com!csanta!comeau / BIX:comeau / CIS:72331,3421
	    Voice:718-945-0009 / Fax:718-441-2310 / Prodigy: tshp50a
Newsgroups: comp.sys.atari.st.tech
From: klamer@mi.el.utwente.nl (Klamer Schutte)
Subject: Re: Trouble with templates in GNU C++
Organization: University of Twente, BSC-El
Date: Thu, 15 Oct 1992 18:59:46 GMT

In <CMY7YZP@mailgzrz.tu-berlin.de> subiaagb@w350zrz.zrz.tu-berlin.de (Andre Pareis) writes:

>But, if I put the definition of Get directly below the class A
>declaration, it works. I want to know: Is it a problem of the C++
>language or the compiler or the linker (which is PL31)?

I understand this is correct behaviour. You have to specify the
function before using it, in at least one compilational unit.

But note that ARM specifies this to be implementation defined...


>Another question is:
>In the infos about libg++ I found a description of generic list,
>stack and queue classes, but my g++.olb doesn't contain such things.
>Is it impossible to implement it with G++?

It is possible. You should use the genclass program.
Oops! genclass is a /bin/sh script. Get a /bin/sh compatible shell
(bash will do, if you have the memory -- haven't tried it!), and
use genclass.

As usual, talking about the Sun version of gcc, as i don't have enough
memory on my ST to run g++ :-(.

Klamer
--
Klamer Schutte			Tel: +31-53-892778	Fax: +31-53-340045
Faculty of electrical engineering -- University of Twente, The Netherlands
preferred: klamer@mi.el.utwente.nl     SMTP: klamer@utelmi01.el.utwente.nl
From: abaddon@uk.ac.liverpool.scm.suprenum (Kevin o donovan)
Newsgroups: comp.sys.atari.st.tech
Subject: Re: VT52 variables? (was: What makes the Screen Scroll *UP* ?)
Date: 12 Oct 92 12:45:39 GMT
Organization: Centre for Mathematical Software Research, Univ. Liverpool, UK

Except that VDI output has nothing to do with the line A variables. Try 
dividing the size of your window by the size of a character cell.

Kev
Newsgroups: comp.sys.atari.st.tech
From: boyd@shmop.cs.fsu.edu (Mickey Boyd)
Subject: Re: No red in monitor
Reply-To: boyd@nu.cs.fsu.edu
Organization: Florida State University Computer Science Department
Date: Wed, 7 Oct 92 04:55:45 GMT

In article <1992Sep30.060527.20549@ultb.isc.rit.edu>, jad2433@ritvax.isc.rit.edu writes:
>In article <BvAs2G.2up@acsu.buffalo.edu>, v5914ane@ubvmsd.cc.buffalo.edu (Steve) writes:
>>Does anyone have any Idea on why my atari color monitor lost the red in the 
>>picture??
>
>In this case there are some immediate things to check.
>
>Making sure its unpluged and discharged of any static electricity, open the
>monitor casing removing the back cover housing.

I don't wish to be picky, but the "discharged of any static electricity" part 
above is nontrivial.  Monitors can hold a lethal charge for some time after 
the unit is unplugged!!  Discharging them involves grounding a screwdriver to 
the chassis, then pushing it under the rubber boot at the back of the tube 
(usually with a loud "pow!" as a result). I would not advise it to a novice. 
There can be some serious juice in there! 

I suggest that you try playing with the connector (as the poster above 
recommends), and if that fails send it to a repair facility.  Leave monitor 
guts alone unless you really know what you are doing.  


-- 
  ****************************************************************************
  *                              Mickey Boyd                                 *
  *                         Systems Administrator                            *
  *          Florida State University Computer Science Department            *
  * email:  boyd@cs.fsu.edu  Office:  (904) 644-7339  Pager:  (904) 657-6425 *
  ****************************************************************************
From: jhenders@jonh.wimsey.bc.ca (John Henders)
Newsgroups: comp.sys.atari.st.tech
Distribution: world
Organization:  One of these days for sure
X-News: HERMES MMAIL 1.04 Rev. Sep  5 1992
Subject: Re: Removable Drives
Date: Sun, 11 Oct 1992 23:01:52 -0700

In <VDaisB3w165w@sys6626.bison.mb.ca> genius@sys6626.bison.mb.ca (Trevor Cordes) writes:

>I recently bought a 88-meg removable Syquest drive for my TT.  I haven't 
>really thought about it until today, but does the drive auto-park?  
>Should I be taking the carts out before every power off?

>Right now, I pretty much always leave a cart in the drive, even when it's 
>not on.  Is this bad for the cart or drive?  What do all you other 
>Syquest owners do?

    I have had a 44 meg for over a year. I leave the disk in the drive almost
all the time, and the drive running. I haven't had any problems except that
after a little less than a year, my first cartridge started to stall if I had
turned off the drive and the powered it back up. This seems to be a cartridge 
problem, as other cartridges start fine. Also, after I moved my news system 
to another cart, and ran the new cart for a while, It stated to do it too. 
But to make matters even more bizarre, the original cart started working fine
again. SO I just switch between the 2 cartridges when one gets fussy, and 
everthing appears to be alright. Ejecting the cartridge when not in use and 
keeping it in the box would probably be the best way to go, but not possible
when your news system does a lot of work at night. 


-- 
       John Henders      jhenders@jonh.wimsey.bc.ca
    I think your "evolutionary scale" needs an adjustment.  Either 
      that, or you've got your thumb on it. -> (lefty@apple.com)
From: sheppard_r@kosmos.wcc.govt.nz
Newsgroups: comp.sys.atari.st.tech
Subject: Re: Using RBG/Sync monitors with ST
Date: 17 Oct 1992 00:50:48 GMT
Organization: Wellington City Council (Public Access), Wgtn, Nz
Reply-To: sheppard_r@kosmos.wcc.govt.nz
NNTP-Posting-Host: kosmos.wcc.govt.nz

>Or you can make one yourself. The biggest problem is to get that
>din-plug to fit Atari's monitor socket. I must say mine does
>not work perfectly as there is some ghosting in b/w mode and
>I do not know what is the problem (bad cable, the switch or something
>to do with impedance, as I just connected the monochrome out to
>R/G/B-lines).
>
>--
>* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>Kimmo Lahtinen                      E-Mail : lahtinen@gideon.fmi.fi       
>Finnish Meteorological Institute    Phone  : +358 0 758 1322


Well this could be some help to you all, the Atari puts out some
1 volt pk-pk video signal, this can overload some monitors (gives ghosts)
that can only take some 0.75 volts, so fit small 22 ohm resistors in the
monitor plug, must be at monitor end, one for each colour..


If you are having problem getting the monitor connectors, we have plenty here
at $2.95nz.

  NOTE: Sony also make this monitor connector.

 Part No. is 1-560-946-00  PLUG (WITH lOCK) 13P



Roger............              sheppard_r@kosmos.wcc.govt.nz

Newsgroups: comp.sys.atari.st.tech
From: seimet@rhrk.uni-kl.de (Uwe Seimet)
Subject: Re: HD-trouble, DMA-IC?
Organization: University of Kaiserslautern, Germany
Distribution: eunet
Date: Thu, 15 Oct 1992 10:10:40 GMT

eualty@eua.ericsson.se (Torgny Lindberg) writes:

>Well what do I need HELP from the net with? I remember a diskussion a
>while ago on the net about faulty DMA-ICs. I think the symptom of these
>faulty ICs where as described above. Can someone please tell me if this
>is correct?
Your description fits the symptons of the faulty DMA-ICs in the STE exactly.
A friend of mine had the same problems and after changing the IC everything
was fine.

***************************************
*        Uwe Seimet                   *
*        seimet@rhrk.uni-kl.de        *
*        seimet@chemie.uni-kl.de      *
*-------------------------------------*
* I really hate this damned machine,  *
*     I wish that they would sell it. *
* It never does that what I mean      *
*     but only what I tell it.        *
***************************************
From: ekrimen@wet.UUCP (Ed Krimen)
Newsgroups: comp.sys.atari.st.tech
Subject: Re: Using RBG/Sync monitors with ST
Keywords: Omniswitch, multisync switch, Monitor Master
Date: 16 Oct 92 22:48:07 GMT
Organization: Wetware Diversions, San Francisco

In article <1992Oct15.131412.7139@digi.lonestar.org> rgoseweh@digi.lonestar.org (Roy Gosewehr) writes:
>For mulitsyncs, you need the Omniswitch, the IB Multisync switchbox, or
>the switcher made by Omnimon Peripherals ( I can't remember the name),
>depending on your connection requirements.

Stay far, far away from the Talon Omniswitch.  Others have had luck with it,
but I haven't.

The IB Computers Multi-Switch is good.

Omnimon Peripherals is no longer in business or is no longer supporting the
ST.  This is according to Neil Weinress on GEnie who worked with them.  They
produced the OmniX3 multisync switchbox as well as a 1.44meg floppy modification
for the ST.

Toad Computers in Maryland has multisync switchboxes, as well as ATY Computers
in Oakland, CA who custom builds them, made-to-order.  Both companies advertise
in ST magazines.


-- 
   |||    Ed Krimen
   |||    ekrimen@wet.uucp   Contributing Editor, Atari Explorer Online
  / | \   E.KRIMEN (GEnie)            Vice-President, ABACUS User Group
From: jhenders@jonh.wimsey.bc.ca (John Henders)
Newsgroups: comp.sys.atari.st.tech
Distribution: world
Organization:  One of these days for sure
X-News: HERMES MMAIL 1.04 Rev. Sep  5 1992
Subject: Re: Questions about colors and the vdi.
Date: Fri, 16 Oct 1992 14:19:14 -0700

In <81681@ut-emx.uucp> timg@ccwf.cc.utexas.edu (Tim Gallivan) writes:

>Hi,

>In trying to fix the color in the Ghostscript screen driver, I have come
>upon the following problem: I want to use the vdi so that the code I
>write will work on all machines, but Ghostscript wants me to tell it
>which COLOR REGISTER a given color is in. The problem is that the vdi
>color indices (which all the vdi routines seem to use) to not correspond
>to the ST color registers.
 
   I beleive the vdi color mapping just moves the black from 2 to
whatever  the top number of colours is, and shifts the other colours
down accordingly. I don't have access to the TT notes to see if this is
onsistant throught the tt video modes though.


-- 

 "If Rush fans were braindead, why are there so   Bruce Bufalini
 many people posting to alt.music.rush?"              PSU
From: lp@shlink.hanse.de (Lutz Petersen)
Newsgroups: comp.sys.atari.st.tech
Subject: Re^2: Any articles on Falcon?
Date: 12 Oct 92 15:53:08 GMT
Organization: 'shlink public site +49 4121 63587'

Im Artikel <mattera.718559744@turtle21> schreibt mattera@rtsg.mot.com (Michael Mattera):
> Are there any articles that give the Falcon's Spec's?
> What magazines are they in? Do the Atari dealers have

 Yesterday I saw a 4-side Paper here in Hamburg (Germany) in the computer-
 corner of a store, published by Atari Germany/Swisse/Austria about the
 FALCON030 :


 - system	- CPU: Motorola MC68030, 16Mhz, intern Cache
		- FPU: socket for optional MV 68881/68882
		- RAM: modul-socket for 1, 4 or 14 MByte
		- ROM: 512 KByte
		- BLiTTER: co-processor, ST-compatible, 16 MHz

 - video	- video-subsystem for VGA, RGB and TV, extern
		  synchronisation for GENLOCK
		- VGA: 640x480x256 colours from 262.144
		       320x480x65.536 colours
		       320x480x32.768 colours with Overlay-Bit
		- RGB/TV: 768x480x256 colours from 262.144, interlaced
		          768x480x65.536 colours interlaced
		          768x480x32.768 colours, interlaced with
		          Overlay-Bit
		- All ST-Modi, 640x400 s/w 71 Hz
		- Hardware Overscan option
		- Hardware Scrolling all modi

 - Coprozessor Subsystems	- Digital signalprocessor Motorola
				  DSP 56k, 32 MHz with 32kx24 Bit
				  SRAM, 0 Waitstates
				- BLiTTER Coprocessor 16 Mhz ST-compatible

 - Devices	- Parallel port
		- Modem/RS232
		- MIDI in
		- MIDI out/through
		- Cartridge Port
		- SCSI-II (50-Pin-Connector) with SCSI-DMA
		- LAN Local Area Network (compatible with TT/M-STE)
		- Mouse

 - Sound	- 16 Bit Stereo AD and DA in CODEC
		- In for stereo-microphone
		- Out for stereo-headphone
		- Speaker (mono)
		- Mulitiplexer for DSP, CODEX and Sound-DMA
		- 8 channel 16 Bit DMA call and recall up to 50 KHz
		  (CD 44,1 KHz)
		- Stereo 8 Bit PCM DMA Sound (compatible TT/M-STE/STE)
		- 3 channel PSC-Sound (ST-compatible)
		- IN/OUT for Digital Audio and DSP

 - Joysticks	- 2 STE compatible joystick-ports
		- 2 standard-joysticks

 - Floppy	- 1.44 MByte Floppy (PC-compatible)

 - Harddisk	- intern optional IDE Harddisk, 2.5''

 - Keyboard	- ( you know it from the 'good old ST' ..). The text
		  tells something nasty ;-)

 - Mouse	- 100 dpi

 - Also		- Battery-buffered clock
		- Intern BUS with all CPU, Bus-control, Interrupt and
		  tact-signals
		- Intern RAM-Bus



 PS: In the text there is mentioned MultiTOS as the operating-system for
 the FALCON030 !


 Lutz


--
\\ lutz petersen, 22oo elmshorn, germany, +49 4121-65023 \\
 \\ e-mail: lp@shlink.hanse.de oder lp@shlink.zer.sub.org \\
From: grellier@ufrima.imag.fr (GRELLIER thierry)
Newsgroups: comp.sys.atari.st.tech
Subject: WF_NEWDESK
Keywords: 1
Date: 13 Oct 92 09:32:03 GMT
Organization: Univeristy of Grenoble


	I've tried to define a new desk background, but it
	has not given what I expected to.
	My new background (just a g_box with a standart pattern)
	was actually redrawn but it covers the drives and trash
	icons. And when I select blindly one icon, it draws
	the icon in the old desk background.
	So my question is : could someone send me a tiny example
	to show me how using wind_set(0, WF_NEWDESK, ...) in
	C or post it as an answers to my article.

-- 
		      _..-'(                       )`-.._
	           ./'. '||\\.       (\_/)       .//||` .`\.
	        ./'.|'.'||||\\|..    )O O(    ..|//||||`.`|.`\.
	     ./'..|'.|| |||||\`````` '`"'` ''''''/||||| ||.`|..`\.
Newsgroups: comp.sys.atari.st.tech
From: hyc@hanauma.jpl.nasa.gov (Howard Chu)
Subject: Re: gcc2.2.2 cross-compiler
Organization: SAR Systems Development & Processing, JPL
Date: Tue, 13 Oct 1992 07:21:19 GMT

In article <TERJEVE.92Oct11183938@kolsaas.ifi.uio.no> terjeve@ifi.uio.no (Terje Vernly) writes:
>I just downloaded the source for gcc2.2.2 from a.a and have made
>myself a cross-compiler (hosted on a Sun Sparc, SunOS 4.1.1).
>
>When I compile a program with the -mbaserel option, the program
>crashes with 4 bombs as soon as it starts.
>But if i omit the linking on my cross-compiler and link the program
>with gcc2.2.2 on my ST instead, the program works perfectly.
>
>Both linkers are Patchlevel 31.
>
>Help! :-)

Ah, sorry about that. You just *think* both linkers are the same
patchlevel, I forgot to change the version string in the linker
binary that I uploaded. It is most definitely beyond level 31,
and as I mentioned in the Readme files, you cannot use an older
linker to link the baserel code.

But never fear, Jwahar Bammi's update25 is now available, so you
can get the full set of assembler and linker diffs as well.
-- 
  -- Howard Chu @ Jet Propulsion Laboratory, Pasadena, CA

All true wisdom is conveyed in one-line witticisms.