[Coco] Hard drive trouble
George Ramsower
georgeramsower at gmail.com
Sun Apr 6 01:17:34 EDT 2008
Bob,
I'm going to do some more extensive testing to try and get some logical
data on the results that may lead to an informed decision as to what the
problem may be.
As of now, I've just been trying things without much logic involved. This
has to stop as it's resulting in frustration.
So I'm going to re-arrange the physical layout of this computer so I can
more easily try different things, without having to move the monitor, the
hard disks, and all that stuff.
This computer is a re-pack in a VERY difficult cabinet. I don't remember
what it was, Dell, Compac, or some other danged fool configuration.
So let's take a break on this until I can get some real data to work with.
Everything I've done so far hasn't made any sense.
I need to find the original floppy that the SCSISYS is stored on, or where
it is on the hard drive. I'm thinking it may have come with it's own
descriptors which I may have mixed up with other descriptors. I don't know.
Worse case, I can finish backing up the existing hard disk to this PC and
go back to KenTon drivers and re-format, start over and move everything back
to the coco.
This is my MAIN coco and everything coco related is centered around this
machine. My CNC coco would be difficult to work without this machine. My
internet ventures would not work without this machine. The joy of running
this machine from this PC wouldn't be possible without this coco.
So what this means is...... I won't get discouraged and throw it out in the
driveway and drive over it with my truck.
It's gonna work correctly!
Meanwhile, go ahead and let me have this....
>>>I notice you're using SCSISYS. That driver should have a program with it
>>>to create the descriptors for you. (DescGen???) I have a disk image of
>>>the SCSISYS disk here somewhere, if you need it.
>>> For this to work, the driver *MUST* be called SCSISYS
PLEASE, don't send a DSK file. It takes me hours to glean the files out of
those things.
Just Zip em up(not preferred) or send them as individual attachments. All
coco stuff is so small, it is not much to attach a file to an email.
I can save an attachment to the drive on this PC and directly transfer it to
my coco via Hyperterminal.
I don't use a com program on the coco, I do this....
Shell i=/t2&
Then Hyperterminal becomes just an extension of OS-9
I have utilities to upload and download files, control my coco from
hyperterminal as if I were at the coco's keyboard(except for graphics).
Check this out....
It's 11:05 Pm
OS9[t3]:dir /h0
Directory of /h0 23:06:09
BBS CMDS DEFS HTML
LANG LIB LOG SYS
TODAY TOYS sources startup
last_boot makecmds TRYING BACKUPS
LOTTO CNC h0 h1
OS9[t3]:
It's still 11:05 Pm
I LOVE IT!
Okay, the clock on the coco is off a little.
I'm having fun with this(as you can tell)
This problem with my hard drive isn't really a problem, it's an adventure
and a challenge.... an opportunity to learn something.
George
----- Original Message -----
From: "Bob Devries" <devries.bob at gmail.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Saturday, April 05, 2008 9:11 PM
Subject: Re: [Coco] Hard drive trouble
>I your second drive doesn't work, even though it appears to be selected
>(i.e. the select LED goes on), I'd say there's a hardware problem.
>
> I'm going to assume the LED isn't always on, but just when you try to
> access the drive.
>
> Do you have the termination resistors in the second drive when you're
> using it by itself?
>
> If the second drive (H1) is the last drive when you're using the two
> together, then H0 should have no termination resistors.
>
> Are the termination resistors installed the correct way 'round?
>
> Have you changed the SCSI address on the drive when you try to use the
> drives separately, and do you have them set at two different addresses
> when you use them together?
>
> My Quantum drives have three other jumpers, one of which is EP (Enable
> Parity). None of these are jumpered.
>
> I have my H0 drive jumpered at SCSI address 0 and the H1 drive at SCSI
> address 1. That is, No jumpers on A0, A1, A2 on drive H0, and a jumper on
> A0 on drive H1.
>
> --
> Regards, Bob Devries, Dalby, Queensland, Australia
>
> Isaiah 50:4 The sovereign Lord has given me
> the capacity to be his spokesman,
> so that I know how to help the weary.
>
> website: http://www.home.gil.com.au/~bdevasl
> my blog: http://bdevries.invigorated.org/
>
> ----- Original Message -----
> From: "George Ramsower" <georgeramsower at gmail.com>
> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
> Sent: Sunday, April 06, 2008 1:58 PM
> Subject: Re: [Coco] Hard drive trouble
>
>
>> As I was exploring around my hard drive and the floppies of this stuff, I
>> just discovered this fact about the same time this 'puter went DingDong
>> on your message.
>> .
>> I remember now that I'm using 512 byte sectors and the driver to do
>> so(SCSISYS). I believe that's what I did, replaced the KenTon driver with
>> the SCSISYS driver and set it all up for 512 byte sectors. It's
>> "supposed" to give more storage space, but I never needed it. I got
>> greedy.
>> Right now, I'm trying to find the source of SCSISYS. So far, I haven't.
>>
>> Anyway, can this make my problem appear several years later?
>>
>> I can't go back to 128 byte sectors until I can fix this problem I'm now
>> having.
>>
>> Like I said earlier, it used to work fine with two drives using
>> everything I'm now using unless I did something that I don't remember.
>> I've been using this setup for many years.
>>
>>
>>
>> ----- Original Message -----
>> From: "Bob Devries"
>>
>>
>>>I notice you're using SCSISYS. That driver should have a program with it
>>>to create the descriptors for you. (DescGen???) I have a disk image of
>>>the SCSISYS disk here somewhere, if you need it.
>>> For this to work, the driver *MUST* be called SCSISYS
>>
>> It came with... I think.... ScsiSys Scsidesc Scsifmt
>>
>> I recall using those a LONG time ago.. Scsifmt is what I used to reformat
>> my second drive when I discovered it was broke.
>> However, I'm not so sure it's really broke. I think something in my
>> system messed it up as there is that conflict with addressing the /h0
>> drive and the /h1 drive at the same time.
>> What's wierd is that my primary drive is working fine. No lost files or
>> problems at all. It's just that when I try to access /h1, the /h0 drive
>> appears in it's place, even if the second drive is on the cable.
>> If I put the second drive online all by itself, it too responds to /h0
>> and /h1, even though it doesn't work, the drive light still lights up.
>>
>>
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
More information about the Coco
mailing list