[Date Prev] [Date Next] [Thread Prev] [Thread Next] Date Index Thread Index Search archive:
Date:Mon Aug 22 23:43:35 2002 
Subject:Re: pop11 on a PC : does HELP work? 
From:jeffb 
Volume-ID:1020822.02 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In message <200208221401.g7ME1uY24302@acws-0051.cs.bham.ac.uk>, Aaron 
Sloman <A.Sloman@cs.bham.ac.uk> writes
>There are two versions of windows poplog on the abvoe freepoplog site.
>The older one V15.5 includes a setup.exe which creates a desktop
>shortcut which can be used to invoke pop11 inside a versio of Ved,
>which can then switch in and out of split screen mode using ESC w.
>
>The newer one V15.53 does not have that set up.
>
>So it depends which version your colleague is using.
>
>It would be very nice if some clever windows programmer could make the
>newer version work like the old one.

I have just installed what I think is 15.53 as a sibling to my 15.5 
installation, copied the shortcut for the 15.5 on my desktop and 
modified it to point to 15.53. The command is:

X:\Poplog\15.53\pop\pop\winpop11.exe +STARTUP

starting in

X:\Poplog\15.53\pop\pop

I have also modified my %usepop% variable to point to the newer version.

This seems to start ved in a window, although I haven't tested anything 
beyond this.

Since I've been playing around trying to get a single tree containing 
Windows and Unix/Linux/X-Windows code so that I can experiment with 
Windows+Cygwin, Windows+U/Win and native Windows 2000 versions, I wasn't 
sure that the version I moved was based on 15.53, especially if, as you 
say, the newer version doesn't have pop11+ved in a window set up. I may 
also have remnants of the 15.5 registry settings in place. However the 
version string appearing in this version is "Sussex Poplog (Version 
15.53 06/04/2001 18:46:40)".

By the way, I have encountered some problems with Poplog's use of 
environment variables. The scripts usually define lower case versions of 
the names, but some of the tools in the unholy mixtures I am trying 
expect upper-case versions and others, lower-case. In particular, one of 
the Bourne-shell tools I was working with - momentarily, I forget which 
- - insisted on requiring all environment variables to be in upper-case 
with shell variables in lower-case. Has anyone else encountered and/or 
surmounted this problem? (I.e. Do you have any scripts I can filch to 
save me rewriting them!)

Regards,
- -- 
Jeff

-----BEGIN PGP SIGNATURE-----
Version: PGPsdk version 1.7.1

iQA/AwUBPWV2MfHj+enJbeYqEQKDpgCg9t0cmD9RnHxcb1UKCWCQ2qa4B+AAn14E
kb56U9K3Mqn8n3RyqDpj6xnA
=04pi
-----END PGP SIGNATURE-----