What happened to the DIR command

Discussion in 'Windows Desktop Systems' started by Guru-Choc, Mar 15, 2002.

  1. Guru-Choc

    Guru-Choc Guest

    Doing it in a directory now displays nothing even if the files are there, what should I use instead. I can't see the sense in taking this out.
     
  2. pc_tek

    pc_tek Guest

    try using a folder that has something in it :D

    dir works fine.
     
  3. Guru-Choc

    Guru-Choc Guest

    Um don't you think I would of tried that ??

    Tried all my drives, can't see anything when I type DIR, but I can type filenames in there and execute them fine.

    C:\Documents and Settings\Gareth Hall>dir
    Volume in drive C is MAIN
    Volume Serial Number is 0C67-12F7

    Directory of C:\Documents and Settings\Gareth Hall


    Directory of C:\Documents and Settings\Guru-CHoc

    File Not Found

    C:\Documents and Settings\Guru-Choc>e:

    E:\>dir
    Volume in drive E is VIDEOS
    Volume Serial Number is 3B66-1000

    Directory of E:\


    Directory of E:\

    File Not Found

    E:\>
     
  4. pc_tek

    pc_tek Guest

    wierd... my first guess would be that your cmd.exe got corrupt somehow. If i am not mistaken, the dir commend comes from that file. So I have zipped up my cmd.exe file for you to try to replace.

    Make a backup of your original first. Then drop mine into c:\windows\system32

    Let me know if this works.
     
  5. AmarSingh

    AmarSingh Guest

    yeah...dir should work fine, but you can also use the unix command ls that has options -l, -a, -F, -R etc
     
  6. Guru-Choc

    Guru-Choc Guest

    Thanks pc_tek, no joy at all :(

    Very weird indeed.
     
  7. pc_tek

    pc_tek Guest

    ntfs by chance?
     
  8. pc_tek

    pc_tek Guest

    one other thing.... entertain me here...

    try this..

    dir /ah

    :D
     
  9. Guru-Choc

    Guru-Choc Guest

    C:\>dir /ah
    Volume in drive C is MAIN
    Volume Serial Number is 0C67-12F7

    Directory of C:\


    Directory of C:\

    File Not Found

    C:\>
     
  10. Electronic Punk

    Electronic Punk Administrator Staff Member Political User Folding Team

    Messages:
    18,590
    Location:
    Copenhagen, Denmark
    I use NTFS and dir works fine.
     
  11. insaNity

    insaNity Guest

    you might be on the right track there - Try this instead:
    dir *.* /a

    that should show any file; be it hidden, system, normal or read only.

    also, what is your output of this command?:
    echo %dircmd%
     
  12. Guru-Choc

    Guru-Choc Guest

    Ah-ha, that works with the *.*, but why should Ii need too when others don't, is there some switch/setting that may be foobar ??
     
  13. insaNity

    insaNity Guest

    I think something is setting the %dircmd% environmental variable to a different filespec. The variable is there to customise DIR so you don't have to type in common switches every time.

    what is the output of:
    echo %dircmd%

    ?
     
  14. Guru-Choc

    Guru-Choc Guest

    Yes, I had changed a setting in the enviromental variables when I first installed XP, and hadn't used the dos window since, deleted that and all is well. Thanks for the help. I knew I musta done something wrong :)
     
  15. insaNity

    insaNity Guest

    Glad to help.

    Always satisfying to hear back that all is well :)
     
  16. pc_tek

    pc_tek Guest

    coolness... good job!
    :D
     
  17. phishhead

    phishhead OSNN Senior Addict

    Messages:
    422
    Location:
    San Diego, California
    the unix cmds don't work here...damn that would have been cool tool:mad: pc tek long time no see...peppys back and gone again be back up in a few days da boys have been asking about you over there same with rootnik:D
     
  18. insaNity

    insaNity Guest

    Unixisim. Just extract the files to a directory in your path enviro. variable.
     
  19. AmarSingh

    AmarSingh Guest

    oops...it must be that I have cygwin installed and the directory with the bins is set as an environment variable. I didnt even think of that, but i guess that explains why ls works. I just assumed that it was an added feature by MS. now that i check...most unix commands like make and rm work so it that must be the case. Sorry