News Group Posts

OSR5 Merge 5.3 and MS-DOS 6.22 WARNING:

Merge: _M_vmonitor: unknown opcode 00000039

From: "Bob Bailin" <72027.3605@compuserve.com>
References: <bdn191$pka$1@ngspool-d02.news.aol.com>
<WamMa.7360$cz2.2057688131@newssvr10.news.prodigy.com>
<20030702031949.GF24551@sco.com> 
Subject: Re: Merge 5.3 and older DOS
Date: Wed, 02 Jul 2003 18:24:33 GMT


"Bela Lubkin" <belal@sco.com> wrote in message
news:20030702031949.GF24551@sco.com...
> Bob Bailin wrote:
>
> > > After (finally) upgrading our system from 5.0.5 to 5.0.7 and
installing
> > > Merge 5.3 in the process, I found that I could no longer run MS-DOS
6.22
> > > under Merge 5.3 as I could under Merge 4.1.1.
> > >
> > > (Dual P III system w/512MB memory.)
> > >
> > > Understand, I could *install* DOS 6.22 just fine using dosinstall, and
the
> > > images created in the process with mkimg were built without a problem,
but
> > > trying to run 'dos' afterwards from the console results in a screen
blanking
> > > and a brief display of the mouse driver message, followed by another
> > > blanking and a return to the unix prompt. The merge error log shows
that the
> > > VM86 process has died, as expected. Interestingly, if I run dos in an
> > > X-Windows, or if I have an X-Window running on another multiscreen, I
get an
> > > additional error window with the message: "Unknown command opcode 89",
(I'll
> > > have to check on that exact number), and the separate dos window which
> >
> > Jun 26 16:57:58 pilgrim WARNING: Merge: _M_vmonitor: unknown opcode
00000039
> > Jun 26 17:02:08 pilgrim WARNING: Merge: _M_vmonitor: unknown opcode
00000083
> >
> > > doesn't blank out shows that the process died just after initializing
the
> > > mouse driver but before the CD-ROM driver. If I disable the mouse
driver and
> > > clear out the config.sys files, the process still dies but obviously
without
> > > any reference points to gauge where it died during the DOS boot
process.
>
> I asked about this and was given the following workaround, which I have
> not tested myself and probably cannot answer questions about.  The
> problem was apparently an unintentional side-effect of changes to
> support WinME; a fix is being put into ongoing source so that future
> releases of Merge will support DOS 6.22 by default.
>
> The workaround I was given:
>
> " As super user:
> "
> "    cd /usr/merge/image
> "
> " Add the line
> "
> "    install = mrgtsr.exe
> "
> " to the END of the file config.mki
> "
> " Then run the following commands:
> "
> "    dos2unix config.mki > /tmp/config.mki
> "    unix2dos /tmp/config.mki > config.mki
> "    mkimg
> "
> " Whenever you start DOS, on the DOS screen, you may see a message
> " "Merge TSR / Windows DRV is already installed." following the
> " "Virtual Bus Mouse Driver installed" message.  This extra message
> " is purely informational and can be safely ignored.
>
> Please post a followup after you've tried this...
>
> >Bela<

It works perfectly!! Yes, there is the "...is already installed" message
upon each boot, but I think I can live with it. Windows 3.1 started up
without a hitch, surprisingly, because the default DOS configuration
allocates 2MB of memory to the session instead just 640K. (Note:
Win 3.1 does not work with later versions of dos, and you can't use
'win' to start up Win 3.1 directly from unix, although you can create
an alias that will start it up like any other dos program in /usr/ldbin .)

You can save a little typing by entering the ^M directly using: ^V^M
instead of the dos2unix, unix2dos gyrations.

You can make the change permanent for future (re-)installations of
DOS 6 by editing /usr/lib/merge/for_image/config6.mki (a read-only
file) instead.

Thank you, Bela!!!

Bob

Comments?

Jump to Comments

Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.

Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.

We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.