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 ... 19 20 [21] 22 23 ... 26
301
Setup & Installation / Re: Re-organizaing OS/2-eCS Directories.
« on: August 07, 2014, 04:09:38 am »
1) LANGUAGE. Moving this folders seems to be a problem. When "UNICODE.SYS" loads in the boot procedure it gives some errors that can not found the files that I moved.
It seems I reach a deadlock here, if someone knows more about UNICODE.SYS and can suggest something it will be appreciated.

UNICODE.SYS has the path \LANGUAGE\ path hard-coded into it (you can easily confirm this by scanning through the driver with a hex editor). Technically, it isn't the boot drive but the current working drive (at the moment UNICODE.SYS is loaded) that it looks at, but unless you're doing something unorthodox like booting from Veit's MEMDISK environment, it comes to the same thing.

So yes, I think there's nothing you can do about that.

Quote
b.- There used to be some audio problem with UniAud driver that made the sound to loop. It was fixed on eCS, but after moving MMOS2 the problem showed up again.

I believe this is what MMFIX.EXE did (loaded from CONFIG.SYS). I think David A. may have written that... you could ask him maybe.

302
Setup & Installation / Re: Re-organizaing OS/2-eCS Directories.
« on: August 04, 2014, 03:34:04 am »
Any thoughts? Can UNIXROOT be pointed to a specifically directory, or only to a drive letter?

It can be, but it's not recommended. According to Yuri, the packages he's ported should in theory work OK like that, but there's no guarantee that other ports will.

I tried putting it all under a subdirectory on one system... it appeared to work OK but I didn't use it extensively.

303
Setup & Installation / Re: Adding fonts to be used by Ghostscript
« on: August 04, 2014, 03:31:14 am »
This might work but I'm not 100% sure.
In the gs\gs-whatever\lib directory, copy the sample file FAPIcidfmap to cidfmap, then add some lines similar to the following at the end:
Code: [Select]
/MS-Mincho  << /FileType /TrueType /Path (C:/PSFONTS/msmincho.ttc) /SubfontID 0 /CSI [(Japan1) 3] >> ;
/MS-PMincho << /FileType /TrueType /Path (C:/PSFONTS/msmincho.ttc) /SubfontID 1 /CSI [(Japan1) 3] >> ;
Obviously, change the file paths as appropriate.  That should allow GS to map the font names 'MS-Mincho' and 'MS-PMincho' to the TTC file.

Then you might be able to add an alias for 'Shingo-medium' to 'MS-Mincho' in the file fontmap.  I've never tried that, though.
A more brute-force approach in cidfmap might be possible as well:
Code: [Select]
/Shingo-medium  << /FileType /TrueType /Path (C:/PSFONTS/msmincho.ttc) /SubfontID 0 /CSI [(Japan1) 3] >> ;
Again, I have tested none of this.

304
Setup & Installation / Re: Is eComStation DEAD?
« on: August 03, 2014, 04:52:41 am »
Like, the core linux kernel is already mature, with 90% hardware support and support for existing technologies (64 bit etc).
Why not make a new linux distribution, using the already existing technology - and then focuse on specific things that could make it more like os/2?
For example if we the community created a linux distro with a WPS like desktop experience, it would effectly become a new os/2 at least from the user gui experience.

So then instead of having to create a completely new os, now you can just focus all the effort on the desktop experience, since os/2 has a very unique WPS interface that has never been replicated.

And who knows, as we get more users, then you could futher add features, like an os/2 "classic" emulator that can run native os/2 & dos apps - similar to what apple did with os/x.

So yeah.. I think we could aim for a new os called Lin/2 :).

This has been proposed many times, and in fact was attempted at least once: IIRC this was basically what the Voyager project was about, although I think they went with another OS kernel rather than Linux.

I've never been a fan of the idea... at least, not if it takes the approach of simply creating a WPS on top of a whole Linux OS.  I think it's sad to imply that what makes OS/2 special is nothing more than the GUI experience. 

You can take a Ferrari's chassis, dash and seats, and stick them onto the innards of a Volvo... but what you end up with will not be a Ferrari. It might be a nice car, but neither Ferrari lovers nor Volvo lovers would likely be impressed.

305
Setup & Installation / Re: Re-organizaing OS/2-eCS Directories.
« on: July 26, 2014, 06:08:36 pm »
Now, I tried PSFONTS.

To move the folder what I did was, I used the "System Setup-> Fonts" tool to first uninstall all the fonts from PSFONTS. I moved the folder to other location "C:\Resources\Fonts" on my case.  And after that I drag and drop them again on  "System Setup-> Fonts"  to install them again.

It seems to be working. But I'm not sure if that was the right way to do it.

OS/2 (i.e. Presentation Manager) doesn't care in the slightest what directory fonts are installed in, as the complete path to each font file is specificed in the PM_Fonts section of OS2.INI. You can install fonts to anywhere you like, even to multiple directories on multiple drives.

Now, some applications which want to do their own font lookups might default to looking in ?:\PSFONTS - for example I think Ghostscript and/or maybe gsview are by default configured to search for fonts in ?:\PSFONTS and a couple of other well-known paths, and don't use OS2.INI to search for fonts.

Some early and/or app-specific versions of fontconfig also defaulted to looking in ?:\PSFONTS, and I think one or two older versions of Java did as well. Fortunately, current fontconfig/mzfntcfgft versions are smart enough to check the INI file.

306
Setup & Installation / Re: Re-organizaing OS/2-eCS Directories.
« on: July 22, 2014, 11:34:57 am »
It seems that "C:\DMISL" was also a no brainer. I moved it to "C:\OS2\SYSTEM\DMISL" and changed the config.sys to "SET DMIPATH=C:\OS2\SYSTEM\DMISL\BIN".... But I'm not sure what it does either. The SLDB.DMI file was recreated again on the next eCS boot on the new directory.

It's part of the "Problem Determination Tools" component.  Look in your "Installed Features" folder and examine "Feature Install Base" --> "Problem Determination Tools". 

307
Hardware / Re: HP 1600 and eCS 2.2 Beta?
« on: July 09, 2014, 01:46:24 am »
According to this it should work with the foo2hp package: http://foo2hp.rkkda.com/

You could try with Paul's port of foo2qpdl (available on the eCups site) which includes foo2hp.

308
Your ecsinst.log indicates that SEINST and/or RSPINST was the failing component.  (This is the base OS installer, from IBM.) The error code given was a generic one so you need to check 1_BASE.L1 for the actual error report.

There is an ACPI bugtracker on trac.netlabs.org where you can file bug reports specific to ACPI.

Checking ecsinst.log from the aborted phase two install should tell you what it was doing when the system rebooted.

309
Setup & Installation / Re: driver trouble with Warp 3
« on: May 06, 2014, 05:07:17 am »
FixPaks explained in general: http://www.altsan.org/os2/fixpaks/index.html

The easiest way of downloading and installing a FixPak: http://www.altsan.org/os2/fixpaks/index.html

I believe you want FixPak 40 German, about halfway down the first table, which was the last free FixPak for Warp 3.  (FixPak 42 and 43 are newer, but only installable on Warp Server unless you have the special subscription versions from IBM).

310
Hardware / Re: eCS on an Asus X55U?
« on: April 13, 2014, 11:33:15 am »
?I don't see the quoted message anywhere...?

Anyway, just cancel out of the installer on the first screen to get to the maintenance console.

311
Hardware / Re: eCS on an Asus X55U?
« on: April 12, 2014, 03:41:07 pm »
Just use the built-in eComStation disk utility to wipe the drive. The manual should tell you how to do this, but you can access it from the Maintenance Console, "Disk" menu.

312
Quote
As I said, its main limitation is that it can't recreate setup string settings that WPTOOLS doesn't recognize.

IMO that isn't a limitation. Your app is able to handle specific icons. The only missing thing that comes to my mind is the XCenter setup string.

There are definitely some built-in WPS settings that aren't capable of being saved.  I discovered this a couple of years ago when doing a restore.  Unfortunately I can't find my notes so I don't remember what was missing; I just remember that some objects were broken because of it.

Quote
Apparently not: Some icons are missing in my test. Sorry, I won't test it further due to lack of time.

I was fairly restrictive in how it saves and restores icons. It only does so with the icons of abstract objects (not filesystem objects) which are explicitly set as custom in OS2.INI.

This means that custom icons of folders and anything else that exists in the filesystem (e.g. URL objects and certain other things) will always use icon(s) in the Extended Attributes if any, or the class default icon if none. 

That was a deliberate choice.  It seems to me that if you are creating WPS objects from a saved directory/file structure, the icons should already be saved in the EAs.

313
As I said, its main limitation is that it can't recreate setup string settings that WPTOOLS doesn't recognize. Also, until today it didn't support restoring custom icons, but I added that feature this morning (very experimentally so far) before importing the code. :P

Once I have it tested a bit more I probably will release it more publicly. I want to figure out exactly what things are missing from the setup strings, though.  At least it's now in SVN and on the FTP site for people to play with if they need it.

The thing is that I almost never update it except when I'm doing a migration or reinstall, which is pretty infrequent.  Then I use it, notice something else that needs doing, tweak it a bit more, then forget about it until the next round. :D

314
I mostly use my own tool that I wrote. I use it to create REXX scripts to regenerate various individual folder trees; I've never tried it on the entire desktop at once, but it might work.

I never released it publicly before, as it's got significant limitations. It mostly depends on WPTools.DLL to query object properties, and WPTools so far hasn't been updated to recognize certain late additions to WPS setup string syntax. I was meaning to try and tackle that, but I never got around to it. Right now I don't even remember what features are missing, although next time I do a restore I'll probably rediscover them :P.

The source is in the VXApps repository on NetLabs, and I just put a current (very much alpha, not properly tested) build here. It's pretty simple: just drag and drop a WPS folder into the window and it'll generate an object tree of all its contents. You can then export the results to a REXX script or a couple of installer-specific formats which I've never really tested.

If you want it to save custom object icons then you need Rich Walsh's OO.EXE installed somewhere (eCS has included this program for years). I just added this feature to the latest version and it hasn't been tested extensively. If you don't have OO, then the program should still work but custom abstract object icons won't be saved.

Provided mainly for the curious and the daring. Absolutely no warranty!

315
Setup & Installation / Re: Cups won't print PDFs
« on: February 22, 2014, 01:48:10 pm »
Quote
Warpin gives an error 'Invalid package index "5"

This is something that is wrong in the WarpIn installer. However, it can be worked around, by installing all of the other WarpIn packages first, then install the cups-base-1_4_8_3.wpi package.

That error is caused by missing libusbdll10.wpi - not a problem in the installer per se but in the README which wasn't updated to mention that this file is now used.

Pages: 1 ... 19 20 [21] 22 23 ... 26