Omnivore, the Atari 8-bit Binary Editor

[playermissile]

That happens for me as well. I haven't tried the bitmap scrolling yet.

 

I've fixed both these issues; I'll post a new version tonight.

[AtariGeezer]

 

Long term, probably. Looks complicated, though. Found a reference here for the extended binary file format: http://sdx.atari8.info/sdx_files/4.47/sdx_4-47_progr_guide.pdfbut didn't see a reference to the on-disk structure. Any pointers? I think the directory & VTOC are totally different than Atari DOS, right?

Check out this page on Sparta format: http://atari.kensclassics.org/dos.htm

[playermissile]

Check out this page on Sparta format: http://atari.kensclassics.org/dos.htm

 

I've used that page before but never understood the SpartaDOS stuff before. Does this mean that the bitmap sectors are always contiguous? And are sector maps stored at the beginning of each file, so that the file data comes right after the sector map?

 

I have a bunch of other questions, but I suppose I should start a different thread for low-level SpartaDOS hacking.

[flashjazzcat]

Does this mean that the bitmap sectors are always contiguous?

Yes, contiguous starting at the sector pointed to by the 16-bit word at $10 in the boot sector.

 

And are sector maps stored at the beginning of each file, so that the file data comes right after the sector map?

No. Sector maps are pointed to by directory entries, and a sector map in turn comprises a list of that file's data sectors, which may be anywhere on the disk. The first two words of the each sector map sector form a doubly linked list of sectors in the map.

Edited February 3, 2016 by flashjazzcat

[AtariGeezer]

 

I've used that page before but never understood the SpartaDOS stuff before.

I have a bunch of other questions, but I suppose I should start a different thread for low-level SpartaDOS hacking.

 

Does this mean that the bitmap sectors are always contiguous?

Not always, there are 4 bytes in the beginning of each bitmap sector that points to the previous bitmap sector and the next bitmap sector of a directory or file bitmap. If a file is deleted from a disk and another is added later, it's possible that a bitmap sector won't be contiguous.

 

Edit: For bitmap sectors in relation to a VTOC, they should be...

 

 

And are sector maps stored at the beginning of each file, so that the file data comes right after the sector map?

The first one usually is, but Not Guaranteed, you have to look at the sector map to be sure...

Edited February 3, 2016 by AtariGeezer

[playermissile]

No. Sector maps are pointed to by directory entries, and a sector map in turn comprises a list of that file's data sectors, which may be anywhere on the disk. The first two words of the each sector map sector form a doubly linked list of sectors in the map.

 

Not always, there are 4 bytes in the beginning of each bitmap sector that points to the previous bitmap sector and the next bitmap sector of a directory or file bitmap. If a file is deleted from a disk and another is added later, it's possible that a bitmap sector won't be contiguous.

 

OK, I think I'm getting it now. Bitmap sectors (e.g. SpartaDOS's VTOC) are contiguous, pointed to by $10 in the boot sector. Directory sector map is located in the boot sector. Directory entries are stored in a file just like regular files. Sector maps contain list of sectors used by the file, in the order they should be read in to load the file into memory.

[flashjazzcat]

Exactly. Sector maps are not to be confused with bitmaps.

[AtariGeezer]

Exactly. Sector maps are not to be confused with bitmaps.

True , as per my edited post above... (Still waking up here)

Edited February 3, 2016 by AtariGeezer

[eccofonic]

When trying to start up Omnivore after install, on Windows XP SP3 I get a box that says:

 

"Unable to execute file.

CreateProcess failed; code 14001."

 

And then upon trying again:

 

"This application failed to start because the application configuration is incorrect."

 

Edit: I installed the Visual C++ 9.0 libraries and it worked.

Edited February 4, 2016 by eccofonic

[playermissile]

When trying to start up Omnivore after install, on Windows XP SP3 I get a box that says:

 

"Unable to execute file.

CreateProcess failed; code 14001."

 

And then upon trying again:

 

"This application failed to start because the application configuration is incorrect."

 

Edit: I installed the Visual C++ 9.0 libraries and it worked.

 

Huh, I thought that I was including the correct VC++ 9.0 libraries. Maybe that means I need to add a manifest file? My Windows dev skills are zero, but I remember something about that when I was using XP. I'm building on Win 7 and it's not requiring a manifest file. Any ideas?

[devwebcl]

I am using Mac OS X Yosemite, and I get

 

File "setup.py", line 64, in <module>
import traitsui
ImportError: No module named traitsui

 

 

using enthought ?

[fujidude]

 

Huh, I thought that I was including the correct VC++ 9.0 libraries. Maybe that means I need to add a manifest file? My Windows dev skills are zero, but I remember something about that when I was using XP. I'm building on Win 7 and it's not requiring a manifest file. Any ideas?

 

Try PyInstaller. I think it might take include a manifest; not sure though.

[Kyle22]

 

Huh, I thought that I was including the correct VC++ 9.0 libraries. Maybe that means I need to add a manifest file? My Windows dev skills are zero, but I remember something about that when I was using XP. I'm building on Win 7 and it's not requiring a manifest file. Any ideas?

No big deal. It's easy to find. Here it is if anyone needs it. https://www.microsoft.com/en-us/download/details.aspx?id=8328

[playermissile]

I am using Mac OS X Yosemite, and I get

 

File "setup.py", line 64, in <module>

import traitsui

ImportError: No module named traitsui

 

using enthought ?

 

Yes, using a hacked version of Enthought's libraries to support additional features of wxPython. I have an error in the README which I will fix; if you check out the source from github, the hacked Enthought libs are not included, so you have to run the script ./rebuild-enthough.sh in order to check out all the libs and put them in the correct places. Then setup.py should work.

 

Or you can download the source distribution from https://github.com/robmcmullen/omnivore/releaseswhich bundles my hacked Enthought libs.

[playermissile]

Try PyInstaller. I think it might take include a manifest; not sure though.

 

Still haven't worked up to PyInstaller; I was able to get the win32 executable working using py2exe. I guess my real problem isn't including the manifest file, it's the contents of the manifest file itself. How do you tell it to include the MSVCP90.dll file? Or maybe that's not even my problem?

[Kyle22]

I used EMCO MSI Package Builder to make an Omnivore installer that includes the MSVCP90.DLL file, but it's too large to upload here (15.3M).

If you have that tool, you can use it and put the file up on your github site.

[playermissile]

No big deal. It's easy to find. Here it is if anyone needs it. https://www.microsoft.com/en-us/download/details.aspx?id=8328

 

I'll include a link in the README.

 

I used EMCO MSI Package Builder to make an Omnivore installer that includes the MSVCP90.DLL file, but it's too large to upload here (15.3M).

If you have that tool, you can use it and put the file up on your github site.

 

I'm using the NSIS installer, but I'm sure I ran into this problem before. Maybe I just have to copy it over manually before I create the package. Did you just include it in the root folder where all the wx*.dll files are included?

[Kyle22]

It lives in %WINDIR%\SYSTEM32 on my machine, or you should be able to put it in the same folder as omnivore.exe.

 

Edit: you may need to register it before use. regsvr32 /i msvcp90.dll

Edited February 4, 2016 by Kyle22

[playermissile]

It lives in %WINDIR%\SYSTEM32 on my machine, or you should be able to put it in the same folder as omnivore.exe.

 

Edit: you may need to register it before use. regsvr32 /i msvcp90.dll

 

I've got it included in the installer now, so hopefully that will work. I have found a few old XP virtual machines, but none without VC++ 9.0 already installed so I don't have a good test system.

[fujidude]

Still haven't worked up to PyInstaller; I was able to get the win32 executable working using py2exe. I guess my real problem isn't including the manifest file, it's the contents of the manifest file itself. How do you tell it to include the MSVCP90.dll file? Or maybe that's not even my problem?

 

I find it pretty easy to use. Here is a list of the Windows specific features. It seems to handle the C++ run time issue:

• Windows-specific features:
  • Support for code-signing executables (see Recipe Win Code Signing for details).
  • Full automatic support for CRTs: no need to manually distribute MSVCR*.DLL, redist installers, manifests, or anything else; true one-file applications that work everywhere!
  • Selectable executable icon.
  • Fully configurable version resource section and manifests in executable.
  • Configurable .exe requirement running as administrator - UAC admin (PyInstaller 2.2+)

Here is the command syntax for the PyInstaller program:

Usage: pyinstaller [opts] <scriptname> [ <scriptname> ...] | <specfile>

Options:
  -h, --help            show this help message and exit
  -v, --version         Show program version info and exit.
  --distpath=DIR        Where to put the bundled app (default: .\dist)
  --workpath=WORKPATH   Where to put all the temporary work files, .log, .pyz
                        and etc. (default: .\build)
  -y, --noconfirm       Replace output directory (default:
                        SPECPATH\dist\SPECNAME) without asking for
                        confirmation
  --upx-dir=UPX_DIR     Path to UPX utility (default: search the execution
                        path)
  -a, --ascii           Do not include unicode encoding support (default:
                        included if available)
  --clean               Clean PyInstaller cache and remove temporary files
                        before building.
  --log-level=LOGLEVEL  Amount of detail in build-time console messages
                        (default: INFO, choose one of DEBUG, INFO, WARN,
                        ERROR, CRITICAL)

  What to generate:
    -F, --onefile       Create a one-file bundled executable.
    -D, --onedir        Create a one-folder bundle containing an executable
                        (default)
    --specpath=DIR      Folder to store the generated spec file (default:
                        current directory)
    -n NAME, --name=NAME
                        Name to assign to the bundled app and spec file
                        (default: first script's basename)

  What to bundle, where to search:
    -p DIR, --paths=DIR
                        A path to search for imports (like using PYTHONPATH).
                        Multiple paths are allowed, separated by ';', or use
                        this option multiple times
    --hidden-import=MODULENAME
                        Name an import not visible in the code of the
                        script(s). This option can be used multiple times.
    --additional-hooks-dir=HOOKSPATH
                        An additional path to search for hooks. This option
                        can be used multiple times.
    --runtime-hook=RUNTIME_HOOKS
                        Path to a custom runtime hook file. A runtime hook is
                        code that is bundled with the executable and is
                        executed before any other code or module to set up
                        special features of the runtime environment. This
                        option can be used multiple times.
    --exclude-module=EXCLUDES
                        Optional module or package (his Python names,not path
                        names) that will be ignored (as thoughit was not
                        found).This option can be used multiple times.
    --key=KEY           The key used to encrypt Python bytecode.

  How to generate:
    -d, --debug         Tell the bootloader to issue progress messages while
                        initializing and starting the bundled app. Used to
                        diagnose problems with missing imports.
    -s, --strip         Apply a symbol-table strip to the executable and
                        shared libs (not recommended for Windows)
    --noupx             Do not use UPX even if it is available (works
                        differently between Windows and *nix)

  Windows and Mac OS X specific options:
    -c, --console, --nowindowed
                        Open a console window for standard i/o (default)
    -w, --windowed, --noconsole
                        Windows and Mac OS X: do not provide a console window
                        for standard i/o. On Mac OS X this also triggers
                        building an OS X .app bundle.This option is ignored in
                        *NIX systems.
    -i <FILE.ico or FILE.exe,ID or FILE.icns>, --icon=<FILE.ico or FILE.exe,ID or FILE.icns>
                        FILE.ico: apply that icon to a Windows executable.
                        FILE.exe,ID, extract the icon with ID from an exe.
                        FILE.icns: apply the icon to the .app bundle on Mac OS
                        X

  Windows specific options:
    --version-file=FILE
                        add a version resource from FILE to the exe
    -m <FILE or XML>, --manifest=<FILE or XML>
                        add manifest FILE or XML to the exe
    -r <FILE[,TYPE[,NAME[,LANGUAGE]]]>, --resource=<FILE[,TYPE[,NAME[,LANGUAGE]]]>
                        Add or update a resource of the given type, name and
                        language from FILE to a Windows executable. FILE can
                        be a data file or an exe/dll. For data files, at least
                        TYPE and NAME must be specified. LANGUAGE defaults to
                        0 or may be specified as wildcard * to update all
                        resources of the given TYPE and NAME. For exe/dll
                        files, all resources from FILE will be added/updated
                        to the final executable if TYPE, NAME and LANGUAGE are
                        omitted or specified as wildcard *.This option can be
                        used multiple times.
    --uac-admin         Using this option creates a Manifest which will
                        request elevation upon application restart.
    --uac-uiaccess      Using this option allows an elevated application to
                        work with Remote Desktop.

  Windows Side-by-side Assembly searching options (advanced):
    --win-private-assemblies
                        Any Shared Assemblies bundled into the application
                        will be changed into Private Assemblies. This means
                        the exact versions of these assemblies will always be
                        used, and any newer versions installed on user
                        machines at the system level will be ignored.
    --win-no-prefer-redirects
                        While searching for Shared or Private Assemblies to
                        bundle into the application, PyInstaller will prefer
                        not to follow policies that redirect to newer
                        versions, and will try to bundle the exact versions of
                        the assembly.

  Mac OS X specific options:
    --osx-bundle-identifier=BUNDLE_IDENTIFIER
                        Mac OS X .app bundle identifier is used as the default
                        unique program name for code signing purposes. The
                        usual form is a hierarchical name in reverse DNS
                        notation. For example:
                        com.mycompany.department.appname (default: first
                        script's basename)

  Obsolete options (not used anymore):
    -X, -K, -C, -o, --upx, --tk, --configfile, --skip-configure, --out, --buildpath
                        These options do not exist anymore.

Edited February 4, 2016 by fujidude

[playermissile]

New version! 0.8.3 available here: https://github.com/robmcmullen/omnivore/releases/tag/0.8.3

Primarily it fixes the problems with horizontal bitmap scrolling and the file browser pane. From the ChangeLog:

* Fixed py2exe to include msvcp90.dll and friends

* Updated readme to include instructions on checking out modified Enthought libs

* Fixed page up/down in grids to be based on number of visible rows

* Changed max cursor position so can't position off the end of the document

* Fixed horizontal scrolling refresh problem in bitmap scroller

* Fixed file browser attepmting to open directories as files instead of expanding them

Edited February 4, 2016 by playermissile

[playermissile]

New version! 0.8.4 available here: https://github.com/robmcmullen/omnivore/releases/tag/0.8.4

The beginnings of filesystem support (for Atari DOS only at this point, but I'm learning about SpartaDOS!): it shows all the files on the disk in the Segments pane. Also supports KBoot images, which are those boot disks that don't contain a regular filesystem but instead an embedded XEX and a bootloader. You can now extract those embedded XEX files using the File -> Save Segment As... menu item (or right click on the segment). Also, from the ChangeLog:

* Added context menu to segments list to save segment

* Fixed menu item segment parser that wasn't being set correctly

* Added KBoot disk image support from atrcopy 2.0

* Fixed disassembler references to segment data to properly handle IndexedByteSegments

* Fixed map editor overlay command where mouse released on same tile as pressed: no last command in batch = error

* Added log file recording on all platforms

[devwebcl]

Does it only support Getaway maps ?

[playermissile]

Does it only support Getaway maps ?

 

It has some hard-coded support for Getaway maps (setting the correct map width, setting the font, etc.) but it should be able to handle arbitrary maps.

[playermissile]

Does it only support Getaway maps ?

 

Well.... I clearly have a lot of work to do. There are quite a few rough edges, but here's Mountain King after I saved out the map and font and loaded them back in to the editor. Among other problems, note the character picker hasn't been updated to show the Mountain King font.