home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os2.apps
- Path: sparky!uunet!nevada.edu!jimi!big-joe.cs.unlv.edu!slumos
- From: slumos@big-joe.cs.unlv.edu (Steve E. Lumos)
- Subject: Re: REXXShip 2.0: Self-Extrac
- Message-ID: <1992Sep9.000209.28920@unlv.edu>
- Sender: news@unlv.edu (News User)
- Reply-To: slumos@big-joe.cs.unlv.edu (Steve E. Lumos)
- Organization: UNLV Computer Science and Electrical Engineering
- References: <5288.688.uupcb@spacebbs.com>
- Distribution: na
- Date: Wed, 9 Sep 92 00:02:09 GMT
- Lines: 24
-
- In article <5288.688.uupcb@spacebbs.com>, michael.hagerty@spacebbs.com (Michael Hagerty) writes:
- )
- ) Tried running it per instructions and all I got was a file of binary
- ) garbage after running it. I assume that if I got the messages: Decoding
- ) and then "Done" it had created the correct file. Perhaps it was corrupted
- ) enroute.
- )
- ) A lot of people are now getting this conference via UUPCB, which splits
- ) messages up into 100 line segments as that is what PC Board is expecting.
- ) If you are going to send this out in the future, you might want to keep
- ) that in mind. Perhaps REXXShip might reasonably be expected to have a
- ) count on each line which is checked to see if the sections got put together
- ) wrong...
- )
- ) Regards, Mikey
- ) ---
- ) . JABBER v1.2 #42 . Basset Hounds make better friends than most people.
- )
- We should NOT start limiting messages to 100 lines. The 64k limit is bad
- enough. Start flaming Clark Developement to fix PCB. I'm sick of the 100
- line limit when I go BBSing already, I don't want to have to put up with
- it here too.
- --
- Steve Lumos - slumos@cs.unlv.edu
-