CompassLearning
From Wine-Wiki
These are the (agonizing) steps I am going through to get Compass Learning working on a Linux Terminal Server. I hope to use this page to chronical the adventure. Hope that's OK.
This work is a work in progress, if you have any suggestions or hints, put them here, or email me and I will.
Note that new installations of Compass Learning are all web-based, so none of this applies for new installations, I think. See this post on k12osn and the Compass Learning home page
This project uses the k12ltsp.org Linux distribution as it's base. This is a Linux Terminal Server distribution. The hope is to be able to eventually turn the aging machines in our computer lab into terminals. We are in the development stages so far. Here is a step-by-step of what I have been able to accomplish to date. We aren't done yet, but we'll get there.
This also assumes that you already have Compass Learning installed on the server side.
Download, install and configure k12ltsp to your liking. Be sure to include samba in the install. Precdures for doing this are beyond the scope of this document. Help here.
Download, install and configure wine. I used the RPM available from the downloads section of WineHQ. I currently use wine20050419. In the wine config file, under the section titled [Version], enter the following line:
"Windows" = "win2k"
All other lines should be commented out.
Create a mount point for your Compass Learning share:
$ mkdir /mnt/cl1
In the dosdevices directory create a symlink to /mnt/cl1 for the G: drive
$ ln -s /mnt/cl1 g:
Now mount your Compass Learning share. You may want to refer to the man pages for mount(8) and smbmount(8). My mount command looks something like this:
$ mount -t smbfs -o username=user/domain,password=passwd //win2k-compass-server/cl1 /mnt/cl1
Now run the Compass Client installer, like so:
$ wine /mnt/cl1/CURRIC/WRKSTATN/SETUP.EXE
This process was fairly painless for me.
After running the Compass setup program, edit $FAKE_WINDOWS/Compass/IDWSOCK.ini and add this line to the bottom ofthe file:
SERVER_ADDRESS = "server_ip_address"
For example: SERVER_ADDRESS = 192.168.21.22 You may not need to do this if your terminal server is configured to authenticate on a Windows domain (YMMV).
Here is where I get hungup:
$ wine "c:\\Compass\\START.EXE"
Compass almost runs. The screen flickers and I get a blank dialog box with with this in the title bar:
"Failed to Load cpWebWriteCurrentLessonData()..."
The following is also dumped to the terminal:
[root@ltsp Compass]# wine "c:\\Compass\\START.EXE" fixme:hook:SetWindowsHookEx16 System-global hooks (5) broken in Win16 fixme:winsock:convert_sockopt Unimplemented or unknown socket level err:winsock:WS_setsockopt Invalid level (-1) or optname (128)
Resources
Contents |
[edit] Wine Application Database
As of Aug 07there are no entries in the application database.
- Please consider submitting your test results for running this software under Wine.
| |
Regularly Submitting results for installing and running on the latest version of Wine makes a big difference for others considering using Wine. By looking at how well the software runs others can be encouraged to try it themselves and together you can make progress in finding workarounds. By testing the software you will also notice when something breaks and when you make a bug report, the bugzilla team will often point it out to the person who broke it. If you are slightly more technically minded, you are able to regularly compile wine and test it before each fortnightly release then you will catch breakages before each wine release.
A big advantage of being a maintainer is that as you quickly become familiar with installing and using wine with your software, you can have a direct hand in improving wine and your software. Many times you will find very handy tips posted by others and by posting a summary many benefit from your work. When you are asked a question you don't know, simply post in the wine-users forum and perhaps someone can help. Just by being there, you make a difference. A maintainer quickly tests each monthly release of wine, and adds to the application database a rating of how good it runs.. gold/silver/bronze or garbage. Wine is constantly being improved, and occasionally something breaks. When you do spot a breakage, file a bug in bugzilla and if you want to try and fix it you can then post to the wine-devel mailing list for advice. However, if you have a little spare time (usually about 2 hours, in between doing other things) regression testing allows you to identify which patch caused the break. By filling out a bugzilla report, posting the name of the software, and the patch which broke it to the wine-devel mailing list, the developer who broke it can have a look at fixing it.
|
[edit] Links
