3 ms·
Technically, you could even do dual monitors with IBM PC, by having both a CGA card and a MDA/Hercules card. Obviously, the utility was limited, but apparently
by jchw 8y ago
Technically, you could even do dual monitors with IBM PC, by having both a CGA card and a MDA/Hercules card. Obviously, the utility was limited, but apparently people did it.
- ngcc_hk 8y agoHave to if you want a bit graphic those days. The Cga is so low resolution you can’t use it totally on its own. But OP is amazing to do this btw.
- sllabres 8y agoObviously, the utility was limited, but apparently people did it. For graphics yes. But around that time all Borland (C, Pascal) products supported debugging with to monitors (VGA+Hercules). And I used a little TSR for years that transferred the contents of the main VGA Screen to Hercules via 'PtrScr' key, which was handy too. All text mode of course.
- jchw 8y agoDefinitely not saying it was useless, just that the utility was limited because of the usual limitations of MDA; that is, it's definitely not the same as what people would think of as a dual-head setup today. That said, I literally was born after Windows 3.0. So... I never personally dealt with such a setup. Maybe some day, as a matter of exploring older computers, I will get a chance to actually run such a setup and see what it was like.
- jungler 8y agoIt was definitely a thing to run multiple screens in a "one-per-task" kind of setup - the real difference is that hardly anything back then networked or multitasked, and so you had to design the workflow you wanted to use specifically around the idea of using all your displays. In the context of any specific application(coding, document editing, CAD etc.) the possibility of a custom tailored solution existed - it just wasn't the highest priority most of the time. You could get a lot of multitasking mileage out of more antiquated technologies like printed documents and pens in tandem with your computer. "Code review" meant literally printing it out and going over it with highlighters like an exam grader. I'm sure it still does in some shops.
- myself248 8y agoOh yeah, you could run CGA+VGA, too -- they ran at different address ranges. A lot of graphical software had commandline switches to override the videocard autodetection, "in case it failed", but this could also be used to force the software onto one monitor or another. I ran dual-head under DesQview for quite a while. The CGA monitor whined like mad so I kept it off most of the time, but when I needed more display real estate, I'd turn it on and put my text sessions over there, leaving the graphical stuff on the VGA.
- mschaef 8y agoI always wanted a setup like this to put debugging information on another screen. When I got to where I had the money to buy it, there were the beginnings of the much better approaches we have today. It's probably worth mentioning that the idea of developing Windows software in Windows was something that only came around until 1990-91 or so. Prior to that, all the tooling (except for things like the message Spy and the resource editor) ran in the command line in text mode, including the debugger. Visual Basic gets a huge amount of grief, but when it was first released, this was a huge part of the reason why it was so amazing. It took Windows development from a relatively complex and obscure process involving a multi-step build/edit/compile and turned it into 'drag the button where you want it, click, and add an event handler... all in Windows itself.'