Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Computer Learning -- Ignore unavailable to you. Want to Upgrade?

To: d. alexander who wrote (12022)	9/22/2000 11:46:27 AM
From: PMS Witch	Read Replies (3) \| Respond to of 110653

50 Line DOS ... DOS windows act in many ways just like a DOS machine. But since they are windows, they are text representations on your monitor which is operating in graphics mode. Windows translates your DOS text into graphics which looks like text and displays it in your DOS windows. You can choose the typeface (font) and size. One other choice, is how many lines your window will display. Right-click your DOS icon, choose the screen tab and select from the Initial size area -- 25, 43, or 50 lines along with Default. (Don't forget to click Apply!) It goes without saying that 50 line windows have tiny characters. Most DOS software is designed for 25 line screens. WordPerfect, for example, only occupies the top half of a 50 line DOS window. DIR, TYPE, and programs which simply print text usually take advantage of the extra available lines. Some MSFT software 'expands' while others doesn't. A general rule seems to be that programs manipulating the screen don't adjust well, while programs which simply print do. I've altered my programs to sense window sizes and act appropriately. Now, if I could only get my husband to act appropriately. Cheers, PW. P.S. I was mystefied on how my programs would sense the window sizes they were running in and I posted to this thread for assistance. In short order, I receieved replys pointing me in the right direction. To those who've helped, I owe, and wish to express, much gratitude. P.P.S. One thing I had to get used to upon moving from a DOS to Windows system was my DOS programs getting their memory requests filled by Windows. Typically, a DOS program requests memory from DOS and this desired memory is allotted instantly. On a Windows machine, windows fills the memory request. If Windows hasn't been inactive for a while, it tends to doze off, and before it grants additional memory to DOS, it must become alert first. This delay is noticable, but not particularly disturbing. In fact, I can just picture DOS giving Windows a poke and shaking it off the couch to do some work.