DIR /W command and system32 folder

[Saxet Nitsua]

Ok, this has me going insane. I am unable to get the DIR/W command to display wide inside the c:\windows\system32 folder in windows 7. It only displays single column, any command parameter that I try with the DIR command inside the system32 folder will not function. I cannot even get the /P or the /A or any of them to work, just SQUAT. The DIR command functions normally outside the system32 folder and this has me baffled. I am sick and tired of this whacked out security in windows 7 on my hard drive and folders and it is maddening when you cannot even perform the most basics of console commands like DIR without something weird going on; this also applies to other functions, but that is another story. It is like Microsoft wants you to do jack on the computer inside a console. Do they think we are a bunch of imbecilic retarded people?

I have changed the security access rights on the entire drive and the same thing still happens, I try to do a basic DIR/W in the system32 folder and it is single column listing, I even tried using DIR/W c:\windows\system32\*.* and the same single column will be produced.

If anyone can shed some light on this it would be gratefully welcome on my end. I am an avid console user and do not like using the mouse unless I have to. So I tend to operate windows solely within a console window.

Thanks...
The Doster Prompenstein (Doctor Frankenstein, pun)

 

[popatim]

are you running the cmd window with admin right? (rt click the cmd icon & then select Run as Administrator)

 

[Saxet Nitsua]

are you running the cmd window with admin right? (rt click the cmd icon & then select Run as Administrator)

---
Yes, I am running the cmd console in Administrator mode. I am always in Admin mode for console mode. I do not use GUI mode. Thanks for the thought though. I have found the reason though for why the DIR/W command was not functioning. I have posted it on my thread. The reason is quite strange. You might want to read it.

Again, thank you for your response.

Saxet
The Doster Prompenstein

 

[getochkn]

What thread did you post your solution on?

 

[Saxet Nitsua]

Ok, I have found the solution on my own, and this makes no sense. Oddly enough the DIR/W command has a screen format in Windows 7 Professional that is not standard for some odd reason.

Here is what I have found out. As with other previous operating systems, all files and formats were geared and set for a screen width of 80 characters.With further investigation as to why DIR/W was not functioning in the system32 folder I decided to let this forum try to bang away at it and I continued to configure my console the way I had it on all other systems. I use on a 27 inch monitor with a resolution of 1920x1080 and the console buffer size to 235x80, and windows size 235x80, with position set to 0x0, I do not let system position window.

Here is where it got weird, the DIR/W command was working normally after that. As to the reason the /W parameter did not work in normal console window default size is left unknown, I have yet to get a response back from TechNet at Microsoft when I called them about this, they basically ignored me and said they will get back with me. This was yesterday morning and they have not responded, I guess they never will. And I have a business account with them.

So I found that default console will not display the command DIR/W correctly in some Windows 7 Pro directories due to screen width formatting. The threshold setting for the system32 folder is a width of 109, this is different for other folders due to file name size and folder name size. This makes no sense as to why this is, and again Microsoft seemed to just ignore me when I called TechNet support.

Some people might want to personalty see this on their systems running Windows 7 Professional, this possibly is also present in other Windows operating systems above XP but I do not know. I was forced to use Windows 7 Pro in June due to my last system being fried in a lightning storm when lightning struck the back of my house.

This glitch was never in windows XP and why it is in Windows 7 Pro is beyond me. So I just chock this up as another strange thing Microsoft does to bug the hell out of the consumer.

I thank popatim for his reply about console admin privilege, even though it was not the problem, it was a good reply.
Thank you popatim.

Saxet
The Doster Prompenstein (Doctor Frankenstein, pun)

 

[Saxet Nitsua]

What thread did you post your solution on?

This thread, I just posted it.