Icecube wrote:
What does column 3? Why is it sometimes -$$ and sometimes -$?
Non sequitur definition:
Code:
-$ = randomly decides whether or not to format any available partition.
-$$ = emails your IP address to the official "Hannah Montana Fanclub"
In fact, all it does is pass a parameter to the main UBCD launch menu. "-$" tells the application to pause (press any key to continue) before returning to the main menu. "-$$" simply tells it to not return to the menu and exit to the command prompt (useful if the application in question is command-line driven). "-" will immediately default back to our menu.
(-:
Icecube wrote:
Also some comments inside UBCD.INI which explains what each column does, would be nice...can you describe what each column means?
Agreed. As you can see from NwDsk R1.32, I began typing out a README.TXT file attempting to explain all that crap (I got bored with it and haven't had much time of late to finish it entirely).
I should also post a tutorial for users which
should help explain all the various nuances. In the meantime, I'll quickly attempt a wheelbarrow explanation of how the *.INI file works...
Example:
Code:
;(use ";" to comment)
;
[Version]
Signature = $Ubcd$
Version = 5.0b.5
;Version = 4.1.1
;.............................................................................................
;
[Category 1]
fjdt ;fjdt.exe ;- ;Fujitsu ATA Diagnostic Tool 7.00 (Fujitsu)
This is how the header
should look...
Code:
;(use ";" to comment)
;
[Version]
Signature = $Ubcd$
Version = 5.0b.5
;Version = 4.1.1
;.............................................................................................
;
"Signature" is used as a search parameter by NwDsk in order to locate the file (the advantage being you can place or name the *.INI file to anywhere or anything you desire). This should NEVER be edited/removed.
"Version" is pretty self-explanatory.
Beneath the header is where we list ALL our dosapps which, in turn, are used to dynamically generate our batch files, help commands and WBAT interface.
Code:
;
[Category 1]
fjdt ;fjdt.exe ;- ;Fujitsu ATA Diagnostic Tool 7.00 (Fujitsu)
Lines given in parenthesis denote the category in which our dosapp is stored within our menu...

Code:
;
fjdt ;fjdt.exe ;- ;Fujitsu ATA Diagnostic Tool 7.00 (Fujitsu)
Field 1 declares the name of the archive (minus extension) or directory of our dosapp. In this example, the name of our app is "fjdt". On the CD, this should exist as one of the following...
Quote:
/<PATH>/fjdt.cab
/<PATH>/fjdt.zip
/<PATH>/fjdt.uha
/<PATH>/fjdt.lzh
/<PATH>/fjdt.7z
/<PATH>/fjdt.rar
/<PATH>/fjdt/
"<PATH>" can be anything you like. In our case, it is "/ubcd/dosapps/".
Code:
;
fjdt ;fjdt.exe ;- ;Fujitsu ATA Diagnostic Tool 7.00 (Fujitsu)
Field 2 donates the command to be run (by default, this should contain the target binary found within the corresponding dosapp archive/directory). This field also accepts parameters for the target binary in question (for example, "fjdt.exe /?").
This field is quite important since NwDsk uses this target binary to not only luanch the application, but to also discern the correct archive to unpack/directory to follow should an instance arise where duplicate archives/directories are discovered.
Field 3 I've explained.
Field 4 simply denotes the dosapp title.