Changeset 54 for trunk


Ignore:
Timestamp:
Apr 13, 2014, 9:13:58 PM (11 years ago)
Author:
Ben Rietbroek
Message:

Preparing for v1.1.0 [2013-04-05]

During v1.0.8 it was decided that odd minor numbers will be
test-versions. Since v1.0.8 was actually a test-version with several
test-releases but with an even minor number, it was decided to bump the
final release to v1.1.0.

Thus, v1.1.1 will be the next test-version after the upcoming official
v1.1.0 release. When such test-versions are published, for instance to
get feedback, or solve a particular issue, the build-date and BLDLEVEL
information will identify such a test-release. This information can be
viewed by pressing the TAB-key while the Main Menu is displayed. Such
test-releases will also have a slightly different visual appearance to
distinguish them from official releases.

Because all test-versions between official releases identify themselves
with the same version number, upgrading from one test-release to another
requires the /forcecode option on the Installer.

Following this scheme, v1.1.2 will be the next official release after
the upcoming v1.1.0 release.

It is possible however, that major changes break compatibility with
previous releases, in which case the middle number will be incremented
to reflect this.

Note that this commit still identifies as v1.0.8.

Changes

o Bumped version information to v1.1.0
o Updated version dependent code in the Installers and SETABOOT.EXE

Location:
trunk
Files:
20 edited

Legend:

Unmodified
Added
Removed

  • trunk/1README.TXT

    r46 r54  
    11===============================================================================
    2  1README.TXT -- General Information about AiR-BOOT v1.0.8
     2 1README.TXT -- General Information about AiR-BOOT v1.1.0
    33===============================================================================
    44

  • trunk/AiR-BOOT.TXT

    r37 r54  
    1 == CONCEPT ==
    2 
    31======================
    4 AiR-BOOT version 1.0.8                                                 nov 2011
     2AiR-BOOT version 1.1.0                                                 apr 2013
    53======================
    64
    … …  
    119version numer internally are not affected.
    1210
    13 The following has been fixed:
     11During v1.0.8 it was decided that odd minor numbers will be
     12test-versions. Since v1.0.8 was actually a test-version with several
     13test-releases but with an even minor number, it was decided to bump the
     14final release to v1.1.0.
     15
     16Thus, v1.1.1 will be the next test-version after the upcoming official
     17v1.1.0 release. When such test-versions are published, for instance to
     18get feedback, or solve a particular issue, the build-date and BLDLEVEL
     19information will identify such a test-release. This information can be
     20viewed by pressing the TAB-key while the Main Menu is displayed. Such
     21test-releases will also have a slightly different visual appearance to
     22distinguish them from official releases.
     23
     24Because all test-versions between official releases identify themselves
     25with the same version number, upgrading from one test-release to another
     26requires the /forcecode option on the Installer.
     27
     28
     29The following summation of fixes.
     30For more details see AIRBOOT.HIS in the BOOTCODE directory.
     31
    1432
    1533
    … …  
    2745  A SYSINSTX would solve such a problem, as did the dl-feature in AB v1.06.
    2846
    29   With this 1.0.8 version, this feature has become almost obsolete.
    30   If the information is missing from the HPFS partition, AB recreates it
    31   from the LVM information related to that partition.
    32   It only does that in memory, just before booting the system and thus does not
    33   alter/fix the HPFS partition on disk. The user can do that by regenerating
    34   the system using SYSINSTX.
    35 
    36   One case where the drive-letter feature can still be of value is when
    37   restoring a pre-LVM system from archive to an HPFS partition.
     47  With this 1.1.0 version, this feature has become almost obsolete, except
     48  when installing multiple eComStation systems using the same drive-letter.
     49  In that case, each such an installation needs to have it's drive forced
     50  to the letter of it's boot-drive.
     51
     52  This feature feature can still be of value is when restoring a pre-LVM
     53  system from archive to an HPFS partition.
    3854  In this case there will be no LVM information AiR-BOOT can use, so the
    3955  user can use the dl-feature to force the proper boot-drive.
    … …  
    4157  permanently fix the HPFS partition. After that, the dl-feature can be
    4258  turned off since now the proper information is present.
    43 
    44   Another situation might occur when the ordering of primary partitions
    45   is changed. There are situations when partitioning an empty harddisk,
    46   the LVM subsystem creates so called cross-linked entries.
    47   This means that the first pointer in the partition table does not point to
    48   the first partition on disk. This can happen when creating multiple
    49   partitions in MiniLVM and saving them all at once.
    50   Good practice is to create-save-create-save...
    51 
    52   Having primary partitions cross-linked is normally not a problem,
    53   but if the user corrects the ordering, i.e. with Linux fdisk (not advised!),
    54   the relation between those primaries and their LVM information
    55   get's mixed up. (The LVM-info is still in the old order)
    56   In this case the AiR-BOOT drive-letter feature could be used to force
    57   the correct drive-letter. The user should recreate the LVM-info with
    58   MiniLVM by unssigning and reassigning the drive-letters for the primary
    59   partitions to regenerate the LVM information. After this,
    60   the partition should boot and the dl-feature can be turned off.
    6159
    6260  * Please note that the dl-feature should be used with caution *
    … …  
    9492  (Not advised or supported anyway)
    9593  Previous versions of AiR-BOOT used the v1.x location of the signature.
    96   Starting with v1.0.8 the 'I13X' signature is at both places in the AB MBR.
     94  Starting with v1.1.0 the 'I13X' signature is at both places in the AB MBR.
    9795
    9896
    … …  
    127125  ----------------------
    128126  AB v1.07 internally had the release date of v1.06.
    129   AB v1.0.8 has a correct internal release date.
     127  AB v1.1.0 has a correct internal release date.
    130128  This is a non-impact fix.
    131129
    … …  
    137135The fixes above also involved the installer, AIRBOOT2.EXE and SET(A)BOOT.EXE
    138136of which new versions are provided.
    139 Therefore, you should not try to install v1.0.8 by using the v1.07 installer.
     137Therefore, you should not try to install v1.1.0 by using the v1.07 installer.
    140138It will report a broken configuration while this is not the case.
    141139

  • trunk/BOOTCODE/AIR-BOOT.ASM

    r52 r54  
    18031803                ; configuration has. The v1.0.8 installer handles upgrading.
    18041804                ;
     1805                ; It has been decided that uneven minor numbers will be
     1806                ; test-versions. Therefore v1.0.8 has been bumbed to v1.1.0.
     1807                ;
    18051808                ; It is not required for the config to have the
    18061809                ; same version as the code, so in the future

  • trunk/BOOTCODE/AIR-BOOT.HIS

    r51 r54  
    2424; Rousseau: Fixes, Enhancements and fresh bugs :-)
    2525; ------------------------------------------------
     26;
     27; v1.1.0-pre
     28; ----------
     29; # Updated textual version information from v1.0.8 to v1.1.0
     30;   This does not include the version identifiers.
     31;   During v1.0.8 is was decided that odd minor versions will be test-versions.
     32;   Since v1.0.8 was a test-version all the way, the final stuff has been
     33;   bumped to v1.1.0, including the version of the configuration.
     34;   v1.1.1 will be any following test-version, with build-dates separating
     35;   test-releases. Version 1.1.2 would be a next release.
     36;
     37; # Fixed Virus Regression
     38;   Using the enhanced drive-letter feature to boot eCS installations using
     39;   the same drive-letter caused the PBR-virus protection to activate.
     40;   This was caused by a missing update to the PBR CRC in the AB configuration.
     41;   This has been fixed.
    2642;
    2743; v1.0.8-rc3-bld20120909
    … …  
    362378;
    363379;
    364 ; v1.07
    365 ; -----
     380; v1.07-final
     381; ===========
    366382; # Huge Drives and LVM #
    367383;   When using disks >512GB under eComStation, the drive geometry changes to
    … …  
    391407;
    392408; v1.06
    393 ; -----
     409; =====
    394410; This is the last version developed by Martin Kiewitz.
    395411; It serves as the base for the versions above.

  • trunk/BOOTCODE/Makefile

    r51 r54  
    595595        @if exist AIRBT-EN.BIN $(CP) AIRBT-EN.BIN ..$(DS)RELEASE$(DS)OS2$(DS)$(TARGET)
    596596        @if exist AIRBT-EN.BIN $(CP) AIRBT-EN.BIN ..$(DS)RELEASE$(DS)LINUX$(DS)$(TARGET)
     597        @cd ..
     598        @cd INSTALL$(DS)C
     599        @$(MAKE) dist
     600        @cd ..$(DS)..
     601        @cd TOOLS$(DS)OS2$(DS)SETABOOT
     602        @$(MAKE) dist
    597603
    598604

  • trunk/BOOTCODE/REGULAR/DRIVEIO.ASM

    r51 r54  
    6868
    6969        ; AB v1.07 stores a 5 sector configuration with a 5 sector checksum.
    70         ; AB v1.0.8 *should* stores a 7 sector configuration with a
     70        ; AB v1.0.8+ *should* stores a 7 sector configuration with a
    7171        ; 7 sector checksum.
    72         ; Because 5 was hardcoded here, SET(A)BOOT v1.07 will see see an AB v1.0.8
     72        ; Because 5 was hardcoded here, SET(A)BOOT v1.07 will see see an AB v1.0.8+
    7373        ; config as corrupted, while this is not the case.
    74         ; So, for compatibility reasons, in v1.0.8, the checksum stored is over
     74        ; So, for compatibility reasons, in v1.0.8+, the checksum stored is over
    7575        ; 5 sectors, to be compatible with v1.07.
    7676        ; This may change (be corrected) in future versions !
    … …  
    10061006        jz      DIOSS_UseNormal
    10071007        ; Are we forced do use LBA via Setting?
    1008         ; Always use INT13X on v1.0.8.
     1008        ; Always use INT13X on v1.0.8+.
    10091009        ;~ test    byte ptr cs:[CFG_ForceLBAUsage], 1
    10101010        ;~ jnz     DIOSS_UseExtension

  • trunk/BOOTCODE/REGULAR/OTHER.ASM

    r51 r54  
    462462
    463463        ; AB v1.07 stores a 5 sector configuration with a 5 sector checksum.
    464         ; AB v1.0.8 *should* stores a 7 sector configuration with a
     464        ; AB v1.0.8+ *should* stores a 7 sector configuration with a
    465465        ; 7 sector checksum.
    466         ; Because 5 was hardcoded here, SET(A)BOOT v1.07 will see see an AB v1.0.8
     466        ; Because 5 was hardcoded here, SET(A)BOOT v1.07 will see see an AB v1.0.8+
    467467        ; config as corrupted, while this is not the case.
    468         ; So, for compatibility reasons, in v1.0.8, the checksum stored is over
     468        ; So, for compatibility reasons, in v1.0.8+, the checksum stored is over
    469469        ; 5 sectors, to be compatible with v1.07.
    470470        ; This may change (be corrected) in future versions !

  • trunk/BOOTCODE/REGULAR/PARTMAIN.ASM

    r53 r54  
    12261226
    12271227    ;
    1228     ; Always use INT13X v1.0.8.
     1228    ; Always use INT13X v1.0.8+.
    12291229    ;
    12301230    ;~ test    byte ptr [CFG_ForceLBAUsage], 1

  • trunk/BOOTCODE/REGULAR/PARTSCAN.ASM

    r51 r54  
    302302    PSSP_IgnorePartition:
    303303        ; L”scht das Boot-Able Flag...
     304        ; CHECKME: About clearing the active flags, TRACK ticket #6
    304305        and     byte ptr [si+LocBRPT_Flags], 7Fh ; Reset the Active-Flag
    305306        add     si, LocBRPT_LenOfEntry     ; 16 Bytes per partition entry

  • trunk/BOOTCODE/REGULAR/STD_TEXT.ASM

    r52 r54  
    5353            db BLDLVL_MAJOR_VERSION,'.'
    5454            db BLDLVL_MIDDLE_VERSION,'.'
    55             db BLDLVL_MINOR_VERSION,' - (c) '
     55            db BLDLVL_MINOR_VERSION,' - (c) 1998-'
    5656            db BLDLVL_YEAR
    57             ;~ db ' M. Kiewitz  <<Internal Release 3o>> (bld: '
    58             ;~ db ' M. Kiewitz  <<@ Interim Release @>> (bld: '
    59             ;~ db ' M. Kiewitz  <<Release Candidate 2>> (bld: '
    60             db ' M. Kiewitz  <<Release Candidate 4>> (bld: '
     57            ;~ db ' Martin Kiewitz, Dedicated to Gerd Kiewitz'
     58            db ' M. Kiewitz  <<  v1.1.0-pre  >> (bld: '
     59            ;~ db ' M. Kiewitz  << Test Version >> (bld: '
     60            ;~ db ' Rousseau    << Test Version >> (bld:'
    6161            db BLDLVL_YEAR
    6262            db BLDLVL_MONTH

  • trunk/BOOTCODE/SETUP/PART_SET.ASM

    r52 r54  
    697697
    698698    ; This code is used for BR and LVM checking
    699     ; Rousseau: Because AiR-BOOT v1.0.8 uses the LVM_VolumeName, which is copied
     699    ; Rousseau: Because AiR-BOOT v1.0.8+ uses the LVM_VolumeName, which is copied
    700700    ; to the IPT, this compare fails when the LVM_PartitionName is not
    701701    ; the same as the LVM_VolumeName. In that case, only the LVM_VolumeName

  • trunk/BOOTCODE/VERSION.INC

    r53 r54  
    3737AB_YEAR             EQU     2013h
    3838AB_MONTH            EQU     04h
    39 AB_DAY              EQU     03h
     39AB_DAY              EQU     05h
    4040
    4141; The Hours, Minutes and Seconds, again in BCD for easy manipulation.
    42 AB_HOURS            EQU     16h
    43 AB_MINUTES          EQU     10h
    44 AB_SECONDS          EQU     00h
     42AB_HOURS            EQU     01h
     43AB_MINUTES          EQU     00h
     44AB_SECONDS          EQU     08h
    4545
    4646; The AiR-BOOT signature uses big-endian so we shuffle some bits around.
    … …  
    4848AB_SIG_YEAR         EQU     ((AB_YEAR SHR 8) OR (AB_YEAR SHL 8) AND 0FFFFh)
    4949AB_SIG_DATE         EQU     (AB_MONTH SHL 8) OR AB_DAY
    50 
    5150
    5251;

  • trunk/BUILD.NFO

    r46 r54  
    11===============================================================================
    2  BUILD.NFO -- Information on building AiR-BOOT v1.0.8
     2 BUILD.NFO -- Information on building AiR-BOOT v1.1.0
    33===============================================================================
    44
    … …  
    1212
    1313The Open Watcom Linker is now used, which obsoletes the use of the (DOS-only)
    14 exe2bin and tlink programs. WLink replaces the functionality of both while
     14exe2bin and TLink programs. WLink replaces the functionality of both while
    1515also adding extensive cross-platform support.
    1616
    … …  
    4141default tool-chain.
    4242
    43 Building AiR-BOOT v1.0.8 requires the following tools:
     43Building AiR-BOOT v1.1.0 requires the following tools:
    4444- Open Watcom Make Utility v1.9 or higher
    4545- Open Watcom 16-bits C-Compiler v1.9 or higher

  • trunk/INSTALL/C/INSTALL.C

    r51 r54  
    995995        TotalCodeSectorsUsed--;
    996996    }
    997     if (Checksum!=*(PUSHORT)&Track0[0x11]) {
     997    if (Checksum!=*(PUSHORT) &Track0[0x11]) {
    998998        Status_Code = STATUS_CORRUPT;
    999999        return;                                      // Bad checksum for code
    … …  
    10021002    Installed_LanguageID  = Track0[0x0F];
    10031003    Installed_CodeVersion = (Track0[0x0D] << 8) | Track0[0x0E];
    1004     if (Installed_CodeVersion<Bootcode_Version)
     1004    if (Installed_CodeVersion < Bootcode_Version)
    10051005        Status_Code = STATUS_INSTALLEDMGU;                                         // Do upgrade
    10061006    else
    … …  
    10441044        }
    10451045        // Restore checksum
    1046         *(PUSHORT)&Track0[54 * BYTES_PER_SECTOR + 20] = ConfigChecksum;            // Config sector secnum hard-coded !
    1047         if (Checksum!=ConfigChecksum) {
     1046        *(PUSHORT) &Track0[54 * BYTES_PER_SECTOR + 20] = ConfigChecksum;            // Config sector secnum hard-coded !
     1047        if (Checksum != ConfigChecksum) {
    10481048            Status_Config = STATUS_CORRUPT;
    10491049            return;
    … …  
    10511051        // Checksum fine
    10521052        Installed_ConfigVersion = (Track0[54 * BYTES_PER_SECTOR + 0x0D] << 8) | Track0[54 * BYTES_PER_SECTOR + 0x0E];
    1053         if (Installed_ConfigVersion>=Bootcode_ConfigVersion) {
     1053        if (Installed_ConfigVersion >= Bootcode_ConfigVersion) {
    10541054            Status_Config = STATUS_INSTALLED;
    10551055            return;
    … …  
    10581058
    10591059        // Abort if unknown installed config version.
    1060         if ((Installed_ConfigVersion > 0x108)) {
     1060        if ((Installed_ConfigVersion > 0x110)) {
    10611061            if (!Option_CID) {
    10621062                printf("\n");
    … …  
    10681068
    10691069        // Abort if unknown to-install config version.
    1070         if ((Bootcode_ConfigVersion > 0x108)) {
     1070        if ((Bootcode_ConfigVersion > 0x110)) {
    10711071            if (!Option_CID) {
    10721072                printf("\n");
    … …  
    10791079
    10801080        // Those upgrades will copy useful configuration data to the image config
    1081         //  If new configuration data was added, those spaces are not overwritten
     1081        // If new configuration data was added, those spaces are not overwritten
    10821082        // Sector 60 (MBR-BackUp) *MUST BE* copied, otherwise it would be lost.
    10831083        // Rousseau: Upgrade from v0.27
    1084         if (Installed_ConfigVersion<=0x27) {
     1084        if (Installed_ConfigVersion <= 0x27) {
    10851085            // UPGRADE v0.27 and prior versions
    10861086
    … …  
    11071107        }
    11081108        // Rousseau: Upgrade from v0.91
    1109         if (Installed_ConfigVersion<=0x91) {
     1109        if (Installed_ConfigVersion <= 0x91) {
    11101110            // UPGRADE v0.91 and prior versions
    11111111            // Sector 55-57 no changes
    … …  
    11371137        /*
    11381138        // Convert v1.06 hideparttable (30x30) to the v1.07 (30x45) format.
    1139         // Also copy drive-letters to either v1.07 or v1.0.8 location.
     1139        // Also copy drive-letters to either v1.07 or v1.0.8+ location.
    11401140        */
    11411141        if ((Installed_ConfigVersion == 0x102) && (Bootcode_ConfigVersion >= 0x107)) {
    … …  
    11621162            }
    11631163
    1164             // Copy over drive-letters from v1.06 location to v1.08 location.
    1165             if (Bootcode_ConfigVersion == 0x108) {
     1164            // Copy over drive-letters from v1.06 location to v1.08+ location.
     1165            if ((Bootcode_ConfigVersion >= 0x108) && (Bootcode_ConfigVersion <= 0x110)) {
    11661166                memset(&Bootcode[0x6cb0], 0, 45);
    11671167                memcpy(&Bootcode[0x6cb0], &Track0[0x7584], 30);
    … …  
    11721172        // Convert v1.07 hideparttable (30x45) to a packed v1.0.8+ (45x45) format.
    11731173        */
    1174         if ((Installed_ConfigVersion < 0x108) && (Bootcode_ConfigVersion == 0x108)) {
     1174        if ((Installed_ConfigVersion < 0x108) && (Bootcode_ConfigVersion <= 0x110)) {
    11751175            int     i,j;
    11761176            char    c;
    … …  
    11881188                }
    11891189            }
    1190             // Copy temporary table to final v1.0.8 location (packed format)
     1190            // Copy temporary table to final v1.0.8+ location (packed format)
    11911191            memcpy(&Bootcode[0x7400], TempHidPartTable, 45 * 34);
    11921192            // Show LVM Drive Letters.
    … …  
    12831283    // All versions above v1.06 have expanded tables so the MBR-backup
    12841284    // is located 2 sectors higher in the track0 image.
    1285     if (Installed_ConfigVersion<=0x0106)
     1285    if (Installed_ConfigVersion <= 0x0106)
    12861286        bMbrBackup = Virus_CheckThisMBR((PCHAR) &Track0[59 * BYTES_PER_SECTOR]);
    12871287    else
    … …  
    12961296
    12971297    for (i=0; i<511; i++) {
    1298         if (*(PUSHORT)CurPtr==0x13CD) return FALSE;
     1298        if (*(PUSHORT)CurPtr == 0x13CD) return FALSE;
    12991299        CurPtr++;
    13001300    }
    … …  
    14181418    // Rousseau: # Keep compatible with v1.07 CRC #
    14191419    // AB v1.07 had bugs in writing the wrong number of AB config sectors.
    1420     // This is fixed in v1.0.8 but the CRC has to be calculated the "v1.07 way"
     1420    // This is fixed in v1.0.8+ but the CRC has to be calculated the "v1.07 way"
    14211421    // otherwise v1.07 SET(A)BOOT and AIRBOOT2.EXE will think the AB config
    14221422    // is corrupted.

  • trunk/INSTALL/C/INSTALL.H

    r51 r54  
    2828#define     BLDLVL_MINOR_VERSION    "8"
    2929// Build date
    30 #define     BLDLVL_YEAR             "2012"
    31 #define     BLDLVL_MONTH            "09"
    32 #define     BLDLVL_DAY              "09"
     30#define     BLDLVL_YEAR             "2013"
     31#define     BLDLVL_MONTH            "04"
     32#define     BLDLVL_DAY              "05"
    3333// Build time
    34 #define     BLDLVL_HOURS            "09"
    35 #define     BLDLVL_MINUTES          "09"
    36 #define     BLDLVL_SECONDS          "09"
     34#define     BLDLVL_HOURS            "01"
     35#define     BLDLVL_MINUTES          "00"
     36#define     BLDLVL_SECONDS          "08"
    3737// Build machine
    3838//#define     BLDLVL_MACHINE          "ecs-devbox"

  • trunk/INSTALL/DOS/AIRBOOT.ASM

    r37 r54  
    1818
    1919;JUMPS
     20
     21;
     22; THIS SOURCE IS OBSOLETE AND IS REPLACED BY THE C-EQUIVALENT.
     23;
    2024
    2125Include ../../INCLUDE/ASM.INC

  • trunk/TOOLS/INTERNAL/FIXCODE.C

    r51 r54  
    190190    /*
    191191    // Count Code Sectors.
    192     // Obsolete now because since v1.0.8 the Protection Image has moved just
     192    // Obsolete now because since v1.0.8+ the Protection Image has moved just
    193193    // below the Configuration and the code is always max. size.
    194194    // Overlap checking is done while assembling AIR-BOOT.ASM.

  • trunk/TOOLS/OS2/SETABOOT/Makefile

    r51 r54  
    297297dist:   .SYMBOLIC
    298298        @if exist *.EXE $(CP) *.EXE ..$(DS)..$(DS)..$(DS)RELEASE$(DS)OS2
    299 
     299        @if exist *.EXE $(CP) *.EXE ..$(DS)..$(DS)..$(DS)RELEASE$(DS)BOOTCODE
    300300#
    301301# Help on using this Makefile.

  • trunk/TOOLS/OS2/SETABOOT/SETABOOT.C

    r46 r54  
    478478   //puts ("SETABOOT - AiR-BOOT Configuration Utility (OS/2) - (c) 2004-2009 by M. Kiewitz");
    479479   //puts ("SETABOOT v1.07a - AiR-BOOT Configuration Utility - (c) 2004-2011 by M. Kiewitz");
    480    puts ("SETABOOT v1.0.8 - AiR-BOOT Configuration Utility - (c) 2004-2012 by M. Kiewitz");
     480   puts ("SETABOOT v"
     481    BLDLVL_MAJOR_VERSION"."
     482    BLDLVL_MIDDLE_VERSION"."
     483    BLDLVL_MINOR_VERSION" - AiR-BOOT Configuration Utility - (c) 2004-"
     484    BLDLVL_YEAR
     485    " by M. Kiewitz");
    481486
    482487
    … …  
    976981   // Rousseau: # Keep compatible with v1.07 CRC #
    977982   // AB v1.07 had bugs in writing the wrong number of AB config sectors.
    978    // This is fixed in v1.0.8 but the CRC has to be calculated the "v1.07 way"
     983   // This is fixed in v1.0.8+ but the CRC has to be calculated the "v1.07 way"
    979984   // otherwise v1.07 SET(A)BOOT and INSTALL2.EXE will think the AB config
    980985   // is corrupted.

  • trunk/TOOLS/OS2/SETABOOT/SETABOOT.H

    r51 r54  
    1414#define     BLDLVL_MINOR_VERSION    "8"
    1515// Build date
    16 #define     BLDLVL_YEAR             "2012"
    17 #define     BLDLVL_MONTH            "09"
    18 #define     BLDLVL_DAY              "09"
     16#define     BLDLVL_YEAR             "2013"
     17#define     BLDLVL_MONTH            "04"
     18#define     BLDLVL_DAY              "05"
    1919// Build time
    20 #define     BLDLVL_HOURS            "09"
    21 #define     BLDLVL_MINUTES          "09"
    22 #define     BLDLVL_SECONDS          "09"
     20#define     BLDLVL_HOURS            "01"
     21#define     BLDLVL_MINUTES          "00"
     22#define     BLDLVL_SECONDS          "08"
    2323// Build machine
    2424//#define     BLDLVL_MACHINE          "ecs-devbox"
Note: See TracChangeset for help on using the changeset viewer.