home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 29 Fixes_o
/
29-Fixes_o.zip
/
fdisk.zip
/
readme.txt
< prev
Wrap
Text File
|
2000-10-18
|
3KB
|
53 lines
10/18/00
This is a fix for FP XR_M010 or later (this fix is scheduled to go into
FP XR_M015) FDISK.
From XR_M010 up, code was incorrectly introduced into FDISK (both FDISKPM
and FDISK) that would identify FAT32 partitions. There were many fixes
included in the code between XR_M010 and XR_M014, but the real problem was
when an existing FAT32 partition, that was previously not identified and not
given a drive letter, was now identified and assigned a drive letter. This
information is stored in the Boot Manager partition and used during the boot
sequence to assign drive letters.
If that drive happened to be before the Installed OS/2 partition, it would
prohibit your machine from booting. Boot Mananager still could pass control to
OS2LDR, which did load the OS2KRNL, but from there, since the drive letter
booted was not what was in the CONFIG.SYS and INI files, the kernel couldn't
complete boot and the error displayed was usually that OS/2 couldn't operate
the system or drive.
The problem became more apparent to users after brought in Removeable Bootable
Media support was added. This change would write the boot record whenever
you used FDISK.
There were only two ways to get around this problem. One was to use the
initial Install Diskettes, and run FDISK from there to remove and re-install
Boot Manager, or do a lot of work changing OS/2 from being on one drive to
another drive letter. Some might have been able to use an added partition
before the intended install partition, install, install XR_M014, then remove
the added partition, and save using the XR_M014 FDISK, which then would
recognize the C: FAT32 and give it a letter replacing the deleted partition.
This accomplished the same thing, and along with 3rd party device drivers
that were FAT32 aware, allow you to access those drives as well, and FDISK
kept in sync with this setup.
Included in this ZIP file are replacement FDISK's that will NOT recognized
FAT32 drives and assign them drive letters.
File included Disk location
FDISK.COM \OS2
FDISKPM.EXE \OS2
FDISKPM.DLL \OS2\DLL
Before copying over these files, it is suggested you backup/rename the
existing files.
If you are happy with the present FDISK and how it assigns drive letters,
DO NOT APPLY THIS FIX. This is a backout to the same capability that was in
GA WARP 4 for identifing partitions. Some of you may have a working system
using the XR_M010-14 FDISK and 3rd party drivers, and this fix will break
your system.