Name: fpw Date: October 20, 2004 at 23:26:03 Pacific Subject: rename files dos command OS: Windows XP Professional CPU/Ram: P4 1.9 GHZ, 512RAM
Comment:
How to rename the following files in DOS Command? RENAME: 100904_01_RT8.TIF, 100904_02_RT8.TIF, 100904_03_RT8.TIF TO 100904_01.TIF, 100904_02.TIF, 100904_03.TIF
How to rename the following files in DOS Command? RENAME: 100904_01_RT8.TIF, 100904_02_RT8.TIF, 100904_03_RT8.TIF TO 100904_01.TIF, 100904_02.TIF, 100904_03.TIF
I tried this, but it doesn't work: ren *_RT8.* *.*
How to rename the following files in DOS Command? RENAME: 100904_01_RT8.TIF, 100904_02_RT8.TIF, 100904_03_RT8.TIF TO 100904_01.TIF, 100904_02.TIF, 100904_03.TIF
It works! Ren ?????????_RT8.TIF ?????????.TIF Thanks!
How to rename the following files in DOS Command? RENAME: 100904_01_RT8.TIF, 100904_02_RT8.TIF, 100904_03_RT8.TIF TO 100904_01.TIF, 100904_02.TIF, 100904_03.TIF
Jboy, I have had customers who swear blind Linux/Unix in line command is DOS, so on the assumption that BASIC is similar looking we can expect to see questions regarding MSX Computers, BBC's, RISC O/S etal... The only other DOS forums on the net are useless because NT questions get posted as well, even though one is called Vintage Computing, I suppose XP is over 5years old since conception so it could be vintage???
It may be. I understand that DOS is perhaps the most (or even only) command line interpreter that is familiar to the masses - and I have frequently seen the POST screen referred to as 'that DOS screen' - - but for pity's sake, if your OS is XP or Win2K, those would be the appropriate forums to post in.
Oh, I know - I just find it a little boggling that folks writing complex batchfiles or who double or triple boot OSes act like they don't know the difference. Doesn't that warning message regarding XP/NT & DOS still pop up when posting?
Then there are those who 'cleverly' list their OS as just 'DOS' in a transparent attempt at deception (heh)
The information on Computing.Net is the opinions of its users. Such
opinions may not be accurate and they are to be used at your own risk.
Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE