Table of Contents

  • Introduction
  • Installation
  • Handling Challenger
  • Virtual Servers
  • Configuration Examples
  • Modules
  • Filesystems
  • RXML Tags
  • Graphics
  • Proxy
  • Databases
  • Miscellaneous Modules
  • Security Considerations
  • Scripting
  • Frontpage
  • Upgrading
  • Third Party Extensions
  • Portability
    · Introduction
    · Unixes
    · Windows 95/98/NT
  • Reporting Bugs
  • Appendix
  • Windows 95/98/NT
    Roxen Challenger supports Windows NT 4 SP 3 and works as a development environment on Windows 95 and 98 as well.

    Generally, Pike scripts and RXML code can be moved from Unix to Windows systems more or less directly, but there are a few details to keep in mind:

    • Slash/backslash. Unix uses a slash "/" to separate components in path names, while Windows uses backslash "\". User-level Pike code that accesses files might have to be updated to reflect this.
    • There are differences in terms of memory management, user identities, and file protections. While not generally a problem for the basic running of Challenger, security issues may need special attention.

    The Roxen Challanger distribution is adjusted for these things, but third-party modules and user scripts might need some manual adjustment.