This program is save in my opinion, but to prevent nasty things, I will 
NOT be responsible for anything that might happen due to use of this 
program or any related file or document.

p.s. this still stands if there are some spelling errors in the above, 
the  program and this readme file are created within the hour I call it 
OWNYOURRISK-ware.


use: NRename <srcname> <destformat> [<seperator>]
       destformat = [<prefix>]#minw[<postfix>]
             minw = minimal width of number [0..9]
        seperator = a character after which your relevant number will be


Example your files are named:

ozon122.jpg
ozon123.jpg
ozon124.jpg
ozon125.jpg
ozon126.jpg
ozon127.jpg
ozon128.jpg

and you want them to be 

ozon_jpg.122
..
ozon_jpg.128

You do NRename <filename> ozon_jpg.#3

where filename can be %s or something like this in diskmaster
( you have to know how to config these programs of course :) )


PROBLEM 1:

if you have frames like this :
 
ozon1_122.jpg
ozon1_123.jpg
ozon1_124.jpg
ozon1_125.jpg
ozon1_126.jpg
ozon1_127.jpg
ozon1_128.jpg

and you want them to be 

ozon_jpg.122
..
ozon_jpg.128

And you do NRename <filename> ozon_jpg.#3


you wil have wrong results namely 

ozon_jpg.1
..
ozon_jpg.1

and this cannot be because the names are the same.

misery misery misery misery misery misery or not !?!?!?




NO, the solution is there or here .

use a seperator, a what, a seperator !!!!

what is this. this is a vague something which can be used to solve this 
problem.

Example , use this !!

And you do NRename <filename> ozon_jpg.#3 _

now the source filename is scanned till a _ and 
only after this seperator the count-number 122..128 is found, 
and the result will indeed be

ozon_jpg.122
..
ozon_jpg.128


PROBLEM 2:

You got zilion of frames to rename, and it takes diskmaster ages to 
rename all the frames, this is partly due to the fact that it loads
nrename every time from disk.

solution 1 : resident c:nrename FORCE
solution 2 : copy nrename to ram: 
( don't leave the original in a other path like c: and
  make sure a path points to your bits and bytes over there)



PROBLEM 3:

your files are named abcd.00001 etc.
and you want to lose some zero's

solution: Still a wacky one, read below.

Lose one zero at a time by making the seperator a 0

b.v. srename %s abcd.#3 0




Please E-mail bug reports, and let me know you are there.

D.Murray
iron-iq@dds.nl member from the all famous (or should be) lodge.

* * * * * *This program was tested and approved by lodge* * * * * * * *
lodgelodgelodgelodgelodgelodgelodgelodgelodgelodgelodgelodgelodgelodgel
odgelodgelodgelodgelodgelodgelodgelodgelodgelodgelodgelodgelodgelodgelo
* * * * * *This program was tested and approved by lodge* * * * * * * *

 PERMSSN    UID  GID    PACKED    SIZE  RATIO     CRC       STAMP          NAME
---------- ----------- ------- ------- ------ ---------- ------------ -------------
[generic]                 4174    6632  62.9% -lh5- 059e Aug  4  1996 nrename
[generic]                 1251    2894  43.2% -lh5- 4b79 Aug  4  1996 nrename.readme
---------- ----------- ------- ------- ------ ---------- ------------ -------------
 Total         2 files    5425    9526  56.9%            Aug 10  1996