| Author |
Message |
Folkert Rienstra
Guest
|
 Posted:
Fri Oct 29, 2004 5:51 pm Post subject:
Re: Windows will not detect DAT drive |
|
|
"Eric Gisin" <ericgisin@graffiti.net> wrote in message news:clpj6h0qr6@enews2.newsguy.com
| Quote: | "Folkert Rienstra" <see_reply-to@myweb.nl> wrote in message news:2uaq2sF27g1f7U3@uni-berlin.de...
"Eric Gisin" <ericgisin@graffiti.net> wrote in message news:clomtq08e4@enews1.newsguy.com
Download SCSI mechanic: www.scsimechanic.com
What does this Gigabyte-sized download do that Bart's SCSITool (~100kB) can't do?
It uses the Win 2K scsi port driver. It does not require building a boot disk.
|
Ok, but if it relies on that driver and Win2k does rely on that driver and
doesn't see it, then how will it help?
Btw, have you tried Robin Miller's SCU?
http://www.bit-net.com/~rmiller/scu.html
http://www.bit-net.com/~rmiller/kits/windows/scu-nt.tar.gz
it's a mere 450 kB |
|
| Back to top |
|
 |
Mike Tomlinson
Guest
|
| Posted:
Fri Oct 29, 2004 7:30 pm Post subject:
Re: Windows will not detect DAT drive |
|
|
In article <2uf0vpF28f20kU1@uni-berlin.de>, Folkert Rienstra <see_reply-
to@myweb.nl> writes
Ooh, that's handy. Thanks for posting that. I use scu on Tru64 UNIX
and it's very useful. I had no idea it was available for other
platforms.
--
Rarely do people communicate; they just take turns talking.
(source unknown) |
|
| Back to top |
|
|
Eric Gisin
Guest
|
| Posted:
Fri Oct 29, 2004 8:25 pm Post subject:
Re: Windows will not detect DAT drive |
|
|
"Folkert Rienstra" <see_reply-to@myweb.nl> wrote in message
news:2uf0vpF28f20kU1@uni-berlin.de...
| Quote: |
It uses the Win 2K scsi port driver. It does not require building a boot
disk.
Ok, but if it relies on that driver and Win2k does rely on that driver and
doesn't see it, then how will it help?
Win 2K enumerates a startup, and any SCSI utility re-enumerates when it |
starts. May differ, may not.
It only worked under NT4 for me, and predates Win 2K. |
|
| Back to top |
|
|
Folkert Rienstra
Guest
|
| Posted:
Sun Oct 31, 2004 4:50 pm Post subject:
Re: Windows will not detect DAT drive |
|
|
"Rob Turk" <wipe_me_r.turk@chello.nl> wrote in message news:418219e8$0$568$e4fe514c@news.xs4all.nl
| Quote: | "Folkert Rienstra" <see_reply-to@myweb.nl> wrote in message news:2udnguF297mh8U2@uni-berlin.de...
"Rob Turk" wipe_me_r.turk@chello.nl> wrote in message news:4180f73a$0$48933$e4fe514c@news.xs4all.nl
"Folkert Rienstra" see_reply-to@myweb.nl> wrote in message news:2uaq2rF27g1f7U2@uni-berlin.de...
Never use Windows, do you? It's full of SCSI class drivers.
Yes, but why does NT++ need specific 'device' drivers when 9x does not?
Windows NT and family has a defined tape API,
Sounds like ASPI for Tapes. So no specific need for a driver.
No, you're missing the point that NT has a layered structure.
|
Well, I may have missed it because that point wasn't made.
| Quote: | The lowest layer is the SCSI (mini)port driver which directly interacts with the
SCSI HBA hardware. It fiddles with registers and bits on the SCSI card chipset.
It exposes a standard API through which the next layer can send SCSI commands.
This is comparable to ASPI.
|
Yet different.
| Quote: |
The next layer is the tape driver (Disk and CD/DVD drivers are on this same
level). It uses the SCSI (mini)port API to send SCSI commands. On the other
side of this driver it exposes the Tape API which consists of higher level
commands.
|
So the API is indeed included in the driver?
Or is 'driver' just another name for an installable API?
| Quote: | As an example there's a standard API function to partition tapes.
If a backup application wants to use partitions, it simply calls the tape
driver and specifies the number and size of the desired partitions. The
tape driver then sends one or more SCSI commands specific to the tape
drive for which the driver is written.
Those specifics are entirely transparant to the backup application.
|
Except that an application that is unaware of the specifics won't use
those specifics. An application can only do what the API supports
and the API supports only that what was layed down in documentation.
| Quote: | In fact, the tape drive could have any weird interface (floppy, ide,
fibre, QIC-02, you name it),
|
And sends SCSI commands?
| Quote: | and as long as there's a tape driver for it, the backup application can use it.
which allows tape drive manufacturers to implement a driver.
That's mad. Unless the API has to be included in the driver,
i.e. the driver *is* the API. But then, that's mad too.
Once the driver is in place then any backup software that
is written for the API can make use of that tape device.
Windows 9x does not have such API.
ASPI/SPTI/whatever does not support Tapes?
No, ASPI/SPTI support sending SCSI commands to SCSI devices.
|
So does the driver, there must be more to it. ASPI/SPTI are APIs too.
| Quote: | It's the application on top that needs to implement the specifics for each
and every tape drive it claims to support.
|
So how is that different for diskdrives?
| Quote: | That's why you won't find additional drivers for the
backup application that came bundled with Win9x.
It's a monolithic piece of software that can't be persuaded
to talk to anything but a fixed list of supported drives.
Backup software has to directly address the tape hardware and
therefor support all specifics of each 'supported' device on it's own.
Which it can't do without using the W9x driver.
Commercial backup software vendors defined their own layers, wrote their own
tape specifc drivers on Win9x, which then exposed their own proprietary tape
API to their own backup application. A Win9x driver for ArcServe is of no
use to BackupExec.
|
Right, so not really much difference then between 9x and NT++ except that there
is no one specific API.
|
|
| Back to top |
|
|
Folkert Rienstra
Guest
|
| Posted:
Sun Oct 31, 2004 4:50 pm Post subject:
Re: Windows will not detect DAT drive |
|
|
"Eric Gisin" <ericgisin@graffiti.net> wrote in message news:cltrs701cpd@enews4.newsguy.com
| Quote: | "Folkert Rienstra" <see_reply-to@myweb.nl> wrote in message news:2uf0vpF28f20kU1@uni-berlin.de...
It uses the Win 2K scsi port driver. It does not require building a boot disk.
Ok, but if it relies on that driver and Win2k does rely on that driver and
doesn't see it, then how will it help?
Win 2K enumerates at startup, and any SCSI utility re-enumerates when it
starts.
|
I think it does not, but that is with ASPI on W9x, it may differ for W2k.
E.G. Bart's SCSITool under Win9x doesn't do a real scan, it just shows what
ASPI tells it. So does SCSIMechanic on startup. But anyway, SCSIMechanic
allows a rescan and that appears to actually do a real scan (slower) so that may
be academic, unless it only re-scans the devices that Windows says are there.
| Quote: | May differ, may not.
|
A test may be to startup Windows with a device unpowered,
run SCSIMechanic, power the device up and rescan the bus.
|
|
| Back to top |
|
|
NickC
Guest
|
| Posted:
Thu Nov 04, 2004 1:57 pm Post subject:
Re: Windows will not detect DAT drive |
|
|
Now working on a new Adaptec 29160 controller, so it looks like a
design/compatibility fault on the 2940UW was the source of the problem. I
find this a bit worrying because I have always considered Adaptec
controllers to be about the best.
Question is if Adaptec no longer make reliable SCSI controllers who does?
Any suggestion of an alternative SCSI controller manufacturer?
Nick
"NickC" <me@somewhere.com> wrote in message
news:clldbd$8ps$1@hercules.btinternet.com...
| Quote: | Seagate/Certance STD 2401LW DAT drive connected through an Adaptec 2940UW.
The SCSI controller can see the drive ok but Windows (2003) simply refuses
to recognise that there is a tape drive attached. No tape drives visible,
nothing in other devices.
Any ideas?
Cheers,
Nick
|
|
|
| Back to top |
|
|
Folkert Rienstra
Guest
|
| Posted:
Fri Nov 05, 2004 4:14 am Post subject:
Re: Windows will not detect DAT drive |
|
|
"NickC" <me@somewhere.com> wrote in message news:cmdcgt$bq$1@titan.btinternet.com
| Quote: | Now working on a new Adaptec 29160 controller, so it looks like a
design/compatibility fault on the 2940UW was the source of the problem. I
find this a bit worrying because I have always considered Adaptec
controllers to be about the best.
Question is if Adaptec no longer make reliable SCSI controllers who does?
|
So if it works on a newer controller but not on an older
controller, that makes Adaptec currently unreliable.
Nice logic.
| Quote: | Any suggestion of an alternative SCSI controller manufacturer?
Nick
"NickC" <me@somewhere.com> wrote in message news:clldbd$8ps$1@hercules.btinternet.com...
Seagate/Certance STD 2401LW DAT drive connected through an Adaptec 2940UW.
The SCSI controller can see the drive ok but Windows (2003) simply refuses
to recognise that there is a tape drive attached. No tape drives visible,
nothing in other devices.
Any ideas?
Cheers,
Nick |
|
|
| Back to top |
|
|
Rob Turk
Guest
|
| Posted:
Fri Nov 05, 2004 12:19 pm Post subject:
Re: Windows will not detect DAT drive |
|
|
"NickC" <me@somewhere.com> wrote in message
news:cmdcgt$bq$1@titan.btinternet.com...
| Quote: | Now working on a new Adaptec 29160 controller, so it looks like a
design/compatibility fault on the 2940UW was the source of the problem. I
find this a bit worrying because I have always considered Adaptec
controllers to be about the best.
Question is if Adaptec no longer make reliable SCSI controllers who does?
Any suggestion of an alternative SCSI controller manufacturer?
Nick
|
I have not been able to find a manual for the SDT 2401 on www.certance.com,
but you may want to check if the drive happens to be LVD SCSI and doesn't
automatically switch back to Single-Ended on an SE bus? Maybe it needs a
jumper for SE mode? The 2940 is a single-ended controller, the 29160 is LVD.
As Folkert mentioned, attributing this issue to Adaptec does not make sense.
This may be a situation where you simply didn't properly configure the
device.
Rob |
|
| Back to top |
|
|
NickC
Guest
|
| Posted:
Fri Nov 05, 2004 3:22 pm Post subject:
Re: Windows will not detect DAT drive |
|
|
"Rob Turk" <_wipe_me_r.turk@chello.nl> wrote in message
news:418b2964$0$88495$e4fe514c@dreader15.news.xs4all.nl...
| Quote: | "NickC" <me@somewhere.com> wrote in message
news:cmdcgt$bq$1@titan.btinternet.com...
Now working on a new Adaptec 29160 controller, so it looks like a
design/compatibility fault on the 2940UW was the source of the problem.
I
find this a bit worrying because I have always considered Adaptec
controllers to be about the best.
Question is if Adaptec no longer make reliable SCSI controllers who
does?
Any suggestion of an alternative SCSI controller manufacturer?
Nick
I have not been able to find a manual for the SDT 2401 on
www.certance.com,
but you may want to check if the drive happens to be LVD SCSI and doesn't
automatically switch back to Single-Ended on an SE bus? Maybe it needs a
jumper for SE mode? The 2940 is a single-ended controller, the 29160 is
LVD.
As Folkert mentioned, attributing this issue to Adaptec does not make
sense.
This may be a situation where you simply didn't properly configure the
device.
Rob
|
Currently running in SE mode not LVD, the 29160 has plugs for both. The
reason for concluding that this is an Adaptec problem is that I have found a
number of people that have had similar problems with the 2940UW (using
different tape devices) but no others that have had problems with the
Seagate STD2401, so I think it is reasonable to assume this is either an
Adaptec controller design fault or an driver fault, again down to adaptec.
At least thats how I see it anyway.
Nick |
|
| Back to top |
|
|
Mike Tomlinson
Guest
|
| Posted:
Sat Nov 20, 2004 3:50 am Post subject:
Re: Windows will not detect DAT drive |
|
|
In article <cmg5rc$2vo$1@sparta.btinternet.com>, NickC
<me@somewhere.com> writes
| Quote: | Currently running in SE mode not LVD, the 29160 has plugs for both. The
reason for concluding that this is an Adaptec problem is that I have found a
number of people that have had similar problems with the 2940UW
|
The 2940UW is just about the most compatible SCSI card there is.
| Quote: | I think it is reasonable to assume this is either an
Adaptec controller design fault or an driver fault, again down to adaptec.
|
Error in logic. Brain rebooting.
--
..sigmonster on vacation |
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in