home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!elroy.jpl.nasa.gov!ucla-cs!rutgers!njitgw.njit.edu!hertz.njit.edu!dic5340
- From: dic5340@hertz.njit.edu (David Charlap)
- Newsgroups: comp.os.os2.programmer
- Subject: Re: How to install gccbin21.zoo
- Message-ID: <1992Jul23.201608.24607@njitgw.njit.edu>
- Date: 23 Jul 92 20:16:08 GMT
- References: <1992Jul22.094409.433@weyrich.UUCP>
- Sender: news@njit.edu
- Distribution: usa
- Organization: New Jersey Institute of Technology, Newark, N.J.
- Lines: 72
- Nntp-Posting-Host: hertz.njit.edu
-
- In article <1992Jul22.094409.433@weyrich.UUCP> tnet.com!weyrich!orville writes:
- >Hi --
- >
- >I just got gccbin21.zoo from hobbes. When I tried to un-zoo it with my
- >(DOS-based) zoo program, I got a message that it needed "zoo 2.1" to
- >do the extraction. The most recent version of zoo I can find is 2.01.
- >
- >So -- where do I look for zoo 2.1?
-
- Go to ftp-os2.nmsu.edu. The file you want is zoo210.exe. It is a
- self-extracting archive with zoo 2.1. I think it's located in
- /pub/os2/all/archivers.
-
- >Also, I noticed that the file names appear to have been zoo'ed with
- >case sensitive names. Can they be successfully extracted by ANY DOS-based
- >zoo? If not, then I have the additional dilemma of how I can move the
- >files to my OS/2 platform -- gccbin21.zoo is too big to fit on a single
- >floppy, and I don't have kermit or any other tools on my OS/2 platform yet.
- >All I do have is the gccbin21.zoo file sitting on my unix platform (which has
- >DOS-MERGE, so I can run dos applications).
-
- The case-sensitivity shouldn't be a problem. A DOS-based zoo may
- convert it all to upper-case, but that's OK, since HPFS doesn't use
- the case for anything - it just stores it to make things look better.
- If you've an OS/2-based zoo extracter, the case will be preserved.
-
- Yes, the file is too big for a floppy. There are many ways to get
- this home. One way is to use a unix zoo command to unpack it on Unix
- and make smaller archives there.
-
- Another way is to write a small c program to read the file (in binary
- mode) and write it out to multiple files of, say, 1MB each. Once you
- have them on your OS/2 machine, you can just do a
-
- COPY /b part1+part2+part3 gccbin21.zoo
-
- to combine them together again.
-
- The third choice (what I did) requires that you download a UU-decoder
- for OS/2. There exists on one ftp-os2.nmsu.edu. Look for uucode.zoo
- or uuxxcode.zoo in the /pub/os2/all/archivers directory.
-
- Anyhow, the third way involves uu-encoding the entire file into ASCII
- text using the command:
-
- uuencode gccbin21.zoo gccbin21.zoo > gccbin21.zoo.uue
-
- From there, you split the file into multiple parts of smaller size.
- The Unix split command will work here. You can only use split on text
- files, so you couldn't use it with method 2. Anyhow, I find that
- 16000 lines produces files of about 950K. Split it with the following
- command:
-
- split -16000 gcc21bin.zoo.uue gcc21bin.
-
- This will produce multiple files with names like: gcc21bin.aa,
- gcc21bin.ab, etc... Download these. Combine them together under OS/2
- with the following command:
-
- copy gcc21bin.aa+gcc21bin.ab+... gcc21bin.zoo.uue
-
- If you don't have HPFS, you can replace the gcc21bin.zoo.uue with a
- simple gcc21bin.uue.
-
- This being done, you can then run your uudecoder on the output to get
- gcc21bin.zoo. Proceed to extract as you see fit.
-
- --
- |) David Charlap "I don't even represent myself
- /|_ dic5340@hertz.njit.edu sometimes so NJIT is right out!.
- ((|,)
- ~|~ Hi! I am a .signature virus, copy me into your .signature file.
-