Wanted: "DOMMenu" by Clay Halliwell

[ballyalley]

I'm looking for the program "DOMMenu" by Clay Halliwell.  It made menus that looked like this:

 

 

This program was used with some of the disks for "Atari Classics" magazine and well as for, as least, some of the The Lake Almanor Public Domain Library disk catalogs.

 

According to Cleveland Free-Net Atari SIG's "Who's Who in the Atari Community" from December, 5, 1996, here:

 

https://www.atariarchives.org/cfn/12/06.php

 

Clay Halliwell is the "8-bit programmer of FlickerTerm 80, DOMMenu, Pantheon View, MacView 800, EbonView, MazeWar 3D, Cliff Diver, others.  Maintainer of Atari Jaguar Game Cheats and Codes FAQ."

 

The "Atari Classics Software Disk Index" by Steve Hoffee (AC Disk Editor), from October 1993, here:

 

https://www.atarimagazines.com/atariclassics/v2n5/disk_index.php

 

lists the program here:

 

Side B

 

MENU DOCUMENTATION -A complete documentation file that explains the basic setup for ACs new menu (DOMMenu), originally designed for use by usergroup Disk Of the Month librarians, by Earl C. Halliwell.

 

The OCR version of the October 1993 magazine is here:

 

https://www.atarimagazines.com/atariclassics/index/?issue=v2n5

 

While the pdf of the October 1993 issue is here:

 

https://archive.org/stream/Atari_Classics_v2n5_October_1993/#page/n27/mode/2up

 

I can't seem to find the disks for Atari Classics magazine, or (more specifically), the "DOMMenu"  program itself.  Can anyone help provide links to the magazine disks or for the program itself?

 

Adam

 

[+Allan]

I believe I have this. I am copying the physical disk now.

[+Allan]

I think it's on one of these disks. I THINK!

 

Had to fix one (two) things.

 

 

Atari_Classics.zip

[ballyalley]

4 hours ago, Allan said:

I think it's on one of these disks. I THINK!

Atari_Classics.zip 246.14 kB · 6 downloads

 

Thanks, Allan.  You're fast!  I'll take a look at these tomorrow.

 

Adam

[a8isa1]

17 hours ago, ballyalley said:

I'm looking for the program "DOMMenu" by Clay Halliwell.  It made menus that looked like this:

 

Adam

 

 

This declares itself as a Freeware version.  If a non-free version exists I don't have it.

 

I had no idea I even had the program but I hope it's what you are seeking.

 

[EDIT]

Screenshot

-SteveS

 

[EDIT]

p.s. The sig in the *about* file is E.Halliwell

DOM Menu -basic -freeware.zip

Edited February 6, 2020 by a8isa1

[ballyalley]

6 hours ago, a8isa1 said:

I had no idea I even had the program but I hope it's what you are seeking.

 

Thanks for posting the disk for it.  Where did you find it?

 

I've ready over the docs and "printed" them from Altirra.  In case anyone's curious I'm pasting them here.

 

Now... is anyone up for using this to create a February 2020 Disk of the Month for the Atari called, let's say, "Why AtariAge Forum Members Rock!"

 

Adam

 

"DOMMenu" by Clay Halliwell (Documentation)

 

A - About this Disk:

 

This is a demo/utility/distribution disk for DOMMenu, a special-purpose disk
menu program for use with disk-of-the-month and library disks.
 
DOMMenu has provisions for differing hardware configurations and user
expertise levels, and extensive online help.
 
The entries with "dox" next to them have attached documentation files.  Press
any of the alpha chars to move directly to that entry.
 
Enjoy.  Play around.  Consider the alternatives.
 
-- E.Halliwell

--------------------

B - DOMMENU Documentation

DOMMENU
 
Version 1.5  [freeware]
 
Disk of the Month Menu Program
 
Copyright (c) 1993 LonerSoft
by Clay Halliwell
 
October 1993
 
 
Why use DOMMenu?
 
     Why not?  But seriously...
DOMMenu isn't like other disk menu programs.  General-purpose disk menus are
designed to fill a different need than those required by a disk of the month
or library disk.  For this reason, DOMMenu dispenses with such useless frills
as file-management commands (rename, delete, etc...) and irrelevant low-level
information (drive #, free sectors).
     DOMMenu replaces sometimes-cryptic filenames with full program names,
links documentation files with their programs, elminates support files from
the displayed directory, word-wraps documentation files, has an expert mode,
and automatically reconfigures its menus to the user's system configuration.
 
 
SYSTEM REQUIREMENTS/SUPPORT
 
  -- Any 8-bit Atari w/48k
  -- Any DOS
  -- 1 disk drive
  -- Atari BASIC
 
 
INSTALLING DOMMenu
 
     The following files must be on a DOMMenu disk:
     DOS.SYS
     DUP.SYS (optional)
     AUTORUN.SYS (mine or yours)
     M (or whatever... the title program-- must RUN "D:MENU")
     MENU (DOMMenu)
     DOMINFO.DAT
 
     "DOMINFO.DAT" is the core of DOMMenu.  It is a plain ATASCII text file
containing a detailed description of the status and contents of the disk it
resides on.  It may be created with any word processor capable of producing
plain ATASCII files (TextPro, AtariWriter, etc...).  Submenu files use the
same format.  Menu files are in two parts, the header and the file block.
 
     HEADER
 
Header start--     "*BEGIN"
     Any text (remarks, etc...) may precede this.
 
Incarnation #--    any number
     NOT the same as the program version number.  Since identical versions of
DOMMenu may have different header graphics, etc..., this tells DOMMenu that
it's accessing a disk with a slightly differing version of DOMMenu.  When this
happens, DOMMenu is reloaded from the target disk.  To avoid duplication,
select large, random numbers for this entry.
     NOTE: Reserved Incarnation Numbers
        LonerSoft. . . . . -100 - -1
        nwPAC. . . . . . . 0-99
        Atari Classics . . 100-199
        L.A.P.D. . . . . . 400-499
 
Month/year--       date of disk
     This information is left-justified in the text area of the header
graphic.  Max 23 characters.
 
Index #--          disk library index code
     This information is right-justified in the text area of the header
graphic.  Max 23 characters (beware overlap!).
 
Center msg. flag--  0=no/1=yes
     Specifies whether the two message lines are centered.
 
Msg line #1--      any text
Msg line #2--      any text
     These lines of text are placed in the area immediately below the program
descriptions.  Max 39 characters.
 
Title program--    filename
     Name of the title/intro program on the disk.  Used by the "Title redux"
command.  Do NOT include a drivespec ("D:", etc...).
 
DUP present flag-- 0=no/1=yes
     If DUP.SYS has been deleted from the disk to make space, set to "0".  
Used by the Quit menu.
 
 
SAMPLE:
     This is a sample entry  <-- ignored
     *BEGIN                  <-- start of header
     100                     <-- incarnation #
     January '93             <-- date
     #247PD                  <-- index #
     1                       <-- center message lines
     See side two for        <-- message line #1
     more great files!       <-- message line #2
     LOADER                  <-- intro program
     0                       <-- DUP.SYS deleted
 
 
     FILE BLOCK
 
Description--      any text
     The full program name that appears onscreen.  Max 33 characters.
 
Program filename-- filename

     The name of the program.  No drivespec.
 
Program type--     0-3
     0 = Machine language
     1 = Basic
     2 = ReadMe (This type of entry has a documentation file, but no program
file.  Program filename is irrelevant.)
     3 = Submenu (This specifies another DOMINFO.DAT file (with a different
name, obviously).)
 
Docs filename--   filename
     The name of the associated documentation file.  Enter "NODOX" if none.  
No drivespec.
 
Preformatted?--   0=no/1=yes
     If the documentation file has been preformatted (word-wrapped and
paginated) for printer output, set to "1".
 
Separator--       *END/anything
     If this is the last entry, put "*END" here, otherwise anything else
("Anything Else", etc...).
     There may be up to 14 entries.
 
 
SAMPLE:
     ColorSquashView v1.56   <-- description
     CSVIEW                  <-- filename
     1                       <-- BASIC program
     CSVIEW.DOC              <-- documentation
     0                       <-- not formatted
     ***                     <-- more to come!
 

CREATING SUBMENU FILES
 
     To successfully exploit the submenu feature, you must realize that, to
DOMMenu, all menu files are identical.  No internal "directory tree" or path
is maintained.  The only menu DOMMenu knows about is the one currently loaded.
 "DOMINFO.DAT" is simply the default menu file.  Submenu files can be named
anything ("D:ANYTHING").
     That being stated, there are only a few restrictions to keep in mind.  
Most important-- the incarnation number, DUP-present flag, and title program
filename should be identical in all menu files on a disk.  Everything else in
the header (message lines, etc.) can change.
     NOTE: To be perfectly honest, only the incarnation number must remain
constant.  The other stuff can change, though it would seriously confuse the
end user.
 
Submenu Navigation
     You can always return to the top menu by pressing Escape.  However,
you'll probably want to put a "Return to Main Menu" option on your submenus
(which would load "DOMINFO.DAT").
     If you have multiple submenu levels, then you'd want to have an option to
return to the main menu, and one to return to the previous menu.
 
Submenu Applications
     The submenu feature was initially provided in case you ran out of room on
the main menu screen.  Fourteen slots will generally be enough for a SS/SD
disk, but good programs always come prepared.
     At any rate, submenus are for you to do with as you please.  Any submenu
can load any other submenu.  You can have a menu that's nothing but submenus.  
Don't go so submenu-crazy that you overwhelm the end user, though.  
Simplicity!  And it might be a good idea to identify the current submenu level
in the disk date/index area.
 
 
USING DOMMENU
 
     Upon running, DOMMenu reads DOMINFO.DAT and establishes the screen
display (top to bottom):
     Graphic header/date/index (the header may be changed.  See "CUSTOMIZING
DOMMENU")
     Program name area; up to 14 entries.  There is a letter (A-N) placed next
to each entry.  If the entry has a documentation file, or is a ReadMe entry,
the "dox" icon will appear next to it.
     The two message lines
     Three lines of default text (See "CUSTOMIZING DOMMENU")
     The Command Options line
 
     There are two command modes: Novice and Expert.  Both command sets are
available at all times...the only difference is the displayed Command Options
line.  Default is Novice mode.  Type "X" to enter Expert mode.
 
Commands in Novice mode:
     HELP  : Read documentation file
     START : Run program
     SELECT: Advance cursor
     OPTION: New disk
     X     : Expert mode
 
Commands in Expert mode:
     A-N   : Jump cursor to corresponding entry
     -     : Cursor up (wraps at top/bottom)
     =     : Cursor down
     RETURN: Run program
     Esc   : New disk
     R     : Read documentation file
     T     : Re-run title program
     Q     : Quit menu
     Options from Quit Menu:
          B     : Basic
          R     : Reboot (coldstart)
          D     : DOS (if available)
          other : return to main menu
 
Reading documentation files
 
     Upon pressing HELP/R, if there is a documentation file present, DOMMenu
will ask if you want to send the text to the screen or the printer.  Simply
pressing RETURN will send the file to the screen; any other key will abort.  

If you do not have a printer attached, it will default to screen output.   
 
Screen output
     One page at a time will be printed to the screen (with word-wrap!).  
Between each screen, you will be given the following options--
 
     Commands:
          SELECT/Space: Page down
          OPTION/BkSpc: Page up
          START /Esc  : Quit
 
Printer output
     After selecting printer output, DOMMenu will ask if you want to pause
between pages.  Press any key to begin printing.  If you have page pause
selected, you may press ESC between pages to quit printing.  DOMMenu's printer
output routine assumes 80 characters per line, 66 lines per page.  Printer
output is paginated (padded to avoid the page breaks).
 
 
 
DOWNWARD COMPATIBILITY
 
     If DOMMenu reads a DOMINFO.DAT file with a different incarnation number,
it will attempt to reload "D:MENU".
     If DOMINFO.DAT is not found, it will also reload "D:MENU".  This is to
retain compatibility with (for example) older DOM/library disks if you switch
to using DOMMenu in midstream, as it were.  See "CUSTOMIZING DOMMENU".
 
 
 
CUSTOMIZING DOMMENU
 
     There are a few things in the DOMMenu program you will probably want to
change to suit your particular application.
 
The header graphic:
     Included with DOMMenu is MAKEHEAD, which will take any uncompressed
Graphics 8 screen and generate the necessary BASIC code to integrate the image
into DOMMenu.  Also included is TEMPLATE.MIC, which shows the available screen
area.
     MAKEHEAD generates a file which must be ENTERed into MENU.  Don't forget
to SAVE "D:MENU"!
     Also included is GR8EDIT, which lets you edit a header graphic without
having the source file on hand.
 
The standard message area:
     Lines 5270-5280 define the three lines printed in the standard message
area.
 
The old menu filename:
     Lines 4200-4210 define the file loaded when DOMINFO.DAT is not found, and
the message printed when *that* file isn't found.
 
Incarnation number:
     Line 5 (yeah, yeah, it says "VER="...so sue me).
 

Atascii graphics:
     Control-character graphics may be used anywhere in DOMMenu-- program
descriptions, the date/index line, et al.  However, CTRL-I through CTRL-Z are
redefined for the header graphic.  Consider yourself warned.
 
 
"DOMINFO.DAT" SUMMARY FORMAT DESCRIPTION
 
Header:
 
Field           Contents
--------------------------------------
header start    "*BEGIN"
incarnation #   any number
month/year      date of disk
index #         disk library index code
center msg?     0=no/1=yes
msg line #1     any text
msg line #2     any text
title program   filename ("D:" assumed)
DUP present?    0=no/1=yes
 
 
File Block:
 
Field           Contents
--------------------------------------
description     any text
prog. filename  filename ("D:" assumed)
prog. type      0=ML/1=Basic/2=ReadMe/3=Submenu
docs. filename  filename ("D:" assumed; NODOX if none)
preformatted?   0=no/1=yes
separator       *END=done/otherwise=not
 
[max 14 entries]
 
CONTACTING THE AUTHOR
 
     I, Earl C. Halliwell, may be contacted at:
     GEnie: E.HALLIWELL
     PAUGS (602-278-8505): The Loner
 
     Earl C Halliwell
     407 S Second St
     Clinton, MO  64735-2107
 
Feel free to contact me if you'd like to reserve an incarnation number block.

 

[ballyalley]

I printed the formatted documentation for DOMMENU for myself.  I save it as a Word document.  If anyone interested, here it is to read:

 

DOMMENU - Disk of the Month Menu Program (1993)(Clay Halliwell)(Atari 8-Bit)(Docs).doc

 

This utility looks pretty useful.  It came pretty late in the Atari's life cycle, so I guess it probably wasn't used too often.

 

Adam

[+Allan]

11 hours ago, ballyalley said:

I printed the formatted documentation for DOMMENU for myself.  I save it as a Word document.  If anyone interested, here it is to read:

 

DOMMENU - Disk of the Month Menu Program (1993)(Clay Halliwell)(Atari 8-Bit)(Docs).doc 39.5 kB · 6 downloads

 

This utility looks pretty useful.  It came pretty late in the Atari's life cycle, so I guess it probably wasn't used too often.

 

Adam

Nice.

There were a number of well written programs from the late Eighties/early Nineties that never got much attention since many people moved on to STs/PC/Macs/Amigas etc. It would be great to see someone do a blog or a video blog or a general website high-lighting these later 8-bit programs.

 

Allan