Conference 7.286::atarist

    Well, that made a big difference. No hard drive - No problem.
    
    Is this another manifestation of 'weak' 74LS373 bus driver chips?
    

Is having the HD attached what is causing Indy not to work as well?

With the HD attached were you running STETRIS2 from floppy or from the HD.
Maybe you have a bad copy of STETRIS2 on the HD.

	Ray

    		( ATARI HD INTERFACE -->AHDI )
    
    YOU SHOULD TRY IT WITH AHDI VERSION 1.7 , INSTALL VERSION 2.0
    NEWER VERSION'S LIKE 3.0 OR 3.1 ARE NOT WORKING WITH ALL PROGRAMS
    
    PS: AHDI.PRG  OR INSTALL ARE ON THE HD BOOT-DISK
    
    				FRED
    

    re 659.7
    
    Yes, my problems described in the base note seem to be related directly
    the the NEODESK V2.0 printer queue accessory and TOS 1.4.
    
    I held off entering an update to this note until I had done some more
    exhaustive research.
    
    GRIBNIF has rewritten the Printer Queue Accessory, I believe. They are
    scheduled to be at the November NaVaus club meeting. I will be getting
    an upgrade to the latest level of NEODESK at that meeting and we will
    discuss the problem with Rick Flashman.
    
    STETRIS2 did not bomb in a consistent fashion with 1.4/NEOQUEUE but did
    fail. It does not fail when NEOQUEUE is not installed.
    
    Sorry for the faulty alarm on 1.4.
    

>Yes, my problems described in the base note seem to be related directly
>the the NEODESK V2.0 printer queue accessory and TOS 1.4.
    
    That doesn't surprise me, I've seen the same thing.

>GRIBNIF has rewritten the Printer Queue Accessory, I believe.

    I hope so!

>STETRIS2 did not bomb in a consistent fashion with 1.4/NEOQUEUE but did
>fail. It does not fail when NEOQUEUE is not installed.
    
    When I tried out my latest version of GFA Basic, version 3.07, it
    crashed EVERY time I tried to start it up, due, I think, to a bus error.
    When I deinstalled NEOQUEUE, GFA Basic never crashed. Other software
    also seemed to suffer sporadic hangups/crashes, but they all went away
    when I removed NEOQUEUE, so I now avoid it like the plague. NEODESK,
    itself, however, is great!

    
    I posted these two atricles the other night while I was look-
    ing in comp.sys.atari.st.tech for 'bus errors'.  My 1040ST
    just started doing this this past "weekend" sometime.
    
Article: 4438
Newsgroups: comp.sys.atari.st.tech
Path: ryn.mro4.dec.com!ndroid.enet.dec.com!hearn
From: [email protected] (Rich Hearn)
Subject: 1040ST help - bus errors with direct kermit xfr's
Message-ID: <[email protected]>
Sender: [email protected] (USENET News System)
Organization: Digital Equipment Corporation
Date:  2 DEC 91 21:20:44    
 
 
	I've got a TOS 1.0 1Meg 1040ST with 65M h/d that has been
working fine - 'til I tried to do a direct (hardwire - no modem)
xfr between it and another system.  Normally, this works at 9600
with no problem.  Today, I started seeing 'bus error'.  Tried
2400 - same thing.
 
Over the weekend, I did run TOS14FIX (the rainbow TOS fix) to see
what it'd do - I wanted to 'play' with the 19200 baud and thought
I might need it.  I can't see that effecting it, 'specially with
rebooting the system, but thought I'd mention that too.
 
					Any ideas?
 
						Rich
Article: 4444
Newsgroups: comp.sys.atari.st.tech
Path: ryn.mro4.dec.com!ndroid.enet.dec.com!hearn
From: [email protected] (Rich Hearn)
Subject: Re: 1040ST help - bus errors with direct kermit xfr's
Message-ID: <[email protected]>
Sender: [email protected] (USENET News System)
Organization: Digital Equipment Corporation
Date:  3 DEC 91 08:04:32    
 
 
In article <[email protected]>, [email protected] (Rich Hearn) writes...
> 
>	I've got a TOS 1.0 1Meg 1040ST with 65M h/d that has been...
>
	forgot to add - works fine with a modem attached... just a
	problem running "direct".
 
						Rich
    
    That last part about working fine with the modem attached - I found
    out last night it's not true.  If I disconnect my Hard disk (Seagate
    277N w/ BMS200 controller) everything works fine to floppys. 
    
    I can boot the HD, open files, create them, run mint, Gulam, ue new
    files - just can't get CKermit to work anynmore (it has been for
    the past 6 mos. easy).  Any ideas on how to isolate this further?
    
    Is this a bus "driver" problem?  Need moor info?
    
    					Thoughts appreciated,
    
    						Rich
    

re:          <<< Note 666.6 by DETOO::HEARN "Time will tell..." >>>
                    -< Looks like a good place for this... >-
 
>	I've got a TOS 1.0 1Meg 1040ST with 65M h/d that has been
>working fine - 'til I tried to do a direct (hardwire - no modem)
>xfr between it and another system.  Normally, this works at 9600
>with no problem.  Today, I started seeing 'bus error'.  Tried
>2400 - same thing.

Hey, same thing happened to me last weekend (MEGA 1, some kind of
global infection? :-), when I tried to use ckermit to fetch a file
from another system. Using the file transfer capabilities of UNITERM
_did_ work. 

I had no time to look further into it, but if I recall correctly, the
last time ckermit used to work was before I attached a second hard
disk to my OMTI controller. Hmmmm, I'll try to disconnect the hard
disks and check it out. When time allows. 

rdgs,
	-Peter

    
    peter,
    	    one thing I did find out - with Ckermit.tos it appears to
    	bomb with the file create to the hard disk.  It doesn't happen
    	if I use Jeff Lomicka's WHACK.PRG - that ** Successfully ** 
    	works (jeff, how'd you do that? :^)
    							Rich