Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Alex Taylor

Pages: 1 ... 13 14 [15] 16
Programming / Re: Rexx?
« on: July 04, 2013, 11:49:20 pm »
So there is a way, no,  I don't mind some extra work, definitely it is faster than rewriting every time exercises  ::) !

Every time you Run a VX-REXX project (even in the demo) it compiles it to EXE and writes both the EXE and the source code to a temporary directory (called "__tmp?" where ? is a number) under %TMP%.  The three source files you need to save are project.VRP, project.VRM (rename to project.VRX when saving), and project.VRW (rename to project.VRY).   

Programming / Re: Rexx?
« on: June 29, 2013, 02:46:57 am »
Any VX-REXX application project can only be compiled with VX-REXX (although it's possible to do this using only the demo if you don't mind some extra work).

However, separate REXX function libraries and some kinds of macros that are written with VX-REXX may be able to be compiled (with e.g. REXX2EXE) if they are 'plain' REXX and don't rely on the VX-REXX client-server object framework.

It's quite possible to use VX-REXX functions (but not objects, methods or events) in a 'standard' REXX script.

Programming / Re: Install TTF Fonts with Rexx
« on: June 10, 2013, 11:15:56 pm »
There are functions to retrieve the boot drive, but also environment variables to use for backup if the function is not available.
Code: [Select]
ttfs = SysBootDrive()||'\PSFONTS\TTF'Please note that the function is only available with newer rexxutil from Object REXX. So plain vanilla Warp 4 doesn't have it I guess by default, but eCS does.

The so-called "Object REXX" functions were added to the standard REXXUTIL in Warp 4 with FixPak 6 (and to Warp 3 in FixPak 35). 

I looked at your instfont exe Alex and the source code before I wrote the script. It would be very interesting as part of a rexx library, perhaps your RxULS!

Better in RXUTILEX (and it's on my TODO list, in fact).

Programming / Re: Install TTF Fonts with Rexx
« on: June 07, 2013, 05:21:13 pm »
Use InstFont and you won't have to reboot (unless you're updating a previously-installed font, perhaps).

Applications / Re: hwman installation
« on: May 24, 2013, 01:38:43 am »
¿Anybody knows on which part of XWorkplace can be added the description for this classes?

The descriptions are in <Xworkplace-path>\help\xfcls001.txt (or substitute appropriate language code).  Anyone with write access to XWP CVS should be able to make the same change (for everyone) to the file in <cvs-root>\001\misc.

Incidentally, the XWP class list is actually compiled into eWorkplace, it's just not registered or created in a normal install.  With a little REXX knowledge it's possible to register the class and create the object under eCS.  (Although in this case the file xfcls001.txt isn't included at all, so if you want descriptions you'd need to copy it from elsewhere.)

Applications / Re: libusb-1.0 port to OS/2 - help needed
« on: April 26, 2013, 03:13:56 pm »
Tried lsusb here on my TP500.  It detects exactly the same devices as USBDock: fingerprint reader, webcam, mouse, bluetooth, and keypad.  I assume you don't want the debug output if it worked properly. :)

I'll try sane on my other PC later today.

Try setting DefaultFont to "8.Helv".  IIRC this is the default on DBCS versions of OS/2 and so most of the system dialogs should scale fairly well with it.

IIRC the IBM help viewer uses hard-coded fonts in some places, in which case there's nothing you can do about that except maybe use NewView instead (which I would generally recommend anyway, due to clipboard support, etc.).

BTW, if you see clipped dialog text with DefaultFont, it's a bug in that application, not a bug in OS/2.  All dialogs are supposed to be designed to fit the default dialog font (normally System Proportional), whether or not they actually use a different font for display.  This is not unfortunately very well documented for programmers.  However, the fact that the DefaultFont setting causes system-wide rescaling of dialogs is not only the correct behaviour, it is important that it work like this as some environments (including all DBCS versions of OS/2) depend on it.

If you don't have such an environment, then the patch that Andreas mentioned may well work for your purposes... but you do need to understand that this patch works by deliberately breaking part of the correct Presentation Manager behaviour.  It's a trade-off, and you should understand the ramifications.

Multimedia / Re: Guess - what.....
« on: April 13, 2013, 02:00:14 am »
Sexy.  Isn't that one of my old logo graphics?   :D

Article Discussions / Re: eComStation 2.2 Beta First Impressions
« on: April 01, 2013, 03:44:27 pm »
Please note: we have discovered that GenMAC is failing to install properly, which explains most if not all of the networking problems people have experienced after installation. 

This is one of those weird breakages that slipped through into the beta due to a flukish circumstance that managed to circumvent all our testing.  This also explained why I was for so long unable to reproduce the problem: internal builds do not have it.  It's the build process for the final uploaded ISO release itself that caused the failure in GenMAC. 

At any rate, it is likely that anyone who has non-functional networking following the install has been hit by this problem.  The solution is to reinstall \CID\SERVER\ECSPKG\GENMAC2.WPI from the installation DVD.  (It may be necessary to then reconfigure the NIC(s) using NAPS or MPTS.)

I would like to reiterate: these problems are not caused by the new configuration GUI.  However, they have exposed some limitations in the new GUI w.r.t parsing a malformed or corrupted configuration. An updated version which addresses this will be provided in the next release.

Article Discussions / Re: eComStation 2.2 Beta First Impressions
« on: March 31, 2013, 05:43:51 pm »
In other words, just change the 'DEFAULTVIEW=' setup string of each drive object.  All directories on the drive should pick up the change.

I can find nothing that says DEFAULTVIEW=, in each drive object. Care to be a little more specific? Where do I look?

If you mean the Default action, in the Open As menu, yes, I can set that to Tree View, but then every directory also tries to open in Tree View, when they used to open in Icon View (which is usually what I want). I can change each directory to open in Icon view, but it could take days to change all of them.

It's stored in the object setup string.  I don't think there's actually a GUI option to set it, although you can use a Setup String object (from the Templates folder) to try setting "DEFAULTVIEW=DEFAULT;".

OTOH, I just tried this and the results were... inconsistent, to say the least.

However, I've just suggested another possible solution in your ticket #3403.


This is a known issue at the present time.

Okay. If that is the case, I would suggest that Split View should not be the default setting.

Not my decision...

Article Discussions / Re: eComStation 2.2 Beta First Impressions
« on: March 29, 2013, 04:20:30 pm »
So, I now have a better install. Now, I am trying to figure out how to get the Drives folder to open drives in the Tree view (actually, I know how to do that), then how to get the Tree view to open directories in the Icon view, as it did before (I know how to do that too).

As noted, I know how to do both, the question is how do I do it globally, without having to change the properties of every drive, and directory, that I have?

The only thing 2.2 does with the split view is to set 'DEFAULTVIEW=SPLIT' on each drive object.  Undoing that should be sufficient.

In other words, just change the 'DEFAULTVIEW=' setup string of each drive object.  All directories on the drive should pick up the change.

I don't mind the new way of displaying data, BUT, if I go to a directory, and select a file that I want to COPY to another directory, I can't do it without opening an icon view in at least one of them. That seems to be an extra step that I shouldn't need to do. I also tried Pickup, and Drop/copy. The WPS hung, and wouldn't restart from CADH (it said that it did restart). I had to reboot.

Anybody else seeing this? Anybody know of a better way to do a copy, or move, using the Split View? Did I miss a setting somewhere?

This is a known issue at the present time.

Article Discussions / Re: eComStation 2.2 Beta First Impressions
« on: March 27, 2013, 03:14:58 pm »
First, thanks to everyone who's opened tickets on their issues. 

A particular note about the new Network Adapters and Protocols GUI (of which I am the author, BTW).  IMHO this component needs testing more critically than anything else barring ACPI, AHCI and USB.  I know when you have problems you just want to get a solution ASAP, but it's very important that any bugs get ironed out during the beta cycle.

If you experience any of the following w.r.t. the new NAPS GUI, please open a ticket on it. 
  • No network adapters shown (but MPTS does show them)
  • Unexpected error messages
  • Crashes

In your ticket, please include the following:
  • A copy of PROTOCOL.INI (taken from when the problem was occurring)
  • A copy of CONFIG.SYS (likewise)
  • Also, please try running "NAPS.EXE /D" from the command line (in the \ecs\system\naps directory).  The /D switch will cause debug output to be written to the VX console.  Please copy & paste ALL of the contents of this console into a file and also attach it to the ticket.  (You don't have to make any configuration changes unless asked to; simply starting up NAPS should be enough to begin with.)

I should note that problems with non-working NICs immediately following installation are not related to the new NAPS utility, as that does not get used during eCS install at all.  That appears to be a different problem (and a mysterious one, since neither GenMAC nor its install logic has changed one iota since eCS 2.0).

Article Discussions / Re: eComStation 2.2 Beta First Impressions
« on: March 26, 2013, 08:51:42 pm »
As regards installation: needs a little bit of work I think.

1] DOS was deselected but there is a populated \os2\mdos directory and DOS drivers loaded at boot.

This is correct.  We have investigated this in the past.  You will notice that it is not a proper (full) MDOS installation. 

However, a few minimal files for VDM are always installed.  (It is the IBM installer that does this automatically.)  We've found that there is no way around this, as they are required by some core OS components (I believe GRADD requires VDM support; IIRC something else does too, possibly APM or somesuch).

2] JAVA was deselected but I discovered that java11 gets installed anyway in \os2\java\java11

Also correct.  The selectable option in the installer refers to OpenJDK (Java 6) only. 

Java 1.1.8 is now always installed.  This was discussed a couple of years ago in a problem ticket, although I don't have the reference handy.  Certain system components and configuration tools simply do not work stably with any later version of Java.  Attempting to allow flexibility in this just caused too many ongoing problems and compatibility issues.  Given how small and unobtrusive a minimal Java 1.1 installation is, it was decided to simply install it always.  Please note that it is tucked out of the way in a system directory, and adds absolutely nothing to CONFIG.SYS or the environment.

I'm aware that some users will be unhappy about this.  This is one of those issues where it's just impossible to satisfy everyone.  Trying to compromise just led to unhappiness and confusion anyway.

If you're really determined to excise Java 1.1.8 from your system (although it will gain you nothing besides 20 MB of disk space), you are free to uninstall it (from the Feature Install Base tree).

4] What happened to the options to "use pretty clock" and the good search tool pmseek.exe - did I miss them somewhere?

They're still there, in the same place as always: the Install/Remove folder, eComCenter Install/Configure.

This 1 is my fault: I accidentally installed the "enhanced file dialog" thingy. How do I get rid of that and reinstate the old file open/save dialog?

Also see the Install/Remove folder.  I believe the QuickGuide mentions this.

Programming / Re: Rexx?
« on: March 21, 2013, 04:41:48 pm »
The REXX 'SAY' instruction simply prints to standard output (STDOUT).  Unless you use a special REXX environment that redirects STDOUT (such as PMREXX), you will only see this when running the REXX program from a command prompt.

RxMessageBox only works within a process that is running as in graphical (PM) mode.  If you run within PMREXX ('REXX console' on the eCS desktop) then it should work (IIRC, anyway).  You can also convert a REXX script to a graphical program by using a tool like REXX2EXE (use e.g. 'rexx2exe myrexx.cmd myrexx.exe /p').

Normally eCenter widgets are not written in REXX.  I believe somebody wrote a special wrapper widget a few years ago which does allow this, however.  It might be in this package but I'm not sure (and I've never used it so I can't be any more help than that).

My Asus M4A78LT-M boots to a desktop, the Intel Pro/1000 nic is seen and used and I can get to the internet BUT there is no way that I can do anything with the drives on the machine - every time I try to open a drive it gives a windows like message that the drive isn't formatted (they are HPFS and JFS).  As a demonstration that is useless.

Please remember this product is a demo CD - it is not a 'live' CD in the usual sense.  Certain features are disabled to ensure that people cannot use the CD as a substitute OS.  In some cases, IBM specifically required that we disable these features for the free demo. 

Access to OS/2 native fs (HPFS and JFS) drives is intentionally disabled.  Printing is also disabled, as is SMB (Peer and Samba) support.

Pages: 1 ... 13 14 [15] 16