Announcement

Collapse

Forum Rules and Etiquette

Our mission ...

This forum is part of our mission to promote the preservation of vintage computers through education and outreach. (In real life we also run events and have a museum.) We encourage you to join us, participate, share your knowledge, and enjoy.

This forum has been around in this format for over 15 years. These rules and guidelines help us maintain a healthy and active community, and we moderate the forum to keep things on track. Please familiarize yourself with these rules and guidelines.


Rule 1: Remain civil and respectful

There are several hundred people who actively participate here. People come from all different backgrounds and will have different ways of seeing things. You will not agree with everything you read here. Back-and-forth discussions are fine but do not cross the line into rude or disrespectful behavior.

Conduct yourself as you would at any other place where people come together in person to discuss their hobby. If you wouldn't say something to somebody in person, then you probably should not be writing it here.

This should be obvious but, just in case: profanity, threats, slurs against any group (sexual, racial, gender, etc.) will not be tolerated.


Rule 2: Stay close to the original topic being discussed
  • If you are starting a new thread choose a reasonable sub-forum to start your thread. (If you choose incorrectly don't worry, we can fix that.)
  • If you are responding to a thread, stay on topic - the original poster was trying to achieve something. You can always start a new thread instead of potentially "hijacking" an existing thread.



Rule 3: Contribute something meaningful

To put things in engineering terms, we value a high signal to noise ratio. Coming here should not be a waste of time.
  • This is not a chat room. If you are taking less than 30 seconds to make a post then you are probably doing something wrong. A post should be on topic, clear, and contribute something meaningful to the discussion. If people read your posts and feel that their time as been wasted, they will stop reading your posts. Worse yet, they will stop visiting and we'll lose their experience and contributions.
  • Do not bump threads.
  • Do not "necro-post" unless you are following up to a specific person on a specific thread. And even then, that person may have moved on. Just start a new thread for your related topic.
  • Use the Private Message system for posts that are targeted at a specific person.


Rule 4: "PM Sent!" messages (or, how to use the Private Message system)

This forum has a private message feature that we want people to use for messages that are not of general interest to other members.

In short, if you are going to reply to a thread and that reply is targeted to a specific individual and not of interest to anybody else (either now or in the future) then send a private message instead.

Here are some obvious examples of when you should not reply to a thread and use the PM system instead:
  • "PM Sent!": Do not tell the rest of us that you sent a PM ... the forum software will tell the other person that they have a PM waiting.
  • "How much is shipping to ....": This is a very specific and directed question that is not of interest to anybody else.


Why do we have this policy? Sending a "PM Sent!" type message basically wastes everybody else's time by making them having to scroll past a post in a thread that looks to be updated, when the update is not meaningful. And the person you are sending the PM to will be notified by the forum software that they have a message waiting for them. Look up at the top near the right edge where it says 'Notifications' ... if you have a PM waiting, it will tell you there.

Rule 5: Copyright and other legal issues

We are here to discuss vintage computing, so discussing software, books, and other intellectual property that is on-topic is fine. We don't want people using these forums to discuss or enable copyright violations or other things that are against the law; whether you agree with the law or not is irrelevant. Do not use our resources for something that is legally or morally questionable.

Our discussions here generally fall under "fair use." Telling people how to pirate a software title is an example of something that is not allowable here.


Reporting problematic posts

If you see spam, a wildly off-topic post, or something abusive or illegal please report the thread by clicking on the "Report Post" icon. (It looks like an exclamation point in a triangle and it is available under every post.) This send a notification to all of the moderators, so somebody will see it and deal with it.

If you are unsure you may consider sending a private message to a moderator instead.


New user moderation

New users are directly moderated so that we can weed spammers out early. This means that for your first 10 posts you will have some delay before they are seen. We understand this can be disruptive to the flow of conversation and we try to keep up with our new user moderation duties to avoid undue inconvenience. Please do not make duplicate posts, extra posts to bump your post count, or ask the moderators to expedite this process; 10 moderated posts will go by quickly.

New users also have a smaller personal message inbox limit and are rate limited when sending PMs to other users.


Other suggestions
  • Use Google, books, or other definitive sources. There is a lot of information out there.
  • Don't make people guess at what you are trying to say; we are not mind readers. Be clear and concise.
  • Spelling and grammar are not rated, but they do make a post easier to read.
See more
See less

Windows 3.0 VGA color driver for 8088/XT

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #16
    Me i tested it on my Olivetti M240, Windows 3.0 logo starts as VGA but after i have weird MODE 40 dos prompt. Windows doesnt start. If i issue mode 80 i have back black screen dos prompt.
    I have Paradise PVGA1A card.

    I ordered a NEC V30 but using this patch i thought i could have no problem with standard 8086 cpu.

    Comment


      #17
      I had the Windows 3 VGA mono driver working on a bog standard XT with no issues always wondered why vga required a 286

      Comment


        #18
        Ok guys i tried the first version of this patched VGA and with my 8086 Olivetti M240 it works! Sometimes it crashes but considering its retroengineering work, my compliments for this job!!
        I wonder why the second file VGAon8088_11.zip doesnt work. Is it only for 8088 cpu?

        Comment


          #19
          Ok guys sorry, my big mistake. I used mTCP ftp client in wrong way. I moved this file through ftp using ASCII, instead i had to set ftp client to BINARY mode. I tried the VGAon8088.zip driver transferred in binary mode and it works perfectly.

          Comment


            #20
            Time for me to re-dig up this interesting thread
            I have a Trident 8900B and 8088 based "Turbo XT" which I successfully got working with 256 color vga using; a) original VGA driver b) upgrade to the vga11 here then c) https://archive.org/details/TVGAWIN3_ZIP

            Comment


              #21
              oh interesting!

              So that TVGAWIN3 driver, it's fine on XT? What about 286? I'd love to have SVGA modes for my trident cards on windows 3.1 standard mode on my 80286-12.

              Thanks!

              -a

              Comment


                #22
                Does the patch make the driver less performant? I can imagine the newer 186+ instructions being more efficient than the pure 8086 instructions that the patch replaces them with.

                So would it still be preferable to go back to the unpatched driver once you've swapped out the 8088/8086 CPU for a V20/V30 CPU? Or is the effective difference negligible?

                Comment


                  #23
                  Originally posted by erikarn View Post
                  So that TVGAWIN3 driver, it's fine on XT? What about 286? I'd love to have SVGA modes for my trident cards on windows 3.1 standard mode on my 80286-12.
                  Yes it's fine on the XT and given I am using "real mode" the crashes are nothing really unsurprising.
                  If you are using a 286 with standard mode there should be no CPU limitation holding you back for SVGA.
                  Keep in mind VRAM memory and resolution are probably the main limitations

                  Comment

                  Working...
                  X