#HARDDISK/SERIAL CONFLICT
4 messages in this thread
HERE IS A MESSAGE ENTERED ON THE CITADEL BBS NET (AND ECHOED TO MY SYSTEM)
BY SOMEONE WITH A HARDDISK PROBLEM, WHICH I BELIEVE WAS DISCUSSED SOME TIME
AGO HERE ON CI$.
—————————————————————-
I own a Cltd hard drive with their SCSI controller. My problem is
this: while running any program with serial port access, ie: Amiga Citadel,
JrComm, Ncomm, etc. Everytime the drive accesses, it cause a transmission
error on the serial port, Xmodem, Ymodem, makes no difference. I have set
my serial buffer to 16k, and tried slower speeds, still no change. This
makes my system rather unreliable to my users and annoys the crap out of
me. You mentioned you saw something on Compuserve that mentioned how to
correct this problem, I would be very obliged if you could take a look and
grab the solution for me if it wouldn't cost you too much, otherwise I will
see if I can register and get on Compuserve to find it. BTW my system is a
A1000 with 1.5 megs if that makes any difference on the solution. (if
any..) Thanks alot!
Chris,
C.Ltd did a "rotten" thing to get some speed out of their hardware,
they turned interupts off. Luckily, it's user settable. I forget the
exact parameter…but something like DisableIRQ. He needs to check his
manual to see how to change that so the driver no longer disables
interupts.
Don
Chris,
The message didn't state whether it was a Kronos controller or not, but
I'll assume so. (I never owned one of the pre-Kronos CLtd controllers, so I
don't know the differences).
The person needs to edit his/her "DEVSETUP" file (in the DEVS:
subdirectory. Where the drives are initialized "Initialize Units" there is
a FLAG called DisableIRQ. That should be changed to NoDisableIRQ. That
*will* solve the problem.
If that person's controller is setup for AUTOBOOTING, then they must
BOOT from a FLOPPY (KRONOS BOOT) that has that edited DEVSETUP. Now here is
the important part – they MUST boot with the LEFT MOUSE BUTTON DEPRESSED –
otherwise the EEPROM code is activated, and the setting from disk won't
override it. Now it is O.K. to run the "SetAutoBoot" program.
They (CLtd) should NEVER have used that as a default. But they are out
of business now, so who you going to gripe to?
Lloyd
Thanks, I'll post it for him.