Professional Web Applications Themes

Merge 5.3 and older DOS - SCO

"Bob Bailin" <72027.3605compuserve.com> wrote in message news:bdn191$pka$1ngspool-d02.news.aol.com... > After (finally) upgrading our system from 5.0.5 to 5.0.7 and installing Just to be clear ^^^^^^^^^ it was a fresh install of 5.0.7, not an in-place upgrade. > 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. >...

  1. #1

    Default Re: Merge 5.3 and older DOS


    "Bob Bailin" <72027.3605compuserve.com> wrote in message
    news:bdn191$pka$1ngspool-d02.news.aol.com...
    > After (finally) upgrading our system from 5.0.5 to 5.0.7 and installing
    Just to be clear ^^^^^^^^^ it was a fresh install of 5.0.7, not an in-place
    upgrade.
    > 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.
    >


    Bob Bailin Guest

  2. #2

    Default Re: Merge 5.3 and older DOS


    "Bob Bailin" <72027.3605compuserve.com> wrote in message
    news:bdn191$pka$1ngspool-d02.news.aol.com...
    > 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.
    >

    Bob Bailin Guest

Similar Threads

  1. Older Extensions?
    By heavybob in forum Macromedia Exchange Dreamweaver Extensions
    Replies: 2
    Last Post: September 17th, 02:41 AM
  2. older extensions
    By psvanvic@gmail.com in forum Macromedia Exchange Dreamweaver Extensions
    Replies: 0
    Last Post: September 16th, 08:12 PM
  3. Photoshop 7 Merge Linked vs. Merge Down
    By Seth_Thompson@adobeforums.com in forum Adobe Photoshop Mac CS, CS2 & CS3
    Replies: 0
    Last Post: February 25th, 08:14 PM
  4. Merge wont Merge Gradients?
    By Jason_Howard@adobeforums.com in forum Adobe Illustrator Macintosh
    Replies: 1
    Last Post: February 13th, 07:52 PM
  5. Older Mac OS versions and older Macs
    By maron in forum Mac Applications & Software
    Replies: 11
    Last Post: July 29th, 02:13 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139