jonasf@kuling.UUCP (Mad Flax) (12/15/87)
[Whatever..] Had a visit today.. Guess who? My M.O.. Download the three (new) postings of amoeba. (Kermit) Concat #1 & #2. uudecode. unshar #3 and uudecode. Read amoeba.text. Check filesizes. Wow, perfect match. Can't wait, have to try it. Hello guru, no time long see. Aha, try with nofastmem. Hm, he's back again. I tried increasing stacksize. Nope. I haven't installed GOMF yet, but I will. Then maybe I can figure out more about why i get these annoying visits. (I have one tough exam tomorrow, and will spend the night poring over my books.. So... later, maybe.) Anyway, if youze guys who wrote amoeba.text are on the net, read this. amoeba bombs on my A2000, expanded memory, 1.2 (obviously) (Not much help, I KNOW, but you're warned now. ;-) Any mispelings and errors in the above are probably due to the numerous cups with hot infusion of Thea Ternstroemiceae (Sinensis) and Coffea Arabica, that I use to stay awake.
jw@sics.se (Johan Widen) (12/17/87)
In article <583@kuling.UUCP> jonasf@kuling.UUCP (Mad Flax) writes: >Check filesizes. Wow, perfect match. Can't wait, have to try it. >Hello guru, no time long see. Amoeba bombs because some bytes were lost in the transmission. (Yes, I'm speaking of the second posting of amoeba.) At least two characters had disappeared in the file that reached our site. This occurred in the 255'th uuencoded line (in part 1). You would have discovered this if you had used the recently posted version of uudecode (this version recognizes checksums at the end of the lines). -- Johan Widen SICS, PO Box 1263, S-163 13 SPANGA, SWEDEN Tel: +46 8 750 79 70 Ttx: 812 61 54 SICS S Fax: +46 8 751 72 30 Internet: jw@sics.se or {mcvax,munnari,ukc,unido}!enea!sics.se!jw
dbjag@io.UUCP (David Benjamin) (12/19/87)
In article <583@kuling.UUCP>, jonasf@kuling.UUCP (Mad Flax) writes: > . ...stuff... > Download the three (new) postings of amoeba. (Kermit) > Concat #1 & #2. uudecode. > unshar #3 and uudecode. . ...more stuff... > Hello guru, no time long see. . ...more stuff, cries of frustration, attempts with nofastmem, larger stack, still no success. He sighs and realizes he just might have to go back to work.... I've been successfully running AMOEBA on a Amiga 1000 with expanded memory (Insider) and WB1.2 with no problem. You've probably picked this up already, but there are TWO patches to the main uuencoded version of AMOEBA. The second set were submitted as two one-liners (I believe that one had already been included in the second posting of the 3-part set). Anyways, after these patches, you should be able to get going. I'd like to take this posting to thank the folks at Late Night Developments for a TRULY GREAT GAME! Good work, to bad about the posting glitches... Now, if you have a version of Galaxian lying around... -- ...!sun!sunne!ileaf!dbjag | Dave Benjamin -------------------- Interleaf ...!harvard!umb!ileaf!dbjag | -------------------------------------------- -"Three-way bulbs actually have a secret FOURTH way that only dogs can see."- ---------------------------- | --------------------------------------------
ljc@otter.hple.hp.com (Lee Carter) (06/20/88)
Look, I know this keeps rearing it,s ugly head, but I've only just got the game so...... Help please! As many spoilers as you want to send me on Shadowgate, also help with Uninvited and Deja Vu would be appreciated. I have completely solved The Pawn, Hitchhikers Guide and Guild of Thieves if anyone wants to swap hints. Yours in anticipation. Lee Carter.
peter@cbmvax.commodore.com (Peter Cherna) (07/14/90)
In article <12541@june.cs.washington.edu> dylan@june.cs.washington.edu (Dylan McNamee) writes: >In article -38440@sequent.UUCP= cseaman@sequent.UUCP (Chris "I'm Outta Here, Man!" Seaman) writes: >=bscott@nyx.UUCP (Ben Scott) writes: >=- bn@okcusr.UUCP writes: >=- There's a simple clean fix for this. Go in through HD_Toolbox, to "Partition >=- Drive", then click on "Advanced Options" and you'll see a box labeled "Add/ >=- Update Filesystems" -click this and then change the version number of the FFS >=- from 0 to 1. >= >=Sorry, but this doesn't fix anything. I have had this problem since the >=day I installed my 2091, and NONE of the suggested fixes have done anything. >=Believe me, I REALLY wish this was the case. Unfortunately, it isn't. In fact, > >My experience agrees with Chris's; changing the version number did >nothing at all. I still have to run my (56 byte!) clearZero C program. You must understand what is going on here when you change the version number. You may be ONLY CHANGING A NUMBER. The real scoop: When you autoboot of an FFS drive, the FastFileSystem is not loaded from L:, since you need to be up and running to read L: from your hard disk! HDToolBox will install a FastFileSystem into the "Rigid Disk Block" of your hard disk, which can be read before the disk is booted from. Now, some hard disks were prepared with a debugging version of the FastFileSystem, that left a marker in memory location zero, which is the string "gdos". The FFS that was shipped with the 1.3.2 Workbench update does not have this effect. * IT IS NOT SUFFICIENT TO COPY THIS FILESYSTEM TO THE L: DIRECTORY OF YOUR HARD DRIVE. * IT IS NOT SUFFICIENT TO CHANGE THE VERSION NUMBER IN HDTOOLBOX. (Sorry about the caps, but this can't be made clear enough). Here is what to do: Go into HDToolbox, select Partition Drive, then Advanced Options, then Add/Update FileSystem. Then, select Update File System. A requester will appear, which has a filename ("l:FastFileSystem") and a version number in it. (Forget the version number). Ensure that the name points at a 1.3.2 disk's FFS, eg. df0:l/FastFileSystem, if your 1.3.2 disk is in df0:. Then select OK. The size of the FastFileSystem will now appear as 12248 (if you used a 1.3.2 disk). Now exit from HDToolbox, saving changes to your drive. Reboot, and you will be fine. (Changing the version number only would "magically" work if l:FastFileSystem happened to point at a correct FFS when you close the requester.) If you do this correctly, you will NOT find the string "gdos" in location zero anymore. >=If anyone has any other ideas, I am willing to try anything. However, I >=have tried the 'change the version to 1', 'manually force the filesystem >=to be updated', 'install the filesystem from another Workbench disk' tricks >=more times than I care to mention. So please, DON'T suggest I do these >=things again. THEY DON'T FIX THE PROBLEM! Chris Seaman is quite insistent he has done all the right things but still has a problem. I assure you that these steps indeed do fix the problem. I claim Chris has some other problem. Chris: can you tell me what software you launch in your startup-sequence? Do you know what value you find in location zero before you clear it? >=Chris (Insert phrase here) Seaman | /--\ > >dylan -dylan@cs.washington.edu Peter -- Peter Cherna, Software Engineer, Commodore-Amiga, Inc. {uunet|rutgers}!cbmvax!peter peter@cbmvax.cbm.commodore.com My opinions do not necessarily represent the opinions of my employer. "This is a one line proof...if we start sufficiently far to the left."