It makes no difference what operating system you are running on your PC; Windows and Mac should work just fine. All you need is Internet access, a web browser that will let you get out on the Internet and access your site, and an FTP program that you can use to connect to your site.

Q.I8- Why does windows tell me "The C:\xb\*.hlp file is not a Windows Help file, or the file is corrupted."

The trick is to tweak the unix side, using symbolic links or making mount directories that simulate the windows path layout. The best thing is to create the mounts to match the UNC paths. On my network, windows machines see the server's disk as //tahoe/jobs. On the unix machines, I can organize my mount points this way: Or, if your mounts are in a directory like /mnt/jobs and you don't want to change that, you can work around easily enough with symbolic link(s) to make UNC paths work under unix.

Yes. Emacs and XEmacs are available for Windows; they both understand and preserve UNIX end of line characters.

Which operating system you decide to use should depend on what features you need. For example, if you are already using IIS, ASP, VBScript, Windows Media, Microsoft Access, Microsoft SQL Server, or Visual InterDev, and you don't have the time to learn Unix-based solutions, you'll have to choose a Windows NT or Windows 2000-based host. Just because your desktop is Windows-based doesn't mean you should use a Windows host.

For large and/or long jobs, chiller and cloak, our dual-processor Linux boxes. For small jobs and day-to-day computing, stokes or cantor, both Suns.

It is a Perl based tool, but it will work under windows using ActivePerl (a free plug-in for Microsoft webserver software).

Starting in maven 2.0.1, you can reference windows and unix environment variables inside your pom.xml or settings.xml using an expression of the form:

There are only two differences between the GEX standalone and server versions: GEX standalone can only run on a defined CPU station (CPU locked) while GEX server can run on any station over the network (floating license)

MKS Toolkit supports standard UNIX facilities for exchanging files between the two platforms, including rcp and FTP. In addition, Toolkit includes standard UNIX utilities for handling bulk file copies (cpio, pax, and tar). To share files, you can use either NFS or Samba. UNIX text files use a line-feed character to indicate the end of a line, while Windows expects both a carriage return and a line-feed in its text files.

The script is tested on a Unix server not Windows. Each server is set-up in a different way, most will run the script without issue. Sadly I can not offer any technical support on setting up web servers.

Unix provides secure and reliable environment perfect for most of the hosting needs, but sometimes you want to take advantage of some Windows applications such as MS Access, ASP scripting. For that you might want to use Windows account. We provide Windows and Unix accounts at the same prices for the same level of hosting plans. Click here for details.

We recommend Linux (Unix) as it is more robust, stable platform and capable of a lot more load than Windows. This has nothing to do with the software on your PC that you use to surf the Internet.

Our servers operate on Red Hat Linux version 9.0. We will announce news of our Windows hosting plans in the near future.

CVS for UNIX can be downloaded from http://www.cvshome.org. CVSNT can be downloaded from http://www.cvsnt.org.

The first is to use a portable graphics library such as tcl/tk, X11, or V (and others?). Typically, you will end up with a GUI on Windows that requires some runtime support. With tcl/tk, you'll want to include the necessary library files and the tcl/tk DLLs. In the case of X11, you'll need everyone using your program to have an X11 server installed. The second method is to rewrite your GUI using Win32 API calls (or MFC with VC++).

If the file you want to unzip (uncompress) has the extension ".gz" or ".z" type "gunzip {file_name}" at the UNIX prompt. If it has ".zip" then type "unzip {file_name}" at the UNIX prompt. These commands are the UNIX equivalent of using Winzip on Windows.

Even the jpeg libraries at the GIMP web site may not work for all versions. If their jpeg-shared-6.a.tar.gz package doesn't work for you, try:

A long time ago, samba 2.x was installed on the unix side. It allowed one to easily map unix files as a PC drive (usually s: for stokes, the machine it ran on). It worked really well, I didn't have to be involved in any way, it was fast enough, it was easy and everyone was happy. stokes, however, was starting to show its age. We then bought a couple of big honkin' dual-processor linux boxes. The idea was that samba would be moved to one of the boxes.