Announcement

Collapse

Forum 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.


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.


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.



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.


"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.

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

Running MS-DOS in terminal mode, second try

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

    #16
    Originally posted by Chuck(G) View Post
    When (long ago) we did an 8-bit ISA card to direct video output to a terminal, we essentially made a clone of an MDA card, sans video circuitry with a Z80A onboard that snooped the video buffer and sent updates over RS232. This was probably overkill--one could install a timer interrupt routine to do the snooping just as easily. Keeping the payload size down is important to getting any sort of speed.
    Out of curiosity, was that the PC Weasel 2000 or an earlier device? We had a couple of the PC Weasels kicking around the office at my dot-com startup back in the day.

    (Of course these days many high-end servers have lights-off management processors that include the ability to virtualize the entire SVGA console, graphics and all, and let you connect to it across the network via VNC or whatever. You can often even do a full OS install by mapping a virtual CD-ROM drive to either a file or a physical drive on your client computer...)
    My Retro-computing YouTube Channel (updates... eventually?): Paleozoic PCs Also: Blogspot

    Comment


      #17
      Originally posted by Eudimorphodon View Post

      Out of curiosity, was that the PC Weasel 2000 or an earlier device? We had a couple of the PC Weasels kicking around the office at my dot-com startup back in the day.

      (Of course these days many high-end servers have lights-off management processors that include the ability to virtualize the entire SVGA console, graphics and all, and let you connect to it across the network via VNC or whatever. You can often even do a full OS install by mapping a virtual CD-ROM drive to either a file or a physical drive on your client computer...)
      No--it was the Tripas Trilink board--this was about 1984-85, so predates the dot-com stuff by about a decade. Still have one of the boards and may (I'm not sure) have the firmware source. All the junk I hang onto for no good reason...

      Comment


        #18
        Originally posted by Chuck(G) View Post
        No--it was the Tripas Trilink board--this was about 1984-85, so predates the dot-com stuff by about a decade. Still have one of the boards and may (I'm not sure) have the firmware source. All the junk I hang onto for no good reason...
        I was guessing it probably wasn’t after looking up a picture of the Weasel and seeing no Z80 and a Spartan FPGA on it... which is probably a masterpiece of overkill all things considered, but maybe they were thinking ahead to the PCI/VGA-emulating model that I don’t think ever materialized. (The weasel had the misfortune of showing up right around the time ISA slots were going the way of the dodo, as was MDA support.)
        My Retro-computing YouTube Channel (updates... eventually?): Paleozoic PCs Also: Blogspot

        Comment


          #19
          Originally posted by modem7 View Post
          See [here].
          Thank you very much! I just wonder why Google didn't find it. Or I made a typo.

          With kind regards / met vriendelijke groet, Ruud Baltissen

          www.baltissen.org

          Comment


            #20
            Originally posted by Chuck(G) View Post
            Absent ROM dumps, it would seem pretty straightforward to write a DOS TSR that hooks the INT 10h calls and translates them to INT 14h ones....
            I always have been interested in BIOSes in the first place. The advantage of a BIOS doing the trick for you is that it also can work for other operating systems. The disadvantage is that it will work only for one type of a machine. The idea is to stick to an 8088 machine anyway just to stay a bit in the same time line as my Commodore CBMs.

            With kind regards / met vriendelijke groet, Ruud Baltissen

            www.baltissen.org

            Comment


              #21
              Since this is an 8088-only application, why not take some BIOS source, such as the AnnaBooks one, and modify the INT 10h handler yourself?

              Comment


                #22
                Originally posted by Chuck(G) View Post
                Since this is an 8088-only application, why not take some BIOS source, such as the AnnaBooks one, and modify the INT 10h handler yourself?
                That is why I asked for the ROMs, to see how others did it.

                With kind regards / met vriendelijke groet, Ruud Baltissen

                www.baltissen.org

                Comment

                Working...
                X