#C-ltd software
22 messages in this thread
Ben,
I am so fed up with my 2090 I am going to buy a C-ltd just so I can format
my adaptec 4000a and 4070 based drives. I have 2 questions though.
1. Will the formatter automatically find and map out bad sectors
on my old drives with extra media defects over the list?
2. Will the software support 2 drives connected to a single
Adaptec? IE LUN 0 & 1? I hope I hope I hope I hope
Dafve Weinbach
^delete that pesky critter!
Dave,
Sorry to bother you, but why are you fed up with the 2090? (I just bought
one.) I have a few reservations about the purchase I've made. I know I'm
going to have a lot of problems with VideoScape and stuff, but if you have
the time, I wouldn't mind knowing in advance some of the other problems I may
have to deal with. Where but on CIS could I get someone to list the bad
points about a product?
Don Weed
Don,
The only problem I have heard of on the 2090 is the lack of a low level
formatter for the SCSI drives. Mine works flawlessly with ST506 drives, and
others have reported similar experience with SCSI drives, provided they have
been low-level formatted on another controller/machine.
-larry
I agree. Getting rid of a 2090 to pick up a C Ltd controller is kinda like
getting rid of a 911 for a 64 VW because you got a speeding ticket.
Larry,
I'm going to have to go look at my saved file, but somewhere in there
I've got the information on why and/or how to low level format a SCSI with
the 2090. Actualy, in the case in point…since he's using an adaptek 4000
to the 2090's SCSI port…unless he already has 2 ST506 drives attached, he'd
be better off not using the 4000 at all. It's just another step the data has
to go thru.
Don
Don,
True… and I would indeed appreciate hearing more about the problems with
low-level formatting on SCSI.
-larry
Okay,
I DO have a reason for using the adaptec. I have a drive with 9 data heads
(some use 16) but CA elected to only support 8 heads. so it was throw away
11% of my drive or use the adaptec. The problems with 2090 and scsi are two:
1. The documentation is incomplete, inacurate, and internally inconsistant.
2. (not a problem, more of a critical ommission) The 2090 software does not
support the industry standard Adaptec boards, and IMHO really works only with
true scsi drives. I have no idea if, how or when it issues a LL format cmd.
Once I formatted my drives on thye PEE CEE (using my Iomega Scsi, which the
2090 software also does not support.) it works but I cant map out defects and
because of a Forbid() call if it hits a bad sector I have to REBOOT!!! In
summary, I feel other than the 8/16 heads fiasco, the 2090 could easily be
made a respectible product by putting it in the hands of ANYONE! other Than
Jacks Rejects in west chester. Software is the problem. Support is the
Problem. I guess thats what the C key replacing the A key really means.
Dave Weinbach PS: Validation Key already set errors require reformat! fun.
PPS: I am a hardware hacker. The above is probably not a factor if you just
need a way to hook up an st-251. the 2090 is probably not bad for that.
Dave,
The Validation 'key already set' errors can be cleared. Once I
accidentaly re-named a file to a directory's name via a shell program. It
'took'…I had a file and directory named the same thing. I went to access
the directory to delete a file and DOS accessed the file instead…with an
almost instantaneous GURU. The re-boot brought up the infamous 'Key already
set' error on the HD, but with a sector editor…it was a snap to follow the
hash chain and see which of the 2 keys was correct, and NULL the other key.
I lost a few sectors that the disk map thought were in use, but I was able to
then validate the drive, and backup all the files and then I re-formatted
just to clear those lost sectors. DskSalve would have been able to recover
even that file (it was a no big deal file so I didn't care).
While the 'key already set' error may be fatal to a file…it isn't
always fatal to the drive.
Don
Con, (oops. that was a typo, not a commentary) Don,
I understand that it is possible but have been unable to make it work. I
crashed the system twice with the same FILE–>DIR trick. Nice. I tried DiskX
to find the problems but got nowhere, and the Amigados dev. manual was no h.
What software/documentation/method did you use?
Dave Weinbach
Dave,
I used Sectorama (sec.arc in Dl 9) as the editor. I used the
AmigaDOS reference manual (the separate developer's version, but the same as
the Bantam published version) as my 'guide'.
Since I knew which directory I was messing with…I used the sector
editor to jump to that directory header block. I then hashed both filenames,
one a directory and one a file that I was trying to rename. The hash offsets
were different, but the longword value at the hash offsets was the same. I
jumped to that sector, found it was a directory header. Jumped back to the
parent and 0'ed the longword at the hash offset for the filename…thus
leaving the longword at the hash offset for the directory alone.
The disk then validated.
I could have looked for the header block for the file, but it wasn't
worth it. I had other copies. If I had looked for it, and found it…I
would have merely taken it's header's sector number and inserted it in the
longword I had previously 0'ed.
Don
Larry,
Thanks for responding. I pursue this line of questioning because it looks
as though I need to box up my 2090 and 20-meg MiniScribe and send them back
to my dealer (150 mi. north) as I have not gotten any of it to work more than
intermittently. My drive just booted (I just got home), but it won't be here
for long. In a few minutes (if the last three weeks are anything to go by) I
will not be able to access anything, or perhaps even finish this message, and
at that point the drive will not boot the rest of the evening. I can't tell
you how many times I've tried Ctl-Amiga-Amiga this month. It boots maybe once
a day, then refuses to be recognized until the next day. Is this making
sense? I've tried re-prepping, re-formatting, custom formatting, etc. If
anyone knows something I haven't tried (save contacting UPS for re-shipment),
PLEASE let me know!
Don W.
P.S. Finished the message. Yay!
Don,
Sounds like a case of hardware failure, either drive, cables, 2090, or the
slot itself. Good luck with it.
-larry
Larry,
Thanks. But before I open 'er up and pull the stuff out of there (I've put
it off this long), there remains the fact that it boots up faithfully and
flawlessly for me as long as it's my first try of the day. I think I'm
grasping at straws here, but just in case that piece of information makes any
difference to anyone out there reading this, I thought I'd throw it in.
Anyway, my dealers are pretty good guys (I think) so I'm perturbed, not
overly concerned.
Don W.
Don,
A heat related problem would act exactly as you say. When cold, it
works flawlessly, but as it heats up (and in a computer…that can be quick),
it becomes intermittent and then fails.
Until it cools down again…it will stay failed. Generaly something
like that applies to either the circuit board itself (cracked trace) and in
that case…will slowly get worse to the point it won't work even if cold or
to a cold solder joint, poor chip socket or in very rare cases…a chip
itself.
Unfortunately, the only way to find something like that is drugery
and a can of cold spray (compressed air, freon…etc.).
Don
Don,
I agree with you completely. The drive and controller are back in
the hands of my computer store. I hope they have an easy time with it. It was
sure great the few days it worked!
Don W.
Don:
I have not read the other reply to your message yet but as to the
2090…… I had to do a low level format of my Rodime RO-652 on my Amiga
1000's C-LTD controller inorder to use the drive on my A2K. Attempted to
format the drive for about 8 hours after replacing the trackdisk device with
the one here on CIS. The drive finally formated but had lots of errors.
Once it had been low level formatted on the C-LTD controller, it formatted
immediately on the 2090. It has worked just fine since except then it ALWAYS
showes errors (recoverable) when using Draw Plus and only with Draw Plus.
Even PCLO+, another specialized CAD program, does not seem to have any
problems with the drive at all. 73, bill
Bill,
Did you get the new hddisk file here…it should take care of the
overscan caused read/write errors.
Don
Don:
That file will NOT help Draw+ a bit. But yes, I did get it here after
Andy told me about the file. I am not all that ready to blame Draw+ since I
really do have my doubts about that Rodime that is on the system.
73, bill
Bill,
I believe my dealers plan to do a low-level format on the drive. If only
they weren't 150 miles away. The Amiga has yet to make much of an impact on
West Virginia. (Come to think of it, indoor plumbing has yet to make much of
an impact on West Virginia.)
Don W.
Don:
Sorry to hear about that! Fortunately (for me) San Diego has a very
active Amiga community. There must be around a thousand or more (probably
more since the San Diego Amiga Users Group numbers over 350). Lately (the
last few days — just got back from 2 months in Pa.), my Rodime RO-652 has
been giving me access errors. When I left Ca., only Draw+ would have the
errors. Now it seems that everything except WP is having trouble.
I need to check with Cheath to see if he every figured out how to use
the same drive for both the 2090 and the C-LTD controller without
reformatting. 73, bill
Bill,
I envy you San Diego! But at least I have Compuserve. Thanks for the
support.
Don W.
Don:
Don't envy me yet as I am still trying to catch up on two monthes of
backlog. Of course San Diego co-operates nicely since it was just beautiful
the weekend that I got back (resolved to do nothing serious that weekend) and
has been rainy and cloudy all week and weekend (working continously)
<smiiiile> 73, bill