slow speed under Win 2000, et al.

Please use this Board for QBasic related requests ( file research, programming, etc.)

Moderators:Administrator, Global Moderator

Post Reply
Guest
slow speed under Win 2000, et al.

Post by Guest » Thu Feb 12, 2004 3:50 am

I've used QB87 for 12 years.  Compiled code running with BRUN3087 ran fast under older Windows.  The DOS under those Windows operating systems was fine.  The DOS emulated in NT and Win2000 is not fine.  I can tolerate the ugliness of the window display.   The running times are the problem.  I'm designing optics.  My programs are numerical and generally take many hours to run.  With earlier Windows and pentium chips, speed was directly proportional to the clock speed of the chip.  Now Win2000 with a 2GHz chip runs my programs less than half as fast as Win98 with a 500 MHz chip.  Question.  If I install Win98, or DOS, on a new 2GHz system, will the QB87 compiled code run four times as fast as Win98 with a 500MHz system?  Is that how to enjoy quaint QB plus the fast times?
Thanks.
DC

John_Schofield
Full Member
Posts:36
Joined:Tue Mar 18, 2003 3:04 am
Location:Lancashire, UK
Contact:

Re: slow speed under Win 2000, et al.

Post by John_Schofield » Sat Feb 21, 2004 8:40 pm

yes - I think that's your only option - dos is not native on Win2k etc and so has to be a simulated sort of dos mode for qb - at least that's my experience with the pcs at work which have xp whereas I'm still on 95 and 98 machines at home which run as quick (at least) as on the athlon megabest pcs at work

Dr_Davenstein
QBasic God
Posts:166
Joined:Tue Mar 25, 2003 12:45 am
Location:U.S.A.
Contact:

Re: slow speed under Win 2000, et al.

Post by Dr_Davenstein » Sun Feb 22, 2004 1:53 am

I heard something about setting QB's idle sensitivity property to low to cope with the speed problem. I've never used Win2K or WinXP, so I can't really say if this works or not. ???
Come check out [url=http://www.freebasic.net/forum/index.php]FreeBASIC[/url]. The syntax is based on QuickBasic, but it expands to use pointers, operator overloading, etc... The list goes on and on!

Post Reply