krebizfan
Veteran Member
There was a Program Manager for Windows 2 released through the Microsoft BBS. Got enough press for me to notice and download. It was a bit memory intensive so not a good choice for the 640K machines.
"There was a Program Manager for Windows 2 released through the Microsoft BBS."
I'm just not clear about what a "program manager" actually does. What kinds of things do you do with it?
It can be as simple as a folder of .BAT files. You don't need to code anything at all to do that.But from a programming standpoint, a shortcut repository is easy to create.
I'd love to hear some discussion on the memory manager and multi tasking mechanics of early Windows. I like hearing about how early OSes handled multi tasking in a pre-MMU environment.
I'm sure it's similar to how the Mac did it, with the event loops being the ad hoc task scheduler, but curious how the memory manager works as well. The Mac and Apple IIGS Memory managers and linkers are kind of interesting in that regard (with a lot of similarity to how it was done in UCSD Pascal).
I'd love to hear some discussion on the memory manager and multi tasking mechanics of early Windows. I like hearing about how early OSes handled multi tasking in a pre-MMU environment.
I'm sure it's similar to how the Mac did it, with the event loops being the ad hoc task scheduler, but curious how the memory manager works as well. The Mac and Apple IIGS Memory managers and linkers are kind of interesting in that regard (with a lot of similarity to how it was done in UCSD Pascal).
There was a Program Manager for Windows 2 released through the Microsoft BBS. Got enough press for me to notice and download. It was a bit memory intensive so not a good choice for the 640K machines.
Is there some documentation (DDK) on how to write a graphics driver for Windows 1.x or 2.x?
I looked into this. It may have only been a beta release. I believe it's also MIA, and there are people looking for it. Do you still have a copy?
Yes, I realized that's what was happening. Later I found that I could actually read your message in the notification e-mail the forum software sent, but in the forum messaging interface it's just blank. You could try leaving a comment on my site or e-mail to mnecasek at yahoo dot com. Thanks!os2museum the message system here is broken for new users (and some not-so-new users too). I see your message. It was originally blank. I can read it now, but it seems my messages to you are now blank. I’ll try to contact you outside of this site.
Is this available for download somewhere?The OEM Binary Adapation Kit has what MS provided. The documentation is minimal. Tutorials non-existent. At least, a good selection of sample drivers were included.
Is this available for download somewhere?
Indeed. DRDoS 6.0 and GeoWorks Ensemble Pro 1.2 was what I had on my new 286/16 clone system back in the early '90s. 2.x was a bit slower because they changed the code base, but still faster the MS Windows 3.x on the same system. I have GeoWorks Ensemble Pro 1.2 on my current Redstone XT Turbo /EGA box.Well, to be honest....any "minimum requirements" coming from M$ are pretty much a joke.
I ran a PC/XT (640K Ram + 2MB LIM) with Win 3.0 and Geoworks 1.x/2.x blew the doors off it for speed and usability. Now that was a real GUI.