Conference hydra::amiga_v1

    Did you check comp.binaries.amiga?  The executable is in there in
    11 parts.

I have the executables downloaded, unshared, uudecoded, unzooed and
rezooed into four parts, but I can't get through to NORSE:: to post them.
Does anyone know what's wrong with norse ? or can someone let me know
where else to copy them to ? WJG ?? TAPE ??

				Alan T.

Mail me if you do so I can move them to WJG::AMIGA:

John

>< Note 2669.3 by WJG::GUINEAU >
>                   -< you can put them on WJG::SYS$PUBLIC: >-
>
>
>Mail me if you do so I can move them to WJG::AMIGA:
>
>John

Thanks John,
	I'll copy them over as soon as I've posted this note. The files
are MANDV2_1.ZOO, MANDV2_2.ZOO, MANDV2_3.ZOO and MANDV2_4.ZOO

	I've also just downloaded today's offerings from Bob Page,
NOCLICK.ZOO (for machines with kickstart in ROM) and JAZZBENCH.ZOO ( a
workbench replacement) which I will also upload if you don't mind.

All files are Stream_LF for XMODEM downloading.

					Alan T.

I forgot to mention.....

In one of the MANDV2_*.ZOO files is a file called MANDFIX.SH which is a
script file to put everything in their proper subdirectories. Just UNZOO
everything onto one disk and then execute MANDFIX.SH


					Alan T.

The follwing new files are now on WJG::AMIGA: compliments of Alan Thomson:



JAZZBENCH.ZOO;1         287  22-JUN-1989 13:35:31.00  (RWED,RWED,RE,)
MANDV2_1.ZOO;1          342  21-JUN-1989 14:53:24.00  (RWED,RWED,RE,)
MANDV2_2.ZOO;1          123  21-JUN-1989 14:59:40.00  (RWED,RWED,RE,)
MANDV2_3.ZOO;1          172  21-JUN-1989 16:00:50.00  (RWED,RWED,RE,)
MANDV2_4.ZOO;1          211  21-JUN-1989 16:01:56.00  (RWED,RWED,RE,)
NOCLICK.ZOO;1             4  22-JUN-1989 13:36:25.00  (RWED,RWED,RE,)
SETCPU.ZOO;2             62  22-JUN-1989 14:30:53.00  (RWED,RWED,RE,R)


John

    
    FYI Someone here mentioned a while ago that there is a problem with
        the NORSE cluster alias, but you can access norse fine via node
        PILAGE.

I tried NOCLICK last night on my A500 (1Mb, external CUMANA CAX354 floppy)
and it works... (kind of). I have no idea what make my internal drive is.

If I type NOCLICK from the CLI with a disk in both drives OR just a disk in
the internal drive, it runs no problem, my prompt is returned and df1: will
stop clicking (df0: still clicks.)

If I type NOCLICK from the CLI with no disks in either drive then df0:
will stop clicking (df1: still clicks.)

If I type NOCLICK for a second time (irrespective of which drive has disks
inserted) its GURU time.

If I put NOCLICK in my startup-sequence it works (df1: stops clicking) but
it returns a HUGE return code, so you must run > NIL: NOCLICK

Does anyone have any ideas how I can get BOTH drives to stop clicking ?

					Alan T.

BTW It is very usable as it is, as I only have a floppy system, df0: is very
rarely empty, so a quiet df1: is a great improvement.

    re: -1 (noclick)
    
    I had similar problems.  I've got a 2000 with two internals, putting
    noclick in my startup sequence seemed to fix only DF1: for me.  I
    tried at least twenty or so different places/combinations.  My startup
    sequence starts up a WSHell window for me since I usually use the
    CLI.  Noclick seems to work consistently if I wait until this window
    is running then manually enter noclick twice.  The first one stops
    df0: and the second stops df1:.  If I add these to the end of the
    startup for that wshell window, I get the guru.
    
    Really wierd.  Maybe someone with the time can disassemble this puppy
    and fix it (< 500 bytes).  Better yet, maybe Bob Page will post the
    source to usenet in the next few days...
    
    regards,
    
    steve

< Note 2669.9 by TALLIS::MCAFEE "Steve McAfee" >
                           -< it works (sometimes) >-

>    Really wierd.  Maybe someone with the time can disassemble this puppy
>    and fix it (< 500 bytes).  Better yet, maybe Bob Page will post the
>    source to usenet in the next few days...
>    
>    regards,
>    
>    steve

I don't think the source will show up Steve, Bob Page said that he
didn't have the source for it when he "announced" what would be coming
over on comp.binaries.amiga

					Alan T.

    MandelVroom is a neat program, but there seems to be a file missing
    from the version on the Enet: the documentation file!  I have learned
    a lot from reading the copious help files, but some aspects of
    contouring are still obscure to me.  Could someone who has the
    facilities to unshar the Usenet messages put the .DOC file in one
    of the archives, or post it here?
        John Sauter

John, I jsust looked through all 9 parts from USENET. None had *any* 
documentation!


John

    Does anybody have the Fish disk?  Maybe it's there.
        John Sauter

    
    
    	Fish disk 214 has the source code and disk 215 has binary and
    documentation. Both are in 
    
    		TAPE::USER1:[AMIGA.FISH.FFxxx]
    
    
    		Steve Peters
    

    re: .14
    
    It was on FF215.  Thanks.
        John Sauter