IntroductionIntroduction
  InstallingInstalling
  HandlingHandling
  Virtual serversVirtual servers
  ModulesModules
  FilesystemsFilesystems
  RXML tagsRXML tags
  GraphicsGraphics
  ProxyProxy
  Miscellaneous modulesMiscellaneous modules
  Security considerationsSecurity considerations
  ScriptingScripting
  DatabasesDatabases
  LDAPLDAP
  IntraSeekIntraSeek
  LogViewLogView
  FrontPageFrontPage
  UpgradingUpgrading
  Third party extensionsThird party extensions
  PortabilityPortability
    <Unixes>Unixes<Unixes>Unixes
    <Windows 95/98/NT>Windows 95/98/NT<Windows 95/98/NT>Windows 95/98/NT
  Reporting bugsReporting bugs
  AppendixAppendix
 
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:

  • File names. Unix uses a slash "/" to separate components in path names, while Windows uses backslash "\". However, internally Windows accepts "/" as a path separator. Unlike Unix paths on Windows are case insensitive. If a file index.html exists it is impossible to create a file Index.html. Windows also suffers from short file names, a file name can always be abbreviated to be 11 characters long. It is therefore often not possible to treat file names or paths as being unique on Windows, it is usually possible create another form of the file name or path that will be accepted.
  • 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 Challenger distribution is adjusted for these things, but third-party modules and user scripts might need some manual adjustment.