iisakkil@xaloc.tky.hut.fi (Mika R Iisakkila) (12/27/90)
In article <16660001@col.hp.com> mikek@col.hp.com (Mike Karin) writes: > I have seen several requests about the format of the documentation file. > There have been no answers. Doesn't anybody know? I don't, but you can use any binary editor (or pc-tools, or LIST in hexadecimal mode) to read it easily enough.
sophist@brainiac.raidernet.com (Phillip McReynolds) (01/07/91)
iisakkil@xaloc.tky.hut.fi (Mika R Iisakkila) writes: > In article <16660001@col.hp.com> mikek@col.hp.com (Mike Karin) writes: > > I have seen several requests about the format of the documentation file. > > There have been no answers. Doesn't anybody know? > > I don't, but you can use any binary editor (or pc-tools, or > LIST in hexadecimal mode) to read it easily enough. Or try this: strings goose.doc | more = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Phillip A. McReynolds, sophist@brainiac.raidernet.com Licensed Philosopher org: Phillip's Philosophy Shop, Inc. (MPA Certified) "Quality Philosophy Products Since 1990" = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
mjlst3@unix.cis.pitt.edu (Mikes Magik Shoppe) (01/09/91)
>> In article <16660001@col.hp.com> mikek@col.hp.com (Mike Karin) writes: >> > I have seen several requests about the format of the documentation file. >> > There have been no answers. Doesn't anybody know? It's in PFS professional write format, I'll post it tomorrow for those who don't really want to deal with binary tricks. I assume the author simply forgot to save as ascii before making the distribution. (or its just part of the game ;-) Michael J. LeWinter -- All email, no cute messages to mankind : mjl@vms.cis.pitt.edu mjl@pittvms.bitnet
mjlst3@unix.cis.pitt.edu (Mikes Magik Shoppe) (01/10/91)
The following is the stargoose documentation as read in by
pfs professional write and saved out as a text file.
______ cut over there _____
StarGoose Documentation
Copyright 1988 S. Can and G. Everett
The Game
Stargoose is a bit like Zaxxon but is better...
Object of the game is to destroy the mother base... The final
Frontier... You have 4 ships in your squadron.. Your
level will advance by collecting pods... The pods will appear
like colored circles on the playing field and as you collect
the pods the pod indicators to the left of the FUEL, SHIELDS,
AND AMMUNITION will change from the color indicated to a deep
blue. When all six have changed color you will advance to
the next level... The first thing you want to is set your
controls.. You may select left, right, fire thrust, brakes,
left missile and right missile.. You may replenish your
missiles by going through the center of the missile center...
Every time you advance a level you can loose all of you ships
and if you stay and play another round you can stay at the
advanced level and do not have to start from scratch....
Enough tips..... I have left you a few sunrises... Hope you
enjoy... Watch for future releases on a board near you....
Type "GOOSE" to run the game...
Press the F1 key to set your own Keyboard Control
Sorry that this game requires 256K and EGA Controller
You may upload this Game to any bulletin board but it is not
shareware....
This is Freeware...
This means that this program is free to everyone... It is
copyrighted only to prevent duplication in a Commercial
package....
The program is written in C and took over 7600 lines of
code and over 7 months to write..
Copying this game....
Stargoose may be uploaded to bulletin boards with the
stipulation that the following files remain intact..
Goose.doc The document you are reading
Goose.exe The program
Bird1.x
podz1.x
intro.x
newbird.x
blox.x
bird2.x
hiscores
Have Fun and may the force be with you.....
--
All email, no cute messages to mankind : mjl@vms.cis.pitt.edu
mjl@pittvms.bitnetluce@aurs01.UUCP (J. Luce) (02/17/91)
I never saw an answer to this even though I *TRY* to read this group
daily...
How does one get the Star Goose docs into a readable format?
It is nothing my printer or any of 5 word processors understand
(although in fairness, I should mention hey are all circa 1985 WPs).
Thanks!!
-------------------------------------------------------------------
John Luce | Life is the leading cause of death
Alcatel Network Systems | -----------------------------------------
Raleigh, NC | Standard Disclaimer Applies
919-850-6787 | Mail? Here? Try aurs01!aurw46!luce@mcnc.org
| or ...!mcnc!aurgate!luce
-------------------------------- or John.Luce@f130.n151.z1.fidonet.org timur@seas.gwu.edu (The Time Traveler) (02/18/91)
In article <59578@aurs01.UUCP> luce@aurw46.UUCP (J. Luce) writes: >I never saw an answer to this even though I *TRY* to read this group >daily... > >How does one get the Star Goose docs into a readable format? > >It is nothing my printer or any of 5 word processors understand >(although in fairness, I should mention hey are all circa 1985 WPs). > It's a PFS:Write document. I'll try to convert it to text, and post it to comp.binaries.ibm.pc. ----------------------------------------------------------- The Time Traveler Sadder still to watch it die a.k.a. Timur Tabi Then never to have known it Internet: timur@seas.gwu.edu For you - the blind who once could see - Bitnet: HE891C@GWUVM The bell tolls for thee -- Rush
luce@aurs01.UUCP (J. Luce) (02/18/91)
In article <2744@sparko.gwu.edu> timur@seas.gwu.edu () writes: >In article <59578@aurs01.UUCP> luce@aurw46.UUCP (J. Luce) writes: >>How does one get the Star Goose docs into a readable format? >> >> >It's a PFS:Write document. I'll try to convert it to text, and post >it to comp.binaries.ibm.pc. > >Sadder still to watch it die a.k.a. Timur Tabi >Then never to have known it Internet: timur@seas.gwu.edu >For you - the blind who once could see - Bitnet: HE891C@GWUVM >The bell tolls for thee -- Rush Thanks. I appreciate that very much. I can get the basic game going and it looks real good, but can't do much else w/o SOME knowledge :) ------------------------------------------------------------------- John Luce | Life is the leading cause of death Alcatel Network Systems | ----------------------------------------- Raleigh, NC | Standard Disclaimer Applies 919-850-6787 | Mail? Here? Try aurs01!aurw46!luce@mcnc.org | or ...!mcnc!aurgate!luce -------------------------------- or John.Luce@f130.n151.z1.fidonet.org
davidsen@sixhub.UUCP (Wm E. Davidsen Jr) (02/21/91)
I got the stargoose cleartext docs today and will try to get them out
by the weekend. However, I had a meeting last night, tonight, and
tomorrow night, and I got six MB of new stuff today.
Six {<_!!_>} MB.
Bear with me people, I can't even throw it away as fast as it comes
in, much less read and post it. And stuff like the new virus scanners
had to be rushed through to help people protect themselves.
--
bill davidsen - davidsen@sixhub.uucp (uunet!crdgw1!sixhub!davidsen)
sysop *IX BBS and Public Access UNIX
moderator of comp.binaries.ibm.pc and 80386 mailing list
"Stupidity, like virtue, is its own reward" -metcs@mailer.jhuapl.edu (Carl Schelin) (02/21/91)
In article <3250@sixhub.UUCP>, davidsen@sixhub.UUCP (Wm E. Davidsen Jr) says: > > ... > > Bear with me people, I can't even throw it away as fast as it comes >in, much less read and post it. And stuff like the new virus scanners >had to be rushed through to help people protect themselves. >-- >bill davidsen... > ... So the assumption is that if I don't see anything that I sent in, it got thrown away? Not yelling, just curious. I've sent in two items and am about to send in another and I want to know if it is worth sending. I don't remember seeing anything in the frequent posts about criteria for posts. Thanks. Carl Schelin tcs@mailer.jhuapl.edu
davidsen@sixhub.UUCP (Wm E. Davidsen Jr) (02/23/91)
In article <1991Feb21.124047.27606@aplcen.apl.jhu.edu> tcs@mailer.jhuapl.edu (Carl Schelin) writes: | So the assumption is that if I don't see anything that I sent in, it got | thrown away? Never. If I don't use something I'm very careful to tell the submitter why I didn't. If you don't see it in a month or so then you might ask if I got it. When I take things out of the first hopper and determine that all the parts came in I send a first thank you. When the review is done and the item goes into the actual queue ready to post I send another. But if the thank you bounces... tough. I just can't take time to chase anyone based on the mail addresses I get. If the header or the .sig aren't useful I forget it. Stuff is running 2-5 weeks because of how long it takes to review. Did the first thank you have a paragraph about uuencoders which use blanks instead of ` so the trailing blanks get eaten in mailing? Did I get five parts with no part numbers in the header? Did I get a load of uuencoded SOMETHING with no clue in the first message as to what this is? Or a self unpacking binary? If any of these things are true then it goes in a "slush pile" and I do a few a day. The ones which come in with a description, part numbers, clean encoding... those go out faster. We used to have a problem with nothing going out, now we have a problem with more coming in than going out. We are staying in the top ten groups for volume every month, so I guess the readers are getting a fair share, just the posters are getting delayed. Since there's a step which is currently being taken between machines via floppy disk, I could lose a disk full of submissions and have no fallback. After I write it and read it back the submissions are blown away from the machine which gets the stuff first. It could be worse. Look at comp.sources.unix. -- bill davidsen - davidsen@sixhub.uucp (uunet!crdgw1!sixhub!davidsen) sysop *IX BBS and Public Access UNIX moderator of comp.binaries.ibm.pc and 80386 mailing list "Stupidity, like virtue, is its own reward" -me
tcs@mailer.jhuapl.edu (Carl Schelin) (02/25/91)
In article <3279@sixhub.UUCP>, davidsen@sixhub.UUCP (Wm E. Davidsen Jr) says: > >In article <1991Feb21.124047.27606@aplcen.apl.jhu.edu> tcs@mailer.jhuapl.edu (Carl Schelin) writes: > >| So the assumption is that if I don't see anything that I sent in, it got >| thrown away? > > Never. If I don't use something I'm very careful to tell the submitter >why I didn't. If you don't see it in a month or so then you might ask if >I got it. When I take things out of the first hopper and determine that >all the parts came in I send a first thank you. When the review is done >and the item goes into the actual queue ready to post I send another. >But if the thank you bounces... tough. I just can't take time to chase >anyone based on the mail addresses I get. If the header or the .sig >aren't useful I forget it. > Understood. I received a message from you (or your mailer) that said that you did get the first program. Nothing from the second but I sent it in in the past few weeks. > > Stuff is running 2-5 weeks because of how long it takes to review. Did >the first thank you have a paragraph about uuencoders which use blanks >instead of ` so the trailing blanks get eaten in mailing? Did I get five >parts with no part numbers in the header? Did I get a load of uuencoded >SOMETHING with no clue in the first message as to what this is? Or a >self unpacking binary? If any of these things are true then it goes in a >"slush pile" and I do a few a day. The ones which come in with a >description, part numbers, clean encoding... those go out faster. > I don't remember the gist of the first message. Just that it was received. I don't think there was anything about blanks because I would have resent it corrected. I'm sure that I sent a small paragraph stating what it was and I made sure to put the name and 01/01 in the subject. I sent in a .zoo file. I remember because you said that it was what you prefered so I had to unzip it and zoo it back up. The second one may have been a .zip file. It was in response to the small disk utility that was posted a week or two ago. Free returns the total drive space, how much is left and the current directory for each drive. I thought it was a better utility than the one posted. The two programs I sent were small (the first about 50k the second no more than 20k). > We used to have a problem with nothing going out, now we have a >problem with more coming in than going out. We are staying in the top >ten groups for volume every month, so I guess the readers are getting a >fair share, just the posters are getting delayed. Since there's a step >which is currently being taken between machines via floppy disk, I could >lose a disk full of submissions and have no fallback. After I write it >and read it back the submissions are blown away from the machine which >gets the stuff first. > > It could be worse. Look at comp.sources.unix. >-- While I have had no reason to look at that group, I agree that you are doing a great job. I am certainly NOT complaining about the posts in any way. I will unzoo, delzh, unzip, unarc or whatever you want to do. I consider it your group and we're just kibitzers (sp?). Thanks again for doing such a great job. >bill davidsen - davidsen@sixhub.uucp (uunet!crdgw1!sixhub!davidsen) > sysop *IX BBS and Public Access UNIX > moderator of comp.binaries.ibm.pc and 80386 mailing list >"Stupidity, like virtue, is its own reward" -me Carl Schelin tcs@mailer.jhuapl.edu