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 ... 24 25 [26] 27
376
There are a few caveats involved in updating MPTS on Warp 4 without TCP/IP 4.1.  See: http://www.altsan.org/os2/fixpaks/mpts.html (especially the section at the bottom).

377
I believe the Warp Connect CD has a script 'install' in the root directory which installs the networking stuff on an existing Warp system.

378
Marketplace / Re: OS/2, software and books on eBay
« on: August 08, 2013, 09:57:28 pm »
Got the Panov/Salomon book, arrived today. :) 

Been looking for that for years, thanks!

379
Networking / Re: FTP
« on: August 04, 2013, 02:12:50 am »
Firefox itself is SMP safe.  However, the IBM TCPIP32.DLL is not, and IIRC this can cause problems with Firefox among other things.  There's a patched SMP-safe version of TCPIP32.DLL available from various sources, such as recent versions of the ACPI WPI packages.

On that note, the Mozilla FireFTP extension is a fairly decent graphical FTP client.  It's available for SeaMonkey as well as Firefox.  I've never tried it with files that large, but I'd expect them to be supported.

380
Setup & Installation / Re: UEFI & SecureBoot?
« on: July 28, 2013, 04:12:58 am »
Not for eCS 2.2, but I believe there are some longer-term plans in the works.

Unfortunately it's not simple or easy to implement.

381
Utilities / Re: 7z archiver
« on: July 28, 2013, 04:11:35 am »
Yeah, IMO 7z is only suitable for exchanging archives other platforms. 

ZIP 3.x is probably a better alternative for OS/2.

382
Applications / Re: Apache OpenOffice 4.0
« on: July 23, 2013, 03:41:23 am »
I see a similar SYS3170 exception in DOSCALL1.DLL on closing OO 4.  My system is dual-core.

I also got the following on highlighting a paragraph of text and hitting the Del key:

07-19-2013  17:58:04  SYS3175  PID 0048  TID 0001  Slot 0097
E:\PROGRAMS\APACHE\OPENOFFICE 4\PROGRAM\SOFFICE.BIN
c0000005
0faa35be
P1=00000001  P2=00000008  P3=XXXXXXXX  P4=XXXXXXXX 
EAX=00000000  EBX=1668af84  ECX=21051000  EDX=00000000
ESI=1668662c  EDI=00000000 
DS=0053  DSACC=d0f3  DSLIM=5fffffff 
ES=0053  ESACC=d0f3  ESLIM=5fffffff 
FS=150b  FSACC=00f3  FSLIM=00000030
GS=0000  GSACC=****  GSLIM=********
CS:EIP=005b:13ad0899  CSACC=d0df  CSLIM=5fffffff
SS:ESP=0053:0012fc70  SSACC=d0f3  SSLIM=5fffffff
EBP=0012fc88  FLG=00010213

SWOO.DLL 0001:000835be


Otherwise, I have to say this dev build is a lot more stable (if slower to load) than the v3.4 ones were.  I was quite pleased with how much more so, at least up until I got this crash. :P

383
Networking / Re: Various Warp Connect v3 networking problems
« on: July 16, 2013, 05:07:20 pm »
Actually, I only ever used a GUI tool that I believe only works on Warp 4, or the "floppy toaster" method you mention. Wasn't aware that CSF could do it from hard disk. Any pointers would be greatly appreciated! Will definitely apply the fixes you recommended, once I know how to go about doing so.

See the section "How to Install a FixPak"on this page (about halfway down): http://www.altsan.org/os2/fixpaks/index.html

There's another way to do it as well (which doesn't require the RSU version of CSF) which I didn't describe, but basically consists of setting the environment variable SET CSFCDROMDIR=<path> (where <path> is wherever the FixPak files were extracted to) before running SERVICE.

384
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).   

385
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.

386
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). 


Quote
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).

387
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).

388
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.)

389
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.

390
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.

Pages: 1 ... 24 25 [26] 27