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 - Doug Bissett

Pages: [1] 2 3 ... 66
Applications / Re: VirtualBox problems
« on: March 23, 2018, 05:17:50 am »
Did eCS use LCSS?

LCSS should work with any version of OS/2, but it has only been tested with eCS, and ArcaOS. Testing on eCS will cease (I don't use it any more), but it should continue to work. Please, READ the instructions, if you use it. You may wish to tweak your CONFIG.SYS to retain comments.

Applications / Re: VirtualBox problems
« on: March 22, 2018, 07:48:08 pm »
Any thoughts on the above problems, anyone?

I run the old VBox 1.6.1, and the beta 5.0.6, under ArcaOS. No unexpected problems. The won't run OS/2, because you need VT-x/AMD-V enabled, and the OS/2 versions of VBox can't do that (be sure that the option is turned off). You can run a 64 bit OS, as a guest, but it will be dead slow, so don't bother even trying (like 12 hours to boot win 7 64 bit).

There is an even later vboxdrv.sys just uploaded so I thought I would give it a try

The driver should match the version that you are running.

Two other suggestions:

1) Be sure that VIRTUALADDRESSLIMIT is set high enough, so you don't run out of virtual address space. I use 2560. 2048 doesn't seem to do the job, and some systems won't work with 3072. This setting has nothing, at all, to do with physical memory.

2) Sort your CONFIG.SYS properly. I use my Logical Config.Sys Sort program (LCSS), which is at HOBBES.

Networking / Re: ArcaOS network compatibility with OS/2
« on: March 11, 2018, 07:38:47 am »
SAMBA and IBM File and Print client, and server can coexist on the same machine.

True, up to a point. As you note, you can use NETBIOS, but not NETBIOS over TCPIP.

I am laboring under the assumption that Netbios is more secure than TCP/IP or Netbios over TCP/IP  because Netbios cannot be routed.

Again, true, up to a point. One big problem with NETBIOS, is that it cannot be routed, so you are are severely restricted in what you can do with it.

I have connected and transferred files fine over WiFi using Netbios with OS/2 machines.  I also have an I/O Gear Ethernet to WiFi adapter that will not connect or tranfer with Netbios via WiFi but will with SAMBA.

Some older WiFi adapters will do NETBIOS, but very few new ones will. Even wired routers won't pass the packets. I suppose that does make it a bit more secure, but at what cost? Then, of course, there is the >2GB file size problem.

Configuring the WSeB networking/server components and users is MUCH easier than setting up a SAMBA server.

That is not really true. What is true, is that there is a learning curve that you must go through. Confusing things, by using NETBIOS, really isn't productive. It has way too many limitations, and, as you noted, you still need SAMBA, if you want to use modern hardware, and networking services.

FWIW, I use SAMBA, client, and server, the same way that I used NETBIOS (with or without over TCPIP), many years ago (PEER to PEER). The server is configured with the shares, and the client accesses shares. In fact, I find it easier to use than the old NETBIOS. Simple Samba Configuration Center (SSCC) makes it pretty easy to set up the server part. The client just looks to see what is available, and lets you attach to any available shares (assuming that you know the passwords etc.). You do not need (and usually don't want) a dedicated server.

Hardware / Re: How to find or extract a Postscript printer driver?
« on: March 11, 2018, 07:07:53 am »
However, I am using the version supplied with ArcaOS5.0.0 so it is possible it has been updated since then and is now more capable?

Yes, there is a problem in 5.0, that is fixed in 5.0.2. It didn't affect every printer, but you may have one that has the problem. It is, apparently a timing thing, where it tries to use the PPD file, before it has been created.  The fix is supposed to be released to the world, but I don't see any announcement. It may be going through the conversion to be a RPM package, which always seems to take a lot longer than one would expect. I noticed an announcement recently, that the BJNP RPM package had been created (that is for Canon wireless printers). If you have the 5.0.2 ISO file, install \CID\SERVER\ARCAPKG\CUPSGUI.WPI and you should get the update.

Networking / Re: ArcaOS network compatibility with OS/2
« on: March 08, 2018, 09:36:14 pm »
* 80% of people select default options in the installer. So, we can make the conclusion that ArcaOS is installed with Samba client by default, without IBMPEERS.

It is probably less that 40%, if the user has any idea of what they are doing. Yes, it is installed without IBMPEERS. That is something that you need to use the advanced install to select, but why would you want to?

* I understand that Samba is modern. There is only one question: can you connect to remote OS/2 disk using Samba client?

Yes. You should also install, and configure, the SAMBA server, so you can present shares to your network. ArcaMapper does share management for remote systems. The client will access IBMPEER networks too, but as I said, you may need to turn off some of the security features. You can run the SAMABA client along side of IBMPEERS, but you can run only one of IBMPEERS and SAMBA server, since they use the same TCP/IP ports. It *may* be possible to run NETBIOS (not NETBIOS over TCPIP) at the same time as SAMBA server, I haven't tried it, and that also has some serious problems, in addition to the file size limit. It won't go through any WiFi, that I have tried.

Networking / Re: ArcaOS network compatibility with OS/2
« on: March 08, 2018, 08:20:24 pm »
It's not clear, does ArcaOS work with other OS/2 computers in local network?

Absolutely. It also works with win 10, and *NIX.

IBMPEERS is absent in ArcaOS. Samba client is installed instead.

IBMPEERS is not missing, you simply did not select the option, when it was presented, or you chose the easy install, which doesn't always make the best choices, but usually works properly.

WHY IBMPEERS is disabled by default?

I don't speak for Arca Noare, but it is simply that SAMBA is far better. Try to copy a 2.5 GB file, or attach to a win 10 network, with IBMPEERS. It isn't going to work. You can still attach to an IBMPEERS network, using the SAMBA client, but you may need to tweak the security stuff (basically turn it off) to be able to do it. It is documented.

Who made the decision?

Those who understand what modern networking is all about.

What to expect in the next version of the OS?

An even more capable SAMBA, of course. I expect that IBMPEERS will still be there, for those who are stuck in the past..

Use IBMPEERS, if you wish, but I abandoned that a number of years ago. It just isn't capable of handling today's networking requirements. Don't get me wrong, SAMBA does have some problems, but the advantages far outweigh the disadvantages, and it is being developed, while IBMPEERS is not likely to get updated, although there was a fix for something, released not too long ago by Arca Noae. It should be available with an ArcaOS subscription. It is in ArcaOS 5.0.2. It is NOT available for other versions of OS/2 (the contract with IBM forbids it).

Hardware / Re: How to find or extract a Postscript printer driver?
« on: March 08, 2018, 07:55:56 pm »
The only good reason for using cups is that the printer needing support is not postscript capable. As Michael has a postscript capable printer cups is not really required.

Perhaps not "required", if you don't mind messing around, for days, to try to make it work. About 2 minutes with the Install Cups Printer applet, and it is done properly.

You should definitely skip the disk test.

No, you shouldn't.

Hardware / Re: How to find or extract a Postscript printer driver?
« on: March 08, 2018, 04:17:10 am »
I just bought an HP OfficeJet Pro 8740 multifunction printer.  It supports Postscript 3 emulation, according to HP, and their Universal Postscript Driver does work in Windows 7.  Is it possible to extract a .ppd file from the Windows driver installer files that could be imported into the ArcaOS5 Postscript driver?  The printer works with the .ppd file from a Linux CUPS installation, but it doesn't offer the choices of which tray, which paper sizes, etc., that the Universal Postscript Driver does.

Is there any GOOD reason why you aren't using CUPS? At least CUPS, installed by ArcaOS 5.0.2, includes that printer.

Applications / Re: File Open dialog not resizable?
« on: March 07, 2018, 03:55:05 am »
Is this by any chance the set of modules from the ECO-runtime series?

It is the File Open Container. I hate the way it works (even though Arca Noae has fixed the worst problems with it), so I don't install it.

Applications / Re: Get removable media widget back
« on: March 07, 2018, 12:12:56 am »
Your mistake was that you uninstalled the Arca Noae version, before installing the full version of XWorkplace. You should have just installed over the Arca Noae version. The widget consists of RemMedia.dll, RemMedia.xqs,  and RemM_EN.msg (EN may be different for different languages). You can extract them from the Arca Noae installer DVD in \CID\SERVER\ARCAPKG\ANXWP_EN.WPI. I use WPIVIEW (from HOBBES) to do things like that.

Usually a crash or hang will invalidate the whole cache.

Perhaps that is what it is supposed to do, but it is my experience, that whatever caused the crash is cached, and FF tries to go back to it, causing another crash. What i try to do, is force it to the default home page, ASAP after the program starts, then go and clear the cache, before going anywhere else. Sometimes, a crash might invalidate the cache, but that is rare, from what I see. A hang never invalidates anything.

There are two things, that I find will help Firefox (and probably the other Mozilla variants). One is to use a small cache. I set it to 50 MB. Of course, individual setups may work better with other sizes.

The other is to use ANPM (RPM/YUM) to install FFMPEG. be careful there because FFMPEG will want to install the sdl (lower case) package, while other things need the SDL (upper case) package. Install SDL (upper case) first. If you already have sdl (lower case) installed, uninstall it (and watch what other packages get uninstalled with it). Then install SDL, and the other packages that got uninstalled, then install FFMPEG.

Those are not going to make FF work perfectly, but I find that it helps.

I can't explain it.  Before I could barely use Firefox.  Right now it is pleasant to use.

It is possible, that you got a bad web page into the cache, and going back to that web page would try to load the bad page. Eventually, that bad page would work it's way out of the cache, fixing the problem. I try to remember to clear the cache, after a crash.

Applications / Re: Curious about these old patches
« on: March 05, 2018, 07:53:58 am »
You should ask Arca Noae about them. They may already be included, replaced by something better, or not used because they cause instability. I would suggest that #4 would probably conflict with ACPI, which does it's own cooling methods.

Programming / Re: Trying to build my First RPM Package
« on: February 27, 2018, 06:30:34 pm »
At least with a zip file it is easy to see what is there, not so with an rpm on a standard OS/2 v4.52 install.

Use Arca Noae Package Manager (ANPM). Find the package in the list, highlight it, RMB to get the menu, and click Contents. It will tell you what is in the package, and where it is (or will be placed) in the directory structure.

There is also the WPIVIEW program (at Hobbes), that will show you what is in WarpIn archives.

The biggest "problem" with RPM/YUM, is that it takes some control away from the user, because everything is expected to be where it is supposed to be. If the user simply goes along with what it does, it usually works well. As soon as the user thinks they are smarter, and tries to modify what RPM/YUM does, all H__L breaks loose.

In Linux, they have the ability to use different versions of the same files, while OS/2 (mostly because of the 8.3 file name restriction) can really only use one, although there are packages that do supply older versions of some files, while still using the newer ones. Since Linux is micro managed by package authors, it should never be necessary for a user to even think about what might be in a package. If it doesn't match what you have, it is supposed to download what you need, or tell you that the package does not apply to your system. Of course, that doesn't always work as it should, and it is one of the reasons why most Linux distros have abandoned RPM/YUM in favor of something better.

We have what we have, and it works pretty well, most of the time. Using ANPM makes using RPM/YUM a whole lot easier, than trying to use the command line. Additionally, all new files are supposed to be backward compatible, so that breakage does not occur. Of course, that also has problems. One of the biggest problems is the old EMX package. RPM/YUM will replace some of those files, apparently breaking things that use the old EMX stuff. The problem is solved by removing the old EMX stuff, and install the emxrt package using RPM/YUM (ANPM). I have no idea how a user is supposed to know things like that, but asking in an appropriate place, in an appropriate manner, usually gets answers.

Building a RPM package puts a lot of responsibility on the person who does the packaging. They need to make sure that they don't replace things that shouldn't be replaced, and they need to be sure that everything that is required is installed, where it is supposed to be. Generally, only the program author knows all of the details, so they are really the ones who should be making the package. Trying to do it, as Martin is with a program from another source, can be a bit of a challenge. Another big problem are stray DLLs (and other things), that were previously installed in other ways, can be found, and used, when they shouldn't even exist anywhere on the system. RPM/YUM makes no attempt to delete those things.

Pages: [1] 2 3 ... 66