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 ... 8 9 [10] 11 12 ... 20
136
General Discussion / Re: Windows 10 and privacy
« on: August 03, 2015, 05:35:27 am »
FAT installation of eCS was not officially supported (except possibly in version 1.1).  However, it does work, at least as recently as (IIRC) version 2.0.  I'm not sure about 2.1; ISTR it will no longer work in 2.2 because some required components with long filenames are now installed on the boot drive.

(FWIW, I wrote the relevant parts of the eCS installer and I put considerable care into making sure that FAT installation was still possible up until the last version or two; it just got too hard to do eventually.)

The eCS installer will not let you format the boot volume as FAT. However, if it's already formatted as FAT then it will still let you install to it (at least pre 2.2).

137
Applications / Re: Problems with ArcView...
« on: July 30, 2015, 03:02:56 am »
Actually ArcView uses 7z by preference instead of rpm2cpio, but it falls back to the latter if the former can't be found on the path.

FWIW, the precise command it uses is:
Code: [Select]
7z x -so -bd -y whatever.rpm 2>NUL | cpio -d -i -v -u --no-absolute-filenames --quiet [file_to_extract] 2>&1
If the necessary programs are missing it will tell you.


138
General Discussion / Re: XEU.com and eComStation
« on: July 19, 2015, 05:47:08 pm »
So it appears that the USB keyboard problem is what I mentioned earlier, a lack of communication between USBKBD.SYS and KEYBOARD.DCP because the Chinese keyboard need a special translate table for which there is no provision.  Sounds as if your team are in for a serious re-write of all that area, just make sure all the changes are tested against non Chinese installs before you release them.

IIRC, each DBCS version has its own unique KEYBOARD.DCP anyway (and its own unique KBDBASE.SYS).

139
General Discussion / Re: XEU.com and eComStation
« on: July 16, 2015, 11:11:23 am »
I have a program called timewait, I don't recall now where I found the source but I compiled it to give a 5 second delay.

I wrote that, assuming it's the same one. I use it to insert a delay between HELPERW and NETBIND to avoid GenMAC initialization problems.

FWIW I don't think that's the issue with the USB problem on Chinese. DBCS is rather more complicated than SBCS when it comes to everything that has to happen at bootup, and I've found there's more scope for things to go wrong. (I remember I never could get full-screen CMD sessions working while booted from CD on DBCS, for some weird reason.)

140
Setup & Installation / Re: Samsung ML-2165W Printer
« on: July 13, 2015, 02:31:50 am »
This seems to be an entry-level raster printer using a proprietary interface language (SPL). There is a chance it might work with SpLIX (although it's not listed as supported), but I'd say it's probable that it wouldn't work under OS/2 at all.

141
General Discussion / Re: News from the front line
« on: July 10, 2015, 04:54:30 am »
14.106 is certainly an official IBM release. Several people have told me that it came with XR_C006. However, I seem to recall that the XR_C006 that was leaked publicly was a beta version. Perhaps the final, official version of XR_C006(which AFAIK was only available to IBM customers and presumably OEM partners like Mensys) contained 14.106.

142
Hardware / Re: H.P. 2025 need help Per!
« on: July 04, 2015, 09:23:53 am »
Also, Alex recommended I try using "Generic Postscript (enhanced), which I also can't find, is that possibly in the hplip drivers? And is that also where to find the "Simplified" version you mentioned?

The driver I referred to is NOT part of CUPS, it is in the PSPRINT driver for your desktop printer object.  See the attached screenshots.  You will probably have to install the driver (the second picture shows where to find it if you're using my PM Printer Manager, but the corresponding window in the standard OS/2 printer setup dialogs looks almost identical).
  • If you have PM Printer Manager (printman.exe) then go to the Drivers page and select 'Install'.
  • If you use the standard OS/2 dialogs only, go to the Printer Driver page as seen in the first screenshot, right-click on any driver icon and choose 'Install (new driver)".
In either case, enter the directory where you unpacked the PSPRINT driver files and in the 'other printer driver' selection. Then look for 'Generic Postscript (Enhanced)' (this is NOT the same as 'Generic Postscript Printer').  Alternatively, if James's report is to be believed, you could look for 'HP Color LaserJet 9500 PS' and try that one instead.

Note:
From everything you've described, your CUPS settings do not need to be changed, the CUPS component is working correctly as it is. Don't try to mess with them for the time being. The problem is almost certainly in the OS/2 printer object.

143
Hardware / Re: H.P. 2025 need help Per!
« on: July 01, 2015, 03:58:11 am »
POPUPLOG.OS2 would probably help (only the corresponding entries, please!) but I suspect I may know what's happening.

The most likely cause of the crash is that the PPD is either too large, or contains some data item which is too large, to be successfully imported into the driver.  Unfortunately this is an increasingly-common problem with modern PPDs.  The program that imports them, PIN, was written for an age when a typical PPD was around 10-50 KB in size and had a fairly simple format.  Nowadays it's common to encounter PPDs in the hundreds of KB and with extremely complex contents, and PIN just can't cope.  (I and others have tried to incorporate some fixes into PIN over the years, but it's really running up against architectural limitations.  It's an exceptionally badly written program to begin with, with fixed-size buffers and no built-in validity checking.)

I suggest you change the desktop printer object's driver to the built-in 'Generic PostScript (Enhanced)' and see if you have better luck with that.

144
Hardware / Re: H.P. 2025 need help Per!
« on: June 30, 2015, 01:32:58 pm »
I wonder if it's significant that Windows (from what you posted) seems to be printing through IPP instead of LPR...

To get more information about the crash, it's best to look at your POPUPLOG.OS2.

145
Hardware / Re: Unexeptable printer speed.
« on: June 30, 2015, 01:29:11 pm »
Does this slow job problem only happen with Lucide?  What about printing from other applications?

Lucide uses a rather unorthodox printing mechanism which is not how most OS/2 programs do things.

146
Hardware / Re: H.P. 2025 need help Per!
« on: June 29, 2015, 05:35:27 pm »
I suggest you use my CUPS printer wizard to create the printer object.
http://www.altsan.org/os2/printing/#cupswiz

Since you already created the printer in CUPS, choose 'Other printer (manual configuration)' and then choose 'Existing CUPS printer' on the first drop-down.  Enter 'localhost' as the 'CUPS server name', and select the printer from the 'CUPS printer name' dropdown.

That should create the printer object for you.  Hopefully it's fairly straightforward.

147
Hardware / Re: H.P. 2025 need help Per!
« on: June 28, 2015, 04:16:09 am »
In SLPR1 try setting performance to LPRPORTD compatible.

Are you certain the printer is configured to accept LPR connections?

You said it works from CUPS. What protocol are you using in CUPS? (BTW if printing a test page works from CUPS then you can definitely get it working through CUPS.)

148
Hardware / Re: H.P. LaserJet Pro CP 1025nw
« on: June 27, 2015, 02:27:25 pm »
98% of the time you can just enter * as the printer name, although it's possible some printers may want a specific value.

149
Hardware / Re: Unexeptable printer speed.
« on: June 24, 2015, 01:06:46 pm »
Are printing direct, or using CUPS?

150
Setup & Installation / Re: Canon MG7550 issues
« on: June 24, 2015, 01:04:10 pm »
In an OS/2 printer object there are two places you have to set the paper size: in the driver properties, and in the default job properties.

You should also make sure that the application isn't overriding the paper size in the job properties.

And, if you are using CUPS, you should ALSO check the CUPS job properties for that printer.

So in total there are four possible places that an incorrect paper size could be hiding.  Not counting in the actual printer.

Pages: 1 ... 8 9 [10] 11 12 ... 20