| author | ecalot
<ecalot> 2004-06-07 01:57:29 UTC |
| committer | ecalot
<ecalot> 2004-06-07 01:57:29 UTC |
| parent | 4154c4d92a8617a37cfaf292540680951ad14efe |
| PR/doc/editionfaq.htm | +82 | -0 |
| PR/doc/faq2.htm | +77 | -0 |
| PR/doc/shellusage.htm | +371 | -0 |
diff --git a/PR/doc/editionfaq.htm b/PR/doc/editionfaq.htm new file mode 100644 index 0000000..0c86a50 --- /dev/null +++ b/PR/doc/editionfaq.htm @@ -0,0 +1,82 @@ +<h3>PR 0.9-R2 Resource edition Frequent Asked Questions</h3><div align=justify> + +<p><dd><b><font color=red>Q:</font> What extraction formats are supported?</b> + +<p><dd><b><font color=red>A:</font></b> Take a look at the current version readme.txt file for explained specifications. Anyway, BMP, WAV, MID, PAL (jasc format) and PLV are supported. + +<p><dd><b><font color=red>Q:</font> I'm importing an image but it gots corrupted in the game, why?</b> + +<p><dd><b><font color=red>A:</font></b> Perhaps this is a bug, we aren't perfect. Anyway, be careful to keep the format options in the extracted file (don't change the number of colour sets, format compression, etc). We invite you to contribute and report the bug, in that case please check that you are having the latest version and fill in the bug report form from <a href=http://project.princed.com.ar>http://project.princed.com.ar</a>. + +<p><dd><b><font color=red>Q:</font> I'm importing an image but PR doesn't want to import it?</b> + +<p><dd><b><font color=red>A:</font></b> First use the -v or --verbose option to see what image is that. Then check if the image exists and, if you are un unix-like systems, check case of the file, remember some operating systems are case sensitive. If the image exists, check that this image has a palette of 16 colours and the format is correct. Some images are in a two-color format, make sure that images aren't one of them (check them in resources.xml if palette is set to monochrome). + +<p><dd><b><font color=red>Q:</font> I don't understand the palettes!</b> + +<p><dd><b><font color=red>A:</font></b> First of all, remember we made the editor, not the dat format, so there are some things we would change if we where the game coders, for example this one. The DAT format supports only one palette for a group of images. This means that if you want to change the palette for one image you have to change all other images' palettes. Read the questions below to understand it. + +<p><dd><b><font color=red>Q:</font> So, how can I edit a palette of a group of images?</b> + +<p><dd><b><font color=red>A:</font></b> You have to edit the palette of one image and export it to the PAL file that represent this group. For example for all images in vdungeon.dat the palette is called dungeon.pal. If you want to know what palette belongs to what image, just take a look at resources.xml. Note that the palettes in each BMP files are just for viewing purposes, changing them won't change the original palette; the only way to change the original palette is changing the PAL file. The import tool will always ignore the palettes for all BMPs files, and use the PAL file. Make sure to use the JASC PAL format (supported by Paint Shot Pro), other format like MS PAL aren't supported. + +<p><dd><b><font color=red>Q:</font> Ok, I changed the palette file, now what?</b> + +<p><dd><b><font color=red>A:</font></b> If you want all the BMP files you are editing to be updated with the new palette, just import the file and re export it again. The new palette will be propagated to all the files. Now you can edit the files using the palette that will be displayed in the game. + +<p><dd><b><font color=red>Q:</font> I replaced the PAL file and now all the images have the colours swapped. Any suggestions?</b> + +<p><dd><b><font color=red>A:</font></b> Remember that the palette has an index order, you must keep this order if you want the images to be displayed correctly in the game. To prevent/solve this problem you have to fix the palette order, the easy way is applying the new palette using the nearest colour method to the affected images before the palette changing. A palette will be exported rightfully only if the colour indexes are in the same order as the PAL file, to check this you can apply the palette using the palette index number method. + +<p><dd><b><font color=red>Q:</font> Is there any definition loss?</b> + +<p><dd><b><font color=red>A:</font></b> Yes JASC palettes has 24 bit RGB values (16,7 millions of colours), DAT palettes has 18 bit RGB values (262144 colours). Colours are approached to the nearest 18-bit colour equivalence. For example the RGB colour (123,122,121) will became (124,124,120) using all multiples of 4. This is the only definition loss. After this approaching is done the first time, you can export and import a DAT file all the times you want and the definition will be the same. + +<p><dd><b><font color=red>Q:</font> I'm not sure where to find the correct PAL file for an image</b> + +<p><dd><b><font color=red>A:</font></b> This is the hardest way, but if you insist... Open resources.xml with a simple text editor (vim, notepad, TextPad, etc). Look for the file name of the BMP image. This will appear in an item tag like this <code><item value="478" external="chopped.bmp">Prince Chopped</item></code>. this item belongs to a bigger item,in that case <code><folder external="deaths"></code>. This means that the file is in the deaths folder. This item is in a bigger item section like this: <code><folder name="Our prince and mouse images" file="kid.dat" external="kid" palette="400" itemtype="image"></code>. Now we know that the folder that contained the image is in directory "kid" and its palette value is 400. Then just look at a resource where value="400" inside the folder of the same file, in this case file="kid.dat", so we'll find <code><item value="400" external="kid.pal" itemtype="palette">Resource number 400</item></code>. This means that a palette value 400 is correctly a palette and the external name is kid.pal. + +<p><dd><b><font color=red>Q:</font> How can I edit resources.xml?</b> + +<p><dd><b><font color=red>A:</font></b> Open it, read instructions and comments written there and happy editing. + +<p><dd><b><font color=red>Q:</font> How can I edit PCS files?</b> + +<p><dd><b><font color=red>A:</font></b> We will release our little piano program some day! Anyway, readme.txt explains the format. + +<p><dd><b><font color=red>Q:</font> How can I edit the other guards?</b> + +<p><dd><b><font color=red>A:</font></b> All guards are sharing the BMP files, and have different palettes, so you can only edit the palettes. If you really want to edit them, there is a file in prince.dat called guard palettes.ext. Using an <a href="http://www.chmaas.handshake.de/delphi/freeware/xvi32/xvi32.htm">hex editor</a> you may edit it this way: There are 16 colours per guard, each colour has 3 bytes. So a guard has 48 bytes (the file has 7 guards and 336 bytes). The colour index numbers are in order. So if you want to locate the colour 4 of the guard type 3 it is: +<br><dd><dd><code>3*colourNumber+48*guardNumber = 3*4+48*3 = 156</code> +<br><dd>Remember the enumeration starts from 0. A colour field of 3 bytes has this format: one byte for the Red saturation value, one for the green and one for the blue following that order. The values are unsigned and from 0 to 64. So you have to multiply this values by 4 to get the palette saturation value. For example the 3 bytes that starts in 156 are 1E 17 0E in hex and 30, 23, 14 in decimal. 30*4=120; 23*4=92; 14*4=56; so the RGB value of the fifth colour (indexed 4) of the palette of the fourth guard (3 if we count the first guard as 0) is (120,92,56). Note they are all multiples of 4. Maybe some day we will include a support of this file in PR. + +<p><dd><b><font color=red>Q:</font> I improved a bit resources.xml in order to make easier my editing</b> + +<p><dd><b><font color=red>A:</font></b> What are you waiting? Send it! We may include it in the next release! + +<p><dd><b><font color=red>Q:</font> I edited resources.xml but now my compiled files are broken?</b> + +<p><dd><b><font color=red>A:</font></b> Use the provided resources.xml's, we have tested them a lot. In case you invested too much time in that and you don't want it to be wasted, send it, we have developed some tools to check, detect errors and fix broken resources.xml. Remember: <b>don't delete items</b> you don't know what are them for, if one item is missing or has another identification value, all imported DAT files using this item may be broken. Even ext files are needed. + +<p><dd><b><font color=red>Q:</font> PR doesn't work in my game set?</b> + +<p><dd><b><font color=red>A:</font></b> Current resources.xml file only supports POP 1.4. You may want to make your own resources.xml for your version, in that case, empty the current resources.xml you have, only leave the itemtypes and ?xml version tags and export the dat files. Exported files will be autodetected and saved in the unknown folder with the unknown.xml file. There it is the information of your dat file, you can add it to the resources.xml you made and edit the descriptions, etc.</a>. + +<p><dd><b><font color=red>Q:</font> Ok, I've finished a graphic or level set, can I publish it?</b> + +<p><dd><b><font color=red>A:</font></b> Yes, of course, it's your work and you can publish. We ask you to publish it under the GPL or any compatible license. We have a site where we centralized all the level, graphic ans sound sets made for Prince of Persia, we recomend you to publish it there because it is there where the people will look first. The site is <a href="http://www.princed.com.ar/artworks/">http://www.princed.com.ar/artworks</a>. + +<p><dd><b><font color=red>Q:</font> I Hex-edited a DAT file and now prince of persia asks me for the disks. How did you do to avoid this problem?</b> + +<p><dd><b><font color=red>A:</font></b> Work, work and more work. Each resource has a checksum, there is an index for each dat file, the format is very complicated. If something is wrong the game will ask for the instalation disks. Hex-editing a dat file without any expirience or reading any documentation could become a bit frustrating and damage your dat files. We spent a lot of time getting this error until we discovered how to calculate the checksums, how the index works, how to locate it, etc. We are working in a DAT file format specification for those people who wanna know how he format is. Anyways we highly recommend coders to use our libraries. We don't want to make people work in something that was already done, so we opened the source and you are able to look into and edit it under the terms of the GPL. + +<p><dd><b><font color=red>Q:</font> How to contact you?</b> + +<p><dd><b><font color=red>A:</font></b> <a href=http://forum.princed.com.ar>here</a>. +</div> +<pre> + +(c) 2003 - Copyleft Princed Development Team + http://www.princed.com.ar + +Last update: 2004-02-18 16:57 UTC-3</pre> diff --git a/PR/doc/faq2.htm b/PR/doc/faq2.htm new file mode 100644 index 0000000..1753118 --- /dev/null +++ b/PR/doc/faq2.htm @@ -0,0 +1,77 @@ +<h3>PR 0.9-R2 Usage Frequent Asked Questions</h3> + +<p><dd><b><font color=red>Q:</font> What features has PR got?</b> + +<p><dd><b><font color=red>A:</font></b> PR was designed for three basic functions: +<ul> + <li>Extracting DAT files into directories + <li>Importing directories into DAT files + <li>Getting information on DAT files +</ul> +<p><dd><b><font color=red>Q:</font> What exactly is extracting a DAT file?</b> + +<p><dd><b><font color=red>A:</font></b> When you have a file (e.g. vdungeon.dat) and you want the resources that are saved inside to be saved in directories in known formats (e.g. bmp) + +<p><dd><b><font color=red>Q:</font> What is resources.xml?</b> + +<p><dd><b><font color=red>A:</font></b> Is a file that saves easy names and descriptions for the content of the DAT files. When the extracted resources are re-imported the filenames are read from here. + +<p><dd><b><font color=red>Q:</font> What is to import a directory?</b> + +<p><dd><b><font color=red>A:</font></b> When you are reading a resource directory (e.g. a directory with the bmp or wav you need to make the DAT file) to make a DAT file, you are importing this directory. You need to have all resources there, in any other case the DAT file won't work fine in the game. + +<p><dd><b><font color=red>Q:</font> When you said the third basic function you said "Getting information on DAT files", what does exactly that mean?</b> + +<p><dd><b><font color=red>A:</font></b> Getting the DAT file type. e.g. vdungeon is image, digisnd is wave. + +<p><dd><b><font color=red>Q:</font> I want the program to make backups of the edited files. Is it possible?</b> + +<p><dd><b><font color=red>A:</font></b> Yes, run PR with the -b or --backup option and specify an extension (e.g. bak) and all files will be backuped in files with this name. (e.g. compiling a new vdungeon.dat will save the old file as vdungeon.dat.bak) + +<p><dd><b><font color=red>Q:</font> I don't want the program to ask if I want to replace a file, what can I do?</b> + +<p><dd><b><font color=red>A:</font></b> Use the -f or --force option. + +<p><dd><b><font color=red>Q:</font> I'm a web coder and I want to classify a file that is in the server</b> + +<p><dd><b><font color=red>A:</font></b> Run the program in the --cgi mode and capture the output in order to parse it. Take a look at the Princed Uploading System (that is under the GPL) at the Princed home page; this system uses PR to classify uploaded DAT files. + +<p><dd><b><font color=red>Q:</font> I'm extracting a level set (levels.dat) and I want to set the author of the extracted PLV levels to me</b> + +<p><dd><b><font color=red>A:</font></b> Use PR with the -a or --setauthor option and add a name to save in the author field of the PLV information. If you don't do that, the default author name "PR user" will be saved instead. + +<p><dd><b><font color=red>Q:</font> Can I use another resources.xml file?</b> + +<p><dd><b><font color=red>A:</font></b> If there is another newer version of the resources xml file, it is recommended to upgrade PR. But if you want to, you can rename your file to resources.xml or use the -m or --resource directive. + +<p><dd><b><font color=red>Q:</font> What is the raw option?</b> + +<p><dd><b><font color=red>A:</font></b> This is for format developers. But if you are interested, DAT files are archives, like tar and zip files. The files are stored indexed and compressed. The raw option exports or imports the files from the archive without performing any type of conversion or compression/decompression, so the extracted file is in the format the game uses (not compatible in most cases). + +<p><dd><b><font color=red>Q:</font> The program seems to work, but the result is an 8 bytes-length file.</b> + +<p><dd><b><font color=red>A:</font></b> Upgrade PR + +<p><dd><b><font color=red>Q:</font> The program seems to work, but the result is a file that doesn't work.</b> + +<p><dd><b><font color=red>A:</font></b> Try the -v or --verbose option, and check if all files are Ok. The verbose option has lots of extra information. + +<p><dd><b><font color=red>Q:</font> Is it possible to extract all dat files that are in all subdirectories of the specified directory?</b> + +<p><dd><b><font color=red>A:</font></b> Use PR -R or --recursive (take care with the upper case). This will recourse into directories and check out all dat files located in this directory and subdirectories. + +<p><dd><b><font color=red>Q:</font> What is the --unknown option for?</b> + +<p><dd><b><font color=red>A:</font></b> Hey, if you want to be a resources.xml writer, just contact us! + +<p><dd><b><font color=red>Q:</font> I'm working on a file called dungeonbyjohn.dat, and I don't want to rename it to vdungeon.dat each time I do an extraction. How can I do?</b> + +<p><dd><b><font color=red>A:</font></b> Use the -t or --datfile option. That is what it was made for. For example, if you want dungeonbyjohn.dat to be treated like vdungeon.dat, the valid syntax should be: +<dd><code>pr -tvdungeon.dat -xdirectory dungeonbyjohn.dat</code> + +<pre> + +(c) 2003 - Copyleft Princed Development Team + http://www.princed.com.ar + +Last update: 2004-02-12 01:06 UTC-3</pre> diff --git a/PR/doc/shellusage.htm b/PR/doc/shellusage.htm new file mode 100644 index 0000000..ca9b39e --- /dev/null +++ b/PR/doc/shellusage.htm @@ -0,0 +1,371 @@ +<h3>PR 0.9-R2 Compilation, shell commands and running samples</h3> + +<h4>Legend</h4> +<ul> +<li><font color=blue>OS Command line</font></li> +<li><font color=red>Typed by user</font></li> +<li><font color=green>Output text</font></li> +</ul> + +<h4>1) Shell Example of LCC Compilation under Win32</h4> +<pre> +<font color=blue>C:\princed\src></font><font color=red>set path=%path%;c:\lcc\bin + +</font><font color=blue>C:\princed\src></font><font color=red>path +</font><font color=green>PATH=C:\WINDOWS;C:\WINDOWS\COMMAND;<b>C:\LCC\BIN</b> + +</font><font color=blue>C:\princed\src></font><font color=red>ren makefile makefile.gcc + +</font><font color=blue>C:\princed\src></font><font color=red>ren makefile.lcc makefile + +</font><font color=blue>C:\princed\src></font><font color=red>make +</font><font color=green>Compiling import module... +Compiling compression module... +Compiling export module... +Compiling main module in standard mode... +Compiling resource manager module... +Compiling extra tasks module... +Compiling disk access functions... +Compiling xml parsing module... +Compiling xml search features... +Compiling bitmap files support (bmp)... +Compiling midi audio files support (mid)... +Compiling JASC palette support (pal)... +Compiling digital wave audio support (wav)... +Compiling prince level files support (plv)... +Compiling memory manager... +Porting the dirent structure... +Porting the Unix-like getopt function (first part)... +Porting the Unix-like getopt function (second part)... +Linking files... +<b>Program successfully compiled</b> + +Please read readme.txt for syntax information + +Time: 9.89 seconds + +</font><font color=blue>C:\princed\src></font> +</pre> +<h4>2) Shell Example of a normal GCC Compilation under several unix-like OS</h4> +<pre> +<font color=blue>-shell-2.05b$</font><font color=red> make +</font><font color=green>Compiling import module... +Compiling compression module... +Compiling export module... +Compiling resource manager module... +Compiling extra tasks module... +Compiling disk access functions... +Compiling xml parsing module... +Compiling xml search features... +Compiling bitmap files support (bmp)... +Compiling midi audio files support (mid)... +Compiling JASC palette support (pal)... +Compiling digital wave audio support (wav)... +Compiling prince level files support (plv)... +Compiling memory manager... +Compiling main module in standard mode... +Uncompressing resources... +Linking files... +<b>Program successfully compiled</b> + +Please read readme.txt for syntax information + +</font><font color=blue>-shell-2.05b$</font> +</pre> +<h4>2.1) Clearing object files</h4> +<pre> +<font color=blue>-shell-2.05b$</font><font color=red> make clean +</font><font color=green>Erasing temporary object files... +</font><font color=blue>-shell-2.05b$</font> +</pre> +<h4>2.2) Build Example</h4> +<pre> +<font color=blue>-shell-2.05b$</font><font color=red> make build +</font><font color=green>Erasing temporary object files... +Compiling import module... +Compiling compression module... +Compiling export module... +Compiling resource manager module... +Compiling extra tasks module... +Compiling disk access functions... +Compiling xml parsing module... +Compiling xml search features... +Compiling bitmap files support (bmp)... +Compiling midi audio files support (mid)... +Compiling JASC palette support (pal)... +Compiling digital wave audio support (wav)... +Compiling prince level files support (plv)... +Compiling memory manager... +Compiling main module in standard mode... +Linking files... +<b>Program successfully compiled</b> + +Please read readme.txt for syntax information + +</font><font color=blue>-shell-2.05b$</font> +</pre> +<h4>2.3) Problems with old Make versions. Very common in BSD systems</h4> +<pre> +<font color=blue>-shell-2.05b$</font><font color=red> make +</font><font color=green>"Makefile", line 9: Missing dependency operator +"Makefile", line 13: Need an operator +"Makefile", line 16: Need an operator +<b>make: fatal errors encountered -- cannot continue</b> +</font><font color=blue>-shell-2.05b$</font><font color=red> mv Makefile Makefile.new +</font><font color=blue>-shell-2.05b$</font><font color=red> mv Makefile.old Makefile +</font><font color=blue>-shell-2.05b$</font><font color=red> make +</font><font color=green>Compiling import module... +Compiling compression module... +Compiling export module... +Compiling resource manager module... +Compiling extra tasks module... +Compiling disk access functions... +Compiling xml parsing module... +Compiling xml search features... +Compiling bitmap files support (bmp)... +Compiling midi audio files support (mid)... +Compiling JASC palette support (pal)... +Compiling digital wave audio support (wav)... +Compiling prince level files support (plv)... +Compiling memory manager... +Porting the Unix-like getopt function (first part)... +Porting the Unix-like getopt function (second part)... +Compiling main module in standard mode... +Linking files... +Program successfully compiled + +Please read readme.txt for syntax information + +Compiling main module in library mode... +Making dynamic library... +Library successfully compiled + +Please read readme.coders.txt and pr.h for interfaces + +</font><font color=blue>-shell-2.05b$</font> +</pre> +<h4>2.4) PR Running Example</h4> +<pre> +<font color=blue>-shell-2.05b$</font><font color=red> cd bin +</font><font color=blue>-shell-2.05b$</font><font color=red> ./pr +</font><font color=green>Princed resources (PR) V0.9-R2 FreeBSD +(c) Copyright 2003 - Princed Development Team +http://www.princed.com.ar + +Usage: + pr [-x[EXTRACTDIR]|-c[COMPILEDIR]|-d] [DATFILEPATH] + pr [OPTIONS] [DATFILEPATH] + + Mandatory arguments to long options are mandatory for short options too. + + -c, --import[=DIRNAME] imports from DIRNAME into given dat file + -d, --classify returns the DAT file type + -x, -e, --export[=DIRNAME] extracts given dat file into DIRNAME + + -a, --setauthor=NAME sets your name in extracted PLV files + -b, --backup[=EXTENSION] backup your files + -f, --force default option, you cannot disable it, + so please make a backup of your files + -g, --cgi run as CGI and output mime headers + -h, -?, --help display this help and exit + -m, --resource=RESFILE uses an user-specific resource xml file + -r, --raw uses raw format + -R, --recursive searches for all dat files (only if DATFILEPATH + is not a dat file) + -t, --datfile=DATFILE specifies a dat file to read resources + different than the original file + --unknown generate the unknown file without performing + any extraction + -v, --verbose explain what is being done + --version output version information and exit + +</font><font color=blue>-shell-2.05b$</font> +</pre> +<h4>2.5) Version about</h4> +<pre> +<font color=blue>-bash-2.05b$</font><font color=red> cd bin +</font><font color=blue>-bash-2.05b$</font><font color=red> ./pr --version +</font><font color=green>Princed resources (PR) V0.9-R2 NetBSD +(c) Copyright 2003 - Princed Development Team +http://www.princed.com.ar + +Authors: + Coding & main routines + Enrique Calot + Santiago Zamora + + Graphic compression algorithms + Tammo Jan Dijkema + Enrique Calot + + Graphic format development + Tammo Jan Dijkema + Anke Balderer + + MID Sound format development + Christian Lundheim + + Resources.xml edition + Steven Fayers + +</font><font color=blue>-bash-2.05b$</font> +</pre> +<h4>2.6) Windows running examples</h4> +<pre> +<font color=blue>C:\princed\src\bin></font><font color=red>pr -xdir c:\prince + +</font><font color=green>Princed resources (PR) V0.9-R2 Win32 +(c) Copyright 2003 - Princed Development Team +http://www.princed.com.ar + +Scanning dat files in given directory +Extracting 'c:\prince\CDUNGEON.DAT' to 'dir' +Result: Ok (0) +Extracting 'c:\prince\CPALACE.DAT' to 'dir' +Result: Ok (0) +Extracting 'c:\prince\DIGISND1.DAT' to 'dir' +Result: Ok (0) +Extracting 'c:\prince\DIGISND2.DAT' to 'dir' +Result: Ok (0) +Extracting 'c:\prince\DIGISND3.DAT' to 'dir' +Result: Ok (0) +Extracting 'c:\prince\EDUNGEON.DAT' to 'dir' +Result: Ok (0) +Extracting 'c:\prince\EPALACE.DAT' to 'dir' +Result: Ok (0) +Extracting 'c:\prince\FAT.DAT' to 'dir' +Result: Ok (0) +Extracting 'c:\prince\GUARD.DAT' to 'dir' +Result: Ok (0) +Extracting 'c:\prince\GUARD1.DAT' to 'dir' +Result: Ok (0) +Extracting 'c:\prince\GUARD2.DAT' to 'dir' +Result: Ok (0) +Extracting 'c:\prince\IBM_SND1.DAT' to 'dir' +Result: Ok (0) +Extracting 'c:\prince\IBM_SND2.DAT' to 'dir' +Result: Ok (0) +Extracting 'c:\prince\KID.DAT' to 'dir' +Result: Ok (0) +Extracting 'c:\prince\MIDISND1.DAT' to 'dir' +Result: Ok (0) +Extracting 'c:\prince\MIDISND2.DAT' to 'dir' +Result: Ok (0) +Extracting 'c:\prince\PRINCE.DAT' to 'dir' +Result: Ok (0) +Extracting 'c:\prince\PV.DAT' to 'dir' +Result: Ok (0) +Extracting 'c:\prince\SHADOW.DAT' to 'dir' +Result: Ok (0) +Extracting 'c:\prince\SKEL.DAT' to 'dir' +Result: Ok (0) +Extracting 'c:\prince\TITLE.DAT' to 'dir' +Result: Ok (0) +Extracting 'c:\prince\VDUNGEON.DAT' to 'dir' +Result: Ok (0) +Extracting 'c:\prince\VIZIER.DAT' to 'dir' +Result: Ok (0) +Extracting 'c:\prince\VPALACE.DAT' to 'dir' +Result: Ok (0) +Extracting 'c:\prince\levels.dat' to 'dir' +Result: Ok (0) + +</font><font color=blue>C:\princed\src\bin></font><font color=red>cd dir + +</font><font color=blue>C:\princed\src\bin\dir></font><font color=red>dir + +</font><font color=green> Drive C label is PRTEST + Serial number id 1380-0FE3 + Directory of C:\princed\src\bin\dir + +. <DIR> 02-15-04 10:37p . +.. <DIR> 02-15-04 10:37p .. +UNKNOWN <DIR> 02-15-04 10:37p unknown +DIGISND1 <DIR> 02-15-04 10:37p digisnd1 +DIGISND2 <DIR> 02-15-04 10:37p digisnd2 +DIGISND3 <DIR> 02-15-04 10:37p digisnd3 +FAT <DIR> 02-15-04 10:37p fat +GUARDS <DIR> 02-15-04 10:37p guards +IBM_SND1 <DIR> 02-15-04 10:37p ibm_snd1 +IBM_SND2 <DIR> 02-15-04 10:37p ibm_snd2 +KID <DIR> 02-15-04 10:37p kid +MIDISND1 <DIR> 02-15-04 10:37p midisnd1 +MIDISND2 <DIR> 02-15-04 10:37p midisnd2 +PRINCE <DIR> 02-15-04 10:37p prince +PV <DIR> 02-15-04 10:37p pv +SHADOW <DIR> 02-15-04 10:38p shadow +SKEL <DIR> 02-15-04 10:38p skel +TITLE <DIR> 02-15-04 10:38p title +VDUNGEON <DIR> 02-15-04 10:38p vdungeon +VIZIER <DIR> 02-15-04 10:38p vizier +VPALACE <DIR> 02-15-04 10:38p vpalace +LEVELS <DIR> 02-15-04 10:38p levels + 0 files 0 bytes + 22 directories 394,055,680 free bytes + +</font></pre><small><b>Note</b>: now you can edit the files in each of those directories</small><pre> + +<font color=blue>C:\princed\src\bin\dir></font><font color=red>cd .. + +</font><font color=blue>C:\princed\src\bin></font><font color=red>pr -cdir c:\prince + +</font><font color=green>Princed resources (PR) V0.9-R2 Win32 +(c) Copyright 2003 - Princed Development Team +http://www.princed.com.ar + +Importing all valid files from given directory +Compiling 'c:\prince\title.dat' from 'dir' +File title.dat already exists. Replace? [Y/n/a]:y +Result: File succesfully compiled (0) +Compiling 'c:\prince\vdungeon.dat' from 'dir' +File vdungeon.dat already exists. Replace? [Y/n/a]:y +Result: File succesfully compiled (0) +Compiling 'c:\prince\vpalace.dat' from 'dir' +File vpalace.dat already exists. Replace? [Y/n/a]:a +Result: File succesfully compiled (0) +Compiling 'c:\prince\pv.dat' from 'dir' +Result: File succesfully compiled (0) +Compiling 'c:\prince\prince.dat' from 'dir' +Result: File succesfully compiled (0) +Compiling 'c:\prince\kid.dat' from 'dir' +Result: File succesfully compiled (0) +Compiling 'c:\prince\midisnd1.dat' from 'dir' +Result: File succesfully compiled (0) +Compiling 'c:\prince\midisnd2.dat' from 'dir' +Result: File succesfully compiled (0) +Compiling 'c:\prince\digisnd1.dat' from 'dir' +Result: File succesfully compiled (0) +Compiling 'c:\prince\digisnd2.dat' from 'dir' +Result: File succesfully compiled (0) +Compiling 'c:\prince\digisnd3.dat' from 'dir' +Result: File succesfully compiled (0) +Compiling 'c:\prince\ibm_snd1.dat' from 'dir' +Result: File succesfully compiled (0) +Compiling 'c:\prince\ibm_snd2.dat' from 'dir' +Result: File succesfully compiled (0) +Compiling 'c:\prince\skel.dat' from 'dir' +Result: File succesfully compiled (0) +Compiling 'c:\prince\vizier.dat' from 'dir' +Result: File succesfully compiled (0) +Compiling 'c:\prince\shadow.dat' from 'dir' +Result: File succesfully compiled (0) +Compiling 'c:\prince\fat.dat' from 'dir' +Result: File succesfully compiled (0) +Compiling 'c:\prince\guard.dat' from 'dir' +Result: File succesfully compiled (0) +Compiling 'c:\prince\guard1.dat' from 'dir' +Result: File succesfully compiled (0) +Compiling 'c:\prince\guard2.dat' from 'dir' +Result: File succesfully compiled (0) +Compiling 'c:\prince\levels.dat' from 'dir' +Result: File succesfully compiled (0) + +</font><font color=blue>C:\princed\src\bin></font> +</pre> +<hr size=1 color=red> +<pre> + +(c) 2003 - Copyleft Princed Development Team + http://www.princed.com.ar + +Last update: 2004-02-18 15:06 UTC-3</pre>