🚀 go-pugleaf

In article <10429@stag.math.lsa.umich.edu> hyc@math.lsa.umich.edu (Howard Chu) writes:
>In article <51989@ccicpg.UUCP> paulm@ccicpg.UUCP (tmp Paul Moreau usenet acct) writes:
>>Well it seems that the LHARC is going to take over the atari archiving
>>world.  I for one use a UNIX system for posting and recieving news
>>and binaries.   I uudecode, and unarc on the unix system and examine
>>the stuff before going through the expense of going home, making a 
>>LONG DISTANCE call to work and download the stuff.  If LHARC is to be
>>the new standard (which I can see the benefit in smaller archives) I'd
>>like to get the source so I can port it to our UNIX system.
>>If the source is protected (which it seems to be) then I don't think
>>I'll be downloading any more files unless I know what to expect in them.

>I have the source for LHARC. I haven't bothered doing anything with it yet.
>It's 80% 8086 assembler. Even the C source code is full of ASM compiler
>directives. Most of the comments are in Japanese, for a Kanji character
>set, and show up as weird diacriticals on an ST display. I doubt any
>printer would like them very much.

I strongly support Moreau's call for a Unix version.  I run a BBS on a
Unix system with archives on a PC with a huge drive.  Both zoo and arc
formats are supported by all three OS's, but LHARC is creating lots of
problems for me.  It should not be used for a group like this unless it
can run on all machines through which the code is likely to pass.

-- 
Bill Silvert, Habitat Ecology Division.
Bedford Institute of Oceanography, Dartmouth, NS, Canada B2Y 4A2
	UUCP: ...!{uunet,watmath}!dalcs!biomel!bill
	Internet: biomel@cs.dal.CA	BITNET: bs%dalcs@dalac.BITNET