If reading this file within your WebFunds directory, you might like to check the latest version.
Current Version: 1.8.1:
1.8.1 is the more robust version of 1.8.0 (which should not be used, it has a killer bug).
1.8.0: represents a migration to a new low-level SOX wallet, which also brings a lot of hidden changes.
Because of the substantial changes to internal code, and the likelihood that more problems will be faced as we bed this code in, the middle number has upped.
Go to History on site for earlier changes or this release History to see details of all prior changes.
In general, you need a JVM program. See Other Components for more help on Java.
|. . .||MacOS|
There seems to be a problem with StuffIt Expander's unzip feature, so unzip the package with something else, like MacZip, instead.
There is no need to move swingall.jar from the /Swing 1.1.1/ directory to the /WebFunds/ directory.
|Prepare (once only, if you Save Settings... As Application)|
Run JBindery from the /MRJ SDK 2.1/JBindery/ directory.
Select Command in left column and type in the first line: webfunds.client.Core
Select ClassPath in left column and click on the add .zip file button.
Open the Jars in the order listed in the above
Note that as you are running JDK 1.1, you will
Highlight each of the .jar files, except
Leave swingall.jar below $CLASSPATH.
Hit Save Settings..., make sure that Save as Application is checked, and then hit Run.
|. . .||Unix|
Assuming that you want WebFunds installed in
$ cd appl $ unzip /tmp/WebFunds.zip $ cd WebFunds
|Prepare (once only)|
Create runlocal and set the variables as indicated in run. Here's an example:
export JDK=/apps/java/jdk1.1.8 export SWING=/apps/java/swingall.jar # only for jdk 1.1The
You might also need to do:
$ chmod 755 run
$ cd appl/WebFunds $ ./run
This version is only for developer access, there is no support for install wizards from WebFunds.org. The download page on the site might include some hints as to where to get user-friendly downloads.
|. . .||DOS|
Unzip it somehow, but *preserve* the directories.
|Prepare (once only)|
Create runlocal.bat by copying runlocal_example.bat and set the variables in there.
Double-click on the [DOS] run PIF file.
The order above is known to work, other orders may not.
run* scripts for further hints.
Cryptix.jar is now no longer
required for releases 1.7 and after.
3rd party wallets such as Trader from Systemics
should be installed in
Ask your vendor for details.
Beginning with 1.7.2 there is a
under the top
In that, clieck on
File then Explorer.
Use the Explorer to access the wallet package you have already
downloaded. The UpgradesManager will then attempt to install it
in the right place.
The right place is the
This is early code, so monitor progress carefully.
When reporting difficulties, bear in mind:
stderrduring every run. (Save that file before restarting WebFunds...)
You need these first:
You need a JDK or JRE. WebFunds is expected to work with any of these distributions:
- Java 2 - JDK 1.3
reported as working on DOS.
- Java 2 - JDK 1.2
from Sun's Java page - v1.2.2 (at time of writing)
- Java 1 - JDK 1.1
from Sun's Java page - preferably the latest (1.1.8 at the time of writing).
swingall.jaris needed for JDK 1.1 only. Preferably 1.1.1-RELEASE (1.1.1b2 will work for the main screens but won't display correct text in some new areas like the SignContractWizard). 1.1 will not work at all.
You have to obtain these from Javasoft or somewhere similar. JRE's should also work. Nobody has reported it as working with any non-Javasoft sourced JVM.
To introduce new contracts, hit the [new] button. It should show a browse dialog with some files.
Contracts are files with a .asc suffix. Select one. It will appear on the contracts browser in the main box.
On the main box, left-click (double-click for Macs) on the little icon to open it up Then, right-click (option-click) for a pop-up menu (bug, only on the hash/name). Select [add account]. Select the SOX wallet (the only one there currently).
With no money, you can always do two things to test WebFunds:
If WebFunds reports that it cannot get through to the servers, it may be that your firewall is blocking outward connections. WebFunds uses HTTP protocols, but is directed to non-HTTP ports by the servers. This is the "correct" thing to do, but will in future also attempt to communicate on the HTTP port 80 in order to bypass firewall checks.
Check with your administrator to see if outward connections get blocked to higher-number ports.
Activity is now stored in History on site for latest changes or release History to see details of all changes prior to this release.