Changeset 32 for trunk/BUILD.NFO


Ignore:
Timestamp:
Jan 13, 2013, 8:46:36 AM (13 years ago)
Author:
Ben Rietbroek
Message:

Fixed Win7 boot from FAT32 and HPFS zero-drive ussue [2011-11-20]

Fixes

o Fixed booting Windows 7 from FAT32

Booting Windows (NT/2K/XP/Vista/7) from FAT32 when the actual system
resides on an NTFS partition actually chainload the Windows
boot-loader in the FAT32 partition.
A bug in the handling of such a FAT32 partition with the Windows
boot-loader caused it not to find NTLDR is some cases.

o Fixed HPFS zero-drive issue

The BPB contains a field that indicates the boot-drive to the
OS2BOOT and OS2LDR programs. When creating an HPFS partition and
then restoring a system from archive (i.e. a zip-file) of course
does not set this field, since only files are restored.
This causes the boot process to halt with "...cannot operate..."
or even boot another HPFS partition. This field is now derived from
the LVM drive-letter if it contains an incorrect value.

o Corrected CRC calculations on AiR-BOOT configuration

V1.07 expanded the number of partitions from 30 to 45.
However, this was not done correctly and the configuration CRC was
still caclulated over 5 sectors. Initial v1.0.8 code corrected this
but this results in the v1.07 installer and setaboot programs
breaking on v1.0.8 code. So, for the time being the CRC caclucation
is reverted back to 5 sectors for the sake of v1.07 compatibility.
Save and restore of the configuration use 7 sectors of course.

o Corrected contact information

V1.07 shipped with the wrong contact information, causing issues
to be reported on sourceforge instead of netlabs.

Changes

o Renamed original README.TXT to README.MKW
o Added 1README.TXT
o Added COPYING (GNU License)

Note

This commit and all following commits upto and including the RC3
commit [2012-09-09] are delayed commits from a local repository.
Also, the RC (Release Candidate) naming of the corresponding commits
is a bit misleading. One would label a revision with RC when near to
a final release. Since many things have changed between RC1,RC2 & RC3,
these RC's should be interpreted as mile-stones.

WARNING!!

All commits upto and including the commit of [2012-05-13] contain
a severe bug!! Building from these sources and then disabling
the 'force LBA' feature while also using the drive-letter feature or
editing the label can destroy the MBR on all attached disks!!
DO NOT DISABLE 'FORCE LBA USAGE' WHEN BUILT FROM THE ABOVE COMMITS!!

File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/BUILD.NFO

    r30 r32  
    1 =====================================================
    2  BUILD.NFO -- Information on building AiR-BOOT v1.07
    3 =====================================================
     1======================================================
     2 BUILD.NFO -- Information on building AiR-BOOT v1.0.8
     3======================================================
    44
    5 Building AiR-BOOT v1.07 requires the following tools:
     5Building AiR-BOOT v1.0.8 requires the following tools:
    66- Borland Turbo Assembler v4.1 for DOS
    77  (TASM.EXE 136.018 bytes)
    … …  
    1313  (Used to build the installer and setaboot etc.)
    1414
    15 Putting these executables in ?:\OS2\MDOS will enable them to be found
    16 when running the build scripts.
     15Put these DOS executables (not Open Watcom) in a directory
     16and append that directory to the PATH as defined in ?:\AUTOEXEC.BAT.
     17This will enable DOS sessions to find them when called
     18by the Rexx build scripts from an OS2 CMD session.
    1719
    1820Note that only the loader, installer and setaboot targets are built.
Note: See TracChangeset for help on using the changeset viewer.