| 1 | ===============================================================================
|
|---|
| 2 | AiR-BOOT v1.1.2-RELEASE [2017-04-13]
|
|---|
| 3 | ===============================================================================
|
|---|
| 4 |
|
|---|
| 5 | This is the version distributed with the release of ArcaOS v5.0.
|
|---|
| 6 | Besides the focus-shift from eComStation to ArcaOS, substantial parts have
|
|---|
| 7 | been reimplemented and other features added.
|
|---|
| 8 |
|
|---|
| 9 | Below is a short summation:
|
|---|
| 10 | ---------------------------
|
|---|
| 11 |
|
|---|
| 12 | o Corrected many hard coded 80h bootd-disk BIOS numbers
|
|---|
| 13 | This should improve booting AiR-BOOT when BIOS boots a non-80h disk.
|
|---|
| 14 |
|
|---|
| 15 | o Allow Ctrl-Alt-Del to do a warm reset when AiR-BOOT halts
|
|---|
| 16 | An AiR-BOOT halt can be caused by an USB stick with a confusing layout left
|
|---|
| 17 | left in a slot. While CAD is faster, remember that AiR-BOOT halted for a
|
|---|
| 18 | reason, so some proper investigation is still required !
|
|---|
| 19 |
|
|---|
| 20 | o Improved LVM-info handling
|
|---|
| 21 | This code has virtually been rewritten and might solve some 'LOAD/SAVE ERROR'
|
|---|
| 22 | issues.
|
|---|
| 23 |
|
|---|
| 24 | o Better handling of removable (USB) media
|
|---|
| 25 | Note that this does also depend on the BIOS
|
|---|
| 26 |
|
|---|
| 27 | o Better validation before writing important sectors
|
|---|
| 28 | Sectors containing partition-tables or LVM-info and their location are
|
|---|
| 29 | more extensively checked before writing to disk.
|
|---|
| 30 |
|
|---|
| 31 | o Better handling of OS/2 systems using the same boot-drive
|
|---|
| 32 | This is an advanced feature which essentially allows multiple installations
|
|---|
| 33 | of OS/2 using the same drive-letter to boot from.
|
|---|
| 34 |
|
|---|
| 35 | o Revamped pre-MENU screen (press TAB to switch)
|
|---|
| 36 | Better layout and more information, including removable devices and LVM-info.
|
|---|
| 37 |
|
|---|
| 38 | o Initial support for LARGE FLOPPY formatted media
|
|---|
| 39 | Not bullet-proof yet...
|
|---|
| 40 |
|
|---|
| 41 | o Fixed issues reported on Trac
|
|---|
| 42 | See: http://trac.netlabs.org/air-boot/report
|
|---|
| 43 | for detailed info.
|
|---|
| 44 |
|
|---|
| 45 | More details can be found here:
|
|---|
| 46 |
|
|---|
| 47 | http://trac.netlabs.org/air-boot/log
|
|---|
| 48 | -- or --
|
|---|
| 49 | https://github.com/rousseaux/netlabs.air-boot/commits/master
|
|---|
| 50 |
|
|---|
| 51 |
|
|---|
| 52 | Resources:
|
|---|
| 53 | ----------
|
|---|
| 54 | Netlabs Project Page : http://trac.netlabs.org/air-boot
|
|---|
| 55 | Netlabs Respository : http://trac.netlabs.org/air-boot/browser/trunk
|
|---|
| 56 | Netlabs Revision Log : http://trac.netlabs.org/air-boot/log
|
|---|
| 57 | Bug tracking: : http://trac.netlabs.org/air-boot/report
|
|---|
| 58 | GitHub Project Portal : http://rousseaux.github.io/netlabs.air-boot
|
|---|
| 59 | GitHub Repository : http://github.com/rousseaux/netlabs.air-boot
|
|---|
| 60 | Contact e-mail : rousseau.os2dev@gmx.com
|
|---|
| 61 |
|
|---|
| 62 |
|
|---|
| 63 |
|
|---|
| 64 |
|
|---|
| 65 |
|
|---|
| 66 | ===============================================================================
|
|---|
| 67 | AiR-BOOT version 1.1.0-RELEASE [2013-04-05]
|
|---|
| 68 | ===============================================================================
|
|---|
| 69 |
|
|---|
| 70 | This is the version as included on the eCS v2.2-beta CD's.
|
|---|
| 71 | It was technically a pre-v1.1.0 release, with the final v1.1.0, including some
|
|---|
| 72 | minor patches, to be included with eCS v2.2-GA. Because this version is now
|
|---|
| 73 | known to be v1.1.0, we'll keep it that way. The minor patches and meanwhile
|
|---|
| 74 | done fixes will soon appear as v1.1.1 test-version commits to be consolidated
|
|---|
| 75 | to a v1.1.2 release. Issues regarding removable media are planned for the
|
|---|
| 76 | v1.1.4 release as this requires removal of obsolete code and optimizing
|
|---|
| 77 | existing code to create space in the ~32K block (track0) the loader resides in.
|
|---|
| 78 |
|
|---|
| 79 | With this version of AiR-BOOT, the display of the version number has changed
|
|---|
| 80 | to be compatible with the WarpIN versioning system.
|
|---|
| 81 | So all digits are now separated by a dot.
|
|---|
| 82 | This change is only visual and tools relying on the way AiR-BOOT stores it's
|
|---|
| 83 | version numer internally are not affected.
|
|---|
| 84 |
|
|---|
| 85 |
|
|---|
| 86 | The following has been fixed:
|
|---|
| 87 |
|
|---|
| 88 | - AiR-BOOT cleared the bootable flag on all drives (TRAC ticket #6)
|
|---|
| 89 | -----------------------------------------------------------------
|
|---|
| 90 | This interferred with booting other drives, not containing AiR-BOOT,
|
|---|
| 91 | directly from the BIOS. Now AiR-BOOT only clears the bootable-flag on the
|
|---|
| 92 | boot-drive, which is the one where AiR-BOOT got activated from.
|
|---|
| 93 |
|
|---|
| 94 | AiR-BOOT would use INT13X extensions before checking their availability
|
|---|
| 95 | -----------------------------------------------------------------------
|
|---|
| 96 | Now the availability of INT13X is checked and a popup is displayed and the
|
|---|
| 97 | system halted when they are not available. INT13X is a requirement for
|
|---|
| 98 | this and higher versions of AiR-BOOT.
|
|---|
| 99 |
|
|---|
| 100 | - AiR-BOOT does not remember drive-letters (issue #2987)
|
|---|
| 101 | ------------------------------------------------------
|
|---|
| 102 | When using the drive-letter feature, AB would not remember the drive-letter.
|
|---|
| 103 | This has been fixed.
|
|---|
| 104 |
|
|---|
| 105 | The purpose of this feature is to force a drive-letter onto the booting
|
|---|
| 106 | system if it otherwise refuses to boot. ("... cannot operate harddrive ...")
|
|---|
| 107 | This would occure on systems that have been formatted with HPFS and have
|
|---|
| 108 | their system restored from archive. (i.e. from a zip-file)
|
|---|
| 109 | In this case the HPFS partition misses the information needed by the loader
|
|---|
| 110 | to indicate which drive-letter to use. (issues #3067 and #3119)
|
|---|
| 111 | A SYSINSTX would solve such a problem, as did the dl-feature in AB v1.06.
|
|---|
| 112 |
|
|---|
| 113 | With this 1.1.0 version, this feature has become almost obsolete.
|
|---|
| 114 | If the information is missing from the HPFS partition, AB recreates it
|
|---|
| 115 | from the LVM information related to that partition.
|
|---|
| 116 | It only does that in memory, just before booting the system and thus does not
|
|---|
| 117 | alter/fix the HPFS partition on disk. The user can do that by regenerating
|
|---|
| 118 | the system using SYSINSTX.
|
|---|
| 119 |
|
|---|
| 120 | When using multiple eComStation systems installed on the same drive-letter,
|
|---|
| 121 | the drive-letter feature is still needed to force the correct letter on the
|
|---|
| 122 | system being booted and hide the others. See the documentation on how to
|
|---|
| 123 | install multiple OS/2 systems using the same drive-letter.
|
|---|
| 124 |
|
|---|
| 125 | Another case where the drive-letter feature can still be of value is when
|
|---|
| 126 | restoring a pre-LVM system from archive to an HPFS partition.
|
|---|
| 127 | In this case there will be no LVM information AiR-BOOT can use, so the
|
|---|
| 128 | user can use the dl-feature to force the proper boot-drive.
|
|---|
| 129 | After booting the pre-LVM system, it's advised to do a SYSINSTX to
|
|---|
| 130 | permanently fix the HPFS partition. After that, the dl-feature can be
|
|---|
| 131 | turned off since now the proper information is present.
|
|---|
| 132 |
|
|---|
| 133 | Yet another situation might occur when the ordering of primary partitions
|
|---|
| 134 | is changed. There are situations when partitioning an empty harddisk,
|
|---|
| 135 | the LVM subsystem creates so called cross-linked entries.
|
|---|
| 136 | This means that the first pointer in the partition table does not point to
|
|---|
| 137 | the first partition on disk. This can happen when creating multiple
|
|---|
| 138 | partitions in MiniLVM and saving them all at once.
|
|---|
| 139 | Good practice is to create-save-create-save...
|
|---|
| 140 |
|
|---|
| 141 | Having primary partitions cross-linked is normally not a problem,
|
|---|
| 142 | but if the user corrects the ordering, i.e. with Linux fdisk (not advised!),
|
|---|
| 143 | the relation between those primaries and their LVM information
|
|---|
| 144 | might get mixed up. (The LVM-info is still in the old order)
|
|---|
| 145 | In this case the AiR-BOOT drive-letter feature could be used to force
|
|---|
| 146 | the correct drive-letter. The user should recreate the LVM-info with
|
|---|
| 147 | MiniLVM by unssigning and reassigning the drive-letters for the primary
|
|---|
| 148 | partitions to regenerate the LVM information. After this,
|
|---|
| 149 | the partition should boot and the dl-feature can be turned off.
|
|---|
| 150 |
|
|---|
| 151 | * Please note that the dl-feature should be used with caution *
|
|---|
| 152 | Supplying incorrect information can cause system boot failure !
|
|---|
| 153 | The drive-letter entered in this feature should be the same as the one
|
|---|
| 154 | used in the CONFIG.SYS corresponding to that system.
|
|---|
| 155 |
|
|---|
| 156 | As a convenience, a drive-letter in the dl-feature pop-up can now be set
|
|---|
| 157 | to "Disabled" by pressing backspace.
|
|---|
| 158 | (As opposed to arrowing up/down to get to the "Disabled" entry)
|
|---|
| 159 |
|
|---|
| 160 |
|
|---|
| 161 |
|
|---|
| 162 | - HPFS zero-drive boot-bug (issues #3067 and #3119)
|
|---|
| 163 | -------------------------------------------------
|
|---|
| 164 | AiR-BOOT would sometimes refuse to boot older OS/2 systems on HPFS.
|
|---|
| 165 | This has been fixed.
|
|---|
| 166 |
|
|---|
| 167 | The nature of this bug is described above.
|
|---|
| 168 | AiR-BOOT now checks for this condition and tries to use the drive-letter
|
|---|
| 169 | from the partition's LVM info. If that's not possible, the system will refuse
|
|---|
| 170 | to boot and the user can reset the system and turn on the dl-feature
|
|---|
| 171 | to force a boot-drive. The system should then boot, after which the user is
|
|---|
| 172 | advised to repair the HPFS volume by regenerating the system with SYSINSTX.
|
|---|
| 173 |
|
|---|
| 174 |
|
|---|
| 175 |
|
|---|
| 176 | - Double 'I13X' signature (issue #3002)
|
|---|
| 177 | -------------------------------------
|
|---|
| 178 | The LVM-engine from eComStation v1.x puts the 'I13X' signature in a
|
|---|
| 179 | different location in the MBR (Master Boot Record) than the
|
|---|
| 180 | LVM-engine from eComStation v2.x does.
|
|---|
| 181 | The true impact of this is unknown at the time but could involve scenario's
|
|---|
| 182 | where a v1.x IBM-BM is used with a v2.x generated MBR, or vice-versa.
|
|---|
| 183 | (Not advised or supported anyway)
|
|---|
| 184 | Previous versions of AiR-BOOT used the v1.x location of the signature.
|
|---|
| 185 | Starting with v1.1.0 the 'I13X' signature is at both places in the AB MBR.
|
|---|
| 186 |
|
|---|
| 187 |
|
|---|
| 188 |
|
|---|
| 189 | - Windows cannot find NTLDR/BOOTMGR (issue #3064)
|
|---|
| 190 | ---------------------------------------
|
|---|
| 191 | AiR-BOOT v1.07 could not boot Windows XP/Vista/7 if it was installed in a
|
|---|
| 192 | logical partition.
|
|---|
| 193 | This has been fixed.
|
|---|
| 194 |
|
|---|
| 195 | Unlike OS/2 and eComStation, Windows cannot truly boot from a logical
|
|---|
| 196 | partition. It always needs a primary partition where it can store it's
|
|---|
| 197 | loader. When the partition used for the loader is FAT32, the loader code
|
|---|
| 198 | cannot find the NT kernel-loader (a file on disk) if the field that
|
|---|
| 199 | otherwise belongs to the physical disk identifier is overwritten.
|
|---|
| 200 | This field has a different meaning in FAT32 and AiR-BOOT now treats it
|
|---|
| 201 | as such.
|
|---|
| 202 |
|
|---|
| 203 |
|
|---|
| 204 |
|
|---|
| 205 | - Contact information corrected
|
|---|
| 206 | -----------------------------
|
|---|
| 207 | An unfortunate mistake was made with v1.07 in that it contained the *wrong*
|
|---|
| 208 | contact information in it's SETUP display.
|
|---|
| 209 | This still pointed to the sourceforge site, causing lot of confusion.
|
|---|
| 210 | Version 1.07 and up reside on Netlabs, see the end of this document for
|
|---|
| 211 | links.
|
|---|
| 212 |
|
|---|
| 213 |
|
|---|
| 214 |
|
|---|
| 215 | - Release date corrected
|
|---|
| 216 | ----------------------
|
|---|
| 217 | AB v1.07 internally had the release date of v1.06.
|
|---|
| 218 | AB v1.1.0 has a correct internal release date.
|
|---|
| 219 | This is a non-impact fix.
|
|---|
| 220 |
|
|---|
| 221 |
|
|---|
| 222 |
|
|---|
| 223 |
|
|---|
| 224 | Note:
|
|---|
| 225 | -----
|
|---|
| 226 | The fixes above also involved the installer, AIRBOOT2.EXE and SET(A)BOOT.EXE
|
|---|
| 227 | of which new versions are provided.
|
|---|
| 228 | Therefore, you should not try to install v1.1.0 by using the v1.07 installer.
|
|---|
| 229 | It will report a broken configuration while this is not the case.
|
|---|
| 230 |
|
|---|
| 231 |
|
|---|
| 232 |
|
|---|
| 233 |
|
|---|
| 234 |
|
|---|
| 235 | ===============================================================================
|
|---|
| 236 | AiR-BOOT version 1.07-RELEASE [2011-05-06]
|
|---|
| 237 | ===============================================================================
|
|---|
| 238 |
|
|---|
| 239 | With eComStation v2.1, as released in may 2011, AiR-BOOT replaces the familiar
|
|---|
| 240 | but aging IBM Boot Manager. While it is still possible to use IBM-BM,
|
|---|
| 241 | it will not function correctly on huge disks (>502GiB) or play well in
|
|---|
| 242 | conjunction with Windows 7 OEM installations.
|
|---|
| 243 |
|
|---|
| 244 | While AiR-BOOT v1.06, the latest version by it's original developer
|
|---|
| 245 | Martin Kiewitz, could almost be used as-is, a couple of things needed to be
|
|---|
| 246 | fixed.
|
|---|
| 247 |
|
|---|
| 248 | These include the following:
|
|---|
| 249 |
|
|---|
| 250 |
|
|---|
| 251 | - Support for eComStation phase1
|
|---|
| 252 | ------------------------------
|
|---|
| 253 | When eComStation is being installed, it needs to reboot the system without
|
|---|
| 254 | displaying any boot-manager menu after completing phase1.
|
|---|
| 255 | With IBM-BM installed, it "programs" it using the SETBOOT utility.
|
|---|
| 256 | While AiR-BOOT v1.06 already contained SET(A)BOOT, this functionality
|
|---|
| 257 | was lacking. It has been implemented starting with the v1.07 version.
|
|---|
| 258 |
|
|---|
| 259 |
|
|---|
| 260 |
|
|---|
| 261 | - Support for huge disks (>502MiB)
|
|---|
| 262 | --------------------------------
|
|---|
| 263 | When using eComStation on huge disks, it uses a special geometry that
|
|---|
| 264 | has a different number of sectors per track. (127 or 255 instead of 63).
|
|---|
| 265 | This impacts the location of the LVM information which is usually stored in
|
|---|
| 266 | the last sector of track0 or just below the logical partition. Also,
|
|---|
| 267 | partitions do not start at a multiple of 63 sectors anymore, but on a
|
|---|
| 268 | multiple of 127 or 255 sectors, depending on the size of the disk.
|
|---|
| 269 | Support for huge disks has been implemented starting with v1.07.
|
|---|
| 270 |
|
|---|
| 271 |
|
|---|
| 272 |
|
|---|
| 273 | - Support for legacy systems on huge disks
|
|---|
| 274 | ----------------------------------------
|
|---|
| 275 | Since it's always best to use the OS/2 Volume Manager (MiniLVM) to partition
|
|---|
| 276 | disks that also contain OS/2 volumes, on huge disks this implies that such
|
|---|
| 277 | volumes have a different alignment due to the special geometry in use.
|
|---|
| 278 | With v1.07 support has been added for booting legacy systems like PC-DOS
|
|---|
| 279 | and FreeDOS and the DOS based 32-bit versions of Windows (95/98/ME) on
|
|---|
| 280 | such huge disks.
|
|---|
| 281 |
|
|---|
| 282 |
|
|---|
| 283 |
|
|---|
| 284 | - Adjusted color-theme
|
|---|
| 285 | ---------------------
|
|---|
| 286 | While the bright and shiny colors of v1.06 are arguably nice, they do not
|
|---|
| 287 | fit a distinguished product like eComStation.
|
|---|
| 288 | To prevent "culture shock", the color-theme has been adjusted to more
|
|---|
| 289 | resemble the IBM Boot Manager.
|
|---|
| 290 |
|
|---|
| 291 |
|
|---|
| 292 |
|
|---|
| 293 |
|
|---|
| 294 | Note:
|
|---|
| 295 | -----
|
|---|
| 296 | I't important to know that AiR-BOOT versions 1.07 and up are *not* developed
|
|---|
| 297 | by the original autor, Martin Kiewitz.
|
|---|
| 298 | Technically, version 1.07 and up are forks of the 1.06 version and maintained
|
|---|
| 299 | by a different developer. As such, addressing the original author with regard
|
|---|
| 300 | to v1.07 and up is not the correct path.
|
|---|
| 301 |
|
|---|
| 302 | The ArcaOS Edition of AiR-BOOT resides on Netlabs and not on Sourceforge.
|
|---|
| 303 |
|
|---|
| 304 |
|
|---|
| 305 |
|
|---|
| 306 | Ben Rietbroek <rousseau.os2dev@gmx.com>,
|
|---|
| 307 |
|
|---|
| 308 | AiR-BOOT maintainer.
|
|---|
| 309 |
|
|---|
| 310 |
|
|---|
| 311 | ########################## INFO PENDING TO BE MERGED ##########################
|
|---|
| 312 |
|
|---|
| 313 | ;
|
|---|
| 314 | ; v1.1.0-final
|
|---|
| 315 | ; ============
|
|---|
| 316 | ; # Bumped Version Number
|
|---|
| 317 | ; During v1.0.8 is was decided that odd minor versions will be test-versions.
|
|---|
| 318 | ; Since v1.0.8 was a test-version all the way, the final stuff has been
|
|---|
| 319 | ; bumped to v1.1.0, including the version of the configuration.
|
|---|
| 320 | ; v1.1.1 will be any following test-version, with build-dates separating
|
|---|
| 321 | ; test-releases. Version 1.1.2 would be a next release.
|
|---|
| 322 | ;
|
|---|
| 323 | ; # Updated version numbers
|
|---|
| 324 | ; All version identifiers updated from v1.0.8 to v1.1.0
|
|---|
| 325 | ; AIRBOOT.BIN, INSTALL[D2WL].EXE and SETABOOT.EXE.
|
|---|
| 326 | ;
|
|---|
| 327 | ; # Fixed Virus Regression
|
|---|
| 328 | ; Using the enhanced drive-letter feature to boot eCS installations using
|
|---|
| 329 | ; the same drive-letter caused the PBR-virus protection to activate.
|
|---|
| 330 | ; This was caused by a missing update to the PBR CRC in the AB configuration.
|
|---|
| 331 | ; This has been fixed.
|
|---|
| 332 | ;
|
|---|
| 333 | ; # Only clear bootable flag on boot-drive
|
|---|
| 334 | ; This interferred with booting other drives, not containing AiR-BOOT,
|
|---|
| 335 | ; directly from the BIOS. Now AiR-BOOT only clears the bootable-flag on the
|
|---|
| 336 | ; boot-drive, which is the one where AiR-BOOT got activated from.
|
|---|
| 337 | ;
|
|---|
| 338 | ; # Check for INT13X extensions before using them
|
|---|
| 339 | ; Now the availability of INT13X is checked and a popup is displayed and the
|
|---|
| 340 | ; system halted when they are not available. INT13X is a requirement for
|
|---|
| 341 | ; this and higher versions of AiR-BOOT.
|
|---|
| 342 | ;
|
|---|
| 343 | ; v1.0.8-rc3-bld20120909
|
|---|
| 344 | ; ----------------------
|
|---|
| 345 | ; # Added Show LVM Drive Letters in SETUP/BASIC #
|
|---|
| 346 | ; This will toggle the display of LVM drive-letters in the main menu.
|
|---|
| 347 | ; By default this option is enabled.
|
|---|
| 348 | ;
|
|---|
| 349 | ; # Reduced MBR Protection Image from 1024 bytes to 768 bytes #
|
|---|
| 350 | ; The fight for code-space continues...
|
|---|
| 351 | ; Luckily the MBR Protection Image code does not exceed 768 bytes,
|
|---|
| 352 | ; so that gives us another 256 bytes of precious code-space.
|
|---|
| 353 | ; Now the non-EN versions are happy again.
|
|---|
| 354 | ; Note that the alignment for the image changed from 512 to 256 bytes.
|
|---|
| 355 | ; MBR-PROT.ASM, FIXCODE.C, PARTMAIN.ASM and AIR-BOOT.ASM have been
|
|---|
| 356 | ; adjusted for this change.
|
|---|
| 357 | ;
|
|---|
| 358 | ; # Updating from v1.06 now also copies over drive-letters #
|
|---|
| 359 | ; When the user has forced drive-letters in v1.06 these will be copied over
|
|---|
| 360 | ; to the v1.0.8 configuration when upgrading.
|
|---|
| 361 | ; Because the drive-letter feature is broken in v1.07, the drive-letter
|
|---|
| 362 | ; table does not get copied over when upgrading from v1.07.
|
|---|
| 363 | ;
|
|---|
| 364 | ; # Fixed a minor bug with displaying LVM drive-letters #
|
|---|
| 365 | ; When more partitions that can be displayed were present, scrolling the
|
|---|
| 366 | ; menu would not scroll the drive-letter. Fixed.
|
|---|
| 367 | ;
|
|---|
| 368 | ; # Added DOCU directory for documentation #
|
|---|
| 369 | ; This contains the AiR-BOOT User Manual in Open Office .odt-format.
|
|---|
| 370 | ; To also have OS/2 INF format, a transformation script and sheet have been
|
|---|
| 371 | ; created to convert the .odt document to an ipf-source that can be compiled
|
|---|
| 372 | ; with Watcoms wipfc ipf compiler. (IBM ipfc does not work correctly)
|
|---|
| 373 | ; This makes it possible to write documentation in OOo Writer and export that
|
|---|
| 374 | ; to PDF and INF format.
|
|---|
| 375 | ;
|
|---|
| 376 | ; # Fixed a bug with regard to the drive-letter feature #
|
|---|
| 377 | ; When partitions were deleted, and some partitions above the deleted
|
|---|
| 378 | ; partition(s) had a drive-letter forced, these partitions would lose this
|
|---|
| 379 | ; assignment. This bug is also present in v1.06.
|
|---|
| 380 | ;
|
|---|
| 381 | ; # Implemented a very simple interactive debugger #
|
|---|
| 382 | ; Making use of the main menu-loop, pressing a digit or a letter activates
|
|---|
| 383 | ; some debugging routine. Mostly such a routine dumps a part of the internal
|
|---|
| 384 | ; state to the com-port. Other purposes are the interrogation of certain
|
|---|
| 385 | ; BIOS functions, as these can differ substantially between machines.
|
|---|
| 386 | ;
|
|---|
| 387 | ; # Made FX-code optional to compile in #
|
|---|
| 388 | ; The FX-code supplies the shifting screen-effects when 'Cooper Bars' is
|
|---|
| 389 | ; enabled in the setup. With the current enhancements made however,
|
|---|
| 390 | ; there is a continuous lack of code-space, especially when debug-code is
|
|---|
| 391 | ; included during development. The FX-code occupies some 1200 bytes, a space
|
|---|
| 392 | ; that can be put to better use. Therefore inclusion the FX-code has been
|
|---|
| 393 | ; made conditional to make room for either debugging or future new features.
|
|---|
| 394 | ;
|
|---|
| 395 | ; # Also write PBR to HPFS #
|
|---|
| 396 | ; Earlier, a fix was made to write a modified PBR back in case JFS was used.
|
|---|
| 397 | ; This was done to enable the drive-letter feature on JFS, since the PBR
|
|---|
| 398 | ; JFS-bootcode does not use the supplied PBR in memory.
|
|---|
| 399 | ; With the enhancements in the drive-letter feature, the HPFS PBR needs to
|
|---|
| 400 | ; be updated on disk also, to cope with zero drive-letters in the HPFS PBR.
|
|---|
| 401 | ;
|
|---|
| 402 | ; # Added drive-letters in display for LVM volumes #
|
|---|
| 403 | ; A populair request was to show drive-letter information in the menu.
|
|---|
| 404 | ; Drive-letters however, are OS specific and AiR-BOOT cannot accurately
|
|---|
| 405 | ; predict what drive-letter DOS would assign to what partition.
|
|---|
| 406 | ; eCS LVM drive-letters however are stored in the LVM-record and can thus
|
|---|
| 407 | ; be displayed. This has been implemented.
|
|---|
| 408 | ;
|
|---|
| 409 | ; # Enhanced drive-letter feature #
|
|---|
| 410 | ; Enable multiple eComStation installations using the same drive-letter
|
|---|
| 411 | ; This makes it possible to clone a system with XCOPY /h /e /s /t /r /v
|
|---|
| 412 | ; to another drive and have that boot from the same drive-letter.
|
|---|
| 413 | ; (Or installing to the same drive by hiding the other system)
|
|---|
| 414 | ;
|
|---|
| 415 | ; # Removed Force LBA Usage from Setup #
|
|---|
| 416 | ; When AiR-BOOT is installed on an USB-stick, there is a possibility that
|
|---|
| 417 | ; the CHS-geometry varies between different machines where the stick is
|
|---|
| 418 | ; booted. This would invalidate the CHS-values in the partition table
|
|---|
| 419 | ; and also the values that were stored in the AiR-BOOT's internal partition
|
|---|
| 420 | ; table, the IPT.
|
|---|
| 421 | ; To prevent more nasty things like below from happening, LBA-addressing
|
|---|
| 422 | ; is now always used and the setting has been removed from the setup-menu.
|
|---|
| 423 | ; While this may prevent AiR-BOOT from running on very old systems,
|
|---|
| 424 | ; the focus of AiR-BOOT development is geared towards the future.
|
|---|
| 425 | ; Such old systems can use v1.06.
|
|---|
| 426 | ;
|
|---|
| 427 | ; # Added extra MBR protection #
|
|---|
| 428 | ; When AiR-BOOT is active, it is only AiR-BOOT that writes to the MBR.
|
|---|
| 429 | ; To protect the MBR from programming errors, like the one below,
|
|---|
| 430 | ; any write to the MBR is now checked for validity.
|
|---|
| 431 | ; In essence this is protecting your MBR from bad programming done by me...
|
|---|
| 432 | ;
|
|---|
| 433 | ;!## Fixed a very very nasty bug that can destroy the MBR on multiple disks ##!
|
|---|
| 434 | ; When Force BIOS-LBA usage is disabled (the default is enabled), and the
|
|---|
| 435 | ; the driveletter feature is being set, and valid LVM information is present,
|
|---|
| 436 | ; then the MBR of the disk containing the partition of which the driveletter
|
|---|
| 437 | ; is changed will be overwritten with the LVM sector !
|
|---|
| 438 | ; In addition, if the driveletter was already in use by another partition
|
|---|
| 439 | ; on another disk, the MBR of that disk will be overwritten too !!
|
|---|
| 440 | ;
|
|---|
| 441 | ; # Fixed a nasty bug when eCS phase1 is active #
|
|---|
| 442 | ; When creating a partition in a free space between partitions for
|
|---|
| 443 | ; eCS installation, the phase1 boot-through code would calculate the
|
|---|
| 444 | ; wrong index for the new partition. As a result the next partition
|
|---|
| 445 | ; would be auto-booted instead of the newly installed system.
|
|---|
| 446 | ; This has been fixed.
|
|---|
| 447 | ; This bug is also present in v1.07 and does not apply to previous versions.
|
|---|
| 448 | ;
|
|---|
| 449 | ; v1.0.8-rc2-bld20120423
|
|---|
| 450 | ; ----------------------
|
|---|
| 451 | ; # Fixed some minor Installer bugs with SPT < 63 #
|
|---|
| 452 | ; Some extra var StatusCode was used instead of Status_Code.
|
|---|
| 453 | ; This caused too few tracks not to be reported.
|
|---|
| 454 | ; No installation was done however.
|
|---|
| 455 | ; This bug is also present in the v1.06 code.
|
|---|
| 456 | ;
|
|---|
| 457 | ; # Fixed Installer to handle packed hideparttable #
|
|---|
| 458 | ; Implemented upgrading from v1.06 directly to v1.0.8.
|
|---|
| 459 | ; Fixed minor stuff when upgrading from v1.06 to v1.07.
|
|---|
| 460 | ; Hide partition configuration is now preserved when upgrading.
|
|---|
| 461 | ; Fixed minor display bug when SPT < 63.
|
|---|
| 462 | ;
|
|---|
| 463 | ; # Implemented DOS code in C cross-platform installer
|
|---|
| 464 | ; There is now one C source for 4 platforms:
|
|---|
| 465 | ; DOS,WIN32,OS2 and LINUX (Linux portion not ready yet)
|
|---|
| 466 | ; This obsoletes AIRBOOT.ASM/AIRBOOT.COM.
|
|---|
| 467 | ; DOS Installer is now AIRBOOTD.EXE.
|
|---|
| 468 | ;
|
|---|
| 469 | ; # Merged 16-bit Assembler bitfield code to the Installer #
|
|---|
| 470 | ; The installer needs to handle the v1.0.8 configuration.
|
|---|
| 471 | ; This requires access to the 6-bit packed 'hideparttable'.
|
|---|
| 472 | ; To 'not-reinvent-the-wheel', by coding this in C, the Assembler
|
|---|
| 473 | ; bitfield functions are integrated using Open Watcom's '_asm' capability.
|
|---|
| 474 | ; It may not be pretty and the functions themselves are limited,
|
|---|
| 475 | ; but this method prevents maintaining seperate Asm and C implementations.
|
|---|
| 476 | ; Will be improved later.
|
|---|
| 477 | ;
|
|---|
| 478 | ; # Implemented BLDLEVEL support #
|
|---|
| 479 | ; AIRBOOT.BIN, the Installers and SET(A)BOOT now support OS/2 BLDLEVEL
|
|---|
| 480 | ; information. This enhances identification and problem tracking/solving.
|
|---|
| 481 | ; While BLDLEVEL is an OS/2 command, the BLDLEVEL information itself can
|
|---|
| 482 | ; be embedded in any binary. Invoking BLDLEVEL from within OS/2 on, let's
|
|---|
| 483 | ; say, the AIRBOOTL.ELF Linux executable, will also show the BLDLEVEL info.
|
|---|
| 484 | ; A slight deficiency of BLDLEVEL is that is forces a format on the version.
|
|---|
| 485 | ; So, AiR-BOOT v1.0.8 will be shown as v1.00.8.
|
|---|
| 486 | ;
|
|---|
| 487 | ; # Added support for Masm6 and Wasm v1.9 -- Experimental use only #
|
|---|
| 488 | ; Trying to assemble with Masm6 or Wasm v1.9 reveiled some interesting
|
|---|
| 489 | ; behavior aspects in general. While this version can now be assembled with
|
|---|
| 490 | ; Masm6 and Wasm too, this was only done to get a 'cross-feeling' for this
|
|---|
| 491 | ; project. Future versions will drop support for Tasm, Masm6 and Wasm since
|
|---|
| 492 | ; much conditional assembly is needed to support all of them. This was an
|
|---|
| 493 | ; experimental excercise only. JWasm is the assembler of choise for this
|
|---|
| 494 | ; project and any future versions.
|
|---|
| 495 | ;
|
|---|
| 496 | ; # Implemented stop scanning when max. partitions limit exceeded #
|
|---|
| 497 | ; Previous versions halted the system when the maximum number of partitions
|
|---|
| 498 | ; that can be handled (45) was exceeded.
|
|---|
| 499 | ; This required the user to boot from alternate media to correct the problem.
|
|---|
| 500 | ; Now, when the partition limit is exceeded, AiR-BOOT displays a pop-up
|
|---|
| 501 | ; and waits for a key-press. When the user presses a key, AiR-BOOT continues
|
|---|
| 502 | ; and the boot-menu is shown, enabling the user to boot a system to correct
|
|---|
| 503 | ; the problem. To indicate this situation, the color of the selection-bar
|
|---|
| 504 | ; is displayed in red.
|
|---|
| 505 | ;
|
|---|
| 506 | ; # Fixed hiding partitions above old max 30-partitions limit #
|
|---|
| 507 | ; Hiding partitions is a per partition setting and it is kept in a table
|
|---|
| 508 | ; in the AiR-BOOT image on disk. In previous versions, including v1.0.8-rc1,
|
|---|
| 509 | ; this table still held the old number of maximum partitions (30).
|
|---|
| 510 | ; So configuring a hide-setting for partitions >30 or hiding more than
|
|---|
| 511 | ; 30 partitions per partition would not work properly.
|
|---|
| 512 | ; Unfortunately, there was no room to expand this table, since it resides
|
|---|
| 513 | ; just below the MBR backup, at the end of the AiR-BOOT image.
|
|---|
| 514 | ; To work around this, the table now uses a 6-bits packed format and the
|
|---|
| 515 | ; drive-letter array, which followed this table has been moved elsewhere.
|
|---|
| 516 | ; This is a change in the configuration layout since the previous version,
|
|---|
| 517 | ; so the config-version has been bumped to v1.0.8.
|
|---|
| 518 | ; TODO: Add upgrade-code to the installer to cope with this.
|
|---|
| 519 | ;
|
|---|
| 520 | ; # Removed requirement for LVM P and V name to be the same to edit #
|
|---|
| 521 | ; However, when both are the same before the edit, the V name will be
|
|---|
| 522 | ; synved to the P name to have them both the same again after the edit.
|
|---|
| 523 | ; If they differ, only the V name is updated.
|
|---|
| 524 | ;
|
|---|
| 525 | ; # Trying to edit the label of a type 0x35 partition now shows a popup #
|
|---|
| 526 | ; The user is informed that type 0x35 labels cannot be edited.
|
|---|
| 527 | ;
|
|---|
| 528 | ; # Type 0x35 partitions cannot be added to the AB-menu anymore #
|
|---|
| 529 | ; They are not bootable anyway. The user is informed by a popup.
|
|---|
| 530 | ;
|
|---|
| 531 | ; # De-tasemized the Assembler sources for JWasm compatibility #
|
|---|
| 532 | ; AiR-BOOT can now be built using JWasm, which is the preferred
|
|---|
| 533 | ; assembler as of this release. Tasm support will be dropped in the future.
|
|---|
| 534 | ;
|
|---|
| 535 | ; # Completely reworked the build-system #
|
|---|
| 536 | ; Everything is now done with Makefiles using WMake, Wlink and the
|
|---|
| 537 | ; C/C++ Compilers from the Open Watcom development tools together with JWasm.
|
|---|
| 538 | ; This obsoletes tasm, tlink and exe2bin.
|
|---|
| 539 | ;
|
|---|
| 540 | ; # Cross-Platform support #
|
|---|
| 541 | ; AiR-BOOT and it's helpers can now be built on: DOS, Win32, OS/2 and Linux.
|
|---|
| 542 | ;
|
|---|
| 543 | ; # Rewrote FIXCODE.ASM in C so the tool-chain is not dependent on a DOS .COM #
|
|---|
| 544 | ; Now FIXCODE is built platform-specific and takes care of the embedding
|
|---|
| 545 | ; of MPR-protection image.
|
|---|
| 546 | ;
|
|---|
| 547 | ; # Created FIXCODE bash-script to accomplish embedding of MBR-protection #
|
|---|
| 548 | ; Building on Linux requires that no DOS-tools are used in the tool-chain.
|
|---|
| 549 | ; This script essentially performs the same functionality but does not check
|
|---|
| 550 | ; certain conditions, like image-too-big, etc.
|
|---|
| 551 | ; It is a 'quick-hack' until the Linux version of FIXCODE is operational.
|
|---|
| 552 | ;
|
|---|
| 553 | ; v1.0.8-rc1-bld20120124
|
|---|
| 554 | ; ----------------------
|
|---|
| 555 | ; # Changed version format to be more WarpIN compatible #
|
|---|
| 556 | ; This is a cosmetic change only, the internal format has not changed.
|
|---|
| 557 | ;
|
|---|
| 558 | ; # Show LVM VolumeName instead of LVM PartitionName #
|
|---|
| 559 | ; Previous versions of AiR-BOOT used the LVM PartitionName as the Label
|
|---|
| 560 | ; if LVM-info was present for the partition.
|
|---|
| 561 | ; This is inconsistent with MiniLVM which shows the LVM VolumeName.
|
|---|
| 562 | ; Starting with v1.0.8 the LVM VolumeName is displayed.
|
|---|
| 563 | ;
|
|---|
| 564 | ; # LVM Partition and Volume name Synchronization #
|
|---|
| 565 | ; Changing the Label of a partition with LVM-info now synchronizes
|
|---|
| 566 | ; the LVM Partition Name with the LVM Volume Name.
|
|---|
| 567 | ; This is the same behavior as MiniLVM.
|
|---|
| 568 | ; Note however that the Label can only be changed when both the
|
|---|
| 569 | ; LVM PartitionName and LVM VolumeName are the same.
|
|---|
| 570 | ; See protected editing below.
|
|---|
| 571 | ;
|
|---|
| 572 | ; # Protected editing of the Label when LVM-info is present #
|
|---|
| 573 | ; When the LVM VolumeName differs from the LVM PartitionName, the user can
|
|---|
| 574 | ; edit the label but it will not be saved to the LVM record on disk.
|
|---|
| 575 | ; This is to protect configurations created with the classic LVM tool.
|
|---|
| 576 | ; Since MiniLVM assigns the same name to both the Partition and the Volume,
|
|---|
| 577 | ; the Label can be edited and will be saved for such partitions.
|
|---|
| 578 | ; To further protect a given configuration, LVM volumes with type 0x35
|
|---|
| 579 | ; cannot be edited at all. This is to ensure that the LVM PartitionNames
|
|---|
| 580 | ; remain unique when Spanning Volumes are used.
|
|---|
| 581 | ;
|
|---|
| 582 | ; # Editing the Label appended spaces #
|
|---|
| 583 | ; When editing and changing the Label of a System using SETUP,
|
|---|
| 584 | ; trailing spaces were stored in the LVM Volume and Partition names.
|
|---|
| 585 | ; These labels need to be padded with zero's.
|
|---|
| 586 | ; This has been fixed.
|
|---|
| 587 | ; This bug is also present in v1.06.
|
|---|
| 588 | ;
|
|---|
| 589 | ; # Reworked Primary Partition <-> LVM-info association #
|
|---|
| 590 | ; The previous way was to use a 1:1 correspondence between the PT-index
|
|---|
| 591 | ; and the LVM-index. However, when the PT is cross-linked, lower entries
|
|---|
| 592 | ; pointing to higher locations on the disk, or vice-versa, incorrect
|
|---|
| 593 | ; LVM-info was associated. Such a cross-linked PT is sometimes generated
|
|---|
| 594 | ; by the LVM engine when creating or deleting multiple partitions at once.
|
|---|
| 595 | ; Best is to intermediately save after creating or deleting a partition
|
|---|
| 596 | ; with (Mini)LVM.
|
|---|
| 597 | ; The new way is to search the LVM-entries for the partition requested.
|
|---|
| 598 | ;
|
|---|
| 599 | ; # Reworked MBR-code to provide two I13X signatures #
|
|---|
| 600 | ; The normal LVM MBR-code uses a special setup to indicate Int13X capability.
|
|---|
| 601 | ; It contains the instruction, MOV EAX,'X31I', and some software checks
|
|---|
| 602 | ; for the presence of the 'I13X' string in the MBR.
|
|---|
| 603 | ; However, the location of this instruction differs between eCS 1.x and
|
|---|
| 604 | ; eCS 2.x LVM MBR-code.
|
|---|
| 605 | ; For compatibility, the v1.0.8 MBR has the 'I13X' string at both locations.
|
|---|
| 606 | ;
|
|---|
| 607 | ; # Fixed booting older eCS installations on HPFS #
|
|---|
| 608 | ; When restoring systems from archive or otherwise generated systems,
|
|---|
| 609 | ; the HPFS BPB sometimes lacked information that AiR-BOOT did not fill in.
|
|---|
| 610 | ; The result was that a wrong partition was booted or that booting
|
|---|
| 611 | ; stalled with the "unable to operate harddisk" message.
|
|---|
| 612 | ; This has been fixed.
|
|---|
| 613 | ;
|
|---|
| 614 | ; # Fixed booting Windows from a logical partition with loader on FAT32 #
|
|---|
| 615 | ; Depending on the configuration, sometimes the NTLDR could not be found.
|
|---|
| 616 | ; This has been fixed.
|
|---|
| 617 | ;
|
|---|
| 618 | ; # Fixed drive-letter feature which was broken in v1.07 #
|
|---|
| 619 | ; a) v1.07 did remember the drive-letter feature was active for a partition,
|
|---|
| 620 | ; but it failed to store the drive-letter because too few configuration
|
|---|
| 621 | ; sectors were saved. This resulted in arbitrary values to be assigned
|
|---|
| 622 | ; to the drive-letter for the partition.
|
|---|
| 623 | ; b) The JFS PBR-code does not use the in-memory BPB but uses the one
|
|---|
| 624 | ; that is on disk. This prevented AiR-BOOT from passing the user assigned
|
|---|
| 625 | ; drive-letter. AiR-BOOT now inserts the drive-letter in the BPB on disk,
|
|---|
| 626 | ; but only if the partition is JFS.
|
|---|
| 627 | ; AB v1.06 is also unable to use the drive-letter feature on JFS.
|
|---|
| 628 | ; As a convenience, a drive-letter in the dl-feature pop-up can now be set
|
|---|
| 629 | ; to "Disabled" by pressing backspace.
|
|---|
| 630 | ; (As opposed to arrowing up/down to get to the "Disabled" entry)
|
|---|
| 631 | ;
|
|---|
| 632 | ; # Fixed stuck phase1 indicator when wrong name entered #
|
|---|
| 633 | ; When using SET(A)BOOT /4:NAME with the MEMDRIVE env-var set,
|
|---|
| 634 | ; and NAME being a non-existing partition, the phase1 indicator
|
|---|
| 635 | ; would stay stuck between reboots.
|
|---|
| 636 | ; This has been fixed.
|
|---|
| 637 | ;
|
|---|
| 638 | ; # Fixed DOS installer (AIRBOOT.COM) #
|
|---|
| 639 | ; Behavior should now be the same as the eCS and WIN installers.
|
|---|
| 640 | ; This re-enables the use of a bootable floppy or usb-stick
|
|---|
| 641 | ; to install AiR-BOOT.
|
|---|
| 642 | ;
|
|---|
| 643 | ; # Fixed booting from FloppyDrive #
|
|---|
| 644 | ; This is actually also broken in v1.06 when Int13X is forced on.
|
|---|
| 645 | ; Now regular BIOS calls are used when booting from floppydrive.
|
|---|
| 646 | ; A fresh AiR-BOOT installation now includes the floppydrive menu entry.
|
|---|
| 647 | ;
|
|---|
| 648 | ; # Fixed chainloading IBM Boot Manager #
|
|---|
| 649 | ; AiR-BOOT v1.06 could chainload IBM-BM but only when it resided on
|
|---|
| 650 | ; the first disk and was located below the 1024 cylinder and forced Int13X
|
|---|
| 651 | ; extensions were disabled.
|
|---|
| 652 | ; AiR-BOOT v1.0.8 can now chainload IBM-BM with forced Int13X extensions
|
|---|
| 653 | ; enabled (the default) and if IBM-BM resides above the 1024 cylinder limit.
|
|---|
| 654 | ; Also, chainloading IBM-BM from the second disk is supported.
|
|---|
| 655 | ; Do not use chainloading IBM-BM unless you really have a need to.
|
|---|
| 656 | ; See the AiR-BOOT Manual for "gotcha's" when using both AiR-BOOT and IBM-BM.
|
|---|
| 657 | ;
|
|---|
| 658 | ; # Corrected contact links #
|
|---|
| 659 | ; Version 1.07 still presented the old contact links to the sourceforge
|
|---|
| 660 | ; repository and the original author.
|
|---|
| 661 | ; This caused confusion with regard to issues with v1.07.
|
|---|
| 662 | ; This has been corrected.
|
|---|
| 663 | ;
|
|---|
| 664 | ; NOTE:
|
|---|
| 665 | ; AB v1.07 had a bug with saving and loading the correct size of the
|
|---|
| 666 | ; configuration. This broke the drive-letter feature.
|
|---|
| 667 | ; As a result, the CRC over the config was also calculated wrongly.
|
|---|
| 668 | ; While AB v1.0.8 fixes this, it has to use the v1.07 way of CRC calculation.
|
|---|
| 669 | ; Otherwise SET(A)BOOT from the eCS v2.1 would break on AB v1.0.8 because it
|
|---|
| 670 | ; sees a corrupt AiR-BOOT configuration.
|
|---|
| 671 | ; This means that the CRC over the AB config is calculated over 5 sectors
|
|---|
| 672 | ; instead of 7, just like in v1.07.
|
|---|
| 673 | ;
|
|---|
| 674 | ; NOTE:
|
|---|
| 675 | ; Because of space constraints most of the debug code has been commented
|
|---|
| 676 | ; out in this version.
|
|---|
| 677 | ; Possibly it will be re-enabled after code cleanup and changing to JWasm.
|
|---|
| 678 | ;
|
|---|
| 679 | ;
|
|---|
| 680 | ; v1.07-final
|
|---|
| 681 | ; ===========
|
|---|
| 682 | ; # Huge Drives and LVM #
|
|---|
| 683 | ; When using disks >512GB under eComStation, the drive geometry changes to
|
|---|
| 684 | ; 127 or 255 sectors per track. Since LVM-info is written at the last sector
|
|---|
| 685 | ; of a track, and AiR-BOOT uses the geometry of the MBR, it cannot find the
|
|---|
| 686 | ; LVM-info and the eCS partition / volume bootsector.
|
|---|
| 687 | ; This has been fixed.
|
|---|
| 688 | ; Now, when an eCS-partition is discovered and the drive is >512GB, AiR-BOOT
|
|---|
| 689 | ; will use the eCS geometry to locate the LVM-info and the bootsector.
|
|---|
| 690 | ;
|
|---|
| 691 | ; # Special loader handling #
|
|---|
| 692 | ; The special handling of partition boot-loaders has been enhanced to
|
|---|
| 693 | ; enable booting of legacy systems on huge drives with or without OS/2
|
|---|
| 694 | ; extended geometry.
|
|---|
| 695 | ;
|
|---|
| 696 | ; # eComStation boot-through after phase 1 #
|
|---|
| 697 | ; Special functionality is implemented to directly boot a newly
|
|---|
| 698 | ; installed eCS system after completing phase 1 of the installation.
|
|---|
| 699 | ; This works in conjuntion with the OS/2 specific SET(A)BOOT.EXE program,
|
|---|
| 700 | ; also part of the AiR-BOOT package.
|
|---|
| 701 | ;
|
|---|
| 702 | ; # Math, Debug, Conv and Aux modules #
|
|---|
| 703 | ; These are used for 32-bit arithmatic on 16-bit code,
|
|---|
| 704 | ; debug the boot process, converting between data-types
|
|---|
| 705 | ; and outputting log-data to the com-port.
|
|---|
| 706 | ;
|
|---|
| 707 | ;
|
|---|
| 708 | ; v1.06
|
|---|
| 709 | ; =====
|
|---|
| 710 | ; This is the last version developed by Martin Kiewitz.
|
|---|
| 711 | ; It serves as the base for the versions above.
|
|---|
| 712 | ; Please do not post your feedback on sourceforge or bother Martin with
|
|---|
| 713 | ; regard to issues with the above versions.
|
|---|
| 714 | ; Use the eCS bug-tracker or the Trac project-page at netlabs and see the
|
|---|
| 715 | ; documentation of this newer versions for the relevant contact information.
|
|---|
