FAQ - Table of Contents
|1.1||What common operating systems SAWS does NOT run on?
The only "common" operating systems SAWS does not run on are MacOS7, MacOS8 and MacOS9. SAWS works just fine on MacOSX.
|1.2||Does SAWS support ASP pages?
ASP is Windows-only, ancient technology, so ASP is not supported by SAWS. There are a lot of Perl frameworks for building dynamic web sites that are much more flexible than ASP.
|1.3||Does SAWS support PHP pages?|
|1.4||The source code of SAWS does not look like Perl code. Why?
It is Perl code, but it's protected from analysis and illegal reuse using our perl obfuscation tool - Stunnix Perl-Obfus. We greatly recommend all professional Perl programmers to use it for their projects in order to protect their intellectual property.
|1.5||We have a site and wish it to be adapted to be run from CDROM using SAWS.
Do you offer such services?
Yes, we do provide such services. Please contact us at firstname.lastname@example.org for more information.
|User experience of using SAWS|
|2.1||Does SAWS require Perl to be already installed on user's computer?
No, Perl needs not to be installed to run SAWS if Perl interpreter is included with SAWS. Just try our sample CDROM image.
|2.2||If Perl interpreter is included with SAWS, what will be the installation
process of Perl interpreter from user's point of view?
If Perl interpreter is included with SAWS, it will just run from the location it's put to (and in case of CDROM with SAWS - from CDROM); user won't have to install it at all. Just try our sample CDROM image to see it yourself.
|2.3||What happens when user inserts CDROM with SAWS on it?
The SAWS for this CDROM will be started without any noticable effects (except that mouse cursor will turn into hourglass a couple of times for a fraction of a second), and the browser window will be opened with start page of the site.
|2.4||What will happen once user closes last browser window with the site in it?
SAWS will stay running in background, in order next time CDROM is inserted or browser-based application is run, the browser page will appear immediately. The SAWS processes will be terminated on the user's logoff.
But it's greatly recommended to put some kind of "release CDROM" button on link to your site, otherwise users of operating systems other than Windows will be unable to eject CDROM with SAWS on it. There is a special support for stopping and releasing media in SAWS.
|2.5||You say that SAWS runs on a user's computer listening for network connections
- will anybody from other computer be able to also access site on CDROM
(or browser-based application)? Will any virus or hacker be able to try to
break into computer through SAWS?
No, SAWS by default is configured not to listen on any network interfaces except a special "loopback" interface accessible only from the same computer; programs from other computers will even be unable to know that SAWS is running and will be unable to communicate with it in any way, so it's safe to run SAWS even on computer directly connected to the Internet. It can be configured to accept connections from other computers though.
|3.1||Can several instances of SAWS run on the same computer?
Yes, of course. Even different CDROMs (or browser-based apps) can be run on the same computer - each of them will get their own instance of SAWS.
|3.2||How can we replace tooltip on the icon residing in the Windows taskbar, or translate some menu items shown when clicking
on that icon?
To replace tooltip, edit "site/stunnixwebsrv/win32-trayicon.pl" file (it's Perl script), updating this line:
-tip => "Stunnix Web Server - http://stunnix.com/"To translate menu items, edit "sub do_populate_menu_entries()" in that file.
|4.1||How do you recommend us to create icons for Favicon and CD (for windows Explorer)?
There are a lot of tools to create icons. You can also draw them in Photoshop - see this document for more info (it contains generic info too, about resolutions of .ico files). There are a lot of other documents out there. You can also order icon creation - it will cost you about $50 in some studios.
|4.2||We wish to replace an icon of runcd.exe (used on Windows) - how to do that?
Once you create an icon in .ico file format, you can use any tool that allows to edit "resources" inside .exe files - just google for "replace .ico exe". One of them is Restuner tool.
|4.3||We wish to replace an icon shown in taskbar on Windows - how to do that?
Just replace file site/stunnixwebsrv/stunnixsrv.ICO with your icon.
|4.4||We wish to replace an icon shown in Dock on Mac OS X - how to do that?
Go to a directory with your Prototype, right click on "Run CD on MacOS X" (i.e. the icon used to start SAWS on Mac), select "Show package content". A Finder window appears, go to "Contents", "Resources" directory. There you will find file "stunnix" with ".icns" extension. Just replace it with your file in .icns format. There are a lot of ways to create an .ICNS file, they are described here.
|Developing for SAWS|
|5.1||Do we have to modify our site somehow in order to put in CDROM?
The only change that is greatly recommended is addition of a link or button to stop SAWS and release media - otherwise users on operating systems other than Windows will be unable to eject CDROM.
If your site was developed for Windows web servers, you may also will have to ensure that case of filenames in filesystem matches case of filenames that are used to refer to them in the site, otherwise your site won't work on OSes other than Windows. So if you have file named ProductInfo.html, then links to it using name productINFO.html or productinfo.Html or even ProductInfo.HTML will not work; you will have to link to it only using name ProductInfo.html. If this is a great limitation for you, please contact us and we will probably develop a solution.
|5.2||Why evaluation versions of Stunnix Obfuscation tools for Windows
are not in a form of a site packed into executable, but have usual installer?
Do you recommend us to follow this approach and produce "usual" installers
for Windows rather than packing entire site into executable?
When developing browser-based applications (but not CDROMs!) with SAWS we recommend you to follow the approach we choose; using an installer for application allows you to permamently install application AND perl interpreter runtime to the user's hard disk (thus eliminating the time need to extract perl interpreter and your site to some temporary directory); it also allows you to show some License Agreement to the user and to create some menu items for Programs menu. We recommend you to use free NSIS installer framework, it's sufficiently advanced and powerfull for most uses.