"enable" (at least for the xor test) requires you to hit "enter" at
various times - so try that before rebooting :-)
you might want to run "freq 28" after enable

this staticaly linked executable is compiled for a 2Mb viper, with
this modedb record
"640x480x8"   31   640   684   708   836   480   485   486   514 +hsync +vsync

it's just for fun
-------------------------
setmode from himalayan s/w sets vertical and horiz. polarity wrong
(it inverts the polarity from what you tell it to set)
and it leaves out some of the constant parameters.
Finn.doc and viper.txt also have the polarity wrong for sync.
Diamond's vprmode 2.02 gets the polarity right.
---------------------------
ini2xconfig - interprets your viper.ini, and outputs modedb lines
for you Xconfig.
ini2xconfig here is a statically linked (so it runs under any linux?)
ini2xconfig is different from the original diamond method of
interpreting viper.ini - it will accept mode sections and hardware
section - on if it starts in the 1st column of the line like:

[1152x900x8]
or
[hardware]

 ... while

;[1152x900x8] or
anything[1152x900x8]

are treated like commments

also ini2xconfig:

- has more error detection, no defaults for resolution dependent
  stuff, and tells you what it uses for defaults on res-independent
  stuff.
- accepts dos OR unix format files (issues warning for DOS format)

-----------------------------
ini2xconfigallmodes
quick and dirty - looks at all 8 bit modes in your viper.ini with ini2xconfig
