|
-
Jan 18th, 2006, 01:29 PM
#1
Command Console stupidity
I thought I was being clever, but it turns out I shot myself in the foot...
I had a command console opened and it only filled up half of my screen. I right clicked it in the taskbar and under properties, changed it to full window and applied it to all instances. I was hoping it would help with line breaks (it doesn't, just makes everything HUGE).
Each time I open a command promt now, it changes my resolution momentarily. I repoened a new command prompt, did the exact same thing to undo it (changed it back to the original settings) and applied it to all console windows, but it's not working. Whenever I rebuild a solution in .Net, it runs the compiler and momentarily blacks out my screen to change it's resolution.
Is there another place I can change this setting? This is driving me nuts...
Rate up to anyone who can help.
-
Jan 18th, 2006, 03:14 PM
#2
Re: Command Console stupidity
When you changed it back to window, did you save it?
TPM
Add yourself to the VBForums Frappr Map!!
-
Jan 18th, 2006, 03:15 PM
#3
Re: Command Console stupidity
Yeah, I applied to all instances with the same title.
-
Jan 18th, 2006, 03:30 PM
#4
Re: Command Console stupidity
Hmm that should work. Have you restarted the machine since you changed it back?
TPM
Add yourself to the VBForums Frappr Map!!
-
Jan 18th, 2006, 03:48 PM
#5
Re: Command Console stupidity
Just tried, still have the issue.
Whenever I build, it get to the "Building satellite assemblies" line and then goes black. It also happend whenever I run "C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\ilasm.exe" I attempted to run just that by itself so that I can hold a console window and change it there, but it won't let me. The exe runs and then closes before I can do anything with it. Opening my own command window and then running it doesn't produce the resolution change.
I'm pulling my hair out on this one ><
-
Jan 18th, 2006, 04:08 PM
#6
Re: Command Console stupidity
Check in regedit under these;
hkey_local_machine\software\microsoft\command process
hkey_current_user\software\microsoft\command process
Maybe there's some odd setting there
TPM
Add yourself to the VBForums Frappr Map!!
-
Jan 18th, 2006, 04:20 PM
#7
Re: Command Console stupidity
Nothin. It's just the one executible now. It's not a global issue and it only happens on my account (if I run it as admin, no problem).
-
Jan 18th, 2006, 06:17 PM
#8
Re: Command Console stupidity
Hmm I bet there's some Key under current user then. Try looking for ilasm or maybe framework.
TPM
Add yourself to the VBForums Frappr Map!!
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|