 |
|
|
|
Answers to Frequently Asked Questions |
|
|
Note: the FAQs are specific to Origami and Windows Server Package only. Other FAQs pages are available at:
|
|
|
Question list |
|
|
Have a question which is not answered? Please ask us.
|
|
|
|
|
|
How can I use Origami for Windows for compiling and linking my source files? |
|
|
That's simple. Origami for Windows supports both compiling and linking just from the editor. You can use your favourite DOS/Windows/Win32 tool for that - e.g. Borland make and bcc/bcc32, Microsoft nmake and cl etc.; even if you're using DOS tool, DOS window will not be created - all output comes to special window (like list box) created by Origami. In addition, you can use build-in make and Inmos C/occam2 compiler support. The documentation files supplied with Origami describes how to setup Origami for that.
We've realized making a project from Origami as executing a separate thread. The advantage of this method is that you don't have to wait when the thread will be completed. It means that you can continue the editing process while your compiler is still working.
Please note that compiling and making don't work under Win32s. That because:
a) Windows 3.x is not a multi-threaded operating system (if it's an operating system at all :-)
and
b) Windows 3.x doesn't support pipes (server-side) which we're using to capture output from the compiler.
|
|
|
|
|
|
How can I distribute my transputer applications created with Windows Server Package to end-users? |
|
|
Sorry, you can't do that yet. We're working under run-time version of Windows Server very hard and will try to make it available ASAP.
|
|
|
|
|
|
How can I change the default link address in Windows Server Package (Lite)? |
|
|
The lite version of WSP doesn't allow to change the link address (from default value of 0x150) directly. However, it's easy to do that by adding the environment variable 'LINK' into autoexec.bat. For example, if the transputer motherboard installed at address 0x180, the line should be 'SET LINK=0x180'. Under Windows NT, you can set environment variable via Control Panel (System); it's also required to modify the value Board0PortAddvess under the following key in Registry (it is stored as a DWORD value) using RegEdit tool (regedt.exe):
HKEY_LOCAL_MACHINE\System\CurrentControlSet\B004Drv\Parameters\
|
|
|
|
|
|
Where can I find Elcom software if I have a trouble downloading it from there? |
|
|
Our software also available from HENSA Parallel Archive and ALTA Technology.
|
|
|
|
|
|
Where can I find Win32s to run Elcom software under Windows 3.1? |
|
|
You can download it from Microsoft ftp site.
|
|
|
|
|
|
Where can I find more information about Windows NT driver for thansputer motherboards? |
|
|
We've included the driver for Inmos B004-compatible boards into our Windows Server Package (both full and lite versions). However, it is not our own - we've just made a few modifications to one provided by Jari Salminen.
Developing the NT driver is a very complex task, anyway. You have to be very familiar with Microsoft DDK (Device Development Kit), if you know what I mean...
|
|
|
|
|
|
Why doesn't Windows Server 95 exist in one package for Win32s and Windows NT? |
|
|
That's because we're using Freeman Installer software for generating the setup program for our Windows Server Package. It exists in two versions (16-bit and 32-bit) and has peculiarities which doesn't allow him to work on improper platform (16-bit version can't set Registry keys, and 32-bit version doesn't work under Win32s). However, the Windows Server Package itself (both lite and full versions) is the same for all platforms (Win32s, Windows 95 and Windows NT), as well as Origami for Windows. All packages detect Windows version at run time and work accordingly (e.g. store parameters in private .ini files under Windows 3.1 or in Windows Registry under Windows 95/NT); the WSP setup program also detects Windows NT and installs the hardware driver (which is not required in Windows 95 - this operating system allows direct access to hardware; that's one of the answers to the question why it's not enough stable in comparison with Windows NT). Of course, some specific features (such as multi-threading, priorities setup etc.) will not work under Windows 3.1.
|
|
|
|
|
|
Who is Elcom Ltd.? |
|
|
You can find some information about our company there. And you can find our people and ask them yourself on transputer conferences, like WTC (World Transputer Congress) and WoTUG (World occam and Transputer User Group) Technical Meeting.
|
|
|
|
|
|
What is Win32s? |
|
|
Win32s is a Microsoft software (realized as a set of DLLs and VXDs) allowing user to run Win32 applications (developed for Windows 95 and Windows NT) under Windows 3.1. Of course, with a couple of limitations; but most of Win32 software (including Windows Server Package and Origami for Windows) still can run with almost the same functionality. The worst thing is that it contains a lot of bugs; most of them confirmed by Microsoft, but I think each developer has found at least one new...
All developers can distribute Win32s with there own Win32 applications free of charge. Even IBM's OS/2 Warp now can run Win32 applications (unfortunately only those which correspond to Win32s 1.25, but this release doesn't support most of Windows 95 and Windows NT 3.51 features and user interface... Anyway, I don't think you like OS/2 too much).
|
|
|
|
|
|
What protocols are supported by Windows Server Package? |
|
|
Currently WSP supports 3 main protocols: Inmos (SGS-Thomson) iserver (used in Inmos C/occam2 Toolsets, PACT Parallel C and PACT/ACE Parallel Expert System), 3L afserver (used in 3L family of parallel languages) and Logical Systems cio (used in Logical Systems C Workbench). However, Windows Libraries (API for writing transputer applications with Windows interface) now available only for Inmos C Toolset (we're still working under other libraries now).
|
|
|
|
|
|
When the Origami for Windows will be integrated with Windows Server Package? |
|
|
We're working under this. Currently Origami contains build-in transputer server and link driver - to compile source files with Inmos occam2/C Toolsets.
|
|
|
|
|
|
When the Windows Server Package will work with C40 software? |
|
|
Sorry, we don't know the exact date yet. Probably, never...
|
|
