schung@cory.Berkeley.EDU (Stephen the Greatest) (11/01/87)
In article <15100001@silver> sl131072@silver.bacs.indiana.edu writes: > > > I have had several problems compiling the files for Conquest. If >anyone gets them to compile correctly please contact me. > I have successfully compiled Conquest (first try!) but there are a lot of problems with it. First of all, sometimes you have to press [LINE FEED] instead of [RETURN] to enter a line of text or a choice. But then, since Line-Feeds just jump to the next line, the screen display gets screwed up. I changed all testings for '\n' after getch() to '\r' and it did eliminate some of the problems, but not all. At a lot of places you still need to press [LINE FEED]. Seems to me that you should be able to press both and get the same results... Also, [DELETE] is not interchangable with ^H. I was using a Sun, and have to press [BACKSPACE] instead of [DELETE]. If I press [DELETE], unpredictable things happened. Conquest seems to hang all the time, mostly at random places. I can't do anything, except go to another terminal and kill my login. At some places, it says 'Press [RETURN] to continue', but it continues without waiting for a key-stroke. This happens a lot on the 'c' command. I can't do anything. A lot of commands are not documentated, like 'a', 'f' etc. etc. I have no idea how to use those. Also, the documentation is more of a story-history-background type than actually how to play the darn game. A lot of players send me mail asking, 'Yeah, I got in, but what do I do next?' Just a *VERY SMALL PORTION* of all the problems! - Stephen
lance@kodak.UUCP (dan lance) (11/02/87)
Some problems compiling Conquest: I'm running SunOS 3.4 on a Sun3/260 and cannot get the calls to write(2) in io.c, function writedata(), to work properly. I am pretty sure that the write(2) call in SunOS doesn't like being passed an array of structure elements... Anyways, if anyone has gotten this function to work on a Sun, I would appreciate being mailed the source (plus that to readdata(), for compatibility.) In return, I'll mail you back a copy of my cleaned-up makefile for Conquest. Thanks! --drl ===== Daniel R. Lance Illegitimati non carborundum. Eastman Kodak Company Purdue University Electrical Engineering ..!rochester!kodak!lance lanced@ei.ecn.purdue.edu ..!pur-ee!lanced
stucki@tut.cis.ohio-state.edu (David J. Stucki) (11/02/87)
In article <4696@zen.berkeley.edu> schung@cory.Berkeley.EDU.UUCP (Stephen the Greatest) writes: > > I have successfully compiled Conquest (first try!) but there > are a lot of problems with it. First of all, sometimes you > have to press [LINE FEED] instead of [RETURN] to enter a > line of text or a choice. But then, since Line-Feeds just > jump to the next line, the screen display gets screwed up. > I changed all testings for '\n' after getch() to '\r' and > it did eliminate some of the problems, but not all. At a lot > of places you still need to press [LINE FEED]. Seems to me > that you should be able to press both and get the same results... I have had the same troubles on the Sun 3/50's, but I discovered "by mistake" that if you type CRTL-J instead of <RET> at the end of a numerical input that the game doesn't complain. This isn't a good solution but at least it will work until a more permanent fix is posted. > A lot of commands are not documentated, like 'a', 'f' etc. etc. > I have no idea how to use those. Also, the documentation is > more of a story-history-background type than actually how to > play the darn game. A lot of players send me mail asking, 'Yeah, > I got in, but what do I do next?' We set up a practice world at first to play around with for a week or so, just to let us figure out how to play and get used to the game. If you aren't trying to play to win the first time you sit down with it, it is a lot easier to experiment with the commands and at least get a sense of "oh, if I do this the game will respond with such and such an action". Until there is better documentation it isn't all that hard to figure out how to play the basic game. ~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~ David J Stucki c/o Dept. Computer and P.O. Box 713 Park Hall Information Science 110 W. 11th Ave. 2036 Neil Ave. Columbus, OH 43210 O.S.U Columbus, OH 43210 ...!cbosgd!osu-cis!tut!stucki stucki@tut.cis.ohio-state.edu I DIDN'T EXPECT THE SPANISH INQUISITION!!! +~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+ [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................] [mailer's food.....................................................]
guy%gorodish@Sun.COM (Guy Harris) (11/02/87)
> I'm running SunOS 3.4 on a Sun3/260 and cannot get the calls > to write(2) in io.c, function writedata(), to work properly. > I am pretty sure that the write(2) call in SunOS doesn't like > being passed an array of structure elements... If you're very sure about that, you're very wrong. "write" is quite happy to be passed a pointer to an array of structure elements (which is what that call does). You're better off handing it a "char *", as that's what "write" is defined to take as a second argument (i.e., the second argument should be cast to "char *"), but on some machines, including Suns, all pointers have the same representation so you can get away with that sort of thing. You shouldn't *rely* on being able to get away with it, though. Guy Harris {ihnp4, decvax, seismo, decwrl, ...}!sun!guy guy@sun.com