HP st336706lw 36.4 10K Ultra3 SCSI Drive problem!

Regarding a HP st336706lw 36.4 10K Ultra3 SCSI Drive:

I'm using win/9x and when running this SCSI HDDrive, all I can read
is 1.9GB after a long SCSI aha ultra low level format, and then a Win/9x
reformat...."SCSI Mechanic" or Adaptec's partitioners doesn't see anything
more than 1.9GB partition/ttl drive.

I don't see a minimal 8GB, or anything like the minimal win/95 would
allow.....I forced the SE HDD jumper and termed properly on the cable end
since it has no HDD terminate jumper...it's an LVD of course.

This drive has 36.4GB, where did the other 34.5GB go,......... has
anyone ever experienced this 1.9GB max of a larger scsi drive?

All my other scsi drives have no problem being seen or fully 32bit
partition formatted....

R. LaCasse wrote in newssr0d4lnuso3gtedg6s9pa0nqe08g5pdeh@4ax.com
> Regarding a HP st336706lw 36.4 10K Ultra3 SCSI Drive:
>
> I'm using win/9x and when running this SCSI HDDrive, all I can read
> is 1.9GB

> after a long SCSI aha ultra low level format,

What was that good for.

> and then a Win/9x reformat...."SCSI Mechanic" or Adaptec's par-
> titioners doesn't see anything more than 1.9GB partition/ttl drive.
>
> I don't see a minimal 8GB, or anything like the minimal win/95 would
> allow.....

> I forced the SE HDD jumper and termed properly on the cable
> end since it has no HDD terminate jumper...it's an LVD of course.

Which obviously has nothing got to do with it.

>
> This drive has 36.4GB, where did the other 34.5GB go,......... has
> anyone ever experienced this 1.9GB max of a larger scsi drive?
>
> All my other scsi drives have no problem being seen or fully 32bit
> partition formatted....

http://www.google.com/search?hl=en&q...ch+shortstroke

If shortstroke is not the problem it may be a modulo xxGB BIOS problem.


Oh, and cut the software newsgroups when you reply.

"Squeeze" <rubberduck@duckies.au> wrote in message
news:48d16179$2$29109$8f2e0ebb@news.shared-secrets.com...
> R. LaCasse wrote in newssr0d4lnuso3gtedg6s9pa0nqe08g5pdeh@4ax.com
>> Regarding a HP st336706lw 36.4 10K Ultra3 SCSI Drive:
>>
>> I'm using win/9x and when running this SCSI HDDrive, all I can read
>> is 1.9GB
>
>> after a long SCSI aha ultra low level format,
>
> What was that good for.
>
>> and then a Win/9x reformat...."SCSI Mechanic" or Adaptec's par-
>> titioners doesn't see anything more than 1.9GB partition/ttl drive.
>>
>> I don't see a minimal 8GB, or anything like the minimal win/95 would
>> allow.....
>
>> I forced the SE HDD jumper and termed properly on the cable
>> end since it has no HDD terminate jumper...it's an LVD of course.
>
> Which obviously has nothing got to do with it.
>
>>
>> This drive has 36.4GB, where did the other 34.5GB go,......... has
>> anyone ever experienced this 1.9GB max of a larger scsi drive?
>>
>> All my other scsi drives have no problem being seen or fully 32bit
>> partition formatted....
>
> http://www.google.com/search?hl=en&q...ch+shortstroke
>
> If shortstroke is not the problem it may be a modulo xxGB BIOS problem.
>
>
> Oh, and cut the software newsgroups when you reply.
>

Have you formatted FAT16?

Mike.

"Squeeze" <rubberduck@duckies.au> wrote in message
news:48d16179$2$29109$8f2e0ebb@news.shared-secrets.com...
> R. LaCasse wrote in newssr0d4lnuso3gtedg6s9pa0nqe08g5pdeh@4ax.com
>> Regarding a HP st336706lw 36.4 10K Ultra3 SCSI Drive:
>>
>> I'm using win/9x and when running this SCSI HDDrive, all I can read
>> is 1.9GB
>
>> after a long SCSI aha ultra low level format,
>
> What was that good for.
>
>> and then a Win/9x reformat...."SCSI Mechanic" or Adaptec's par-
>> titioners doesn't see anything more than 1.9GB partition/ttl drive.
>>
>> I don't see a minimal 8GB, or anything like the minimal win/95 would
>> allow.....
>
>> I forced the SE HDD jumper and termed properly on the cable
>> end since it has no HDD terminate jumper...it's an LVD of course.
>
> Which obviously has nothing got to do with it.
>
>>
>> This drive has 36.4GB, where did the other 34.5GB go,......... has
>> anyone ever experienced this 1.9GB max of a larger scsi drive?
>>
>> All my other scsi drives have no problem being seen or fully 32bit
>> partition formatted....
>
> http://www.google.com/search?hl=en&q...ch+shortstroke
>
> If shortstroke is not the problem it may be a modulo xxGB BIOS problem.
>
>
> Oh, and cut the software newsgroups when you reply.
>

Have you formatted FAT16?

Mike.

Michael Hawes wrote in news:48dd5814_3@mk-nntp-2.news.uk.tiscali.com
> "Squeeze" <rubberduck@duckies.au> wrote in message
> news:48d16179$2$29109$8f2e0ebb@news.shared-secrets.com...
> > R. LaCasse wrote in newssr0d4lnuso3gtedg6s9pa0nqe08g5pdeh@4ax.com
> > > Regarding a HP st336706lw 36.4 10K Ultra3 SCSI Drive:
> > >
> > > I'm using win/9x and when running this SCSI HDDrive, all I can read
> > > is 1.9GB
> >
> > > after a long SCSI aha ultra low level format,
> >
> > What was that good for.
> >
> > > and then a Win/9x reformat...."SCSI Mechanic" or Adaptec's par-
> > > titioners doesn't see anything more than 1.9GB partition/ttl drive.
> > >
> > > I don't see a minimal 8GB, or anything like the minimal win/95 would
> > > allow.....
> >
> > > I forced the SE HDD jumper and termed properly on the cable
> > > end since it has no HDD terminate jumper...it's an LVD of course.
> >
> > Which obviously has nothing got to do with it.
> >
> > >
> > > This drive has 36.4GB, where did the other 34.5GB go,......... has
> > > anyone ever experienced this 1.9GB max of a larger scsi drive?
> > >
> > > All my other scsi drives have no problem being seen or fully 32bit
> > > partition formatted....
> >
> > http://www.google.com/search?hl=en&q...ch+shortstroke
> >
> > If shortstroke is not the problem it may be a modulo xxGB BIOS problem.
> >
> >
> > Oh, and cut the software newsgroups when you reply.
> >
>
> Have you formatted FAT16?
>
> Mike.

No, I haven't. You?

On Wed, 17 Sep 2008 20:53:41 +0100, "Squeeze" <rubberduck@duckies.au> wrote:

|>> All my other scsi drives have no problem being seen or fully 32bit
|>> partition formatted....
|>
|>http://www.google.com/search?hl=en&q...ch+shortstroke
|>
|>If shortstroke is not the problem it may be a modulo xxGB BIOS problem.

Lot's of interesting GUI scsi utils.....but they are all the same,
when an HP bare-drive in a non HP machine is used!

On Fri, 26 Sep 2008 22:45:38 +0100, "Michael Hawes"
<michael.hawes1remove@tiscali.co.uk> wrote:

|>
|>Have you formatted FAT16?
|>
|>Mike.

No FAT32 as is in the windows default recognition, only this time it
seemed to recognize too much and made a weird mbr format........

This is a 10 minute format, it should be drawing a lot of lines, but
des not see them?

R. LaCasse wrote in news:897sd45uv5l5l4lhmmhhejammgkavrffse@4ax.com
> On Wed, 17 Sep 2008 20:53:41 +0100, "Squeeze" <rubberduck@duckies.au> wrote:
>
> > > > All my other scsi drives have no problem being seen or fully 32bit
> > > > partition formatted....
> > >
> > > http://www.google.com/search?hl=en&q...ch+shortstroke
> > >
> > > If shortstroke is not the problem it may be a modulo xxGB BIOS problem.

> Lot's of interesting GUI scsi utils.....

Yeah, obviously they are useless.

> but they are all the same, when an HP bare-drive in a non HP machine
> is used!

Yeah, obviously those useless Gui utils only work in HP machines.

On Sat, 27 Sep 2008 04:05:48 +0100, "Squeeze" <rubberduck@duckies.au> wrote:

|>Michael Hawes wrote in news:48dd5814_3@mk-nntp-2.news.uk.tiscali.com
|>> "Squeeze" <rubberduck@duckies.au> wrote in message
|>> news:48d16179$2$29109$8f2e0ebb@news.shared-secrets.com...
|>> > R. LaCasse wrote in newssr0d4lnuso3gtedg6s9pa0nqe08g5pdeh@4ax.com
|>> > > Regarding a HP st336706lw 36.4 10K Ultra3 SCSI Drive:
|>> > >
|>> > > I'm using win/9x and when running this SCSI HDDrive, all I can read
|>> > > is 1.9GB
|>> >
|>> > > after a long SCSI aha ultra low level format,
|>> >
|>> > What was that good for.
|>> >
|>> > > and then a Win/9x reformat...."SCSI Mechanic" or Adaptec's par-
|>> > > titioners doesn't see anything more than 1.9GB partition/ttl drive.
|>> > >
|>> > > I don't see a minimal 8GB, or anything like the minimal win/95 would
|>> > > allow.....
|>> >
|>> > > I forced the SE HDD jumper and termed properly on the cable
|>> > > end since it has no HDD terminate jumper...it's an LVD of course.
|>> >
|>> > Which obviously has nothing got to do with it.
|>> >
|>> > >
|>> > > This drive has 36.4GB, where did the other 34.5GB go,......... has
|>> > > anyone ever experienced this 1.9GB max of a larger scsi drive?
|>> > >
|>> > > All my other scsi drives have no problem being seen or fully 32bit
|>> > > partition formatted....
|>> >
|>> > http://www.google.com/search?hl=en&q...ch+shortstroke
|>> >
|>> > If shortstroke is not the problem it may be a modulo xxGB BIOS problem.
|>> >
|>> >
|>> > Oh, and cut the software newsgroups when you reply.
|>> >
|>>
|>> Have you formatted FAT16?
|>>
|>> Mike.
|>
|>No, I haven't. You?

If you run a lot of SMALLER Win/Dos files, they FAT16 will occupy
more of your disk space and runner some nano seconds faster, rather than the
staggered 32/64 formats.....nothing new there, most of this is
forgotten.....

On Sat, 27 Sep 2008 23:25:37 +0100, "Squeeze" <rubberduck@duckies.au> wrote:

|>R. LaCasse wrote in news:897sd45uv5l5l4lhmmhhejammgkavrffse@4ax.com
|>> On Wed, 17 Sep 2008 20:53:41 +0100, "Squeeze" <rubberduck@duckies.au> wrote:
|>>
|>> > > > All my other scsi drives have no problem being seen or fully 32bit
|>> > > > partition formatted....
|>> > >
|>> > > http://www.google.com/search?hl=en&q...ch+shortstroke
|>> > >
|>> > > If shortstroke is not the problem it may be a modulo xxGB BIOS problem.
|>
|>> Lot's of interesting GUI scsi utils.....
|>
|>Yeah, obviously they are useless.
|>
If it's a "modulo xxGB BIOS problem" there is no source programming
code or Eprom burn in to make the "LVD" drive "click" right...

|>> but they are all the same, when an HP bare-drive in a non HP machine
|>> is used!
|>
|>Yeah, obviously those useless Gui utils only work in HP machines.

I really think that is the planned obsolescence problem, a
proprietary HP drive needing an HP accessory P/N P1169A or HP drivers....

I have never had this problem before......