Big Disk problem with Windows98
etien...@my-deja.com
Windows98. I added two disks (WD and IBM) greater than 8Gb and I am
having a lot of problem accessing partitions above the 8Gb with Win98.
What I am sure of :
- I have the latest BIOS for my motherboard (FIC VA-503+) and I have
checked (with different utilities) the int13h extension.
- FDISK under Win98 can see the correct disks size
- I use Partition Magic (4.01) under win98 without any problem, it can
access all partitions.
- I have a ext2fs primary partition completely above 8Gb which can be
used without any problems by Linux (I suppose this means my bios is ok)
If I try to create (with fdisk or PM) an extended partition greater than
8Gb, the FIRST logical partition inside (which is below the 8Gb limit)
can't be used correctly by Win98, it works correctly as soon as I reduce
the extended partion below 8Gb.
Linux can see all partitions anywhere and any size.
Where is the error (apart using win98).
Can someone help ?
Sent via Deja.com http://www.deja.com/
Before you buy.
Tom Pfeifer
If Win98 fdisk is seeing the correct disk sizes, that is a good
indication that your BIOS properly supports those drives. And, based on
that, you *should* be able to access extended/logical partitions above
8GB on those drives.
What exact problems are you having with the logical drive(s) above 8GB?
You say you have problems with the FIRST one - does that mean you can
access the others OK?
Also, it may help explain things if you could run the PowerQuest utility
partinfo.exe (comes with PM) from a DOS prompt like this...
partinfo > partinfo.txt
...and post the entire contents of the partinfo.txt file here. All it
does is read partition data from your drives and write it to the text
file. Be sure to use the newest version of partinfo.exe that came with
the PM 4.01 update. You may have more than one version of it kicking
around on your disk.
Comments on Linux:
Linux itself doesn't depend on the BIOS to access hard drives. There is
one exception to that - Lilo, the Linux boot loader, depends on the BIOS
during the initial boot process, and can't boot any partition above 8GB
(1024 cylinders).
Linux *can* be booted from partitions above 8GB if you use Loadlin, or
if you boot directly from the Linux kernel (from a floppy). But the fact
that Linux, once booted, can see your ext2fs partition above 8GB means
nothing as far as your BIOS is concerned.
Tom
etien...@my-deja.com
So here is the result of the partinfo.exe. Disk 2 is working now
because I am only using partition under 8Gb with Win98, but for the
test, I have extented my extented partition on Disk 1 to the maximum
(just above the 8Gb).
Win98 stops booting with message "File allocation table bad, drive E",
which is the FIRST partition on the disk 1. With other configurations I
was able to boot but Win98 was trying to chkdsk the first partition and
after exiting the test it did boot but with no access to the E: (but
access to all following drives).
After reducing the extended partition I am able to boot Win98 again.
I appreciate your help
Etienne.
Partition Information Program
Jan 29 1999 - DOS32 Version
Copyright (c) 1994-1998, PowerQuest Corporation
Permission is granted for this utility to be freely copied so long
as it is not modified in any way. All other rights are reserved.
PowerQuest, makers of PartitionMagic, can be reached at
Voice: 801-437-8900 Web site: http://www.powerquest.com
Fax: 801-226-8941 Email: ma...@powerquest.com
=====================================================================
Disk 0: 767 Cylinders, 128 Heads, 63 Sectors/Track.
The BIOS supports INT 13h extensions for this drive.
========================== Partition Tables =========================
Partition -----Begin---- ------End----- Start Num
Sector # Boot Cyl Head Sect FS Cyl Head Sect Sect Sects
--------- - ---- ---- ---- ---- -- ---- ---- ---- --------- ---------
0 0 00 387 0 1 05 766 127 63 3120768 3064320
0 2 80 4 0 1 0B 386 127 63 32256 3088512
0 3 00 0 1 1 11 3 127 63 63 32193
3120768 0 00 387 1 1 06 641 127 63 3120831 2056257
3120768 1 00 732 0 1 05 764 127 63 5902848 266112
5902848 0 00 732 1 1 82 764 127 63 5902911 266049
5902848 1 00 765 0 1 05 766 127 63 6168960 16128
6168960 0 00 765 1 1 83 766 127 63 6169023 16065
=====================================================================
Disk 1: 1027 Cylinders, 255 Heads, 63 Sectors/Track.
The BIOS supports INT 13h extensions for this drive.
========================== Partition Tables =========================
Partition -----Begin---- ------End----- Start Num
Sector # Boot Cyl Head Sect FS Cyl Head Sect Sect Sects
--------- - ---- ---- ---- ---- -- ---- ---- ---- --------- ---------
0 0 00 1 0 1 0F 1023 254 63 16065 16482690
Info: Begin C,H,S values were large drive placeholders.
Info: End C,H,S values were large drive placeholders.
Actual values are:
0 0 00 1 0 1 0F 1026 254 63 16065 16482690
16065 0 00 1 1 1 0B 322 254 63 16128 5172867
16065 1 00 323 0 1 05 515 254 63 5188995 3100545
5188995 0 00 323 1 1 06 515 254 63 5189058 3100482
5188995 1 00 516 0 1 05 644 254 63 8289540 2072385
8289540 0 00 516 1 1 0B 644 254 63 8289603 2072322
8289540 1 00 645 0 1 05 771 254 63 10361925 2040255
10361925 0 00 645 1 1 0B 771 254 63 10361988 2040192
=====================================================================
Disk 2: 1869 Cylinders, 255 Heads, 63 Sectors/Track.
The BIOS supports INT 13h extensions for this drive.
========================== Partition Tables =========================
Partition -----Begin---- ------End----- Start Num
Sector # Boot Cyl Head Sect FS Cyl Head Sect Sect Sects
--------- - ---- ---- ---- ---- -- ---- ---- ---- --------- ---------
0 0 00 1023 0 1 1C 1023 254 63 16450560 3100545
Info: Begin C,H,S values were large drive placeholders.
Info: End C,H,S values were large drive placeholders.
Actual values are:
0 0 00 1024 0 1 1C 1216 254 63 16450560 3100545
0 1 00 1023 0 1 1C 1023 254 63 19551105 5172930
Info: Begin C,H,S values were large drive placeholders.
Info: End C,H,S values were large drive placeholders.
Actual values are:
0 1 00 1217 0 1 1C 1538 254 63 19551105 5172930
0 2 00 1 0 1 05 1023 254 63 16065 16434495
Info: End C,H,S values were large drive placeholders.
Actual values are:
0 2 00 1 0 1 05 1023 254 63 16065 16434495
0 3 00 1023 0 1 83 1023 254 63 25928910 4096575
Info: Begin C,H,S values were large drive placeholders.
Info: End C,H,S values were large drive placeholders.
Actual values are:
0 3 00 1614 0 1 83 1868 254 63 25928910 4096575
16065 0 00 1 1 1 0B 638 254 63 16128 10249407
16065 1 00 639 0 1 05 766 254 63 10265535 2056320
10265535 0 00 639 1 1 0B 766 254 63 10265598 2056257
10265535 1 00 767 0 1 05 895 254 63 12321855 2072385
12321855 0 00 767 1 1 0B 895 254 63 12321918 2072322
12321855 1 00 896 0 1 05 1023 254 63 14394240 2056320
Info: End C,H,S values were large drive placeholders.
Actual values are:
12321855 1 00 896 0 1 05 1023 254 63 14394240 2056320
14394240 0 00 896 1 1 16 1023 254 63 14394303 2056257
Info: End C,H,S values were large drive placeholders.
Actual values are:
14394240 0 00 896 1 1 16 1023 254 63 14394303 2056257
==============================================================================
Disk 0: 3020.1 Megabytes
============================ Partition Information
===========================
Volume Partition Partition Start
Total
Letter:Label Type Status Size MB Sector # Sector
Sectors
------------- --------------- -------- ------- --------- - ---------
---------
*:DRDOS Hidden FAT12 Pri 15.7 0 3 63
32193
C:WIN98 FAT32 Pri,Boot 1508.1 0 2 32256
3088512
Extended Pri 1496.3 0 0 3120768
3064320
EPBR Log 1004.1 None - 3120768
2056320
D:DATA FAT16B Log 1004.0 3120768 0 3120831
2056257
Free Space Log 354.4 None - 5177088
725760
EPBR Log 129.9 3120768 1 5902848
266112
Linux Swap Log 129.9 5902848 0 5902911
266049
EPBR Log 7.9 5902848 1 6168960
16128
Linux Ext2 Log 7.8 6168960 0 6169023
16065
Info: MBR Partition Table not in sequential order.
==============================================================================
Disk 1: 8056.0 Megabytes
============================ Partition Information
===========================
Volume Partition Partition Start
Total
Letter:Label Type Status Size MB Sector # Sector
Sectors
------------- --------------- -------- ------- --------- - ---------
---------
Free Space Pri 7.8 None - 63
16002
ExtendedX Pri 8048.2 0 0 16065
16482690
EPBR Log 2525.8 None - 16065
5172930
E?APPL-WIN FAT32 Log 2525.8 16065 0 16128
5172867
EPBR Log 1513.9 16065 1 5188995
3100545
F:APPL-DOS FAT16B Log 1513.9 5188995 0 5189058
3100482
EPBR Log 1011.9 5188995 1 8289540
2072385
G: FAT32 Log 1011.9 8289540 0 8289603
2072322
EPBR Log 996.2 8289540 1 10361925
2040255
H:DEMO FAT32 Log 996.2 10361925 0 10361988
2040192
Free Space Log 2000.3 None - 12402180
4096575
==============================================================================
Disk 2: 14660.9 Megabytes
============================ Partition Information
===========================
Volume Partition Partition Start
Total
Letter:Label Type Status Size MB Sector # Sector
Sectors
------------- --------------- -------- ------- --------- - ---------
---------
Free Space Pri 7.8 None - 63
16002
Extended Pri 8024.7 0 2 16065
16434495
EPBR Log 5004.6 None - 16065
10249470
I:JEUX FAT32 Log 5004.6 16065 0 16128
10249407
EPBR Log 1004.1 16065 1 10265535
2056320
J:VIDEO FAT32 Log 1004.0 10265535 0 10265598
2056257
EPBR Log 1011.9 10265535 1 12321855
2072385
K:VIDEO2 FAT32 Log 1011.9 12321855 0 12321918
2072322
EPBR Log 1004.1 12321855 1 14394240
2056320
*:DATA Hid.FAT16B Log 1004.0 14394240 0 14394303
2056257
*:WIN98 Hid.FAT32X Pri 1513.9 0 0 16450560
3100545
*:APPL-WIN Hid.FAT32X Pri 2525.8 0 1 19551105
5172930
Free Space Pri 588.3 None - 24724035
1204875
Linux Ext2 Pri 2000.3 0 3 25928910
4096575
Info: MBR Partition Table not in sequential order.
============================================================================
Boot Sector for drive *: (Drive 0, Starting Sector 0x3F, Type: FAT)
============================================================================
1. Jump: EB 56 90
2. OEM Name: NWDOS7.0
3. Bytes Per Sector: 512
4. Sectors Per Cluster: 8
5. Reserved Sectors: 1
6. Number of FATs: 2
7. Root Dir Entries: 512
8. Total Sectors: 32193 (0x7DC1)
9. Media Descriptor: 248
10. Sectors Per FAT: 12
11. Sectors Per Track: 63 (0x003F)
12. Number of Heads: 128 (0x0080)
13. Hidden Sectors: 63 (0x0000003F)
14. Big Total Sectors: 32193 (0x00007DC1)
15. Drive ID: 0x80
16. Dirty Flag: 0x00
17. Extended Boot Sig: 41 BS_FAT
18. Serial Number: 0x383FBCAF
19. Volume Name: DRDOS
20. File System Type: FAT12
21. Boot Signature: 0xAA55
============================================================================
Boot Sector for drive C: (Drive 0, Starting Sector 0x7E00, Type: FAT32)
============================================================================
1. Jump: EB 58 90
2. OEM Name: MSWIN4.1
3. Bytes Per Sector: 512
4. Sectors Per Cluster: 8
5. Reserved Sectors: 32
6. Number of FATs: 2
7. Reserved: 0x0000
8. Reserved: 0x0000
9. Media Descriptor: 248
10. Sectors Per FAT: 0
11. Sectors Per Track: 63 (0x003F)
12. Number of Heads: 128 (0x0080)
13. Hidden Sectors: 32256 (0x00007E00)
14. Big Total Sectors: 3088512 (0x002F2080)
15. Big Sectors Per FAT: 3015
16. Extended Flags: 0x0000
17. FS Version: 0x0000
18. First Cluster of Root: 2034 (0x000007F2)
19. FS Info Sector: 1
20. Backup Boot Sector: 6
21. Reserved: 000000000000000000000000
22. Drive ID: 0x80
23. Reserved for NT: 0x00
24. Extended Boot Sig: 41
25. Serial Number: 0x37D2A2F7
26. Volume Name: WIN98
27. File System Type: FAT32
28. Boot Signature: 0xAA55
============================================================================
Boot Sector for drive D: (Drive 0, Starting Sector 0x2F9EBF, Type: FAT)
============================================================================
1. Jump: EB 3C 90
2. OEM Name: MSWIN4.0
3. Bytes Per Sector: 512
4. Sectors Per Cluster: 32
5. Reserved Sectors: 1
6. Number of FATs: 2
7. Root Dir Entries: 512
8. Total Sectors: 0 (0x0000)
9. Media Descriptor: 248
10. Sectors Per FAT: 255
11. Sectors Per Track: 63 (0x003F)
12. Number of Heads: 128 (0x0080)
13. Hidden Sectors: 63 (0x0000003F)
14. Big Total Sectors: 2056257 (0x001F6041)
15. Drive ID: 0x80
16. Dirty Flag: 0x00
17. Extended Boot Sig: 41 BS_FAT
18. Serial Number: 0x383DCA41
19. Volume Name: DATA
20. File System Type: FAT16
21. Boot Signature: 0xAA55
============================================================================
Boot Sector for drive E: (Drive 1, Starting Sector 0x3F00, Type: FAT32)
============================================================================
1. Jump: EB 58 90
2. OEM Name: MSWIN4.1
3. Bytes Per Sector: 512
4. Sectors Per Cluster: 8
5. Reserved Sectors: 33
6. Number of FATs: 2
7. Reserved: 0x0000
8. Reserved: 0x0000
9. Media Descriptor: 248
10. Sectors Per FAT: 0
11. Sectors Per Track: 63 (0x003F)
12. Number of Heads: 255 (0x00FF)
13. Hidden Sectors: 63 (0x0000003F)
14. Big Total Sectors: 5172867 (0x004EEE83)
15. Big Sectors Per FAT: 5045
16. Extended Flags: 0x0000
17. FS Version: 0x0000
18. First Cluster of Root: 48446 (0x0000BD3E)
19. FS Info Sector: 1
20. Backup Boot Sector: 6
21. Reserved: 000000000000000000000000
22. Drive ID: 0x80
23. Reserved for NT: 0x00
24. Extended Boot Sig: 41
25. Serial Number: 0x383B9E2B
26. Volume Name: APPL-WIN
27. File System Type: FAT32
28. Boot Signature: 0xAA55
============================================================================
Boot Sector for drive F: (Drive 1, Starting Sector 0x4F2DC2, Type: FAT)
============================================================================
1. Jump: EB 3C 90
2. OEM Name: MSWIN4.0
3. Bytes Per Sector: 512
4. Sectors Per Cluster: 64
5. Reserved Sectors: 1
6. Number of FATs: 2
7. Root Dir Entries: 512
8. Total Sectors: 0 (0x0000)
9. Media Descriptor: 248
10. Sectors Per FAT: 217
11. Sectors Per Track: 63 (0x003F)
12. Number of Heads: 255 (0x00FF)
13. Hidden Sectors: 63 (0x0000003F)
14. Big Total Sectors: 3100482 (0x002F4F42)
15. Drive ID: 0x80
16. Dirty Flag: 0x00
17. Extended Boot Sig: 41 BS_FAT
18. Serial Number: 0x70773F96
19. Volume Name: APPL-DOS
20. File System Type: FAT16
21. Boot Signature: 0xAA55
============================================================================
Boot Sector for drive G: (Drive 1, Starting Sector 0x7E7D43, Type:
FAT32)
============================================================================
1. Jump: EB 58 90
2. OEM Name: MSWIN4.1
3. Bytes Per Sector: 512
4. Sectors Per Cluster: 8
5. Reserved Sectors: 33
6. Number of FATs: 2
7. Reserved: 0x0000
8. Reserved: 0x0000
9. Media Descriptor: 248
10. Sectors Per FAT: 0
11. Sectors Per Track: 63 (0x003F)
12. Number of Heads: 255 (0x00FF)
13. Hidden Sectors: 63 (0x0000003F)
14. Big Total Sectors: 2072322 (0x001F9F02)
15. Big Sectors Per FAT: 2021
16. Extended Flags: 0x0000
17. FS Version: 0x0000
18. First Cluster of Root: 22575 (0x0000582F)
19. FS Info Sector: 1
20. Backup Boot Sector: 6
21. Reserved: 000000000000000000000000
22. Drive ID: 0x80
23. Reserved for NT: 0x00
24. Extended Boot Sig: 41
25. Serial Number: 0xA8B2E11D
26. Volume Name:
27. File System Type: FAT32
28. Boot Signature: 0xAA55
============================================================================
Boot Sector for drive H: (Drive 1, Starting Sector 0x9E1C84, Type:
FAT32)
============================================================================
1. Jump: EB 58 90
2. OEM Name: MSWIN4.1
3. Bytes Per Sector: 512
4. Sectors Per Cluster: 8
5. Reserved Sectors: 33
6. Number of FATs: 2
7. Reserved: 0x0000
8. Reserved: 0x0000
9. Media Descriptor: 248
10. Sectors Per FAT: 0
11. Sectors Per Track: 63 (0x003F)
12. Number of Heads: 255 (0x00FF)
13. Hidden Sectors: 63 (0x0000003F)
14. Big Total Sectors: 2040192 (0x001F2180)
15. Big Sectors Per FAT: 1991
16. Extended Flags: 0x0000
17. FS Version: 0x0000
18. First Cluster of Root: 1063 (0x00000427)
19. FS Info Sector: 1
20. Backup Boot Sector: 6
21. Reserved: 000000000000000000000000
22. Drive ID: 0x80
23. Reserved for NT: 0x00
24. Extended Boot Sig: 41
25. Serial Number: 0xE0EE8344
26. Volume Name: DEMO
27. File System Type: FAT32
28. Boot Signature: 0xAA55
============================================================================
Boot Sector for drive I: (Drive 2, Starting Sector 0x3F00, Type: FAT32)
============================================================================
1. Jump: EB 3C 90
2. OEM Name: MSWIN4.1
3. Bytes Per Sector: 512
4. Sectors Per Cluster: 8
5. Reserved Sectors: 32
6. Number of FATs: 2
7. Reserved: 0x0000
8. Reserved: 0x0000
9. Media Descriptor: 248
10. Sectors Per FAT: 0
11. Sectors Per Track: 63 (0x003F)
12. Number of Heads: 255 (0x00FF)
13. Hidden Sectors: 63 (0x0000003F)
14. Big Total Sectors: 10249407 (0x009C64BF)
15. Big Sectors Per FAT: 9994
16. Extended Flags: 0x0000
17. FS Version: 0x0000
18. First Cluster of Root: 57680 (0x0000E150)
19. FS Info Sector: 1
20. Backup Boot Sector: 6
21. Reserved: F6F6F6F6F6F6F6F6F6F6F6F6
22. Drive ID: 0x80
23. Reserved for NT: 0xF6
24. Extended Boot Sig: 41
25. Serial Number: 0xA8A7B791
26. Volume Name: JEUX
27. File System Type: FAT32
28. Boot Signature: 0xAA55
============================================================================
Boot Sector for drive J: (Drive 2, Starting Sector 0x9CA3FE, Type:
FAT32)
============================================================================
1. Jump: EB 3C 90
2. OEM Name: MSWIN4.1
3. Bytes Per Sector: 512
4. Sectors Per Cluster: 8
5. Reserved Sectors: 32
6. Number of FATs: 2
7. Reserved: 0x0000
8. Reserved: 0x0000
9. Media Descriptor: 248
10. Sectors Per FAT: 0
11. Sectors Per Track: 63 (0x003F)
12. Number of Heads: 255 (0x00FF)
13. Hidden Sectors: 63 (0x0000003F)
14. Big Total Sectors: 2056257 (0x001F6041)
15. Big Sectors Per FAT: 2008
16. Extended Flags: 0x0000
17. FS Version: 0x0000
18. First Cluster of Root: 1502 (0x000005DE)
19. FS Info Sector: 1
20. Backup Boot Sector: 6
21. Reserved: F6F6F6F6F6F6F6F6F6F6F6F6
22. Drive ID: 0x80
23. Reserved for NT: 0xF6
24. Extended Boot Sig: 41
25. Serial Number: 0xE0DFA564
26. Volume Name: VIDEO
27. File System Type: FAT32
28. Boot Signature: 0xAA55
============================================================================
Boot Sector for drive K: (Drive 2, Starting Sector 0xBC047E, Type:
FAT32)
============================================================================
1. Jump: EB 58 90
2. OEM Name: MSWIN4.1
3. Bytes Per Sector: 512
4. Sectors Per Cluster: 8
5. Reserved Sectors: 33
6. Number of FATs: 2
7. Reserved: 0x0000
8. Reserved: 0x0000
9. Media Descriptor: 248
10. Sectors Per FAT: 0
11. Sectors Per Track: 63 (0x003F)
12. Number of Heads: 255 (0x00FF)
13. Hidden Sectors: 63 (0x0000003F)
14. Big Total Sectors: 2072322 (0x001F9F02)
15. Big Sectors Per FAT: 2021
16. Extended Flags: 0x0000
17. FS Version: 0x0000
18. First Cluster of Root: 179 (0x000000B3)
19. FS Info Sector: 1
20. Backup Boot Sector: 6
21. Reserved: 000000000000000000000000
22. Drive ID: 0x80
23. Reserved for NT: 0x00
24. Extended Boot Sig: 41
25. Serial Number: 0x191795BB
26. Volume Name: VIDEO2
27. File System Type: FAT32
28. Boot Signature: 0xAA55
============================================================================
Boot Sector for drive *: (Drive 2, Starting Sector 0xDBA3BF, Type: FAT)
============================================================================
1. Jump: EB 3C 90
2. OEM Name: MSWIN4.0
3. Bytes Per Sector: 512
4. Sectors Per Cluster: 32
5. Reserved Sectors: 1
6. Number of FATs: 2
7. Root Dir Entries: 512
8. Total Sectors: 0 (0x0000)
9. Media Descriptor: 248
10. Sectors Per FAT: 255
11. Sectors Per Track: 63 (0x003F)
12. Number of Heads: 255 (0x00FF)
13. Hidden Sectors: 63 (0x0000003F)
14. Big Total Sectors: 2056257 (0x001F6041)
15. Drive ID: 0x80
16. Dirty Flag: 0x00
17. Extended Boot Sig: 41 BS_FAT
18. Serial Number: 0x70824FA6
19. Volume Name: DATA
20. File System Type: FAT16
21. Boot Signature: 0xAA55
============================================================================
Boot Sector for drive *: (Drive 2, Starting Sector 0xFB0400, Type:
FAT32)
============================================================================
1. Jump: EB 58 90
2. OEM Name: MSWIN4.1
3. Bytes Per Sector: 512
4. Sectors Per Cluster: 8
5. Reserved Sectors: 32
6. Number of FATs: 2
7. Reserved: 0x0000
8. Reserved: 0x0000
9. Media Descriptor: 248
10. Sectors Per FAT: 0
11. Sectors Per Track: 63 (0x003F)
12. Number of Heads: 255 (0x00FF)
13. Hidden Sectors: 16450560 (0x00FB0400)
14. Big Total Sectors: 3100545 (0x002F4F81)
15. Big Sectors Per FAT: 3023
16. Extended Flags: 0x0000
17. FS Version: 0x0000
18. First Cluster of Root: 2032 (0x000007F0)
19. FS Info Sector: 1
20. Backup Boot Sector: 6
21. Reserved: 000000000000000000000000
22. Drive ID: 0x80
23. Reserved for NT: 0x00
24. Extended Boot Sig: 41
25. Serial Number: 0x3841275F
26. Volume Name: WIN98
27. File System Type: FAT32
28. Boot Signature: 0xAA55
============================================================================
Boot Sector for drive *: (Drive 2, Starting Sector 0x12A5381, Type:
FAT32)
============================================================================
1. Jump: EB 58 90
2. OEM Name: MSWIN4.1
3. Bytes Per Sector: 512
4. Sectors Per Cluster: 8
5. Reserved Sectors: 33
6. Number of FATs: 2
7. Reserved: 0x0000
8. Reserved: 0x0000
9. Media Descriptor: 248
10. Sectors Per FAT: 0
11. Sectors Per Track: 63 (0x003F)
12. Number of Heads: 255 (0x00FF)
13. Hidden Sectors: 19551105 (0x012A5381)
14. Big Total Sectors: 5172930 (0x004EEEC2)
15. Big Sectors Per FAT: 5045
16. Extended Flags: 0x0000
17. FS Version: 0x0000
18. First Cluster of Root: 48446 (0x0000BD3E)
19. FS Info Sector: 1
20. Backup Boot Sector: 6
21. Reserved: 000000000000000000000000
22. Drive ID: 0x80
23. Reserved for NT: 0x00
24. Extended Boot Sig: 41
25. Serial Number: 0xA8C37A61
26. Volume Name: APPL-WIN
27. File System Type: FAT32
28. Boot Signature: 0xAA55
In article <3843B488...@snet.net>,
Tom Pfeifer
clear that your BIOS supports large drives. I don't have a definitive
answer as to why you're having problems, but I'll throw out a few things
for you to consider - my apologies if this gets a little too long and
technical...
1) I notice that you have a hidden FAT16 partition as the last logical
on the third drive. This is a non-DOS partition as far as Win98 is
concerned. I don't know if this will matter in your case, but I can tell
you that I have had problems with Win9X when I had a non-DOS partition
as the last partition in the extended partition of the last drive AND
also had drives with multiple primary partitions - as you do.
2) This is more of a question: If you keep all partitions below 1024
cylinders (8GB) on the *2nd drive*, can you then use the entire 3rd
drive without problems?
3) The reason for the question in #2 has to do with a section I came
across today in the Linux mini-HOWTO on large disks:
http://metalab.unc.edu/mdw/HOWTO/mini/Large-Disk-11.html
If you read over section 11.1, it talks about how some BIOS can
mis-interpret size info that it reads from the drive. And it also
mentions the specific CHS geometry (1027/255/63) that your 2nd drive has
as a possible result of this.
If you want to check into this further, you can use the Linux utility
hdparm as root user to query the drive directly:
hdparm -I /dev/hdb (assuming that drive is primary/slave)
Optionally you can use 'hdparm -I > driveinfo.txt' to get the data into
a text file. The -I switch causes hdparm to read the info directly from
the drive itself. For example, on my 13 GB drive, here is the result of
that command:
----------------------------------------------------------------------
root@newdebian:~# hdparm -I /dev/hdc
/dev/hdc:
Model=aMtxro9 31068D, FwRev=AP2SB351, SerialNo=8V40QWAV
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=29
BuffType=3(DualPortCache), BuffSize=256kB, MaxMultSect=16, MultSect=off
DblWordIO=no, OldPIO=2, DMA=yes, OldDMA=2
CurCHS=26353/16/63, CurSects=16514064, LBA=yes, LBAsects=26563824
tDMA={min:120,rec:120}, DMA modes: mword0 mword1 mword2
IORDY=on/off, tPIO={min:120,w/IORDY:120}, PIO modes: mode3 mode4
UDMA modes: mode0 mode1 *mode2
------------------------------------------------------------------------
The key information in your case is the LBAsects value which you can
divide by 63 and then by 255 to get the number of translated cylinders
the drive should have. This should be 1027 if your BIOS is reading the
drive info correctly. If this doesn't look correct to you on that drive,
feel free to post back with the data you get
These were all just semi-educated guesses based on what I see in your
partinfo. Hopefully some of it will help you figure out your problem.
Tom
Tom Pfeifer
> hdparm -I /dev/hdb (assuming that drive is primary/slave)
>
> Optionally you can use 'hdparm -I > driveinfo.txt' to get the data into
> a text file. The -I switch causes hdparm to read the info directly from
> the drive itself. For example, on my 13 GB drive, here is the result of
> that command:
Correction: That should be 'hdparm -I /dev/hdb > driveinfo.txt' to get
the data into a text file.
By the way, I have a feeling that there's something simple that both you
and I are overlooking here with this problem. I don't see it, but maybe
someone else will....
Tom
etien...@my-deja.com
I have made a lot of test before. I tried :
- without disk2
- without any hidden partitions
- without multiple primary partitions
With a simple disk 0 (c: primary, d: in extended), disk 1 with 1 largest
possible extended partition (>8Gb) and 2 logical, only the first logical
(e:) gives problem during win98 boot.
So I am sure it has nothing to do with non-DOS partition or other
primary partition, and no if I keep my 2nd drive below 8Gb I still can't
used my entire 3rd drive with win98.
I will try the hdparm utility as soon as I have time to acces my home
computer.
Thanks anyway,
Etienne
In article <38446D09...@snet.net>,
> hdparm -I /dev/hdb (assuming that drive is primary/slave)
>
> Optionally you can use 'hdparm -I > driveinfo.txt' to get the data
into
> a text file. The -I switch causes hdparm to read the info directly
from
> the drive itself. For example, on my 13 GB drive, here is the result
of
> > Thanks for your help.
> >
> > So here is the result of the partinfo.exe. Disk 2 is working now
> > because I am only using partition under 8Gb with Win98, but for the
> > test, I have extented my extented partition on Disk 1 to the maximum
> > (just above the 8Gb).
> >
> > Win98 stops booting with message "File allocation table bad, drive
E",
> > which is the FIRST partition on the disk 1. With other
configurations I
> > was able to boot but Win98 was trying to chkdsk the first partition
and
> > after exiting the test it did boot but with no access to the E: (but
> > access to all following drives).
> >
> > After reducing the extended partition I am able to boot Win98 again.
> >
> > I appreciate your help
> >
> > Etienne.
> >
>
etien...@my-deja.com
/dev/hdb:
Model=DW CCA8304L0 , FwRev=910.W302,
SerialNo=DWW-5T72
Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs
FmtGapReq }
RawCHS=16383/16/63, TrkSize=57600, SectSize=600, ECCbytes=22
BuffType=3(DualPortCache), BuffSize=256kB, MaxMultSect=16, MultSect=off
DblWordIO=no, maxPIO=2(fast), DMA=yes, maxDMA=0(slow)
CurCHS=16383/16/63, CurSects=-66060037, LBA=yes, LBAsects=16514064
tDMA={min:120,rec:120}, DMA modes: mword0 mword1 mword2
IORDY=on/off, tPIO={min:160,w/IORDY:120}, PIO modes: mode3 mode4
So LBAsects 16514064 / 63 / 255 = 1027.9529 cylinders
I guess this is correct.
Any other idea ?
Etienne.
In article <822n9b$v6s$1...@nnrp1.deja.com>,
> > the drive itself. For example, on my 13 GB drive, here is the result
> of
> > > Thanks for your help.
> > >
> > > So here is the result of the partinfo.exe. Disk 2 is working now
> > > because I am only using partition under 8Gb with Win98, but for
the
> > > test, I have extented my extented partition on Disk 1 to the
maximum
> > > (just above the 8Gb).
> > >
> > > Win98 stops booting with message "File allocation table bad, drive
> E",
> > > which is the FIRST partition on the disk 1. With other
> configurations I
> > > was able to boot but Win98 was trying to chkdsk the first
partition
> and
> > > after exiting the test it did boot but with no access to the E:
(but
> > > access to all following drives).
> > >
> > > After reducing the extended partition I am able to boot Win98
again.
> > >
> > > I appreciate your help
> > >
> > > Etienne.
> > >
> >
>
Jordan Russell
partition is inaccessible when the extended partition is > 8 gig! I was
thinking there was something really strange with my configuration,
considering I'd never heard anyone with the same problem until now.
Windows 98 in "Windows mode" sees the partition fine, as does Windows
NT 4.0 and Linux. Windows 98 in *DOS mode* is when the problem occurs.
So I *think* it's fair to call this a bug in Windows 95/98's DOS mode
drivers. But then again, Windows 98's DOS mode is the only OS that goes
through the BIOS to access the disk, so maybe it is a BIOS flaw. (But I
am able to reproduce this on AMI BIOS and Award BIOS.)
But how to work around it is the question. Anyone have more ideas? It's
very important to me, as I'm sure it is others. Has MS confirmed this
problem and posted a fix? I browsed the replies to this thread, and
don't see any real solutions. :-(
Jordan Russell
In article <8204fp$2rp$1...@nnrp1.deja.com>,
etien...@my-deja.com wrote:
> The size of my first disk is 3Gb, it contains a primary partition with
> Windows98. I added two disks (WD and IBM) greater than 8Gb and I am
> having a lot of problem accessing partitions above the 8Gb with Win98.
>
> What I am sure of :
> - I have the latest BIOS for my motherboard (FIC VA-503+) and I have
> checked (with different utilities) the int13h extension.
> - FDISK under Win98 can see the correct disks size
> - I use Partition Magic (4.01) under win98 without any problem, it can
> access all partitions.
> - I have a ext2fs primary partition completely above 8Gb which can be
> used without any problems by Linux (I suppose this means my bios is
ok)
>
> If I try to create (with fdisk or PM) an extended partition greater
than
> 8Gb, the FIRST logical partition inside (which is below the 8Gb limit)
> can't be used correctly by Win98, it works correctly as soon as I
reduce
> the extended partion below 8Gb.
>
> Linux can see all partitions anywhere and any size.
>
> Where is the error (apart using win98).
>
> Can someone help ?
>
Jordan Russell
interested in debugging it. :-)
This is originally from an e-mail I sent to PartitionMagic tech
support, because at first I thought it was a PartitionMagic bug.
1) Start with an empty, unpartitioned 2nd drive that is greater than
8GB in size (mine is 17GB). The 1st drive already has 3 partitions: C,
D, E.
2) With PartitionMagic 5, create an Extended partition on the 2nd drive
with a size of 7000MB. Inside the Extended partition, create a 1019MB
FAT partition, followed by a FAT32 partition filling the rest of the
free space inside the Extended partition. Reboot.
3) At "Starting Windows 98", press F8, and select Command Prompt Only.
Verify that drive F and G (the two partitions just created) are fully
accessible by issuing FORMAT F: and FORMAT G: at the prompt. No errors
are reported by FORMAT.
4) Go back into PartitionMagic 5, and resize the Extended partition to
be 9000MB or more. Apply the change, and notice that the partition type
is now 0F ExtendedX instead of 05 Extended. Reboot.
5) At "Starting Windows 98", press F8, and select Command Prompt Only.
Try FORMAT F: and this time it fails with "File allocation table bad"
(or possibly another obscure error).
Jordan Russell
In article <82ce7k$ng6$1...@nnrp1.deja.com>,
Tom Pfeifer
problem extended partitions start at the *beginning* of the drive,
instead of the more typical placement of extended partitions - which is
*not* at the beginning of a drive.
If you notice, when you create an extended partition at the beginning of
a drive, all partitioning programs that I have seen start the partition
at cyl 1, head 0, sect 1, which is 16,065 sectors from the beginning of
the drive - assuming a X/255/63 translated geometry.
In contrast, when you create a primary partition at the beginning of a
drive, the partition always starts at cyl 0, head 1, sect 1, which is 63
sectors from the beginning of the drive.
I could easily be wrong of course, but I have a hunch that if a primary
is inserted before the extended, the problems would disappear.
I have an 11 GB extended on my master drive and have no problems. The
extended has a primary of 500 MB in front of it and extends well past
1024 cylinders. However, this may not be a valid proof of my theory
because the first several logical partitions inside the extended are not
DOS partitions - they are Linux so the problem may not show up in that
case anyway.
Tom
Jordan Russell
partition, but the very same problem still occurs -- first drive in
extended can't be accessed.
As for your configuration, you have the 11GB drive as your first drive.
I have found that this problem only seems to occur if a <8GB drive is
the first drive and a >8GB drive is the second drive. (Master/slave
make no difference -- I tried moving my second drive to a different IDE
channel and still the same problem.)
I have now swapped my two drives and no longer have problems. But this
is NOT what I want to do, because I want my smaller drive to hold the
OS and be the first drive, and the big drive to hold all my data. So
I'm still looking for any solutions I can find. :-)
Jordan Russell
In article <384A49C6...@snet.net>,
etien...@my-deja.com
Thanks Jordan for giving me a solution, I will now try to put my big
disk as first disk. (just swapping master/slave on first IDE I suppose)
If this works, it would mean that you cannot access correctly a disk
>8Gb if you have a first disk <8Gb, WINDOWS 98 BUG I suppose ?
Can anyone else confirms this ?
Etienne
In article <82et84$a18$1...@nnrp1.deja.com>,
Jordan Russell <jor...@my-deja.com> wrote:
> I have tried creating a primary partition before the extended
> partition, but the very same problem still occurs -- first drive in
> extended can't be accessed.
>
> As for your configuration, you have the 11GB drive as your first
drive.
> I have found that this problem only seems to occur if a <8GB drive is
> the first drive and a >8GB drive is the second drive. (Master/slave
> make no difference -- I tried moving my second drive to a different
IDE
> channel and still the same problem.)
>
> I have now swapped my two drives and no longer have problems. But this
> is NOT what I want to do, because I want my smaller drive to hold the
> OS and be the first drive, and the big drive to hold all my data. So
> I'm still looking for any solutions I can find. :-)
>
> Jordan Russell
>
>
etien...@my-deja.com
results :
disk 0 : 3 Gb
disk 1 : 8.5 Gb : error with extended partition >8Gb
disk 2 : 15 Gb : error with extended partition >8Gb
disk 0 : 8.5 Gb : all OK
disk 1 : 3 Gb
disk 2 : 15 Gb : error with extended partition >8Gb
disk 0 : 8.5 Gb : all OK
disk 1 : 15 Gb : all OK
disk 2 : 3 Gb
So FOR WINDOWS 98, if you use a mix of disk <8Gb and >8Gb you have to
put the smaller disk(s) last, that's the only way I could get them
working correctly.
I consider this a WINDOWS 98 BUG !
I don't have such problems if I boot Linux.
Etienne
In article <82g0mq$1q0$1...@nnrp1.deja.com>,
etien...@my-deja.com wrote:
> So I am not the only one to have this problem !
>
> Thanks Jordan for giving me a solution, I will now try to put my big
> disk as first disk. (just swapping master/slave on first IDE I
suppose)
>
> If this works, it would mean that you cannot access correctly a disk
> >8Gb if you have a first disk <8Gb, WINDOWS 98 BUG I suppose ?
>
> Can anyone else confirms this ?
>
> Etienne
>
> In article <82et84$a18$1...@nnrp1.deja.com>,
> Jordan Russell <jor...@my-deja.com> wrote:
> > I have tried creating a primary partition before the extended
> > partition, but the very same problem still occurs -- first drive in
> > extended can't be accessed.
> >
> > As for your configuration, you have the 11GB drive as your first
> drive.
> > I have found that this problem only seems to occur if a <8GB drive
is
> > the first drive and a >8GB drive is the second drive. (Master/slave
> > make no difference -- I tried moving my second drive to a different
> IDE
> > channel and still the same problem.)
> >
> > I have now swapped my two drives and no longer have problems. But
this
> > is NOT what I want to do, because I want my smaller drive to hold
the
> > OS and be the first drive, and the big drive to hold all my data. So
> > I'm still looking for any solutions I can find. :-)
> >
> > Jordan Russell
> >
> >
>
Jordan Russell
ago, and they don't even confirm the bug's existance, much less provide
a fix... :-(
Jordan Russell
In article <82ij7g$tki$1...@nnrp1.deja.com>,
> > In article <82et84$a18$1...@nnrp1.deja.com>,
> > Jordan Russell <jor...@my-deja.com> wrote:
> > > I have tried creating a primary partition before the extended
> > > partition, but the very same problem still occurs -- first drive
in
> > > extended can't be accessed.
> > >
> > > As for your configuration, you have the 11GB drive as your first
> > drive.
> > > I have found that this problem only seems to occur if a <8GB drive
> is
> > > the first drive and a >8GB drive is the second drive.
(Master/slave
> > > make no difference -- I tried moving my second drive to a
different
> > IDE
> > > channel and still the same problem.)
> > >
> > > I have now swapped my two drives and no longer have problems. But
> this
> > > is NOT what I want to do, because I want my smaller drive to hold
> the
> > > OS and be the first drive, and the big drive to hold all my data.
So
> > > I'm still looking for any solutions I can find. :-)
> > >
> > > Jordan Russell
Walter Clayton
--
Walter Clayton
Microsoft MVP (DTS)
Any technology distinguishable from magic is insufficiently advanced.
http://members.home.com/mvp-l
etien...@my-deja.com wrote in message <82ij7g$tki$1...@nnrp1.deja.com>...
>> In article <82et84$a18$1...@nnrp1.deja.com>,
>> Jordan Russell <jor...@my-deja.com> wrote:
>> > I have tried creating a primary partition before the extended
>> > partition, but the very same problem still occurs -- first drive in
>> > extended can't be accessed.
>> >
>> > As for your configuration, you have the 11GB drive as your first
>> drive.
>> > I have found that this problem only seems to occur if a <8GB drive
>is
>> > the first drive and a >8GB drive is the second drive. (Master/slave
>> > make no difference -- I tried moving my second drive to a different
>> IDE
>> > channel and still the same problem.)
>> >
>> > I have now swapped my two drives and no longer have problems. But
>this
>> > is NOT what I want to do, because I want my smaller drive to hold
>the
>> > OS and be the first drive, and the big drive to hold all my data. So
>> > I'm still looking for any solutions I can find. :-)
>> >
>> > Jordan Russell
>> >
>> >
>>
Walter Clayton
module size
--
Walter Clayton - [DTS MVP]
Any technology distinguishable from magic is insufficiently advanced.
"Jordan Russell" <jor...@my-deja.com> wrote in message
news:82j82h$bt2$1...@nnrp1.deja.com...
> I agree. But I just searched the Windows 98 Knowledge Base a few days
> ago, and they don't even confirm the bug's existance, much less provide
> a fix... :-(
>
> Jordan Russell
>
> In article <82ij7g$tki$1...@nnrp1.deja.com>,
> > > In article <82et84$a18$1...@nnrp1.deja.com>,
> > > Jordan Russell <jor...@my-deja.com> wrote:
> > > > I have tried creating a primary partition before the extended
> > > > partition, but the very same problem still occurs -- first drive
> in
> > > > extended can't be accessed.
> > > >
> > > > As for your configuration, you have the 11GB drive as your first
> > > drive.
> > > > I have found that this problem only seems to occur if a <8GB drive
> > is
> > > > the first drive and a >8GB drive is the second drive.
> (Master/slave
> > > > make no difference -- I tried moving my second drive to a
> different
> > > IDE
> > > > channel and still the same problem.)
> > > >
> > > > I have now swapped my two drives and no longer have problems. But
> > this
> > > > is NOT what I want to do, because I want my smaller drive to hold
> > the
> > > > OS and be the first drive, and the big drive to hold all my data.
> So
> > > > I'm still looking for any solutions I can find. :-)
> > > >
> > > > Jordan Russell
>
>
Jordan Russell
referring to DOS mode. Therefore, esdi_506.pdr wouldn't have any
effect, since this problem happens even if you boot from a Windows 98
Startup disk, which doesn't even have that file. I think the bug must
be in IO.SYS since it holds the FAT file system drivers (and just
everything else) for DOS mode.
Jordan Russell
In article <OIC#YNQQ$GA.273@cppssbbsa05>,
"Walter Clayton" <w-cla...@SPmailandnewsAM.com> wrote:
> Do a find on your system esdi_506.pdr and post back the version, date
and
> module size
>
> --
> Walter Clayton - [DTS MVP]
> Any technology distinguishable from magic is insufficiently advanced.
>
> "Jordan Russell" <jor...@my-deja.com> wrote in message
> news:82j82h$bt2$1...@nnrp1.deja.com...
> > I agree. But I just searched the Windows 98 Knowledge Base a few
days
> > ago, and they don't even confirm the bug's existance, much less
provide
> > a fix... :-(
> >
> > Jordan Russell
> >
> > > > In article <82et84$a18$1...@nnrp1.deja.com>,
etien...@my-deja.com
but the file :
c:\windows\system\iosubsys has a size of 23,8Kb (24.406 bytes)
and a modification date of 11/05/98 20:01.
For me, the problem occurs with Win98 in DOS mode and in normal mode.
It is not realy the order of the disk in size which cause the problem,
but the order of the extended partition (one on each disk of course), if
I have an extended partition <8Gb coming before an extended partition
>8Gb the first logical in the 2nd extended cannot be read.
Etienne
In article <ONsGU5LQ$GA....@cppssbbsa02.microsoft.com>,
"Walter Clayton" <w-cla...@SPmailandnewsAM.com> wrote:
> Do a find for esdi_506.pdr and post back the version, date and module
size.
>
> --
> Walter Clayton
> Microsoft MVP (DTS)
> Any technology distinguishable from magic is insufficiently advanced.
> http://members.home.com/mvp-l
>
> etien...@my-deja.com wrote in message
<82ij7g$tki$1...@nnrp1.deja.com>...
> >> In article <82et84$a18$1...@nnrp1.deja.com>,
> >> Jordan Russell <jor...@my-deja.com> wrote:
> >> > I have tried creating a primary partition before the extended
> >> > partition, but the very same problem still occurs -- first drive
in
> >> > extended can't be accessed.
> >> >
> >> > As for your configuration, you have the 11GB drive as your first
> >> drive.
> >> > I have found that this problem only seems to occur if a <8GB
drive
> >is
> >> > the first drive and a >8GB drive is the second drive.
(Master/slave
> >> > make no difference -- I tried moving my second drive to a
different
> >> IDE
> >> > channel and still the same problem.)
> >> >
> >> > I have now swapped my two drives and no longer have problems. But
> >this
> >> > is NOT what I want to do, because I want my smaller drive to hold
> >the
> >> > OS and be the first drive, and the big drive to hold all my data.
So
> >> > I'm still looking for any solutions I can find. :-)
> >> >
> >> > Jordan Russell
> >> >
> >> >
> >>
Walter Clayton
You'll get the size and date on the first page. Click the version tab to get
the version.
--
Walter Clayton
Microsoft MVP (DTS)
Any technology distinguishable from magic is insufficiently advanced.
http://members.home.com/mvp-l
etien...@my-deja.com wrote in message <82m9of$jlq$1...@nnrp1.deja.com>...
>> >> In article <82et84$a18$1...@nnrp1.deja.com>,
>> >> Jordan Russell <jor...@my-deja.com> wrote:
>> >> > I have tried creating a primary partition before the extended
>> >> > partition, but the very same problem still occurs -- first drive
>in
>> >> > extended can't be accessed.
>> >> >
>> >> > As for your configuration, you have the 11GB drive as your first
>> >> drive.
>> >> > I have found that this problem only seems to occur if a <8GB
>drive
>> >is
>> >> > the first drive and a >8GB drive is the second drive.
>(Master/slave
>> >> > make no difference -- I tried moving my second drive to a
>different
>> >> IDE
>> >> > channel and still the same problem.)
>> >> >
>> >> > I have now swapped my two drives and no longer have problems. But
>> >this
>> >> > is NOT what I want to do, because I want my smaller drive to hold
>> >the
>> >> > OS and be the first drive, and the big drive to hold all my data.
>So
>> >> > I'm still looking for any solutions I can find. :-)
>> >> >
>> >> > Jordan Russell
>> >> >
>> >> >
>> >>
Walter Clayton
drive before too much longer.
Did you use fdisk or a 3rd party app to set the drives up?
>> >> In article <82et84$a18$1...@nnrp1.deja.com>,
>> >> Jordan Russell <jor...@my-deja.com> wrote:
>> >> > I have tried creating a primary partition before the extended
>> >> > partition, but the very same problem still occurs -- first drive
>in
>> >> > extended can't be accessed.
>> >> >
>> >> > As for your configuration, you have the 11GB drive as your first
>> >> drive.
>> >> > I have found that this problem only seems to occur if a <8GB
>drive
>> >is
>> >> > the first drive and a >8GB drive is the second drive.
>(Master/slave
>> >> > make no difference -- I tried moving my second drive to a
>different
>> >> IDE
>> >> > channel and still the same problem.)
>> >> >
>> >> > I have now swapped my two drives and no longer have problems. But
>> >this
>> >> > is NOT what I want to do, because I want my smaller drive to hold
>> >the
>> >> > OS and be the first drive, and the big drive to hold all my data.
>So
>> >> > I'm still looking for any solutions I can find. :-)
>> >> >
>> >> > Jordan Russell
>> >> >
>> >> >
>> >>
Walter Clayton
fdisk to initially create the large logical on HD1? I suspect it doesn't
matter but I am curious.
--
Walter Clayton
Microsoft MVP (DTS)
Any technology distinguishable from magic is insufficiently advanced.
http://members.home.com/mvp-l
Jordan Russell wrote in message <82m3mk$ep8$1...@nnrp1.deja.com>...
>Thanks for your reply, but when we mention "Windows 98" we are
>referring to DOS mode. Therefore, esdi_506.pdr wouldn't have any
>effect, since this problem happens even if you boot from a Windows 98
>Startup disk, which doesn't even have that file. I think the bug must
>be in IO.SYS since it holds the FAT file system drivers (and just
>everything else) for DOS mode.
>
>Jordan Russell
>
>In article <OIC#YNQQ$GA.273@cppssbbsa05>,
> "Walter Clayton" <w-cla...@SPmailandnewsAM.com> wrote:
>> Do a find on your system esdi_506.pdr and post back the version, date
>and
>> module size
>>
>> --
>> Walter Clayton - [DTS MVP]
>> Any technology distinguishable from magic is insufficiently advanced.
>>
>> "Jordan Russell" <jor...@my-deja.com> wrote in message
>> news:82j82h$bt2$1...@nnrp1.deja.com...
>> > I agree. But I just searched the Windows 98 Knowledge Base a few
>days
>> > ago, and they don't even confirm the bug's existance, much less
>provide
>> > a fix... :-(
>> >
>> > Jordan Russell
>> >
>> > In article <82ij7g$tki$1...@nnrp1.deja.com>,
>> > > > In article <82et84$a18$1...@nnrp1.deja.com>,
Bill Drake
the "Int 13h Extensions" which are *required* for correct operation
of W9x with drives larger than 8GB.
Please note, the primary boot partition cannot *safely* be greater
than 8GB unless the Int13h Extensions are present in the
motherboard BIOS.
Furthermore, it is impossible to access partitions beyond the 8GB
mark in DOS -- unless the Int13h Extensions are present in the
motherboard BIOS -- because there are no protected-mode
drivers loaded while in DOS.
That's why the above problem needs a BIOS update -- which
loads even before DOS itself.
The normal solution for this problem is as follows:
1. Update the motherboard flashBIOS to a more-recent version
which has full support for the Int13h Extensions in the BIOS.
Note: This will commonly be noted in the release notes for
the motherboard BIOS version as "Large Disk Support".
This is *not* the same thing as standard LBA -- it is
an *extension* to LBA which breaks the 8GB barrier.
2. If a motherboard flashBIOS update is not available which
adds Int13h-Extension-support to your existing system, then
it is possible to use the disk-translation-software available
from your Hard Disk manufacturer.
Note: Earlier versions of this software are not capable of
working with hard disks larger than 8GB.
You must use the latest version of this software for
compatibility with W98SE and hard disks larger than
8GB.
The latest version of the software is usually freely
available for download from the Hard Disk
manufacturer's website.
Caveats: The use of a Hard-Disk-Drive-overlay (which is the
technical term for this kind of software) is not
considered to be the most desirable solution to the
problem. If anything corrupts the customized copy
of the master-boot-record produced by the DDO
software (such as a virus) -- all your data is gone
unless you have made the proper emergency boot
floppy for the particular version of the DDO software
used to provide access to your Hard Disk.
3. In the absence of a suitable flashBIOS update -- along with
the desire to avoid the use of DDO software -- then the
proper solution to the problem is a motherboard upgrade
which provides full Int13h-Extension support in the new
motherboard's flashBIOS.
Note: Once the Int13h-Extension support is installed, it
is necessary to remove the existing disk drive
partitions and re-FDISK with Int13h support in
place. This is the only way to rewrite the
partition-table data such that large partitions
can be supported reliably in DOS.
Also, it is necessary to use a DOS version
which is "Int13h-Extension-smart" if the user
wishes to access large partitions while in DOS.
This means the use of DOS 7.1 (shipped with
W95b and later) at the *very minimum*.
All previous versions of DOS will not work with
partitions greater than 8GB in size -- and there
is no workaround for this problem as far as I
am aware.
Best I can do for now. <tm>
Bill
etien...@my-deja.com
modif date 11/05/98 20:01
Version 4.0
Product Version 4.10.1998
In article <#xC7S1bQ$GA.255@cppssbbsa05>,
"Walter Clayton" <w-cla...@SPmailandnewsAM.com> wrote:
> Once you've found the file, highlight it, right click and select
properties.
> You'll get the size and date on the first page. Click the version tab
to get
> the version.
>
> --
> Walter Clayton
> Microsoft MVP (DTS)
> Any technology distinguishable from magic is insufficiently advanced.
> http://members.home.com/mvp-l
>
> etien...@my-deja.com wrote in message
<82m9of$jlq$1...@nnrp1.deja.com>...
> >Please tell me how to get the version number of esdi_506.pdf.
> >but the file :
> >c:\windows\system\iosubsys has a size of 23,8Kb (24.406 bytes)
> >and a modification date of 11/05/98 20:01.
> >
> >For me, the problem occurs with Win98 in DOS mode and in normal mode.
> >
> >It is not realy the order of the disk in size which cause the
problem,
> >but the order of the extended partition (one on each disk of course),
if
> >I have an extended partition <8Gb coming before an extended partition
> >>8Gb the first logical in the 2nd extended cannot be read.
> >
> >Etienne
> >
> >
> >In article <ONsGU5LQ$GA....@cppssbbsa02.microsoft.com>,
> > "Walter Clayton" <w-cla...@SPmailandnewsAM.com> wrote:
> >> Do a find for esdi_506.pdr and post back the version, date and
module
> >size.
> >>
> >> --
> >> Walter Clayton
> >> Microsoft MVP (DTS)
> >> Any technology distinguishable from magic is insufficiently
advanced.
> >> http://members.home.com/mvp-l
> >>
> >> etien...@my-deja.com wrote in message
> ><82ij7g$tki$1...@nnrp1.deja.com>...
> >> >I have tried different configurations with my 3 disks. These are
the
> >> >results :
> >> >
> >> >disk 0 : 3 Gb
> >> >disk 1 : 8.5 Gb : error with extended partition >8Gb
> >> >disk 2 : 15 Gb : error with extended partition >8Gb
> >> >
> >> >disk 0 : 8.5 Gb : all OK
> >> >disk 1 : 3 Gb
> >> >disk 2 : 15 Gb : error with extended partition >8Gb
> >> >
> >> >disk 0 : 8.5 Gb : all OK
> >> >disk 1 : 15 Gb : all OK
> >> >disk 2 : 3 Gb
> >> >
> >> >So FOR WINDOWS 98, if you use a mix of disk <8Gb and >8Gb you have
to
> >> >put the smaller disk(s) last, that's the only way I could get them
> >> >working correctly.
> >> >
> >> >I consider this a WINDOWS 98 BUG !
> >> >I don't have such problems if I boot Linux.
> >> >
> >> >Etienne
> >> >
> >> >In article <82g0mq$1q0$1...@nnrp1.deja.com>,
> >> > etien...@my-deja.com wrote:
> >> >> So I am not the only one to have this problem !
> >> >>
> >> >> Thanks Jordan for giving me a solution, I will now try to put my
> >big
> >> >> disk as first disk. (just swapping master/slave on first IDE I
> >> >suppose)
> >> >>
> >> >> If this works, it would mean that you cannot access correctly a
> >disk
> >> >> >8Gb if you have a first disk <8Gb, WINDOWS 98 BUG I suppose ?
> >> >>
> >> >> Can anyone else confirms this ?
> >> >>
> >> >> Etienne
> >> >>
> >> >> In article <82et84$a18$1...@nnrp1.deja.com>,
TIM
motherboard. had to upgrade the bios just last month ...there were some
known issues that were addressed also were the drivers installed that came
with the motherboard...you'll need them....I had several problems till I
installed them. my motherboard came with a CD full of goodies and an
advantage card membership....looks like a credit card...but it ain't ...it
just has the registration number on it for your motherboard..try out FIC's
web site use your card ...ie register and download that new bios
patch...drivers also available....WWW.FIC.COM
Bill Drake <bdr...@direct.ca> wrote in message
news:ej99HwdQ$GA....@cppssbbsa02.microsoft.com...
Philip Sauer
Search the Knowledge Base for Article ID: Q175629
I have the same Problems mentioned in this article and no solution...
I tried to use the Esdi_506.pdr from Windows98 SE which i got mailed
from a friend.
This doesn't fix the bug :-(
Phil Sauer
Jordan Russell schrieb:
>
> I agree. But I just searched the Windows 98 Knowledge Base a few days
> ago, and they don't even confirm the bug's existance, much less provide
> a fix... :-(
>
> Jordan Russell
>
> In article <82ij7g$tki$1...@nnrp1.deja.com>,
> etien...@my-deja.com wrote:
> > I have tried different configurations with my 3 disks. These are the
> > results :
> >
> > disk 0 : 3 Gb
> > disk 1 : 8.5 Gb : error with extended partition >8Gb
> > disk 2 : 15 Gb : error with extended partition >8Gb
> >
> > disk 0 : 8.5 Gb : all OK
> > disk 1 : 3 Gb
> > disk 2 : 15 Gb : error with extended partition >8Gb
> >
> > disk 0 : 8.5 Gb : all OK
> > disk 1 : 15 Gb : all OK
> > disk 2 : 3 Gb
> >
> > So FOR WINDOWS 98, if you use a mix of disk <8Gb and >8Gb you have to
> > put the smaller disk(s) last, that's the only way I could get them
> > working correctly.
> >
> > I consider this a WINDOWS 98 BUG !
> > I don't have such problems if I boot Linux.
> >
> > Etienne
> >
> > In article <82g0mq$1q0$1...@nnrp1.deja.com>,
> > etien...@my-deja.com wrote:
> > > So I am not the only one to have this problem !
> > >
> > > Thanks Jordan for giving me a solution, I will now try to put my big
> > > disk as first disk. (just swapping master/slave on first IDE I
> > suppose)
> > >
> > > If this works, it would mean that you cannot access correctly a disk
> > > >8Gb if you have a first disk <8Gb, WINDOWS 98 BUG I suppose ?
> > >
> > > Can anyone else confirms this ?
> > >
> > > Etienne
> > >
> > > In article <82et84$a18$1...@nnrp1.deja.com>,
> > > Jordan Russell <jor...@my-deja.com> wrote:
> > > > I have tried creating a primary partition before the extended
> > > > partition, but the very same problem still occurs -- first drive
> in
> > > > extended can't be accessed.
> > > >
> > > > As for your configuration, you have the 11GB drive as your first
> > > drive.
> > > > I have found that this problem only seems to occur if a <8GB drive
> > is
> > > > the first drive and a >8GB drive is the second drive.
> (Master/slave
> > > > make no difference -- I tried moving my second drive to a
> different
> > > IDE
> > > > channel and still the same problem.)
> > > >
> > > > I have now swapped my two drives and no longer have problems. But
> > this
> > > > is NOT what I want to do, because I want my smaller drive to hold
> > the
> > > > OS and be the first drive, and the big drive to hold all my data.
> So
> > > > I'm still looking for any solutions I can find. :-)
> > > >
> > > > Jordan Russell
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
--
****************************************************************
MULTIMEDIA WEBDESIGN http://www.stod-multimedia.de
Alles ueber State Of Departmentz und Rap/Hip Hop aus Deutschland
State Of Departmentz-Homiepage http://www.stod.de
updated am: 17.04.1999
Zweimal mit dem WEB.DE COOLSPOT ausgezeichnet!
****************************************************************