Xref: utzoo comp.binaries.ibm.pc.d:206 comp.sys.ibm.pc:15447 Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!nrl-cmf!ames!oliveb!felix!dhw68k!mike From: mike@dhw68k.cts.com (Michael J. Cleary) Newsgroups: comp.binaries.ibm.pc.d,comp.sys.ibm.pc Subject: Re: File Transmission Standards Message-ID: <7870@dhw68k.cts.com> Date: 11 May 88 02:41:24 GMT Reply-To: mike@dhw68k.cts.com (Michael J. Cleary) Organization: Wolfskill residence; Anaheim, CA (USA) Lines: 37 I am surprised at the current methods utilized by the NET for transmitting files. The splitting, cutting, pasting. The uuencoding, uudecoding. The archiving, unarchiving. compress PKARC ZOO ARC Based on the current skill level of the programmers on the NET, I would think that one could write a program that could do all of these functions for both posting (NET format) and deposting (MS-DOS format). Besides streamlining the process, it would avoid the number of manual steps (possible points of errors). I do not know how many times I have seen NETers complain about not being able to run the program after going through the series of manual processes to extract it from Net format. Standardization would also be a side effect of this type of program, as you would not need to *know* which reverse processes needed to be applied. Currently, I do not utilize executables from the NET, as I do not want to get involved in the manual task of deNETting them. I basically call local BBS's and just simply push a button to retrieve the file. If only the NET was so easy. :-) I am *NOT* flaming this sequence of manual tasks passed on from father to son, I am just pointing out that there must be a more professional way to approach the issue. I would like everyone to talk about this, because I would like to see something done about it. -- Michael J. Cleary