Code Comments
Programming Forum and web based access to our favorite programming groups.My first customer installed Vista (Basic) and did not agree to run a programm (clipper 5.3b) in a window. To enable full screen mode I've installed standard video driver and now I have following problems: - default refresh rate is too low and CRT monitor blinks while working with windows programms. Is it possible to change this rate? - program hangs after: ? chr(7) //bell msetcursor(.t.) Has anyone experienced other problems? Those effects are not present on my home's vista with original video driver (and text screens in a window only). Another way to work in full screen is installing XP version of video driver but i've read it could cause unstability. Has someone tried it?
Post Follow-up to this messageHello! XDDM drivers are the answer. Matrox has them, for example: http://www.matrox.com/graphics/en/c...1024234745.htmlquote:I AGREE! :) BTW, what graphics card has your first customer's PC? Regards, Roman "ktos" <ktos@nikt.pl> wrote in message news:fr9c0k$5t6$1@node2.news.atman.pl... > My first customer installed Vista (Basic) and did not agree to run a progr amm (clipper 5.3b) in a window. > To enable full screen mode I've installed standard video driver and now I have following problems: > - default refresh rate is too low and CRT monitor blinks while working > with windows programms. Is it possible to change this rate? > - program hangs after: > ? chr(7) //bell > msetcursor(.t.) > > Has anyone experienced other problems? > > Those effects are not present on my home's vista with original video drive r (and text screens in a window only). > > Another way to work in full screen is installing XP version of video drive r but i've read it could cause unstability. Has someone > tried it?
Matrox Graphics also decided not to redevelop drivers specifically for Windows Vista, as a result, end-users will have to use the so-called XDDM drivers for Vista, which virtually means using Windows XP drivers. Nevertheless, Matrox claims that this is not a drawback, but an advantage.
Post Follow-up to this message"ktos" <ktos@nikt.pl> je napisao u poruci interesnoj grupi:fr9c0k$5t6$1@node2.news.atman.pl... > My first customer installed Vista (Basic) and did not agree to run a > programm (clipper 5.3b) in a window. is there some divantage to run in full-sized windowed mode [the window that covers the whole screen]? the only problem could be to minimise win frame borders and title bar i am not sure for xp, but should expect that cmd win borders are fully adjustable [disappearable]
Post Follow-up to this messageDear sali: "sali" <sali@euroherc.hr> wrote in message news:frambr$md9$1@ls5.tel.net.ba... > "ktos" <ktos@nikt.pl> je napisao u poruci interesnoj > grupi:fr9c0k$5t6$1@node2.news.atman.pl... > > is there some divantage to run in full-sized windowed > mode [the window that covers the whole screen]? Micro$haft "deprecates" full screen DOS console windows on Vista. It is not available with any current video driver, and these drivers will autoupdate whenever Micro$haft feels like messing up your customer's system. > the only problem could be to minimise win frame > borders and title bar. i am not sure for xp, but should > expect that cmd win borders are fully adjustable > [disappearable] Works fine on XP and below. Will not work on Vista, unless you install outdated 16-bit drivers. David A. Smith
Post Follow-up to this message"N:dlzc D:aol T:com (dlzc)" <dlzc1@cox.net> je napisao u poruci interesnoj grupi:AQ9Cj.47185$kp6.2188@newsfe07.phx... > Dear sali: > > "sali" <sali@euroherc.hr> wrote in message > news:frambr$md9$1@ls5.tel.net.ba... > > Micro$haft "deprecates" full screen DOS console windows on Vista. It is > not available with any current video driver, sorry for missunderstanding i was not talking about "full screen dos console", but about "full-sized window" so, in my case it is the regular window, except it is sized so that covers as much as possible the whole screen. there are still win borders and title bar that need to be removed playing with console win properties
Post Follow-up to this messageSali, do you mean a Clipper app? have you found a way to let a Clipper app have dimensions beyond the 80 (or 132) columns and 25 (or 50) rows? The only way i know of is using tamedos console under xp, but have failed to find out how to let the app detect mouse clicks beyond the 80/50 limit; i'm just curious about what you're saying here frank "sali" <sali@euroherc.hr> wrote in message news:frambr$md9$1@ls5.tel.net.ba... > "ktos" <ktos@nikt.pl> je napisao u poruci interesnoj > grupi:fr9c0k$5t6$1@node2.news.atman.pl... > > is there some divantage to run in full-sized windowed mode [the window > that covers the whole screen]? the only problem could be to minimise win > frame borders and title bar > i am not sure for xp, but should expect that cmd win borders are fully > adjustable [disappearable] > >
Post Follow-up to this message"frank van nuffel" <nospam@nospam.be> je napisao u poruci interesnoj grupi:47d93e0c$0$11285$bf4948fe@news.tele2.nl... > Sali, do you mean a Clipper app? have you found a way to let a Clipper app > have dimensions beyond the 80 (or 132) columns and 25 (or 50) rows? The > only > way i know of is using tamedos console under xp, but have failed to find > out > how to let the app detect mouse clicks beyond the 80/50 limit; i'm just > curious about what you're saying here > no, i am just adjusting font size, clipper is still 50/25/80 row/col
Post Follow-up to this messageThx for confirming "sali" <sali@euroherc.hr> wrote in message news:frbjus$utq$1@ls5.tel.net.ba... > "frank van nuffel" <nospam@nospam.be> je napisao u poruci interesnoj > grupi:47d93e0c$0$11285$bf4948fe@news.tele2.nl... app > > no, i am just adjusting font size, clipper is still 50/25/80 row/col
Post Follow-up to this messageOn Mar 13, 6:27=A0am, "sali" <s...@euroherc.hr> wrote: > "N:dlzcD:aol T:com (dlzc)" <dl...@cox.net> je napisao u poruci interesnoj > grupi:AQ9Cj.47185$kp6.2...@newsfe07.phx... > > > > > > sorry for missunderstanding > > i was not talking about "full screen dos console", but > about "full-sized window" The OP says his customer will not accept a window, regardless of how big one might make it. See where he / she said "My first customer ... did not agree to run ... in a window". Micro$haft "Welcomes" you to your own hardware, and now intentionally limits what you can do with it. David A. Smith
Post Follow-up to this message"dlzc" <dlzc1@cox.net> je napisao u poruci interesnoj grupi:727948a9-f93c-4a7c-a7e9-49582c78e846@i12g2000prf.googlegroups.com... On Mar 13, 6:27 am, "sali" <s...@euroherc.hr> wrote: > "N:dlzcD:aol T:com (dlzc)" <dl...@cox.net> je napisao u poruci interesnoj > grupi:AQ9Cj.47185$kp6.2...@newsfe07.phx... > > > > > > sorry for missunderstanding > > i was not talking about "full screen dos console", but > about "full-sized window" The OP says his customer will not accept a window, regardless of how big one might make it. sorry for missunderstanding, but i found just "not accept a window", there is no mention about screen-sized window, just "normal" window i have few places where customer accepted reasonably big window, filling almost whole screen. windowed clipper app has also an advantage that screen-saver will not drop full-screen to taskbar and confuse user, and other tools are also more readily available when run in [big] window than dos-full-screen anyway, i perfectly know what are you talking about, my solution is if you may-not-beat-it, then at-least-try-to-avoid-it!
Post Follow-up to this messagePowered by vBulletin
Copyright 2000-2006 Jelsoft Enterprises Limited.