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: PMS Witch who wrote (12034)	9/22/2000 4:45:21 PM
From: thecow	Respond to of 110654

DOS giving Windows a poke and shaking it off the couch to do some work. I'm sure this reminds you of your husband...LOL tc :-)

To: PMS Witch who wrote (12034)	9/24/2000 6:52:28 PM
From: d. alexander	Respond to of 110654

>>>50 Line DOS ... When I first tried, I didn't follow properly, but went back today & got it!... may have opened Pandora's box here. The only DOS program I have ever used is the Worden TC3. RIP. It was a beauty. When Windows is snoozing, it may be saving power. Everything that saves power seems to operate less than optimally esp. air-conditioners. Indeed a champion thread! And thank you again for all of the DOS assistance. Dorothy

To: PMS Witch who wrote (12034)	11/2/2000 4:34:14 PM
From: PMS Witch	Respond to of 110654

DOS window sizes re-visited... Some time ago, I posted a method for DOS programs to determine the screen sizes they're running in. When I first wanted to do this, the idea seemed simple and straight forward enough -- a few lines of code and a system call should've done the trick. But nooooo! I found myself drawn deeper and deeper into the pit of computer ignorance as I found myself boxed-in at every turn by a lack of information. Finally, I conjured a hack that worked: Move the cursor down LOTS, and read its location. Now I've found the elegant solution I was looking for originally. The information I want is returned in DL by INT 10H function 11H, a job done by only a tiny bit of code. inregs.x.ax=0x1130; int86(0x10, &inregs, &outregs); lines=((outregs.x.dx&0xFF)+1); Needless to say, the workings of this function is for the most part undocumented, (or documented as RESERVED) which makes its use an under-the-table proposition. Further, it's annoying to need to resort to using grey-area programming to get things done. Anyway, if anyone copied my original hack, they may want to take a look at changing it. Cheers, PW.