Some partition is not accessible.

  • Thread starter Thread starter toyota58
  • Start date Start date
T

toyota58

I'm using Windows 98. I just add a second harddisk which is slave 250
GB Hitachi IDE. I did Fdisk and format to 8 partition and everything
is OK. But when I run Windows 98 and checked the partition ...the last
3 partition is not accessible in Windows Explorer. Whenever I double
click the partition in Window Explorer ...for example drive L...the
error says " L is not accessible. A device attach to the system is not
functioning " .

Thank You.
 
Previously toyota58 said:
I'm using Windows 98. I just add a second harddisk which is slave 250
GB Hitachi IDE. I did Fdisk and format to 8 partition and everything
is OK. But when I run Windows 98 and checked the partition ...the last
3 partition is not accessible in Windows Explorer. Whenever I double
click the partition in Window Explorer ...for example drive L...the
error says " L is not accessible. A device attach to the system is not
functioning " .
Click to expand...

If I remember correctly, Win98 has a 128GB limit on drive size.

Arno
 
Your BIOS supports LBA-48, so fdisk & format from DOS work.
Windows 98/ME's IDE driver is only good to 128GB (LBA-28).

You can start Win.com with a flag to run the disks in compatability mode,
or look for the chipset IDE driver (Intel does not have LBA-48 driver).
 
Eric Gisin said:
Your BIOS supports LBA-48, so fdisk & format from DOS work.
Windows 98/ME's IDE driver is only good to 128GB (LBA-28).

You can start Win.com with a flag to run the disks in compatability mode,
or look for the chipset IDE driver
Click to expand...
 
I'm using Windows 98. I just add a second harddisk which is slave 250
GB Hitachi IDE. I did Fdisk and format to 8 partition and everything
is OK. But when I run Windows 98 and checked the partition ...the last
3 partition is not accessible in Windows Explorer. Whenever I double
click the partition in Window Explorer ...for example drive L...the
error says " L is not accessible. A device attach to the system is not
functioning " .

Thank You.
Click to expand...

I finally took the time to make a disk with the sector number written
to each sector, so it would be possible to determine which sectors
Windows 98 actually reads (and writes).

Some examples. The first part of each line is the sector number of the
read command, and the second part is the sector actually read:


OS: Windows 4.10.2222

Disk: 3 Cylinders: 19457 Heads: 255 Sectors: 63 MB: 152625

Start cylinder: 17000 End cylinder: 17000

-------LBA -----Hex ---------CHS Read LBA -----Hex -- Read CHS
273105000 10474068 17000 0 1 17136000 01057980 1066 170 1
273105001 10474069 17000 0 2 17136001 01057981 1066 170 2
273105002 1047406A 17000 0 3 17136002 01057982 1066 170 3
273105003 1047406B 17000 0 4 17136003 01057983 1066 170 4
273105004 1047406C 17000 0 5 17136004 01057984 1066 170 5
273105005 1047406D 17000 0 6 17136005 01057985 1066 170 6
273105006 1047406E 17000 0 7 17136006 01057986 1066 170 7
273105007 1047406F 17000 0 8 17136007 01057987 1066 170 8
273105008 10474070 17000 0 9 17136008 01057988 1066 170 9
273105009 10474071 17000 0 10 17136009 01057989 1066 170 10
273105010 10474072 17000 0 11 17136010 0105798A 1066 170 11
273105011 10474073 17000 0 12 17136011 0105798B 1066 170 12
273105012 10474074 17000 0 13 17136012 0105798C 1066 170 13
273105013 10474075 17000 0 14 17136013 0105798D 1066 170 14
273105014 10474076 17000 0 15 17136014 0105798E 1066 170 15
273105015 10474077 17000 0 16 17136015 0105798F 1066 170 16


OS: Windows 4.10.2222

Disk: 3 Cylinders: 19457 Heads: 255 Sectors: 63 MB: 152625

Start cylinder: 18000 End cylinder: 18000

-------LBA -----Hex ---------CHS Read LBA -----Hex -- Read CHS
289170000 113C6250 18000 0 1 18144000 0114DB00 1129 105 1
289170001 113C6251 18000 0 2 18144001 0114DB01 1129 105 2
289170002 113C6252 18000 0 3 18144002 0114DB02 1129 105 3
289170003 113C6253 18000 0 4 18144003 0114DB03 1129 105 4
289170004 113C6254 18000 0 5 18144004 0114DB04 1129 105 5
289170005 113C6255 18000 0 6 18144005 0114DB05 1129 105 6
289170006 113C6256 18000 0 7 18144006 0114DB06 1129 105 7
289170007 113C6257 18000 0 8 18144007 0114DB07 1129 105 8
289170008 113C6258 18000 0 9 18144008 0114DB08 1129 105 9
289170009 113C6259 18000 0 10 18144009 0114DB09 1129 105 10
289170010 113C625A 18000 0 11 18144010 0114DB0A 1129 105 11
289170011 113C625B 18000 0 12 18144011 0114DB0B 1129 105 12
289170012 113C625C 18000 0 13 18144012 0114DB0C 1129 105 13
289170013 113C625D 18000 0 14 18144013 0114DB0D 1129 105 14
289170014 113C625E 18000 0 15 18144014 0114DB0E 1129 105 15
289170015 113C625F 18000 0 16 18144015 0114DB0F 1129 105 16


273105000 10474068 17000 0 1 17136000 01057980 1066 170 1
289170000 113C6250 18000 0 1 18144000 0114DB00 1129 105 1

273105000 - 17136000 is 255969000
289170000 - 18144000 is 271026000

There is not a fixed difference between the read command sector, and
the sector read.

It should be noted that there are many different versions of the
Windows 98 128 GB problem.

Also note that even if a partition can be seen, it is not safe to
access or use the partition. The short version is that disks larger
than 128 GB should not be in Windows 98 systems. External USB disks
larger than 128 GB may be safe, or only cause minor data corruption.
 
Also note that even if a partition can be seen, it is not safe to
access or use the partition. The short version is that disks larger
than 128 GB should not be in Windows 98 systems. External USB disks
larger than 128 GB may be safe, or only cause minor data corruption.
Click to expand...

External USB disks larger than 128 GB may be safe in Windows 98, or
only have minor problems, but not in DOS.

I my systems, the BIOS provides a BIOS disk number for USB disks, the
disk size is reported correctly, and FAT partitions can be accessed in
DOS (slow), but for sectors after 128 GB nothing actually is read from
or written to the disk. Read or write errors are not reported.
Obviously this can cause partition corruption.

The method to test for this would be: Fill a 512 bytes read buffer
with some unique data, which cannot be on the disk. Read a sector
after 128 GB. If the read buffer has not changed, the 128 GB problem
is present. I may add this test to my GB32 program.
 
Your BIOS supports LBA-48, so fdisk & format from DOS work.
Windows 98/ME's IDE driver is only good to 128GB (LBA-28).

You can start Win.com with a flag to run the disks in compatability mode,
or look for the chipset IDE driver (Intel does not have LBA-48 driver).
Click to expand...

Apparently some Intel chipsets have an IAA (accelerator) that replaces
Microsoft's ESDI_506.PDR driver with INTELATA.MPD.

This thread at microsoft.public.win98.gen_discussion suggests that
Intel's driver may provide 48-bit LBA support:
http://groups.google.com/group/microsoft.public.win98.gen_discussion/msg/4adb76e90870b8f3?hl=en


- Franc Zabkar
 
My 320GB USB HD appears to be safe in both Win98SE and DOS. I'm using
the Maximus Decim NUSB driver set. For DOS support see below.

One gotcha is that neither Scandisk nor Defrag work. They complain of
insufficient memory. However, the Win ME version of Defrag works, but
Win ME's Scandisk also has memory problems.

BTW, I FDISKed the USB drive within a Windows DOS box and formatted it
via the GUI.
External USB disks larger than 128 GB may be safe in Windows 98, or
only have minor problems, but not in DOS.

I my systems, the BIOS provides a BIOS disk number for USB disks, the
disk size is reported correctly, and FAT partitions can be accessed in
DOS (slow), ...
Click to expand...

My ECS L7S7A2 AMI BIOS enables the USB 2.0 EHCI controller but does
not enable USB 2.0 data transfers. Maybe yours behaves likewise?

To enable USB 2.0 support in real DOS (not a DOS window), I use a
Panasonic OHCI/EHCI driver (USBASPI.SYS, version 2.15). It is included
in the following archive:
http://panasonic.co.jp/pcc/products/drive/other/driver/f2h_usb.exe

For HD support I use the Moto Hairu HD driver (DI1000DD.SYS):
http://www.stefan2000.com/darkehorse/PC/DOS/Drivers/USB/mhairu.zip

BTW, the USBASPI.SYS driver produces an extensive report which makes
it a useful diagnostic tool. For example, the following report was
produced by an earlier version of the same driver. This version was
incompatible with my SiS 7002 EHCI controller.

Device
| Function
Bus | |
| | |
Controller : 00-03-0 VID=1039h PID=7001h (1019h-1808h) OHCI
: MEM=CFFFD000h-CFFFDFFFh(4KBytes)

Controller : 00-03-1 VID=1039h PID=7001h (1019h-1808h) OHCI
: MEM=CFFFE000h-CFFFEFFFh(4KBytes)

ERROR : EHCI memory mapped I/O can not be assigned.

The remainder of the report lists the USB devices and their
connectivity.
... but for sectors after 128 GB nothing actually is read from
or written to the disk. Read or write errors are not reported.
Obviously this can cause partition corruption.
Click to expand...

Is that a BIOS limitation or a DOS limitation?
The method to test for this would be: Fill a 512 bytes read buffer
with some unique data, which cannot be on the disk. Read a sector
after 128 GB. If the read buffer has not changed, the 128 GB problem
is present. I may add this test to my GB32 program.
Click to expand...

At the moment my HD contains only test data, so I'd be willing to try
your software on it.

- Franc Zabkar
 
I finally took the time to make a disk with the sector number written
to each sector, so it would be possible to determine which sectors
Windows 98 actually reads (and writes).

Some examples. The first part of each line is the sector number of the
read command, and the second part is the sector actually read:


OS: Windows 4.10.2222

Disk: 3 Cylinders: 19457 Heads: 255 Sectors: 63 MB: 152625

Start cylinder: 17000 End cylinder: 17000

-------LBA -----Hex ---------CHS Read LBA -----Hex -- Read CHS
273105000 10474068 17000 0 1 17136000 01057980 1066 170 1
273105001 10474069 17000 0 2 17136001 01057981 1066 170 2
273105002 1047406A 17000 0 3 17136002 01057982 1066 170 3
273105003 1047406B 17000 0 4 17136003 01057983 1066 170 4
273105004 1047406C 17000 0 5 17136004 01057984 1066 170 5
273105005 1047406D 17000 0 6 17136005 01057985 1066 170 6
273105006 1047406E 17000 0 7 17136006 01057986 1066 170 7
273105007 1047406F 17000 0 8 17136007 01057987 1066 170 8
273105008 10474070 17000 0 9 17136008 01057988 1066 170 9
273105009 10474071 17000 0 10 17136009 01057989 1066 170 10
273105010 10474072 17000 0 11 17136010 0105798A 1066 170 11
273105011 10474073 17000 0 12 17136011 0105798B 1066 170 12
273105012 10474074 17000 0 13 17136012 0105798C 1066 170 13
273105013 10474075 17000 0 14 17136013 0105798D 1066 170 14
273105014 10474076 17000 0 15 17136014 0105798E 1066 170 15
273105015 10474077 17000 0 16 17136015 0105798F 1066 170 16


OS: Windows 4.10.2222

Disk: 3 Cylinders: 19457 Heads: 255 Sectors: 63 MB: 152625

Start cylinder: 18000 End cylinder: 18000

-------LBA -----Hex ---------CHS Read LBA -----Hex -- Read CHS
289170000 113C6250 18000 0 1 18144000 0114DB00 1129 105 1
289170001 113C6251 18000 0 2 18144001 0114DB01 1129 105 2
289170002 113C6252 18000 0 3 18144002 0114DB02 1129 105 3
289170003 113C6253 18000 0 4 18144003 0114DB03 1129 105 4
289170004 113C6254 18000 0 5 18144004 0114DB04 1129 105 5
289170005 113C6255 18000 0 6 18144005 0114DB05 1129 105 6
289170006 113C6256 18000 0 7 18144006 0114DB06 1129 105 7
289170007 113C6257 18000 0 8 18144007 0114DB07 1129 105 8
289170008 113C6258 18000 0 9 18144008 0114DB08 1129 105 9
289170009 113C6259 18000 0 10 18144009 0114DB09 1129 105 10
289170010 113C625A 18000 0 11 18144010 0114DB0A 1129 105 11
289170011 113C625B 18000 0 12 18144011 0114DB0B 1129 105 12
289170012 113C625C 18000 0 13 18144012 0114DB0C 1129 105 13
289170013 113C625D 18000 0 14 18144013 0114DB0D 1129 105 14
289170014 113C625E 18000 0 15 18144014 0114DB0E 1129 105 15
289170015 113C625F 18000 0 16 18144015 0114DB0F 1129 105 16


273105000 10474068 17000 0 1 17136000 01057980 1066 170 1
289170000 113C6250 18000 0 1 18144000 0114DB00 1129 105 1

273105000 - 17136000 is 255969000
289170000 - 18144000 is 271026000

There is not a fixed difference between the read command sector, and
the sector read.

It should be noted that there are many different versions of the
Windows 98 128 GB problem.

Also note that even if a partition can be seen, it is not safe to
access or use the partition. The short version is that disks larger
than 128 GB should not be in Windows 98 systems. External USB disks
larger than 128 GB may be safe, or only cause minor data corruption.
Click to expand...

There are, and have been, several long threads on this issue at
microsoft.public.win98.gen_discussion. The limitation appears to be
due to Microsoft's ESDI_506.PDR driver. Apparently some Intel chipsets
have an IAA (accelerator) that replaces Microsoft's driver with
INTELATA.MPD. There is one person (98 Guy) who has done extensive
research and testing in this area. He seems to believe that
INTELATA.MPD may provide 48-bit LBA support in the Windows environment
(he is testing it now). My understanding is that DOS has no issue with
large PATA drives (> 137GB) provided that the BIOS provides 48-bit LBA
support.

- Franc Zabkar
 
There are, and have been, several long threads on this issue at
microsoft.public.win98.gen_discussion. The limitation appears to be
due to Microsoft's ESDI_506.PDR driver. Apparently some Intel chipsets
have an IAA (accelerator) that replaces Microsoft's driver with
INTELATA.MPD. There is one person (98 Guy) who has done extensive
research and testing in this area. He seems to believe that
INTELATA.MPD may provide 48-bit LBA support in the Windows environment
(he is testing it now). My understanding is that DOS has no issue with
large PATA drives (> 137GB) provided that the BIOS provides 48-bit LBA
support.

- Franc Zabkar
Click to expand...

Just be certain to use the latest Intel Application Accelerator.
Versions included on motherboard manufacturer CD's may have a 128 GB
problem, including the version reporting 2.2.0.2126 in "About".
 
Just be certain to use the latest Intel Application Accelerator.
Versions included on motherboard manufacturer CD's may have a 128 GB
problem, including the version reporting 2.2.0.2126 in "About".
Click to expand...

Thanks. I visited your web site after posting. I've already passed on
your recommendations/warnings in the other forum.

- Franc Zabkar
 
Franc Zabkar wrote in news:[email protected]
I'm using Windows 98. I just add a second harddisk which is slave 250
GB Hitachi IDE. I did Fdisk and format to 8 partition and everything
is OK. But when I run Windows 98 and checked the partition ...the last
3 partition is not accessible in Windows Explorer. Whenever I double
click the partition in Window Explorer ...for example drive L...the
error says " L is not accessible. A device attach to the system is not
functioning " .

Thank You.
Click to expand...

I finally took the time to make a disk with the sector number written
to each sector, so it would be possible to determine which sectors
Windows 98 actually reads (and writes).

Some examples. [snipped]

It should be noted that there are many different versions of the
Windows 98 128 GB problem.

Also note that even if a partition can be seen, it is not safe to
access or use the partition. The short version is that disks larger
than 128 GB should not be in Windows 98 systems. External USB disks
larger than 128 GB may be safe, or only cause minor data corruption.
Click to expand...

There are, and have been, several long threads on this issue at
microsoft.public.win98.gen_discussion.
Click to expand...
The limitation appears to be due to Microsoft's ESDI_506.PDR driver.
Click to expand...

For which there is a replacement if you are willing to pay for it.
And has nothing to do with USB.
Apparently some Intel chipsets have an IAA (accelerator) that replaces
Microsoft's driver with INTELATA.MPD.
Click to expand...

IAA (Intel® Application Accelerator) is a software package.
There is one person (98 Guy) who has done extensive research and testing > in this area.
Click to expand...

Is he now.
He seems to believe that INTELATA.MPD may provide 48-bit LBA
support in the Windows environment (he is testing it now).
Click to expand...

Yeah, why take Intel's word on it: Large Hard Drive Support paragraph.
http://www.intel.com/support/chipsets/iaa/sb/cs-009309.htm
 
Back
Top