I have a 3 scsi cards on this comp, 2 are 2940/UW and all use the
AHA aic78xx.mpd driver.
Problem is after some 3 reboots or so, the computer BSoD blue screen
crashes with a [vxd vtdi error code] so I reinstalled the TCP/IP manager
which the vtdi.vxd file refers to on win95/bmide (busmaster) w/98+ emulation
system, but nothing improved.
The bootlog txt says it crashes when attempting to reload the
aic78xx.mpd driver for the other card, and always crashes at that point.
The AHA Adapter 0 (aic78xx) has 3 internal peripheral disks on it
with the system set to Designated Drive Letter/Removable/no int13...
The only way I can reboot into windows after a crash, is to
reinstall a former registry which is the same as the one being used, and it
logs in...but that is a real drag ater a few thousand times.
On Thu, 1 Nov 2007 23:04:15 +0100, "Folkert Rienstra"
<see_reply-to@myweb.nl> wrote:
|>Robert LaCasse wrote in news:n2lii3tri793mm53ut84t3flru6a9t7qpb@4ax.com
|>> (aic78xx) Boot Problem
|>>
|>> I have a 3 scsi cards on this comp,
|>
|>> 2 are 2940/UW and all use the AHA aic78xx.mpd driver.
|>
|>Try again.
|>
What do you mean try again....are you being facetious or are
questioning the 2 2940U/W cards using the .......aic78xx.mpd or the scsi2
using the sparrow.mpd?
Robert LaCasse <wizard@french-connection.cid> wrote:
> On Thu, 1 Nov 2007 23:04:15 +0100, "Folkert Rienstra"
> <see_reply-to@myweb.nl> wrote:
>
> |>Robert LaCasse wrote in news:n2lii3tri793mm53ut84t3flru6a9t7qpb@4ax.com
> |>> (aic78xx) Boot Problem
> |>>
> |>> I have a 3 scsi cards on this comp,
> |>
> |>> 2 are 2940/UW and all use the AHA aic78xx.mpd driver.
> |>
> |>Try again.
> |>
>
> What do you mean try again....are you being facetious or are
> questioning the 2 2940U/W cards using the .......aic78xx.mpd or the scsi2
> using the sparrow.mpd?
he's talking to himself, or voices in his head.
Notice his mode of operation. Somebody says something that he thinks is
wrong. He won't and can't correct what they said, so he throws out a
simple few word reply. He does this because he's pretty wrong most of the
time anyways, and doesn't understand anything technical enough to actually
provide a meaningful reply in the first place.
Check any archives. He never actually provides any answers- he simply
doesn't have any. The best part is when you correct him, he can't handle
it and the thread sort of stops right there.
In short, he's a total loser, that lacks any technical or social skills.
Why are you using Win 95 and why do expect anyone to support it?
Win 9X barely supports SCSI, nothing advanced like command queuing.
Win NT4 is the minimum to benefit from SCSI.
"Robert LaCasse" <maj-ic12@majestic.cid> wrote in message
news:n2lii3tri793mm53ut84t3flru6a9t7qpb@4ax.com...
> (aic78xx) Boot Problem
>
> I have a 3 scsi cards on this comp, 2 are 2940/UW and all use the
> AHA aic78xx.mpd driver.
>
On Sun, 4 Nov 2007 16:37:43 +0000 (UTC), Cydrome Leader
<presence@MUNGEpanix.com> wrote:
|>Robert LaCasse <wizard@french-connection.cid> wrote:
|>> On Thu, 1 Nov 2007 23:04:15 +0100, "Folkert Rienstra"
|>> <see_reply-to@myweb.nl> wrote:
|>>
|>> |>Robert LaCasse wrote in news:n2lii3tri793mm53ut84t3flru6a9t7qpb@4ax.com
|>> |>> (aic78xx) Boot Problem
|>> |>>
|>> |>> I have a 3 scsi cards on this comp,
|>> |>
|>> |>> 2 are 2940/UW and all use the AHA aic78xx.mpd driver.
|>> |>
|>> |>Try again.
|>> |>
|>>
|>> What do you mean try again....are you being facetious or are
|>> questioning the 2 2940U/W cards using the .......aic78xx.mpd or the scsi2
|>> using the sparrow.mpd?
|>
|>he's talking to himself, or voices in his head.
|>
|>Notice his mode of operation. Somebody says something that he thinks is
|>wrong. He won't and can't correct what they said, so he throws out a
|>simple few word reply. He does this because he's pretty wrong most of the
|>time anyways, and doesn't understand anything technical enough to actually
|>provide a meaningful reply in the first place.
|>
|>Check any archives. He never actually provides any answers- he simply
|>doesn't have any. The best part is when you correct him, he can't handle
|>it and the thread sort of stops right there.
|>
|>In short, he's a total loser, that lacks any technical or social skills.
|>
He's probably a reclusive computer geek like me...hahahahah she was
funny with that line...
So I was wondering with my rebooting problem being impeded, with a
Win/9x platform, where it is logical that a computer will boot with no
problem with a good registry, then on the 2--->4th boot it crashes with a
Blue Screen vtdi.vxd, but it's got nothing to do with the config of the
vtdi.vxd system..not as far as function......
The fact is if there was a bad config somewhere, it wouldn't boot at
all, it would either boot or not...........when it does crash I reload any
previous registry, and the system is good for another 2-->4.boots, it's hard
to upgrade that way...and all the reconfigured calcs of the older Registry I
booted from....
What does the computer learn that makes it want to give up after
some boots, when there is nothing wrong with the 1-->4th original boot.
Is the computer like a person, goes hungry and dies....no but it
seems to be working that way.....sometimes if I change a config and give it
a problem, it will buy me a re-boot....
The 3 internal scsi hddrives are properly set on the 68 pin "lvd
type" woven cable and terminated. Keyword here is internal, all my external
apps work just fine but internal 68pin should work if the 50 pin internal
isn't connected as well....
On Sun, 4 Nov 2007 09:03:19 -0800, "Eric Gisin" <gisin@uniserve.com> wrote:
|>Why are you using Win 95 and why do expect anyone to support it?
|>Win 9X barely supports SCSI, nothing advanced like command queuing.
|>Win NT4 is the minimum to benefit from SCSI.
|>
|>"Robert LaCasse" <maj-ic12@majestic.cid> wrote in message
|>news:n2lii3tri793mm53ut84t3flru6a9t7qpb@4ax.com. ..
|>> (aic78xx) Boot Problem
|>>
|>> I have a 3 scsi cards on this comp, 2 are 2940/UW and all use the
|>> AHA aic78xx.mpd driver.
|>>
Win9x and 3,200 executables, much malware/spyware/sporge/etc. to
kill, and graphic apps/software that won't work with some NT 4....
I do like the variable control of the older platforms, not like
being mickey moused into what THEY want you to have.....not what YOU
want................you know....
I like to have control over my comp, not a bunch of hidden problems
to seek and destroy.....
I do have scsi (command queuing) my other 17 50pin tapes/drives work
well without it....but I also have a drive that says it doesn't support
"scsi linking" in the internal (aic78xx) aha 2940uw 68pin bus....
But then why does it "boot' work sometimes, and not all the time or
never....
This is an INQUIRY command for the optional unit serial number (vital
product parameter 0x80).
> Transfer Ct: 0xff
The driver have provided a buffer with 0xFF bytes for the reply.
> Actual Ct: 0x12
The host have received 0x12 = 18Bytes.
> DataBuffer: 00 80 00 0e 30 30 32 32 33 36 39 35 30 30 30 30
^^ ^^ ^^
| | |
| | +- Number of SN bytes following
| +------- Unit serial number parameter ID
+---------- LUN is "direct access" and connected
It seems that the device supports this option. 4 + 0x0E Bytes results in
18Bytes. The serial number is "002236950000PJ" in ASCII.
> 50 4a 00 00 b0 45 a5 07 00 00 00 00 00 00 00 00
^^
|
+- This is the last byte
The transfer length and the number of bytes in the response matches (and
fit into the buffer). I don't understand what kind of error Windows
assume here. This looks like a bug in the Windows driver for me:
Maybe the length calculation is buggy or the DMA engine was interrupted
and the recovery is buggy.
A bug in the device firmware (STATUS phase before the 18th byte or
another DATA IN phase after the 18th byte) is IMHO not possible here,
because the driver has received 18Bytes according to the "actual count"
above and:
> Target Status:0 (Ok)
This indicates that the device has reported status GOOD (what implicitly
means the status was transferred to the host).
> [Same error for 2 other disks]
>
> OTHER CARDS:
>
> SCSI Cmd: Adapter 1 (sparrow)
> Target: 4:0
> SCSI Cdb: 12 01 80 00 ff 00 [Inquiry]
> Transfer Ct: 0xff
> Actual Ct: 0xb
11Bytes recived here
> DataBuffer: 01 80 00 07 47 43 30 31 35 5a 56 00 00 00 00 00
^^ ^^ ^^ ^^
| | | Last byte
| | |
| | +- Number of SN bytes following
| +------- Unit serial number parameter ID
+---------- LUN is "sequential access" and connected
Same as for the disks. Looks good but Windows think something is wrong.
> [Same error for another tape]
>
> SCSI Cmd: Adapter 2 (ESDI_506)
^^^^^^^^
If this is an Adaptec too (as you have written), why does it print such
wrong things?
The command was rejected by the device. The SKSV bit is cleared,
therefore the device have not reported which byte of the CDB is the
problem (maybe the command is not implemented at all, this is allowed
for some device types). Again no reason for a crash.
For me this looks like Windows trips over the own feet. IMHO other
drivers should help, but because the aic78xx and the sparrow (for
AIC6xxx chipset) driver shows the same behaviour the potential bug maybe
in the common SCSI layer driver.
On Mon, 05 Nov 2007 12:27:31 +0100, Michael Baeuerle
<michael.baeuerle@stz-e.de> wrote:
|>Robert LaCasse wrote:
|>>
|>> [...]
|>
|>A few words what I can read out of the error messages:
|>
|>> SCSI MECHANIC BootLog of 3 AHA cards:
|>>
|>> SCSI Cmd: Adapter 0 (aic78xx)
|>> Target: 0:0
|>> SCSI Cdb: 12 01 80 00 ff 00 [Inquiry]
|>
|>This is an INQUIRY command for the optional unit serial number (vital
|>product parameter 0x80).
|>
|>> Transfer Ct: 0xff
|>
|>The driver have provided a buffer with 0xFF bytes for the reply.
|>
|>> Actual Ct: 0x12
|>
|>The host have received 0x12 = 18Bytes.
|>
|>> DataBuffer: 00 80 00 0e 30 30 32 32 33 36 39 35 30 30 30 30
|> ^^ ^^ ^^
|> | | |
|> | | +- Number of SN bytes following
|> | +------- Unit serial number parameter ID
|> +---------- LUN is "direct access" and connected
|>
|>It seems that the device supports this option. 4 + 0x0E Bytes results in
|>18Bytes. The serial number is "002236950000PJ" in ASCII.
|>
|>> 50 4a 00 00 b0 45 a5 07 00 00 00 00 00 00 00 00
|> ^^
|> |
|> +- This is the last byte
|>
|>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|>> Cmd Status: 1 (SCSI Request Completed Ok!) Error!
|>> Host Status: 12 (Data Under/Over Run)
|>
|>The transfer length and the number of bytes in the response matches (and
|>fit into the buffer). I don't understand what kind of error Windows
|>assume here. This looks like a bug in the Windows driver for me:
|>Maybe the length calculation is buggy or the DMA engine was interrupted
|>and the recovery is buggy.
This device has no DMA specific driver added to it since ALL these
SCSI Devices drives, are configured as Windows Removable/Disconnect no int13
on Card or Windows system.
SCSI card Bios is Disabled/Not Scan on All SCSI cards (3)....as they
are considered peripherals even though they are part of the system with
dedicated folder/dir links....
|>
|>A bug in the device firmware (STATUS phase before the 18th byte or
|>another DATA IN phase after the 18th byte) is IMHO not possible here,
|>because the driver has received 18Bytes according to the "actual count"
|>above and:
|>
|>> Target Status:0 (Ok)
|>
|>This indicates that the device has reported status GOOD (what implicitly
|>means the status was transferred to the host).
|>
|>> [Same error for 2 other disks]
|>>
|>> OTHER CARDS:
|>>
|>> SCSI Cmd: Adapter 1 (sparrow)
|>> Target: 4:0
|>> SCSI Cdb: 12 01 80 00 ff 00 [Inquiry]
|>> Transfer Ct: 0xff
|>> Actual Ct: 0xb
|>
|>11Bytes recived here
|>
|>> DataBuffer: 01 80 00 07 47 43 30 31 35 5a 56 00 00 00 00 00
|> ^^ ^^ ^^ ^^
|> | | | Last byte
|> | | |
|> | | +- Number of SN bytes following
|> | +------- Unit serial number parameter ID
|> +---------- LUN is "sequential access" and connected
|>
|>The serial number is here "GC015ZV" in ASCII.
|>
|>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|>> Cmd Status: 1 (SCSI Request Completed Ok!) Error!
|>> Host Status: 12 (Data Under/Over Run)
|>> Target Status:0 (Ok)
|>
|>Same as for the disks. Looks good but Windows think something is wrong.
|>
|>> [Same error for another tape]
|>>
|>> SCSI Cmd: Adapter 2 (ESDI_506)
|> ^^^^^^^^
|>If this is an Adaptec too (as you have written), why does it print such
|>wrong things?
|>
|>> Target: 0:0
|>> SCSI Cdb: 00 00 00 00 00 00 [Test Unit Ready]
|>> Transfer Ct: 0x0
|>> Actual Ct: 0x0
|>> Host Status: 0 (Ok)
|>> Target Status:0 (Ok)
|>
|>No error here and why there is no INQUIRY?
|>
|>> [...]
|>>
|>> SCSI Cmd: Adapter 2 (ESDI_506)
|>> Target: 0:0
|>> SCSI Cdb: 5a 00 05 00 00 00 00 00 48 00 [Mode Sense Long]
|>
|>This is a MODE SENSE(10) request for the current values of mode page
|>0x05 (this page is device type specific).
|>
|>> Transfer Ct: 0x48
|>> Actual Ct: 0x48
|>> DataBuffer: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|>> Cmd Status: 4 (SCSI Request Error!)
|>> Host Status: 0 (Ok)
|>> Target Status:2 (Check Condition)
|>> Sense Data: 70 00 05 00 00 00 00 0a 00 00 00 00 24 00 00 00
|>> 00 00
|>> Illegal Request Error.
|>> Additional Sense: Invalid Field in CDB
|>> Sense Qualifier: 0
|>
This *Adapter 2 (ESDI_506)* is an IDE CD-ROM seen as a SCSI
adapter.....
|>The command was rejected by the device. The SKSV bit is cleared,
|>therefore the device have not reported which byte of the CDB is the
|>problem (maybe the command is not implemented at all, this is allowed
|>for some device types). Again no reason for a crash.
|>
Right it works the same with or without the device
|>
|>For me this looks like Windows trips over the own feet. IMHO other
|>drivers should help, but because the aic78xx and the sparrow (for
|>AIC6xxx chipset) driver shows the same behaviour the potential bug maybe
|>in the common SCSI layer driver.
|>
Windows may be the problem here and trips itself after a few Boots,
then Dies to a blue screen.....
When I boot into Windows, it has a temporary blank screen with a
"Blinking Cursor" at the top left of the screen, before it goes into the GUI
Desktop....
If the "Blinking Cursor" is consistent, it will boot into the
desktop, if inconsistent, it will crash with a vxd vtdi problem...and I will
see a desktop with all running fine..
Windows is Win95 with BM-ide (Bus Master-IDE system = Win98 ATX
board....Win95 had the same problem before I installed the Bus Master System
The AT boards do not have a SCSI problem like I have on the
ATX.....
Common SCSI Layer driver???
I have switched/disabled/removed/flashed OK scsi cards/drives OK...but
seems like windows asus doesn't like the ASUS MB does not like SCSI cards???
On Wed, 31 Oct 2007 20:28:38 -0800, Robert LaCasse <maj-ic12@majestic.cid>
wrote:
Manfred Preussig <PreussigM@web.de> Emailed:
Hello,
first of all: it's not a good idea to let people only answer directly
since the thread will get incomplete this way.
Let's take a look on this:
Robert LaCasse schrieb:
> (aic78xx) Boot Problem
>
> I have a 3 scsi cards on this comp, 2 are 2940/UW and all use the
> AHA aic78xx.mpd driver.
>
> Problem is after some 3 reboots or so, the computer BSoD blue screen
> crashes with a [vxd vtdi error code] so I reinstalled the TCP/IP manager
> which the vtdi.vxd file refers to on win95/bmide (busmaster) w/98+ emulation
> system, but nothing improved.
>
> The bootlog txt says it crashes when attempting to reload the
> aic78xx.mpd driver for the other card, and always crashes at that point.
>
> The AHA Adapter 0 (aic78xx) has 3 internal peripheral disks on it
> with the system set to Designated Drive Letter/Removable/no int13...
>
> Crash ..........Bootlog.txt
>
> [000B745F] DEVICEINIT = VDEF
> [000B745F] DEVICEINITSUCCESS = VDEF
> [000B7461] Initing hsflop.pdr
> [000B7463] Init Success hsflop.pdr
> [000B7464] Initing drvwq117.vxd
> [000B7474] Init Success drvwq117.vxd
> [000B7474] Initing aic78xx.mpd
That's the first adaptec?
> [000B74E6] Init Success aic78xx.mpd
> [000B74E6] Initing aic78xx.mpd
That's the second one?
>
> ...........END=Blue Screen Crash [vxd vtdi error code]
That's an error of the vxd-incorporation driver itself. Possibly it does
something in parallel so it thinks of the wrong source of crash.
>
>
>
>
>
> SCSI MECHANIC BootLog of 3 AHA cards:
What's the type of the third one? I haven't find the type number yet?
>
> SCSI Cmd: Adapter 0 (aic78xx)
> Target: 0:0
> SCSI Cdb: 12 01 80 00 ff 00 [Inquiry]
> Transfer Ct: 0xff
> Actual Ct: 0x12
> DataBuffer: 00 80 00 0e 30 30 32 32 33 36 39 35 30 30 30 30
> 50 4a 00 00 b0 45 a5 07 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> Cmd Status: 1 (SCSI Request Completed Ok!) Error!
> Host Status: 12 (Data Under/Over Run)
> Target Status:0 (Ok)
What the other answerers don't look on and don't count on: The INQUIRY
is the first command the SCSI system sets on a new-found device. It's
the boot time ans the first device: Where does the additional data
beyond the '4a'-value in the second line come from? Of course the buffer
is zeroed-off before the allocation routine hands it out to the driver.
The 'b0 45 a5 07' data are additional and came from something Possibly
from the device since the buffer is reported as 'ff' in size so
additional data to send and to recieve is no problem on ... in spite of
the fact, that the device only says that this are 0x12, not 0x18.
The second thing is: '12 01' is not the standard inquiry but an enhanced
one (EVDP-Bit set). At boot time I think the standard inquiry data are
needed since there for instance are the names of vendor and product are
reported. So why it begans with the enhanced inquiry?
>
>
> SCSI Cmd: Adapter 0 (aic78xx)
> Target: 1:0
> SCSI Cdb: 12 01 80 00 ff 00 [Inquiry]
> Transfer Ct: 0xff
> Actual Ct: 0x12
> DataBuffer: 00 80 00 0e 4a 4c 31 35 37 31 35 36 30 50 50 42
> 4a 52 00 00 40 42 a5 07 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> Cmd Status: 1 (SCSI Request Completed Ok!) Error!
> Host Status: 12 (Data Under/Over Run)
> Target Status:0 (Ok)
That's the same. The four last bytes not 0 are overrun-data ... and
different from these seen above so no one can think of old data or so.
>
>
> SCSI Cmd: Adapter 0 (aic78xx)
> Target: 8:0
> SCSI Cdb: 12 01 80 00 ff 00 [Inquiry]
> Transfer Ct: 0xff
> Actual Ct: 0x26
> DataBuffer: 00 80 00 22 50 43 42 3d 32 30 31 31 33 30 30 30
> 30 32 20 20 3b 20 48 44 41 3d 31 38 34 37 30 37
> 33 31 33 37 34 39 34 37 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> Cmd Status: 1 (SCSI Request Completed Ok!) Error!
> Host Status: 12 (Data Under/Over Run)
> Target Status:0 (Ok)
>
And for the third one. The data count in third line is 8 so 0x26 is
incorrect too.
>
> OTHER CARDS:
>
> SCSI Cmd: Adapter 1 (sparrow)
But what's that? I thought you have wrote it is an adaptec adaptor too
and what is this sparrow at all? I don't know any adaptor from any
source with such a name but of course I don't know all adaptors so can
someone tell me what this is?
> Target: 4:0
> SCSI Cdb: 12 01 80 00 ff 00 [Inquiry]
> Transfer Ct: 0xff
> Actual Ct: 0xb
> DataBuffer: 01 80 00 07 47 43 30 31 35 5a 56 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> Cmd Status: 1 (SCSI Request Completed Ok!) Error!
> Host Status: 12 (Data Under/Over Run)
> Target Status:0 (Ok)
Here's the count error a little bit more astonishing since here it seems
to be correct ... but possibly not the driver.
>
>
> SCSI Cmd: Adapter 1 (sparrow)
> Target: 6:0
> SCSI Cdb: 12 01 80 00 ff 00 [Inquiry]
> Transfer Ct: 0xff
> Actual Ct: 0xb
> DataBuffer: 01 80 00 07 47 43 30 30 56 53 44 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> Cmd Status: 1 (SCSI Request Completed Ok!) Error!
> Host Status: 12 (Data Under/Over Run)
> Target Status:0 (Ok)
>
Same way too.
>
> SCSI Cmd: Adapter 2 (ESDI_506)
That's really a missmatch. ESDI_506 is one of the predecessors of the
IDE interface and is defined in early 80's I think. It is out-of-date
for long time and I think it's today impossible to find any device for
this interface anywhere outside a museum. So this is of course no
ESDI_506 adaptor.
> Target: 0:0
> SCSI Cdb: 00 00 00 00 00 00 [Test Unit Ready]
> Transfer Ct: 0x0
> Actual Ct: 0x0
> Host Status: 0 (Ok)
> Target Status:0 (Ok)
Of course no reaktion. Test Unit Ready would get no reaction anyway on ESDI.
>
>
> SCSI Cmd: Adapter 2 (ESDI_506)
> Target: 0:0
> SCSI Cdb: 00 00 00 00 00 00 [Test Unit Ready]
> Transfer Ct: 0x0
> Actual Ct: 0x0
> Host Status: 0 (Ok)
> Target Status:0 (Ok)
>
>
> SCSI Cmd: Adapter 2 (ESDI_506)
> Target: 0:0
> SCSI Cdb: 00 00 00 00 00 00 [Test Unit Ready]
> Transfer Ct: 0x0
> Actual Ct: 0x0
> Host Status: 0 (Ok)
> Target Status:0 (Ok)
>
>
> SCSI Cmd: Adapter 2 (ESDI_506)
> Target: 0:0
> SCSI Cdb: 5a 00 05 00 00 00 00 00 48 00 [Mode Sense Long]
> Transfer Ct: 0x48
> Actual Ct: 0x48
> DataBuffer: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> Cmd Status: 4 (SCSI Request Error!)
> Host Status: 0 (Ok)
> Target Status:2 (Check Condition)
> Sense Data: 70 00 05 00 00 00 00 0a 00 00 00 00 24 00 00 00
> 00 00
> Illegal Request Error.
That's correct. Since ESDI doesn't support such a command it is an
illegal request.
> Additional Sense: Invalid Field in CDB
> Sense Qualifier: 0
>
>
> ======================================
>
> The only way I can reboot into windows after a crash, is to
> reinstall a former registry which is the same as the one being used, and it
> logs in...but that is a real drag ater a few thousand times.
>
> Thanx in Advance
What I think of: You use a windows95-System. What is the computer
itself? Which kind of sytem is it? The processor?
And then: What's about the dates: The mpd-driver for the AIC, what is
the date of it? Is it newer then windows itself?
(aic78xx) ReBoot Problem 
Linear Mode
