KitCAD i3 and Windows

KitCAD i3 can be set up on Windows boxes by using the XAMPP server with modified KitCAD i3 files.
See the KitCAD i3 Install information for download links.

The KitCAD i3 Windows XAMPP version differs with many changes; see Note #1, Special Note #2, and take great notice that there is NO KitCAD i3 Security enabled and in most cases it has been disabled where possible.

The ONLY XAMPP Install path supported at this time by the KitCAD i3 Windows web server example is C:/XAMPP/ along with the URL of http://localhost/library/i3/Index.html or

Some windows users may need to update security or have Administrator rights to download, install software, and make changes in the Windows Security settings in order to view localhost pages.

NOTE: The KitCAD i3 XAMPP/WAMPP downloads are full of bugs that may not be fixed as soon as possible.. (only example/s, needs an AutoUpdate option)

PREVIOUS: See the KitCAD 1/2 KPA HTTPD information for past download links to another solution for KitCAD 1 or KitCAD 2 web server users.

5 Responses to “KitCAD i3 and Windows”

  1. Admin Says:

    KitCAD i3 xampp, using Windows:
    htdocs = C:\xampp\htdocs\
    cgi = C:\xampp\cgi-bin\
    perl = C:\xampp\perl\
    php = C:\xampp\php\

    Other xampp install paths (htdocs):
    win = \xampp\htdocs\
    mac = /Applications/xampp/htdocs/
    solars = /opt/lampp/htdocs/

  2. Admin Says:

    Other xampp install paths (htdocs):
    win = /xampp/htdocs/

    (PHP and Pear swap the path symbol on some systems)

  3. Admin Says:

    Win32, NT4, ME, 2003, XP, VISTA users are required to be logged in with Administrator Rights when installing PHP PEAR.

  4. Admin Says:

    Updated served pages and files; xampp/wampp users should also see Apache server header updates to adjust the Deflate option.

  5. Admin Says:

    Updated versions of the xampp/wampp KitCAD i3 files were missing past updates caused by using the orginal linux build files, and running on a win box.

    And as such – Corrected many bugs (these may re-occure). See Bug report for more information. 🙂