[ddots-l] Re: screen resolution
- From: "Robert Hall" <truecut@xxxxxxxxx>
- To: <ddots-l@xxxxxxxxxxxxx>
- Date: Sat, 1 May 2010 19:05:26 -0500
Well Stacy:
I have a wireless keyboard and the only thing I can ever recall doing on my
system that makes me kind of suspicious: was when I accidentally pressed a
button on my keyboard's transmitter, there was a delayed count from the moment
I pressed the key until I heard the next number. It went something like this:
Example: I accidentally pressed the key and then I heard (2) and then maybe
five seconds passed and then I heard my system say (3). The key that I
accidentally pressed is rather flush with the surface of the transmitter and I
keep it on the top of my PC desk just underneath the front set of USB port and
I often switch two USB drives that share the same ports. Perhaps it is vary
sensitive to even the slightest touch, so I try to avoid even touching it when
I have to move it. All I know Stacy, is that none of my sighted buddies never
encountered such strange happenings with my screen before I plugged in my
wireless keyboard. Truthfully Stacy, I don't really know what causes the screen
to rotate because it is not always spoken by JAWS, unless you're inside of
Sonar: but it is a great relief to me to know that (ctrl-shift+ the plus key on
the numpad) will fix it. I hope you resolve your issue soon, Robert.
----- Original Message -----
From: Stacy Blackwell
To: ddots-l@xxxxxxxxxxxxx
Sent: Friday, April 30, 2010 1:17 PM
Subject: [ddots-l] Re: screen resolution
Thank you so much, Robert! I will try this tonight before the incoming storm
hits (hopefully). I will report back on Monday what happens.
If, for some reason I did some type of command accidentally that disengaged
this Video Intercept, then maybe restating the resolution will make things
right. I have a feeling though that the lack of resolution is the result of
the missing V.I., but, I hope the reverse is true -- that the reduced
resolution caused the V.I. dialog to appear.
Robert, if all of this turns out to be true, and for the rest of the list,
can you recall what you did that could have changed your resolution in the
first place? I have pondered this and I do recall pressing incorrect keys and
moving my arrow keys recently and hearing a 1, 2, and 3. I quickly hit escape
and then Alt F4. I do not know, however, if this was the session prior to the
next boot up that revealed the V.I. Intercept dialog. But, hey, buddy, you are
giving me hope! Control-shift +, Got it!
SLB
------------------------------------------------------------------------------
From: truecut@xxxxxxxxx
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: screen resolution
Date: Thu, 29 Apr 2010 22:03:48 -0500
No problem! that's what being on the list is all about, sharing information
and experiences that may someday be useful. Robert.
----- Original Message -----
From: Jörgen Hansson
To: ddots-l@xxxxxxxxxxxxx
Sent: Thursday, April 29, 2010 9:29 PM
Subject: [ddots-l] Re: screen resolution
Hi robert!
thanks for sharing this with us, itmay be very useful some day.
Ragards,
Jörgen Hansson!
Tel +46 703-601296
www.jorgenhansson.com
skype: djtropical4532
----- Original Message -----
From: Robert Hall
To: ddots-l@xxxxxxxxxxxxx
Sent: Thursday, April 29, 2010 11:07 PM
Subject: [ddots-l] screen resolution
Hi guys:
I would like to share an experience with you all especially Stacy! (hope
I spelled your name right). I just finished a recording session with a sited
buddy of minds and I have had this problem before and probably will again in
the near future, except now I know how to correct the problem. Outside of Sonar
because we don't use a monitor as a totally blind musician, it will literally
go un noticed and un spoken by JAWS. I was trying to check my recording levels
using the meters in Sonar: (F2), Sonar JAWS and CT would say "This function
failed, make sure that the main window and child windows are maximized". Ah!
what does this mean to me? well I ran the CT test (ctrl+F12) to check my screen
resolution, CT reported that my screen resolution had somehow changed to a
resolution of 768 by 1024, you got it! exactly the reverse of what it should
be. My sighted buddy said that the screen was literally at an angle, although
at one point when he viewed it, was completely up side down. I tried looking
through the settings for screen resolutions in the control panel to select the
correct settings, 'turns out it was not quite that simple, because even to my
sighted buddy the proper set of numbers were not among the list of choices. So!
what to do! I called another buddy of minds who is a blind computer technician
up and told him about my situation and asked him if he new how to correct this
problem. and he rescued me from a problem that could not be done in the display
menu of the control panel. He told me that it was a Windows command that
allowed computer user to rotate their screen and that there's actually a
keyboard command for us to use that will set the screen back to its proper
position and here it is: (ctrl+shift plus the plus-key). What you must do if Ct
discovers this is the case: shutdown or restart your computer. After your
computer comes back up and all programs have loaded perform the command above
then go into Sonar and open up a project that contains audio, because some of
the functions of CT are apparently not affected by the wrong resolution. Well!
I hope this help some one in some way. Robert
------------------------------------------------------------------------------
Hotmail has tools for the New Busy. Search, chat and e-mail from your inbox.
Learn more.
Other related posts:
