NeoGeo dev update with Neo Thunder

neo thunder

Compiled and Linked under Windows 10

In a round about way I was looking at old NeoGeo hardware having seen the ‘NeoGeo X’ android device for sale.  In a round about way I stumbled onto this page detailing various homebrew projects.  I saw the Neo Thunder, which looked interesting, and more importantly included source code!

What was even better is that there was a download of the full toolchain + emulators to get it up and running!  I downloaded it, and hit the wall quickly as this was built with cygwin circa 2001, which means it will forkbomb any post Windows XP SP2 system.

Well, I couldn’t just let it die on the vine, so I turned back to my Canadian cross compiler build machine, and quickly built a m68k-elf tool chain.  As always, first build a native cross compiler for later building libgcc.a and friends.  I use a 32bit version of Linux with a downgraded MinGW environment so I can use Binutils 2.25.1 and GCC 4.1.2

For anyone who cares, this is my configure strings:

../configure --target=m68k-elf --prefix=/usr/local/m68k-elf
../configure --target=m68k-elf --prefix=/m68k-elf --host=i686-mingw32

../configure --target=m68k-elf --prefix=/usr/local/m68k-elf
../configure --target=m68k-elf --prefix=/m68k-elf --disable-libssp --build=m68k-elf --host=i686-mingw32

With a cross compiler built, the next problem was with the built in tools like bin2elf, fixcnv, gfxcc, and symify.  These were also built with cygwin, and failed to run.  With a LOT of googling however I did find the following link to “Fabrice Martinez’s NeoDev Neo Geo C development library for GCC’. 290 kb Année 7/26/2004 (LINUX)“, out on

I patched up makefiles to my liking, and I could build all the libs, and all of the sample code (well except for the c++ one, because I couldn’t be bothered to build a c++ compiler).  Some of it runs, some doesn’t I’m not sure what is going on.  But for what it’s worth, Neo Thunder actually builds and runs (on mame!).

As always you can MinGW-M68K-ELF(neogeo).7z on my site.  Be sure to read the 404 page for the username password, as it auto-generates from time to time.  I don’t know if anyone will care, but it was kinda cool to track down the needed bits, and build out a working version of Neo Thunder.

My experience with the Gravis UltraSound Part 2: Synergy ViperMax / Gravis UltraSound Extreme

(guest post from Frank Sapone)


Synergy ViperMax / Gravis UltraSound Extreme

A few months ago I made a guest-post about my personal experiences with the
Gravis UltraSound cards.  In this article I mentioned there were a few variants
besides the standard GUS “Classic”, MAX, and PnP series.  I was unable to
comment on the other cards since I did not own them.  Well, that all changed
a few weeks ago when I contacted someone who wrote some pack-in software that
was included with most GUS cards and surprisingly he still had all his cards.
Even better, he was willing to give them to me!

One of the cards I received was the Synergy ViperMax.  I have read some usenet
posts and have talked to other people who were active in the demoscene in the
mid-90s and apparently this card was originally designed by STB and then STB
produced their own card that has an ESS1688 chipset (for SB Pro compatibility
and better Windows drivers) and the GF1 chipset (the IC that makes the GUS
it’s own).  How true is this story?  I have no clue, as I have never seen an
STB variant of this card, but I have seen STB GUS PnP (the AMD Interwave
version) as Compaq OEM clones for sale occasionally.

In any case, Synergy started producing this card and it’s kind of a rare
number.  Again, rumours afloat, that the guy from Synergy was coming to
demoparties and giving these away to groups that won competitions in an
effort to stir up some interest/sales.  And before Advanced Gravis all but
gave up on the sound card market they took the Synergy ViperMax cards and
simply placed stickers over the Synergy logo and card name.  Gravis also maxed
out the onboard RAM to 1MB (the ViperMax comes with 512kb by default). It is
exactly the same board, which leads me to believe Gravis may have purchased
remaining stock of the Synergy cards and unloaded them.  The UltraSound Extreme
may be even more rare than the ViperMax.  It’s hard to say as I have personally
never seen either of these cards for sale on ebay.

Keeping the GUS roots, the card is almost completely plug and play. The only
thing you must change is a jumper for CD-ROM Enable/Disable.  Like the GUS MAX
there is CD-ROM interface support.  Contrary to rumours, this card is NOT GUS
MAX compatible!  It does not contain the Crystal CS4231 CODEC chip or emulate
it.  This means no MAXSBOS and no special demos that will output 48khz (I only
know of one, The Secret Live of Mr. Black by Orange).  I feel this
misinformation was started because of the CD-ROM interface that was also unique
to the GUS MAX.  To setup your card you just run viprinit in DOS with your
appropriate SET BLASTER and SET ULTRASND variables and it configures the rest.
However, I noticed viprinit will not properly change your base address for the
ESS chipset (i.e. you want to change it from A220 to something else).  No fear,
Synergy included the ESSCFG.EXE utility as well allowing you to change the
base address.  Initial configuration is set with VSETUP.EXE from DOS.

Windows 95 installation is basically the same as the earlier cards. You
run the setup.exe and it will install the ESS drivers.  It tries to setup
some extra stuff for UltraSound as MIDI device.  And it does work just fine
but a gotcha is that the DOS stuff will break.  I never had a reason to use
GUS’ MIDI capabilities from within Windows so this wasn’t a deal breaker
for me.  After a reboot you will likely have to reconfigure your card
manually from the device manager but after that it’s smooth sailing.  And yes,
you can install the updated ESS1688 drivers with no ill-effects. However,
if there are any differences in performance I have yet to notice it. Last known
official ESS drivers for Windows 9x at

The ESS chip is really nice, it sounds very similar to the OPL3 and it has
SB PRO compatibility (take THAT SB16!).  Whats the difference?  The SB16 only
states that it’s Sound Blaster compatible, not Sound Blaster PRO compatible.
This means some earlier titles like Wolfenstein 3D will only output in mono
on the SB16.  With the ViperMax, you can hear stereo sounds again.

Wolfenstein 3-D

Wolfenstein 3-D

Someone asked me if SBOS and MegaEm work.  SBOS, no.  MegaEm, yes but with no SB emulation.  You can probably make MegaEm work with the SB emulation if you
want to play around with running ESSCFG, changing your PnP settings, updating
your BLASTER and ULTRASND variables then running viprinit.  But, you’ll need
a lot of free resources and quite frankly I fail to see a point.  If anyone
out there has pulled it off drop me a comment.

Since the card has a GF1 IC there is no comparision between the earlier GUS
cards.  They will all sound the same.  The signal-to-noise ratio is acceptable
though I haven’t measured what it truly is, but for gaming and watching some
demos it’s capable.

All in all, this is a great card.  If it was released earlier and through
Advanced Gravis they could have still been in the market.  Another nice
side effect of this card is that Windows XP has ESS1688 drivers. Just install
the cards as a non-pnp legacy device, configure manually and enjoy sound!

I made a few more rips comparing the differences between the ESS mode and GUS.
The few module files are played with XTC-Play and two of them (ATBIA3 and
Parallel Universe) are XM modules over 1MB.  XTC-Play has a way of quadrupling
the RAM usage by downsampling.  However, the modules still sound quite good
and it’s quite a thing to hear the GUS playing large high-quality modules.



Before I bring this article to a close, here is some ViperMax/GUS Extreme

* Gravis UltraSound Extreme Manual:
* Gravis UltraSound Extreme CD ISO:
* Synergy ViperMax CD ISO:

Enjoy the rips!  In a few weeks I’ll have a write up on the Gravis UltraSound
Plug and Play Pro (waiting for my RAM upgrade) and finally some last minute
thoughts and information about a few other OEM cards and the GUS ACE.

For comparison here is DOOM II Map 06


Sound Blaster

Advanced Gravis

My experience with the Gravis UltraSound

(guest post from Frank Sapone)


Sometime around 1992, Advanced Gravis teamed up with Forte/E-Tek to design a wavetable synthesis card around the ICS11614 IC. This card offered 32 channels, 14 channels @ 44khz and more channels would start dividing down in sound quality until you got to 32 channels at ~19khz. The mixing was done on-board which saved precious CPU cycles in the days of 286 and 386. The card originally advertised sound blaster support, but reading usenet posts from these days you can tell a lot of people were agitated that it was through a TSR, SBOS, that had hit or miss support and sometimes sounded better or worse than the FM because SBOS mixed it all into stereo.

I found out about these mythical cards a few years ago. A buddy went along with me to the local flea market out in the country-side of York, PA and we found a fellow who was trying to sell some P2-era laptops with USB wifi dongles and Windows XP loaded laptops for $100(!). I started talking with this gentleman and eventually convinced him to let me take a trip to his house and see what other stuff he may have. I took home a healthy share of various SB clones (mostly of the ESS variety, but a few Yamahas were in there as well) and some S3 Virge cards all for free. I built a computer with some of these parts, enough to play Doom and Heretic and started hitting up vogons and was reading some fanboism on the Gravis UltraSound cards. Where did I hear that name before? Oh, yes, in my mid-late 90s days of Doom I remember the setup.exe listed this card as an option and so did Duke3D and some other games I used to play quite frequently.

I did a lot of research on the card. Reading about how it used wavetable synthesis instead of FM. Basically, you can upload real MIDI-like patches to the cards RAM to get exceptional sound quality out of these older games and this also opens the window to creating your own patches if you wanted to tweak the sound of the songs.

Ultrasound Classic

Ultrasound Classic

Fast forward a couple of years later, I finally broke down and bought a GUS Classic v2.4 on ebay for $60. Unfortunately, it didn’t work out of the box. Failing to detect the card every single time, even if I removed everything from the computer and even disabled everything in the BIOS, including the FDC, Serial and Parallel ports. I got a refund, but a few days later I noticed some resistor had a broken leg and I soldered this and it started working! Immediately I loaded up Doom and the music sounded so much better than my SB or any of it’s clones.



Enjoying the sound, I started loading up other titles I played a lot back then that I remembered supporting this card: Descent, Heretic, Duke3D, Quake 1. I got a taste of some infamous Gravis issues when it came time to load up any Build engine title (Duke3D, Blood, SW, etc.) and Rise of the Triad. The music sounded great, but the digital voices had some weird clicks and somewhat static-like sound at the end of their samples. More research revealed that the GUS was known for this with those particular titles, and a ìsimpleî workaround is to get an SB card coexisting in the same box.

I amazingly got the SB and GUS living in the same machine after a few hours of fiddling around with some jumpers and tweaking autoexec.bat. Originally, I used one of those stereo to stereo cables. Running line out of the SB to the line in of the GUS, but the GUS’ mixer ìcolouredî the sound of the line in and mic in with entirely way too much bass. I made a cable that ran from line out of the SB16 to the CD-In of the GUS and it sounded excellent. I even found a way to keep my SB working in Win98SE this since it was known that the GUS had shitty support for the Win9x family (more on this later).

There are some shortcomings of the classic cards, the main being the Win9x drivers have no DirectSound support, only software emulation and usenet says that this had unpredictable results. Another annoying thing was no volume mixer(!), they expected you to hook this card up to powered speakers or ideally an amplifier. The v3.7 revision has a volume mixer but had problems with flip flopped stereo (whoops!) and v3.74 (the final GUS classic) fixed this problem. For those curious, for the most part revision versions don’t have bug fixes in their firmware, they just started finding ways to shrink the number of ICs on board. The exception to this was the v3.7 and v3.74 adding the volume mixer. GUS MAX v1.7 apparently had some sort of DMA or IRQ bug (forget these specifics) according to usenet, v1.8 fixed this problem and v2.1 is a v1.8 but lower component count and everything is now soldered on instead of sockets.

Other gotchas include: sound clicking and corruption on High-DMA, sometimes you can resolve this by setting 16-bit delay transactions but not all motherboards have this option and some just won’t work either way. Doubling up on the baseport, i.e. 220 also steals 320. Gravis claims you need to set the GUS and SB Emu IRQ to different values but they can be the same usually and have no problems. Same with the Playback and Recording DMA, unless you want full-duplex. If you’re just gaming it’s irrelevant.

Ultrasound MAX box

Ultrasound MAX box

At some point, I was hungry for more, wanting to try out the later GUS models like the MAX, ACE, and PnP. Particularly the GUS MAX because it included the volume mixer, had a special Crystal CODEC chip for 16-bit recording (was released late in GUS classics life as a daughterboard but it is very rare), the CODEC chip allowed for Windows Sound System, but the port is non-standard (gotcha!) and a special SBOS, MAXSBOS, takes advantage of the CODEC chip as well, and finally some CD-ROM support on board but I was uninterested in that since most of you know how much of a nightmare it is to get that shit working properly. Back to ebay, found a fellow selling a boxed GUS MAX for $100. I didn’t have the total cash on me at the time and it was buy-it-now. Considering the card was fairly hard to find, at least from what I researched at the time, I contacted the guy about paying half now and the other half in a few days. He agreed, and asked that I send it as a gift via paypal. Long story short, he never sent it, stopped replying to my emails and since it was sent as a ìgiftî I had no recourse through ebay or paypal. Learn that lesson when dealing online everyone! Always offer to pay a little extra for the processing fee if they claim this is why they want it set as a gift!

Bummed out, I found another classic, this time a v2.7 and well what do you know, this one doesn’t work either! Tried for 3 days all kinds of things. Cleaning the entire board off with electrical contact cleaner, reseating the contacts on the socketed chips, reflowing solder joints, replacing capacitors, but nothing ever brought it back to life. A year or two later, I found another GUS MAX for sale on ebay, purchased it immediately and it did not work. I tried it in 3 separate PCs and got no results. It always just said baseport UNAVAIALBLE FOR ULTRASOUND for whatever baseport I set it to. However, it wasn’t a total loss. On a whim, I took the GF1 IC from this MAX and placed it in the broken v2.7 classic and it made this card live again.

I setup daily searches for ebay to alert me immediately of any GUS developments appearing. If you’re new to the whole Gravis thing you’ll see theres a guy in Hungary who always has overpriced ones for sale and is unwilling to budge on price. If you check out his feedback you will see that he has been selling GUS cards of all flavours since at least 2010(!) almost monthly. Months and months went by with no MAX showing up and when one finally did it went for way more than I was willing to spend especially with the track record of 2 (almost 3) DOA cards that required soldering and intense cleaning to live again. If you’re planning to experiment with GUS cards be sure the card was tested recently, if you get the typical responses of not having an ISA PC around any more to test it, get the card cheaply and be certain that they will honour the return policy if it does not work.

MAX 2.1 board

MAX 2.1 board

Finally, after a couple of years I did some networking and found some fellow demosceners with GUS MAXes for the price of shipping. I’m waiting on my v2.1, but received two v1.8s. The first one did not work at all, would never detect properly. Tried the usual suspects of cleaning it up, reseating, rocking the caps a little back and forth to make sure everything was making contact, etc. The second one, actually detected the card saying UNAVAIALBLE FOR ULTRASOUND yet again, but this time after I disabled my FDC, Serial and Parallel ports it worked! Excited, I loaded up the usual games and all worked great and the CODEC chip’s mixer program worked properly. Now, I was read to add the SB16 back in but now no matter what base port I would select it always complained it was unavailable, yet again! At some point I got it working sort of but then it wouldn’t let me set any DMA properly in the setup utility. Enough of this nonsense, I thought, I have a few socket 7 towers not being used.

I popped it in to a P1 166MHZ living by itself. Now we can try out that special MAXSBOS!… and unfortunately it doesn’t sound better than SBOS, in fact it sounds worse! And yes, I tried a separate IRQ for SB emulation and low-DMA, high-DMA, making sure the CD-ROM baseport doesn’t conflict with GUS’ baseport and I have 1MB RAM onboard that is 70ns.

At this point I should stop and mention a few other gotchas on these MAX cards. The GUS ìdoublesî up on the baseport. i.e. if you set 220 it will also grab 320. The CD-ROM baseport on these cards will be set, even if you disable the rest of the CD-ROM interface. So make sure you don’t have the CD-ROM set to the same or else it will always complain it’s unavailable for ultrasound in the setup utility. And yes, you just have to remove the IRQ and DMA jumpers on the card and put the jumper on the CD-ROM disable. Panasonic enable jumper appears to make no difference regards to enabling parts of the CD-ROM circuit, unless of course you planned on using the CD-ROM interface. I’m assuming most of you out there won’t be. You also need 70ns rated (or better) 256kx4 chip. The MAX has 512kb RAM on board but you NEED 1MB on any GUS card to get great results or live with missing instruments and all kinds of funnies happening to you. The CODEC also uses some baseport, but this is software selectable so you should have no serious problem there.

Now I go on to try this bad boy out in Win98SE with the special DirectSound enabled drivers. When you install the Gravis GF1 (non PnP) series drivers it will tell you that you have to install the card as a non-PnP device and restart, then manually set the DMA, IRQ, Baseport in the advanced properties for the card. This is fairly trivial if you’re used to DOS, but for newbies just keep it in mind. Another gotcha here is that the drivers will blank out your SET ULTRASND= and SET ULTRA16(for MAX users)= in your autoexec.bat after the reboot so write these values down. I believe this was done on purpose since most people auto loaded SBOS or MEGAEM (the other SB emulator they had) and this conflicts with Windows big time. The drivers do work and the sound quality is fine, but the biggest issue I’ve had is that sndvol32.exe never loads now. You can not adjust the volume or disable the mic-in and line-in and you really should as every card I’ve owned the recording inputs pick up a lot of interference. Moving the mouse and the HDD just all come through your speakers. I haven’t tried Windows 95 yet, maybe the mixer works okay there? At some point I’ll post an update and let internet-land know.

Gravis Ultrasound ACE

Gravis Ultrasound ACE

SoundBuddy 1.0 prototype

SoundBuddy 1.0 prototype

I don’t own these cards, but will mention them for clarity. The GUS ACE (internally referred to as the Sound Buddy) is simply a GUS Classic without the recording capabilities or the gameport. It was meant to be a supplement to a sound blaster or similar clone. You simply run the line out of this card to your line in of your SB16 (or maybe it’s vice-versa? Correct me if need be). You have to update your ultrinit to the last known version because there’s a bug in the official drivers(!) that does not disable the nonexistant gameport and it will steal your other sound cards gameport cause conflicts. For those who need the fix, GUS0047.ZIP. At one point, Gravis struck a deal with AMD to make an enhanced chip, called the InterWave which had GUS support and allows 8MB of samples (16MB apparently if you solder some stuff, but I have yet to see any pictures or even a textfile on this hack). sceners say that it has problems with long loops so some demos may sound wrong. IWSBOS is based from MAXSBOS so I assume it probably sounds just as bad compared to the final revision of SBOS. Usenet posts of users crying that the Win9x drivers are awful too, but again, I don’t own this card so I’m only just passing on what I have heard. Feel free to prove me wrong in the comments.

ViperMAX board

ViperMAX board

Other weirdo cards included the Synergy ViperMAX, which is basically a GUS with an ESS chip for SB compatibility. In theory, this means you should get decent Win9x support through the ESS. These cards are kind of rare now. I have yet to see one appear in the US. But, fellow users have found them across the EU so maybe they are common there. There were some other OEM variants, most similar in design to the ViperMAX. Check out Wikipedia for information on those if you really must know more.

My final thoughts on this long (still not quite yet over) journey is that the GUS Classic is a fun card for breathing some life into the soundtracks of older id and apogee titles with a few silly hang ups on getting it to work initially. The MAX did not live up to its mythical hype with the mixer, special CODEC chip, and Win9x drivers. These cards appear to be very delicate because I have had 3 out of 5 cards DOA and required fooling around to get them to work again. Even though 2 MAX cards still do not work no matter what I’ve tried. Expect to buy more than one to get a working card. The ideal setup would be to get a GUS Classic or ACE and get that to coexist with an SB or compatible clone. I can’t comment on the ViperMAX as I have not located one yet.

Gravis Ultrasound MAX 2.3 prototype

Gravis Ultrasound MAX 2.3 prototype

As much frustration these cards have brought me, they still sound nice when they work! But, it really does make a lot of sense why they are rare today. It is quite aggravating to get one working properly!

All of this would be useless without some samples of what a GUS sounds like, all samples were recorded at 44,100Hz, …

DOOM e1m1

DOOM e2m6

DOOM e2m8

DOOM e3m1

DOOM e3m2

DEMOS on the PDP-11 in SIMH

DEMOS 3 on SIMH's PDP-11 / on Windows 95 Russian

While looking around again for more DEMOS stuff (not to be confused with ‘demo’ argh!) I found Serge Vakulenko’s ready to run DEMOS 3.0 for the PDP-11/SIMH package! And I think this is the corresponding source code. More information can be found on what I think is Serge’s blog.

Now on to running it.

The good news is that I only needed msvcrt.dll from Visual C++ 4.0 to get it to run under Windows 95.. The ‘bad’ news well for me is that I couldn’t think of a good telnet to do Cyrillic/KOI8-R properly. I’ll admit it’s probably me not knowing how to do it correctly. At the same time, I figured the ‘easy’ way out is to just install some Russian version of Windows. Naturally there is the ‘dual keyboard’ layout thing in Windows, which if you can’t read the default language… well. it’s too intimidating. But with enough mousing around I pulled the Russian keyboard out and it seems to operate fine.

There is of course some information here, but the mechanical translation is rought.. The wiki page still talks of 68020 and VAX ports of Demos (among others) I wonder if they’ll ever surface?

Demos Team in Moscow

The DEMOS team.

I’ve even found comprehensive documentation for both Демос and Xenix of all things here.

And to round things off, here is a mechanical translation (thanks google!) of the readme….


This section describes the procedures to be you-
satisfied, as when you first install the system, and in the case
“Complete destruction” of the root file system or replacement
hard disk is described by the root file system and non-
which directories.

The process of preparing the system for operation can be separated by
pour into the following stages:
– The primary installation (or recovery) system
distribution set to floppy disks (FDD);
– Loading system and checking its integrity;
– Set up the system files.
If “partial destruction of the” filesystems recom-
is to try to restore the integrity of the program fsck
(See Annex 2).

1.1. Initial installation of the system
For the initial installation of the system must:
– Tumbler “NETWORK” to include personal computers;
– Insert a floppy disk with the number 0 (the starting disk) in the
top device (null);
– Received an invitation to “@”, press (b), and then
in response to an invitation, “$” (dollar) to introduce “MY0” (or “MY” and
press (VC));
– After a while the screen will receive invitations
of “BOOT :…”; in response to it, you must press
– The query “installing DEMOS requires erasing infor-
tion on the hard disk … “to answer” Y “(YES) and on-
press key (VC); cancel mistyped character (up to
pressing (VC)) may be using the (BZ);
– On request “Enter the time …” necessary to introduce 10
digits and press (VC); time is given as follows-
where he – the last two digits of the year (eg, 90);
mm – month number (from 01 to 12);
dd – day of the month;
hh – hour (00 to 23);
mm – minute (00 to 59);
– The query “capacity hard disk drive …”
must enter the number – the number of drive type and press
key (VC); type of drive is defined as follows:

1. 5 MB 153 cylinder / 0-152 / – Set Database RUBIN impossible
2. 10 MB 306 Cylinders / 0-305 / – Set the database RUBIN impossible
3. 10 MB 306 Cylinders / 0-305 / – Set the database RUBIN possible
4. 20 MB 612 Cylinders / 0-611 / – Set the database RUBIN possible

– More on request “format the hard drive?” necessary-
necessary to introduce a “Y”, if you want to reformat the drive or
enter “N”, if not required;
– After loading the mini systems on the hard drive would you-
given a message to her perevyzova from this disc;
after a while you will be prompted “@”;
– In response to this invitation must type “B”, and
then, in response to an invitation, “$” (dollar) to introduce “DW0” (or
“DW” and press (VC));
– After a while the screen will receive invitations
of “BOOT :…”; in response to it, you must press
– After the system is triggered, it will ask for a floppy disk from the N1
basic set, it must be inserted into any drive
on floppy disks, enter the number of drive and press
key (VC);
– After reading the floppy disk system will ask the following;
necessary to remove the floppy disk with the number 1 from the drive
and insert a floppy disk with the number 2, then number 3 and
so on;
– After the floppy will be read by all base
set, the system will automatically reboot and check the File
lovuyu system on your hard drive (this can happen
– After rebooting the system will prompt “Name:”;
enter the name of the root user to perform
administrative functions in the DEMOS.

If you are logged on for the first time after the initially-
initial installation or complete restoration, it is necessary-
necessary to do the following:
– Set a password for the root user command
– Duplicate the distribution set GMD.

To copy a floppy disk you can use cpfd
(See 4.6.2).
Before turning off the PC user must perform
/ Etc / reboot-h (sure!)

Diskette distribution set should be pasted
markers of protection record. This is to ensure that due
equipment malfunction or careless use is not
destroy information on floppy disks.
During the boot from the floppy disk with the number 0, it
should be without a marker.

1.2. Download and check the integrity of the system
To load the operating system must DEMOS:
– Turn the power on the PC;
– Received an invitation to “@”, press (b), and then
in response to an invitation, “$” (dollar) to introduce “DW0” (or “DW” and
press (VC));
– After a while the screen will receive invitations
of “BOOT :…”; in response to it, you must press
– On request “Enter the time …” necessary to introduce 10
digits and press (VC);
– Further to the request “Check for file system?” need-
Dimo press (VC) (if you want to check file
system), or enter “N” and press (VC) (if not the friction
buetsya check file system);
– After checking the file systems will receive invitations
of “Name:”, enter the name under which the user
registered in the system after its processing realized

Example Remark and e. When checking file systems
may happen to re-reboot.

If the answer to the query “Name:” enter “user”, a Loss-
zoydet login PRACTICE (system description PRACTICE
See Section 3 “Guidebook”).

After completion of the work in the system, on invitation of the
solution to enter commands to type “/ etc / reboot-h”; after
how the system responds “SYNCING DISKS … DONE”, can be switched off-
chit powered PC.

Generating core demos contains the following items change
towards increased efficiency and optimality of the kernel:

a). A new, fastest, and very bright
in the hard disk drive such as “Winchester”, re-
presses of the program is configured rwset.

b). Adjusted and optimized driver floppy

c). A new superuniversalny printer driver
supporting the work of printers such as:
EPSON FX-800, EPSON LX-800, SM 6302, DZM-180, SM 6315,
SM 6900, ROBOTRON SM 6329, D100, D100M, etc.
full ob_eme their functionality
and taking into account the errors in the ROM EPSON FX-800. Modes of Operation
driver software is configured lpset.
For details, see READ_LP file in the root directory.

d). This version of the kernel supports the controller KTSGD
as with ROM KR18101RE2-181 on the board KTSGD and with ROM
KR18101RE2-182, operating in 8-bit character mode.
(Note that the kernel version 2.0 is not capable of work-
a thief with KTSGD on ROM KR18101RE2-182). However, the supplied
graphic protocol / etc / graf, is loaded into RAM KTSGD
and designed for ROM KR18101RE2-181 will not be over-
gruzhatsya in ROM KR18101RE2-182. Currently,
developed a new graphics protocol
latest ROM.

In order to save memory parameters changed
The kernel configuration:

e). Number of I / O buffer.

f). Number of processes in the system.

g). Number of concurrently executable programs.

h). Number of file descriptors.

i). Number of simultaneously open files.

j). “Trapped” statistics on I / O buffer, the sub-
pumping at boot time, for the teams.

k). Reduced the number of overlay core demos.

l). And other stuff …

Fix bug in the loader boot, which allowed
work on different types of hard drives.

Fix bug in intermediate loaders
rwuboot, fduboot.

The new version 4.1 of multiscreen editor red
contains the following changes and additions:

a). (PF1) (i) (VC) set / reset insert mode.

b). (PF1) (b) (VC) set the 132 characters on the screen.

c). (PF1) (l) (VC) set the 80 characters on the screen.

d). (PF1) (g) (VC) set the drawing symbols
pseudographics. Press the (F4) (F5), (F6) (F8)
You can “draw” and “erase” vertical and horizontal
tal solid lines.

e). (PF1) (^ 0) set / reset mode drawing / erasing pseudographics.

f). (PF1) (n) (VC) Exit from the pseudo-graphic.

g). (F1) move the cursor on the word forward.

h). (PF4) move the cursor to end of line.

i). (F5) delete word to the right of the cursor.

j). (PF1) (2) (right arrow) move the cursor
in the right extreme position of the current window.

k). (PF1) (2) (left arrow) move the cursor
in the leftmost position of the current window.

l). (PF1) (2) (up arrow) move the cursor
the upper extreme position of the current window.

m). (PF1) (2) (Down Arrow) move the cursor
the lower extreme position of the current window.

n). (PF1) (octal) (2) (^ 0) input specials. characters
where the number has three digits.

o). Optimized output to the screen with
use shortcuts (F7) (PF1) (F7), (2) (F7) (PF1) (2) (F7)

p). Undo the (FI), as the tab back

Corrected program graf (file etc / graf).
Graphics protocol can now be downloaded as
in compatibility mode (VT52), and in the extended
pulsed mode (VT100) displeya.V file etc / termcap include
Chen esc-sequence installation of roll band from 2
at 22 lines screen, which improves the visibility of pa-
Editor’s red boots, and other minor changes.

Make a convenient initial installation of OS DEMOS on your hard drive
(See above point 1), taking into account their different types and database RUBIN.

Minor changes to the index.html file etc / rc
(Associated with the programs of fsck, mount).

Graphics library libgraph.a is
directory usr / lib and a functional analogue of graphite
cally Library Company “Borland International”. The file
READ_GRAF describes the graphics functions.

* * * * *

Opint program determines the optimal interleaving of sec-
tori, surfaces, cylinders and formats vinchester.Kontrol-
Noe testing after formatting the hard drive with an optimal
interleaving shows that the efficiency of working with hard drive
increased on average by 25-30%. opint program should be run
from floppy disks (the OS is loaded at the same time as floppy disks of numbers under-
rum 0). opint program has the following items keys:

Usage: opint {-i [N] |-f [-q] [-bN] [-lN] [-sN] [-cN]} [-r]

-I [N] to calculate the optimal interleaving factor of
Sector / surfaces / and the cylinders. N-number
working cylinder, the cylinder is also used N-1
(Default N == 152)

-F format the hard drive

-R does not store information on your hard drive (in the informal
matted hard drive, this key is mandatory!)

-Q no questions asked

-BN set the start formatting with the N-cylinder
inclusive (the default cylinder N == 0);
this cylinder (and previous) is used in
as working to find the optimal Interlachen
Ving by a key-b0, or any absence
exists at all, then the worker becomes a 152 cylinder.

-LN set end of formatting to N-cylinder
inclusive (default to the cylinder N == 152)

-SN set interleaving factor N by sektoram/po-
surfaces, (default N == best)

-CN set interleaving factor N in the cylinders
(Default N == best)

Rwset program is used to adjust operating modes
hard disk drive and has the keys:

Usage: rwset [-cN] [[-] w]
-CN – enable precompensation to the N-cylinder
w – include checking account
-W – disable checking account

Lpset program is used to adjust operating modes
printer driver. All inforamatsiya Printing
contained in a file READ_LP.

* * * * * * *


DEMOS/306 operating system designed for installation and
operation on a single hard disk drive (“HDD”, 20MB) with
operating system RT-11. Hard disk capacity of 20MB
between the two operating systems is as follows:

RT-11: from 0 to 305 cylinder (10Mb)
DEMOS: from 306 to 611 cylinders (10Mb)

Initially (power-on) are loaded OS RT-11,
and hard disk drive must be configured to work with
10 MB free disk space (the cylinder to 305 inclusive).
After downloading the RT-11 operating system called DEMOS/306 team DEMOS.

Initial OS installation DEMOS/306 from installing OS DEMOS different
only a single boot floppy N0; the other five disks
distribution N1-N5 are identical for both operating systems.

User tired of two-wheeled scooter RT-11
pressing five keys is transplanted into a strategic
Bomber DEMOS/306!

OS DEMOS/306 – just fantastic!

————– The directory / TEST contains kontolno-demonstration
tional tasks and tests that are run co-
executing / TEST / main.

————– In the supplied distribution into a directory bin /,
usr / bin /, etc / contains utilities and files
(In particular:

c7t10 nroff autoconfig termcap
chgrp pp clri timstat
chown pstat cron ttys
dump restor dostat utpm
dumpdir rline getty wall
edit rmail graf
egrep setcolor group
false smbl group.std
fgrep startcode init
gets starttext iostat
login su lp_daemon
lpf tfd0 mknod
lpset wermit psdatabase
lx accton savecore
mix admclean shutdown

and others …), which are not descriptions of documents
orientation, because description on the tools and files that need-
dimye system administrator or system programming
Misty and not directly related to the work of Paul
transducer outside the scope of this documentation, I have-
ing goal is to give the most relevant information for the user-
converter. Descriptions can be found in various literature
on UNIX operating systems as Most utilities and service
Files are generally accepted in the family of UNIX names.
On the other hand, not all utilities (in particular:

ardos from mkmf splineg
banner hier mm strings
blank hostname prmail sum
checkobj ident rab unifdef
ckdir indent rcs units
colcrt install rcsdiff uptime
ctags last rcsintro uucpc
cxref lastcomm rcsmerge uuxc
ddutok lex rev whoami
error lint rlog badsect
expand look script ncheck
fold merge spell

and others … ) Described in the documentation contained
in the distribution, because documents constitutes a
taking into account further developments.

————– The distribution is not included and are available

a). DBMS “RUBIN”. / With complete documentation /

b). Integrated envelope “Demos Commander” –
analogue of the “Norton Commander”.

————– On a version 3.0 OS DEMOS worked:

Yudin, KE
Sudakov AV
Ryzhonkov KS
Bragin, DN

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~
Copyright 1991 by Research Institute “Scientific Centre”,
lab 462 / 2. All rights reserved.

PHONE: 536-56-42.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~
Moscow, Zelenograd, Research Science Center (lab.462 / 2)

Phone: 536-56-42.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~