Atarimax "Maxflash" Flash MultiCarts

Preliminary Documentation, 07/10/2003

©2003 Steven J Tucker

Important Notice!

The software described below has been superceded by the new Maxflash Studio software application.

This software is still supported for advanced users, but all new users should try the Maxflash Studio suite located here before attempting to use these programs and scripts.

Chapter 5: Using the MaxFlash software.

Table of Contents

  1. Introduction
  2. Key Options
  3. -EXEPACKER Option (Multi-Cart generator)
  4. -DISKPACKER Option (Disk-Cart generator)
  5. -MEMPACKER Option (A8S-Cart generator)
  6. Utility Options
    1. -BIN2ALL
    2. -BIN2CART
    3. -BIN2ATR
    4. -SEGCHECK and -FIXSEG

Introduction

The maxflash software has three main options for creating cartridge images, and a number of support functions.

Execute the maxflash.pl script using the Perl interpreter as perl maxflash.pl

MAXFLASH Multicart Build/Utility Script - c2003 Steven J Tucker
Information and updates at http://www.atarimax.com/

usage: perl maxflash.pl [switches] [hacks] [disk.atr] [cartridge.bin] [dump.a8s]

switches: -4MB        (*) Create image for 4Mb cartridge. (default is 1Mb)
          -8MB        (*) Create image for 8Mb cartridge. (default is 1Mb)
          -ALTPTR     (E) Use alternate address for Atari EXE loader.
          -BASIC      (D) Enable BASIC. (For packing disks that use BASIC)
          -BATCH      (*) Never prompt for optional information.
          -BIN2ALL    (U) Make existing BIN file into CART/ATR images.
          -BIN2ATR    (U) Make existing BIN file into flash programming image.
          -BIN2CART   (U) Make existing BIN file into Atari800 CART image.
          -CART       (*) Write file with Atari800 cartridge header.
          -CHEESE     (E) Enable DLIs, sounds and colors in EXE menu.
          -COLORS     (*) Fill color registers while working. (debug)
          -DISKPACKER (K) Pack ATR image into cartridge using MAXFLASH driver.
          -EXEPACKER  (K) Create multi-cart image using directory of EXE files.
          -FASTKEYS   (E) Faster selection in EXE loader menu.
          -FIXSEG     (U) Combine with -SEGCHECK to try and fix an EXE file.
          -FLASHER    (*) Make bootable ATR image for programming MAXFLASH cart
          -HOLMES     (D) Try to follow archive directives (-bas, -osb, etc).
          -LOFLICKER  (D) Reduce flickering in some modes.
          -LOMEM      (D) Force HIMEM to A000 after installation.
          -MEMPACKER  (K) Pack Atari800 A8S image into cartridge.
          -NOBIN      (*) Delete raw binary after processing.
          -NODISK     (D) Create image with blank disk area.
          -NOEXE      (E) Erase EXE files after packing with -EXEPACKER option.
          -OSB        (*) Build automatic OS-B translator into cartridge.
          -PALHACK    (D) Force OS to detect GITA as PAL.
          -RECURSIVE  (*) Process sub-directories in directory mode.
          -REINIT     (E) Force EXE loader to enter RUN vector via warmstart
          -SEGCHECK   (U) Display segment information in an Atari EXE file.
          -TRANSLATOR (D) Replace OS but not not install any drivers.
          -TRIGGERS   (D) Enable sector triggers.
          -UNDEROS    (M) Unpack memory under OS.
          -VERBOSE    (*) Display useless information.

hacks:    @PORTB      (*) Delete writes to PORT B in image.

Each switch is designated a function class, these are:

When you use the maxflash.pl script, you must always specify at least one (K)ey option or one (U)tility option. All the other switches modify the behavior of these functions.

Switches, filenames and directories can be placed in any order.

Key Options

Key options are designated with the (K) marker. These key options are:

          -EXEPACKER  (K) Create multi-cart image using directory of EXE files.
          -DISKPACKER (K) Pack ATR image into cartridge using MAXFLASH driver.
          -MEMPACKER  (K) Pack Atari800 A8S image into cartridge.

Using the -EXEPACKER option to create a "Muticart"

The exepacker option of the maxflash script it used to automatically generate a fully functional Atari 8-bit multicart image, using only Atari Game/Utility EXE files as a source.

All the work of packing the programs, creating a menu, fitting it on a cartridge and building the final burn image is handled automatically.

MultiCarts created with the -EXEPACKER option will work on any Atari computer, they require no OS functions to operate.

Here is an example of the -exepacker option being used to create a 1Mb flash cartridge image:

>perl maxflash.pl -exepacker -cheese -altptr -cart "Z:\Jellystone Park Archive\games\exe\A-C" MyMultiCart.bin

MAXFLASH Multicart Build/Utility Script - c2003 Steven J Tucker
Information and updates at http://www.atarimax.com/

Looking over EXE files in Z:/Jellystone Park Archive/games/exe/A-C

Using ARENA.exe (7999 bytes), 114881 bytes remaining.
Using ATLANTIS.exe (8334 bytes), 106547 bytes remaining.
Using AceyDuecy.exe (15370 bytes), 91177 bytes remaining.
Using ActionQuest.exe (10440 bytes), 80737 bytes remaining.
Using Adax.exe (33224 bytes), 47513 bytes remaining.
Using Adventure 7 Mystery Fun.exe (19983 bytes), 27530 bytes remaining.
Using AdventureCreator.exe (16491 bytes), 11039 bytes remaining.
Using AdventuresOfMrFish.exe (8797 bytes), 2242 bytes remaining.
Using Amazed.exe (1743 bytes), 499 bytes remaining.
Skipped Anteater.exe, may be damaged, run -SEGCHECK on it.

Assembled 9 files with 499 bytes of slack.

By default the names of the images that appear on the menu of the
flash cartridge will be the same as the files they were taken
from.

You can choose new menu descriptions here, or just
press Enter to keep what is shown (34 characters maximum).

Title                      [ARENA] :
Title                   [ATLANTIS] :
Title                  [AceyDuecy] :
Title                [ActionQuest] :
Title                       [Adax] :
Title    [Adventure 7 Mystery Fun] :
Title           [AdventureCreator] :
Title         [AdventuresOfMrFish] :
Title                     [Amazed] :

Please enter a title for this cartridge.  This text will
appear at the top-most line of the multicart menu.  Just
press enter to keep the default description

Cartridge Title: [ATARIMAX Flash Multicart EXE Loader] :

Saved new binary flash image to MyMultiCart.bin
Saved new Atari800 "CART" image to MyMultiCart.car

E:\maxflash>

The resulting cartridge in use

Click on the picture to see a video of the cartridge in use.
(requires free XviD codec for playback)

When using the -EXEPACKER option, you must also specify:

In the example above, there were options used in addition to those required:

-CHEESEEnables cheesy DLI colors/sounds in MultiCart menu
-ALTPTRMove EXE unpacker to alternate address
-CARTGenerate a Atari800 cartridge image for testing cartridge in emulator.

Some other options that you might use when making a multi-cart are:

-4MB/-8MBMake a larger Multicart for 4Mb or 8Mb cartridge
-OSBRun "400/800 Only" software on XL/XE machines (Translator)
-FASTKEYSMake menu scrolling/selection faster
-COLORSEnable color-register packing while unpacking. Debugging option
-FLASHERCreate the final flash cartridge ATR programming image
-NOBINDelete .bin file after script is finished
-NOEXEDelete .exe files after inserting to cartridge image
-REINITStart MultiCart selection via warmstart vector
-VERBOSEPrint debugging information while script is working

Packing the EXE files

When you use the -EXEPACKER option and specify a directory containing Atari EXE files, the script will try to fit as many of the files on the cartridge as possible.

For example here is the output of the packing portion of the script.

Looking over EXE files in Z:/Jellystone Park Archive/games/exe/A-C
 
Using ARENA.exe (7999 bytes), 114881 bytes remaining.
Using ATLANTIS.exe (8334 bytes), 106547 bytes remaining.
Using AceyDuecy.exe (15370 bytes), 91177 bytes remaining.
Using ActionQuest.exe (10440 bytes), 80737 bytes remaining.
Using Adax.exe (33224 bytes), 47513 bytes remaining.
Using Adventure 7 Mystery Fun.exe (19983 bytes), 27530 bytes remaining.
Using AdventureCreator.exe (16491 bytes), 11039 bytes remaining.
Using AdventuresOfMrFish.exe (8797 bytes), 2242 bytes remaining.
Using Amazed.exe (1743 bytes), 499 bytes remaining.
Skipped Anteater.exe, may be damaged, run -SEGCHECK on it.
 
Assembled 9 files with 499 bytes of slack.

EXAMPLE 8Mb Cartridge

Click on photo to see video of complete Multi-Cart menu.
(requires free XviD codec for playback)

As each file is added the script displays how large each file is after processing and how much space is left on the cartridge.

If the script encounters and Atari EXE files that appear to be broken or unloadable, it will display a message asking you to manually run the -SEGCHECK option on that file to try and fix it.

In the example above, after all the EXE files were added and all the options processed, there were 499 bytes of 'slack' left over.

This is the total unused space left on the cartridge. Its normal to have some slack left over since not may Atari EXE files will fit into a 499 byte window.

If any of the files you want to use are reported as broken, try running the maxflash.pl script on those files using the -SEGCHECK and -FIXSEG options to try and repair the file automatically.


Choosing the Menu Descriptions

When packing the EXE files into the MultiCart image, the script will use the filename of the EXE files as the menu descriptor that will appear when the cartridge is inserted.

For example, if you pack a EXE game called ArchonII_CrackedByYogi.EXE, the script will by default use ArchonII_CrackedByYogi as the description on the Atari menu.

Since you might want nicer looking game descriptions in your cartridge, the script will prompt you to change each filename if you desire to do so.

By default the names of the images that appear on the menu of the
flash cartridge will be the same as the files they were taken
from.
 
You can choose new menu descriptions here, or just
press Enter to keep what is shown (34 characters maximum).
 
Title                      [ARENA] :
Title                   [ATLANTIS] :
Title                  [AceyDuecy] : 
Title                [ActionQuest] :
Title                       [Adax] :
Title    [Adventure 7 Mystery Fun] : 
Title           [AdventureCreator] :
Title         [AdventuresOfMrFish] :
Title                     [Amazed] :

The text in the brackets, for example [ARENA] is the default menu description for the item shown. To keep that description, just press ENTER. Otherwise type the new title and press ENTER.

Keep in mind the Atari has limited screen width, so keep the description under 34 characters long.

Choosing the Cartridge Title

Once you have assigned a name to each MultiCart selection, you may change the title shown on the game selection menu if you choose.

Please enter a title for this cartridge.  This text will
appear at the top-most line of the multicart menu.  Just
press enter to keep the default description
 
Cartridge Title: [ATARIMAX Flash Multicart EXE Loader] :

This string will appear in the top bar of the MultiCart selection menu. Maximum length of this field is 40 characters.

Image Generation

Once you have selected a cartridge title, the script will do the final assembly and generate the images you requested.

Saved new binary flash image to MyMultiCart.bin
Saved new Atari800 "CART" image to MyMultiCart.car

Depending on the options you selected, it will generate the following images:

YourTitle.BINThe raw cartridge image with no header.
YourTitle.CARAn Atari800 CART image for testing your cartridge in an emulator.
YourTitle.ATRAn ATR disk image that may be used to program your cart image onto a real flash cartridge.

The .BIN image will always be generated. You can specify the -NOBIN option if you would like the script to automatically erase it when it is finished using it. The .CAR image will only be generated if the -CART option was specified. The .ATR image will only be generated if the -FLASHER option was specified.

While a .CAR image makes it easier to load the image into Atari800, you can also use the .BIN image. If you choose to load the .BIN image into Atari800, the emulator will prompt you to select the correct cartridge type.

Testing your cartridge in the emulator before using it to program a real cartridge will save you time and effort if there are any changes that still need to be made.

See Chapter 3 for instructions on how to use the .ATR image to program your flash cartridge.

Using the -DISKPACKER option to create a "Disk Cartridge"

Note: These instructions are for single-disk 1Mb cartridges only.

The -DISKPACKER option of the maxflash script it used to automatically convert an Atari 8-bit disk based game to cartridge, using only a standard ATR image as the source.

All the work of packing the program, fitting it on a cartridge, patching the OS, and creating the final burn image is handled automatically.

Disk carts made with the -DISKPACKER (automatic conversion) option require an XL/XE model computer to operate.

Here is an example of the -DISKPACKER option being used to turn the Infocom game 'Zork I' into a cartridge:

>perl maxflash.pl -diskpacker "Z:\Jellystone\atr\T-Z\Zork I.atr" zork_i.bin -cart -flasher
 
MAXFLASH Multicart Build/Utility Script - c2003 Steven J Tucker
Information and updates at http://www.atarimax.com/
 
New binary image [zork_i.bin] created.
Saved new Atari800 "CART" image to zork_i.car
 
When you load the flash cartridge programming disk on the Atari Computer
it will display the title of the software to be programmed.  You can change
what is displayed, or just press ENTER to keep what is shown.  Note: you
may use a maximum of 34 characters in this field.
 
Title       [zork_i] : Zork I The Great Underground Empire
 
Saved new cartridge programming image to "zork_i (maxflash image).atr"

EXAMPLE Disk Cartridge

Click on photo to see video of cartridge in use.
(requires free XviD codec for playback)

When using the -DISKPACKER option, you must also specify:

In the example above, there were options used in addition to those required:

-FLASHERGenerate the final ATR image used to burn data onto cartridge.
-CARTGenerate a Atari800 cartridge image for testing cartridge in emulator.

Some other options that you might use when making a disk-cart are:

-4MB/-8MBMake a larger multi-disk image for 4Mb or 8Mb cartridge
-OSBChange OS to Atari 800 OSB for running non XL/XE software. (Translator)
-BASICEnable BASIC for software on this cartridge image.
-COLORSEnable color-register packing while unpacking. Debugging option
-FLASHERCreate the final flash cartridge ATR programming image.
-HOLMESTry to figure out what options to use from looking at the filename.
-LOFLICKERReduce/eliminate flicker by timing access to cartridge.
-LOMEMDisable access to upper 16k of RAM (Force cart detection).
-VERBOSEPrint debugging information while script is working
-NODISKCreate a blank disk-cart with no disk image.
-PALHACKForce OS to believe GTIA is PAL.
-TRANSLATORCreate a 'translator cartridge'. (Do not patch OS)
-TRIGGERSEnable disk-flipping code. (See Advanced Options)

ALI-BABA WITH TRANSLATOR (-OSB)

Click on photo to see video of cartridge in use.
(requires free XviD codec for playback)

Not all disk images can be automatically converted to cartridge. Most utility disks work fine, for example making a DOS cartridge is generally as easy as making the Zork cartridge shown above.

Cartridges that don't work properly with automatic conversion include those that bypass the Atari OS SIO routines, overwrite the OS region, and fiddle with PORT B.

Generally speaking with some small effort in the emulator, most games can be made to work. Most just require a very small modification to avoid PORT B re-initialization.

Hundreds of games from the Holmes and Jellystone park archive have already been converted by the Beta Test team as of 07/10/2003. Check the archive and the forum to see if someone has already converted the utility/game your working on, it might save you some time.

See the Custom Conversions chapter and the Mule Cartridge Tutorial for more information on how to use the modified Atari800Win emulator to make these conversions easily and for information on how to convert disk games so they will run on non XL/XE hardware.


Setting the Programming Image Title

When you load the flash cartridge programming disk on the Atari Computer
it will display the title of the software to be programmed.  You can change
what is displayed, or just press ENTER to keep what is shown.  Note: you
may use a maximum of 34 characters in this field.
  
Title       [zork_i] : Zork I The Great Underground Empire
  
Saved new cartridge programming image to "zork_i (maxflash image).atr"

During image creation, you will be prompted for a verbose image title. This title will show up on the main screen of the flash programming software when it is started.

Image Generation

Once you have selected a cartridge title (if the -FLASHER option was used), the script will do the final assembly and generate the images you requested.

Saved new binary flash image to MyMultiCart.bin
Saved new Atari800 "CART" image to MyMultiCart.car

Depending on the options you selected, it will generate the following images:

YourTitle.BINThe raw cartridge image with no header.
YourTitle.CARAn Atari800 CART image for testing your cartridge in an emulator.
YourTitle.ATRAn ATR disk image that may be used to program your cart image onto a real flash cartridge.

The .BIN image will always be generated. You can specify the -NOBIN option if you would like the script to automatically erase it when it is finished using it. The .CAR image will only be generated if the -CART option was specified. The .ATR image will only be generated if the -FLASHER option was specified.

While a .CAR image makes it easier to load the image into Atari800, you can also use the .BIN image. If you choose to load the .BIN image into Atari800, the emulator will prompt you to select the correct cartridge type.

Testing your cartridge in the emulator before using it to program a real cartridge will save you time and effort if there are any changes that still need to be made.

See Chapter 3 for instructions on how to use the .ATR image to program your flash cartridge.

Using the -MEMPACKER option to create a A8S Unpacker Cartridge

The A8S support using the -MEMPACKER option was put in mostly to demonstrate how to unpack memory using the cartridge. The functionality of this option is limited, and since 99% of software you might use the -MEMPACKER option for will work using one of the other options, it will likely remain so.

The -MEMPACKER option of the maxflash.pl script is used to automatically convert an Atari800 .A8S emulator state save into a cartridge image.

All the work of packing the image, fitting it on a cartridge, patching the OS, and creating the final burn image is handled automatically.

Cartridges made with the -MEMPACKER option have no special hardware requirements. If the -UNDEROS option is used the cartridge will attempt to unpack the memory under the OS that exists only on XL/XE models.

Here is an example of the -MEMPACKER option being used to turn a Bounty Bob Strikes Back state save into a cartridge:

>perl maxflash.pl -mempacker -underos T:\bounty_bob.a8s bbsb.bin -cart -flasher -colors
 
MAXFLASH Multicart Build/Utility Script - c2003 Steven J Tucker
Information and updates at http://www.atarimax.com/
 
New image [bbsb.bin] created.
Saved new Atari800 "CART" image to bbsb.car
 
When you load the flash cartridge programming disk on the Atari Computer
it will display the title of the software to be programmed.  You can change
what is displayed, or just press ENTER to keep what is shown.  Note: you
may use a maximum of 34 characters in this field.
 
Title         [bbsb] : Bounty Bob Strikes Back!
 
Saved new cartridge programming image to "bbsb (maxflash image).atr"

BOUNTY BOB STRIKES BACK

Click on photo to see video of cartridge in use.
(requires free XviD codec for playback)

When using the -MEMPACKER option you must also specify:

In the example above, there were options used in addition to those required:

-FLASHERGenerate the final ATR image used to burn data onto cartridge.
-CARTGenerate a Atari800 cartridge image for testing cartridge in emulator.
-UNDEROSUnpack saved memory under the OS as well.
-COLORSDisplay colors while unpacking to memory. Debug option.

Some other options that you might use when making a disk-cart are:

-OSBChange OS to Atari 800 OSB for running non XL/XE software. (Translator)
-VERBOSEPrint debugging information while script is working
-PALHACKForce OS to believe GTIA is PAL.

Note that the -COLOR option is intended for debugging. If you view the on this page you will see that while unpacking a lot of seemingly random colors are displayed to show the unpacking progress.

Current limitations using the -MEMPACKER option. (TODO list)

Image Generation

Once you have selected a cartridge title (if the -FLASHER option was used), the script will do the final assembly and generate the images you requested.

New image [bbsb.bin] created.

Depending on the options you selected, it will generate the following images:

YourTitle.BINThe raw cartridge image with no header.
YourTitle.CARAn Atari800 CART image for testing your cartridge in an emulator.
YourTitle.ATRAn ATR disk image that may be used to program your cart image onto a real flash cartridge.

The .BIN image will always be generated. You can specify the -NOBIN option if you would like the script to automatically erase it when it is finished using it. The .CAR image will only be generated if the -CART option was specified. The .ATR image will only be generated if the -FLASHER option was specified.

While a .CAR image makes it easier to load the image into Atari800, you can also use the .BIN image. If you choose to load the .BIN image into Atari800, the emulator will prompt you to select the correct cartridge type.

Testing your cartridge in the emulator before using it to program a real cartridge will save you time and effort if there are any changes that still need to be made.

See Chapter 3 for instructions on how to use the .ATR image to program your flash cartridge.

Utility Options

The maxflash.pl script contains a number of stand-alone utility functions. These functions are designated by the (U) flag in the switch listing.

          -BIN2ALL    (U) Make existing BIN file into CART/ATR images.
          -BIN2ATR    (U) Make existing BIN file into flash programming image.
          -BIN2CART   (U) Make existing BIN file into Atari800 CART image.
          -SEGCHECK   (U) Display segment information in an Atari EXE file.
          -FIXSEG     (U) Combine with -SEGCHECK to try and fix an EXE file.

-BIN2ALL

Syntax: perl maxflash.pl -BIN2ALL FILENAME.BIN

The BIN2ALL option takes an existing .BIN file previously generated by the script, then converts it to both a Atari800 CART image (.CAR) and a flash cartridge programming image (.ATR).

This allows you to take any arbitrary code, even code not generated by the script and convert it to a flash programming image.

Any content in the .BIN file supplied will be programmed into your cartridge.

-BIN2ATR

Syntax: perl maxflash.pl -BIN2ATR FILENAME.BIN

The same as -BIN2ALL above, except only the flash programming image (.ATR) is generated.

-BIN2CART

Syntax: perl maxflash.pl -BIN2CART FILENAME.BIN

The same as -BIN2ALL above, except only the Atari800 CART image is generated.

-SEGCHECK

Syntax: perl maxflash.pl -SEGCHECK [-FIXSEG] ATARIGAME.EXE

This option will analyze the segments in an Atari EXE file and optionally try to correct any errors.

MAXFLASH Multicart Build/Utility Script - c2003 Steven J Tucker
Information and updates at http://www.atarimax.com/
 
Checking segments in Z:\Jellystone\A-C\Archon II Adept.exe
 
Header marker 0xFFFF at 0x0000
Valid segment [0x2D80 - 0x2FFC] at 0x0002
Valid segment [0xD01F - 0xD01F] at 0x0283
Valid segment [0x02E2 - 0x02E3] at 0x0288
Segment sets immediate INIT address of 0x2D80
Valid segment [0x02E0 - 0x02E1] at 0x028E
Segment sets RUN address of 0x2DB6
Header marker 0xFFFF at 0x0294
Warning: Ignoring extraneous header embedded in file.
Valid segment [0x3000 - 0x49FF] at 0x0296
Header marker 0xFFFF at 0x1C9A
Warning: Ignoring extraneous header embedded in file.
Valid segment [0x49DE - 0xBA5D] at 0x1C9C
Valid segment [0x1A1A - 0x1A1A] at 0x8D20
Warning: Ignoring junk segment. (transfer padding)
Valid segment [0x1A1A - 0x1A1A] at 0x8D25
Warning: Ignoring junk segment. (transfer padding)
Valid segment [0x1A1A - 0x1A1A] at 0x8D2A
Warning: Ignoring junk segment. (transfer padding)
Valid segment [0x1A1A - 0x1A1A] at 0x8D2F
Warning: Ignoring junk segment. (transfer padding)
Valid segment [0x1A1A - 0x1A1A] at 0x8D34
Warning: Ignoring junk segment. (transfer padding)
Valid segment [0x1A1A - 0x1A1A] at 0x8D39
Warning: Ignoring junk segment. (transfer padding)
Valid segment [0x1A1A - 0x1A1A] at 0x8D3E
Warning: Ignoring junk segment. (transfer padding)
Valid segment [0x1A1A - 0x1A1A] at 0x8D43
Warning: Ignoring junk segment. (transfer padding)
Valid segment [0x1A1A - 0x1A1A] at 0x8D48
Warning: Ignoring junk segment. (transfer padding)
Valid segment [0x1A1A - 0x1A1A] at 0x8D4D
Warning: Ignoring junk segment. (transfer padding)
Warning: Ignoring junk segment. (transfer padding)
Warning: Ignoring 1 bytes of extra data at end of file.
 
Process completed with 22 warnings and 0 errors.
 
New filename: [Archon II Adept_fixseg.exe] : archon_ii_fixed.exe
 
Wrote archon_ii_fixed.exe, 36124 bytes.
 
MAXFLASH Multicart Build/Utility Script - c2003 Steven J Tucker
Information and updates at http://www.atarimax.com/
 
Checking segments in archon_ii_fixed.exe
 
Header marker 0xFFFF at 0x0000
Valid segment [0x2D80 - 0x2FFC] at 0x0002
Valid segment [0xD01F - 0xD01F] at 0x0283
Valid segment [0x02E2 - 0x02E3] at 0x0288
Segment sets immediate INIT address of 0x2D80
Valid segment [0x02E0 - 0x02E1] at 0x028E
Segment sets RUN address of 0x2DB6
Valid segment [0x3000 - 0x49FF] at 0x0294
Valid segment [0x49DE - 0xBA5D] at 0x1C98
 
Process completed with 0 warnings and 0 errors.

Note that unless -FIXSEG is specified this option will only report the errors.

To save a new, fixed EXE file, combine -SEGCHECK with the -FIXSEG option.

If you specify the -FIXSEG option, you will be prompted for a new filename to save the fixed EXE file in.

Once -FIXSEG completes, the script will re-invoke the -SEGCHECK option to check the fixed EXE file.

Unless you receive a warning during packing with the -EXEPACKER option that a file is broken, you do not need to pre-process your files with the -SEGCHECK or -FIXSEG options.