Melbourne Lightning back online as of Dec 2013
Need a Website? Go Daddy has everything you need to get on the web!

Scan this with your SmartPhone

SIP Member

Hudson Software runs on 100% green power! With our solar panels, we generate more power than we use (and make a substantial profit) !


WHOS-IN Pro - System Requirements


SERVER:

Windows compatible network server capable of supporting UNC (Universal Naming Convention) path names such as: Win95, 98, ME, 2000, NT, XP, 2003 Server, Vista, Novell 4.x and others. (Check your server is capable)
Approximately 15Mb hard disk space.
NOTE: No applications actually 'run' on the server (unless the server also happens to be a shared PC on a peer-to-peer network).


WORKSTATIONS:
Windows NT, 2000, XP, Vista, Windows 7 or Windows 8.
Win95 and Win98 may also run *IF* Office/Access 2000 *OR* the MS Jet 8 Service Pack has been installed.
LAN Card / Network connection.
Pentium 100 or greater preferred.
1024x768 screen resolution or higher (recommended)
NOTE: Under normal circumstances NO files are copied to the workstations. Only an Icon (linking to the user.exe file on the server) is required on the workstations desktop.


REMOTE SERVERS:
Same as server above, but also including HIGH SPEED (Megabits per second) WAN (Wide Area Network) connection. (Microwave or Optical Fiber preferred)


NOT RECOMMENDED:
WAN (Wide Area Network) connections using ISDN or slow DSL.
RAS (Remote Access Server) dialup connections using a MODEM.
NOTE: The data transmission speed for both ISDN (64 & 128k) and modems is too slow for acceptable response times due to the amount of data transmitted.


Peer-to-peer Network Limitations:
Windows XP is no longer recommended as a peer-to-peer server for WHOS-IN due to the simultaneous connection limit (20 users for XP SP1 and 10 users for XP Service Pack 2).

Our recommendation, is to run an OLD PC with Win98 as your WHOS-IN server, which bypasses the XP limitations.
If you do end up using an old PC running Win 98 as your WHOS-IN server, please ensure it is NOT also set up as a print server. If it is, and someone prints a large document, the buffering / printing process consumes 100% CPU cycles - leaving nothing for WHOS-IN database updates etc (which in turn causes errors for your WHOS-IN users).