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] 4 5 ... 64
It probably has something to do with using the wrong which.exe. You should have one, and only one, which.exe, and that should be %unixroot%\usr\bin\which.exe. Others may conflict with that one. If you insist on using some other version, you likely need to use LIBPATHSTRICT with it.

I'm curious, what are you guys setting your VIRTUALADDRESSLIMIT to?

I have been using 2560, but 3072 seems to work just as well. With less than 2560 (2048), I start to run out of shared memory space, after a couple of days. I do use the CLAMD.EXE, supplied by RPM/YUM, from netlabs-rel, and it uses close to 1 GB of upper shared memory space. Not using ClamD.EXE doesn't change anything, except I can use a smaller number for VIRTUALADDRESSLIMIT.

LIBC Error: Couldn't register process in shared memory!

This error seems to have nothing to do with VIRTUALADDRESSLIMIT. It happens when I load DLLs high (I can't even run my system, if I don't do that with AOO, and FF). Take either one of those programs, open, and close, any combination, twice, and I start to get that message with anything that uses LIBC. Other things keep on working properly, but it takes a re-boot to get the problem solved (temporarily).

FWIW, I use the Quick Start feature with AOO, and that helps because it keeps the DLLs loaded, rather than unloading them, witch causes the problem. Firefox is another story. It will either crash, or I need to close it, at least once per day, so the longest that I can go, without a re-boot for the LIBC problem, is 2 days.

FWIW, I had to quit using eCS, because simply closing a program, with DLLs loaded high, would crash the system, about every second try, and trying to run AOO, and FF, at the same time, using DLLs loaded low,  was impossible. At least the new ArcaOS kernel doesn't crash the system, when the problem happens.

Utilities / Re: backup and restore using zip
« on: October 21, 2017, 01:06:26 am »
zip -qryS c:

does make a good backup that works with symlinks (i.e. yum still works after restore)

Be aware, that ZIP and UNZIP,  as supplied by RPM/YUM, don't work without some of the DLLs from the %UNIXROOT% directory structure. You do need those versions of the program, to be able to handle files (in and/or out) that are larger than 2 GB.

Applications / Re: Applications OS/2 Needs
« on: October 20, 2017, 06:17:58 am »
My choices:

1) PM123

2) PMView Not free though.

3) Sorry, not  one of my things...

4) eFTE In fact, I rarely use any editor, other than E (really EA), that is the default OS/2 text editor, but eFTE has a lot of customization options, as well as prepackaged configurations.

Utilities / Re: backup and restore using zip
« on: October 20, 2017, 05:59:28 am »
I use -9yrS. -y is supposed to handle symlinks as a standard file. That part seems to work, although I haven't tested everything.

Right now, I am concerned because -S (include system and hidden files) isn't doing what it says it is supposed to do. As a work around, I do ATTRIB -H -S os2* in the root of the boot drive before ZIP, and  (optionally) ATTRIB +H +S os2* again after. There are a few other SH files, but they are nothing to worry about.

FWIW, I have formatted a boot drive, and UNZIPed a backup into it, many times. It always worked, until -S quit working. By using ATTRIB, it works again.

I have also been looking at 7z as an alternative. It compresses better, and I copy the backups to USB sticks, which seem to be getting smaller, and slower, as time goes on.  :(

Hardware / Re: usb wifi in arca50????
« on: October 17, 2017, 11:19:44 pm »
I used the to link the usb.

USBECD only makes it possible to use a program to read/write to a USB device. It probably would drive the device, IF you wrote a program to read/write all of the proper things. Chances are, that you would never figure out what it needs, to make it work.

Then I followed the instructions on this website.

The instructions there, are to use an unsupported driver with GENMAC. GENMAC is the same level driver as USBECD, and only one of them can drive an individual device. GENMAC knows nothing about USB, it only does PCI(e).

Any help to continue ??

Probably not. You would be far better off to use an external ethernet connected WiFi adapter. There are a few of them available. I use an older D-Link 506L, It works pretty well, and it can be useful for other things.

Networking / Re: Mini PCI wifi cards
« on: October 16, 2017, 04:23:44 am »
I'm trying to figure out what mini PCI cards (for the T4x platform) would work well with OS/2--or really ArcaOS. Sort of thinking out loud.

What is in it? Use PCI.EXE to find out. I think most, of the T4x line has network drivers. Personally, I wouldn't bother trying to replace whatever is in it. You would be better off to get an external WiFi adapter, that connects to the wired NIC. They are usually handy for other things as well.

Setup & Installation / Re: ArcaOS 5.0.1 on Dual Boot.
« on: October 16, 2017, 12:29:56 am »
Doug: I don't know why you wrote "READ" in uppercase. I didn't read it completely. It is an 38 pages readme and the license of use does not says you need to read and memorize the 38 pages readme before using ArcaOS.  Which chapter do you refer to?

Well, if you don't READ the whole thing, you might miss something important. there is an index, if you don't want to READ the whole thing.

I appreciate your suggestion about wiping all the Hard Drive, for the moment it seems to be the only solution. It means there is a limitation of OS/2 and ArcaOS to understand the geometry that Windows 10 uses when it prepared the HDD (Limitation that Linux does not seems to has by the way) (please remember this a  non-UEFI, non-GPT system). It even will be interesting for me to know which drivers, or utilities are the one that need to updated to understand different geometries.

It is the only solution. Microsoft seems to have found another way to mess up OS/2. Fortunately, we have people who figure out ways to work around the problems. Linux is a whole different story, they have an army of developers, and they have the source code to work with. We don't have either one.

I don't know all of the parts that need to change, I think that one of them is the kernel itself, if anybody can figure out what to change. There are other parts as well. LVM would probably be the most challenging, but all of the disk support stuff probably needs changes. Then of course, Microsoft has patents, and copyrights, that need to be sorted out, before anything can happen.

without destroying the partitions and without reinstalling Windows 10 please let me know.

You don't need to reinstall windows. You need to back it up , change the partitions, using OS/2, then restore it. The biggest problem with that, is to use a proper windows backup program, and they are hard to find.

If you have a machine that has a recovery partition, you may need to create the media to replace that, although using it would destroy what you did to make OS/2 work, so you may not want to put it back on the computer. You probably want to keep the recovery media, in case you want to restore the computer to factory condition.

Mail-News / Re: PMMail: 2.00.xx to 3.22 migration...what to do?
« on: October 16, 2017, 12:02:40 am »
You are right, I will not be logging this as a bug though. I was able to come up with a work-around, although the fact that my GROUP.DB file is empty is somewhat strange, because if I understood correctly this stores the Address Book Groups...and I certainly do have them present in my old PMMail...sooo??? LOL

Probably easiest to just recreate the groups. They probably needed trimming anyway.  :)

I will just toss this up to the ancient version of PMMail I have been running. No sense spending any more time on something that's suspect to start off with.

It would be interesting to know what the real problem was. Obviously, there was something wrong with that file, since you couldn't do a CLI copy. However, trying to figure it out could be an exercise in frustration.

Doug, thank you once again for all the insights, suggestions and help, greatly appreciated!

Glad to help. I hope PMMail works well for you, and I hope we can find somebody to do more work on it. The project is mostly paused, at the moment, but it is definitely not dead.

Setup & Installation / Re: ArcaOS 5.0.1 on Dual Boot.
« on: October 14, 2017, 09:15:50 pm »
I think I'm getting the usual limitations of ArcaOS installation tools.
- "Disk 1 reports a corrupt partition table".
- "LVM Error ( 8 ) - Operation is not allowed" when I try to create the partition.

Yes, completely normal.

1) Is there another way to fix how ArcaOS see the partitions without Dfsee ?  (without wiping the hard drive)

Well, first, the ArcaOS tools are extracted from DFSEE, but DFSEE is more informative. Did you READ the README, in the root of the DVD?

Warning: DO NOT use DFSEE, booted form any OS, other than OS/2, to try to adjust anything, or it will probably do it in the windows way, and OS/.2 won't like it.

I encourage you to wipe the hard drive then follow this How-To:

It depends, exactly, how the disk was created. With win 10, you probably got the layout for very large disks, using a geometry that OS/2 cannot use (even though the disk is only about 350 GB). If that is the case, you need to back up win 10 (the ONLY tool, that I know of, that does the backup/restore properly, is ACRONIS. If you have a Seagate disk drive, even in a USB enclosure, you can get the SEAGATE DISK WIZARD, for free. It is a cut down version of Acronis, and works well). Back up win 10, using the files and partitions option, then use the ArcaOS tool to wipe the disk, and partition it properly. Then, you can restore win 10 (don't forget to make the Acronis boot disk first), and proceed to install ArcaOS. Be sure that you do NOT restore the boot record, or you will end up where you started.

If the disk geometry is something that OS/2 understands, the ArcaOS tools should be able to make the adjustments.

If you are going to do a new install windows (linux etc.), be sure that windows (linux etc.) does not  partition the disk. Plan ahead, and use OS/2 (mini)LVM to make all of the partitions, or you will likely end up with windows type partitions, and OS/2 doesn't like that.

Mail-News / Re: PMMail: 2.00.xx to 3.22 migration...what to do?
« on: October 14, 2017, 05:13:19 pm »
I did file a request for a new ID on the bugtracker, but it's been a couple of hours now and I still have not received anything in my email. I'll give it a bit more time.

Did you get a response to this? Apparently the ID was created, and sent. If you didn't get it, I will see if I can figure out what happened.

Mail-News / Re: PMMail: 2.00.xx to 3.22 migration...what to do?
« on: October 14, 2017, 07:33:40 am »
Well, in the end I found out that the GROUP.DB file being 0 (zero) bytes in length is what was causing the problem. Simply including a digit (I used a 0) in the contents of the file allowed the migration tool to successfully pass that check and eventually produced a working PMMail application.

Well, I am glad that you got it. GROUP.DB  is supposed to contain the address groups. If there are no address groups, It can be zero bytes.

On my system attempting to do a CLI copy of that very same file produces an error, which I believe is to be expected. XCOPY on the other hand, which is also used during the migration process, does successfully copy the file over to the NEW install. At least that's what I have been able to surmize given the results I see in the filesystem folders.

That would seem to be somewhat strange. I can copy a zero byte file, with no troubles, so there must be something wrong with that file. Possibly a bad EA, or something like that. Stranger things have happened during a migration.

Given the date/time stamp of the group.db file present in the NEW directory it certianly appears that the Migration process successfully copies it over in the first place, but then fails later on as it attempts to create a backup???

The backup copy is made after the main xcopy, and before the tool modifies the file. In this case no modifications are needed, because it was empty. The copy should have worked though. The only conclusion is that the file was somehow defective. I do know, that there is a flaw in the kernel handling of defective EAs, but trying to prove that now, is probably impossible. If it is the kernel EA problem, ZIP would also crash on it, but adding the "0" seems to have fixed the problem, somehow. Now, you don't have a broken file.

OK, problem solved. I am happy to report that SMTP Authentication works well and that other than this one "gotcha" the massive amounts of my emails across three separate accounts were migrated without any other problems. This is pretty impressive given the amounts of data!

Happy to hear that you got it. You probably should do a Re-Index all, in each account, before doing too much more. If GROUP.DB  was not being used, it should be empty. You may want to open the file, in the editor, and remove the "0" that you put into it, otherwise, you should be good to go. Don't forget to turn off the "Leave messages on the server" flag, in each account (Receive tab), if you got that turned on. If you don't mail will pile up in the server, and that usually causes mail to be rejected.

Don't assume that everything still works exactly the same as before, but most of it will. The Help is much better, but not perfect, and the FAQ (there is a link in the PMMail Help menu) should be mostly correct.

Have you tried just copying the folders over to your new install rather than running the migration tool?  You might need to re-index the folders after.

That would be something to do, when nothing else will work. The problem was not in copying the folders anyway, it was in the GROUP.DB file, which is part of the address book. As I recall, the only changes are to adjust the paths to point to the new location, but there is nothing to adjust if it is empty. Copy works okay, on zero length files, so it should have worked on that one too.

I'm afraid that is not going to work given how old my version of PMMail is. Reading through the documentation it specifically states that the Migration tool makes certain changes to the data files in order to make them usable by the new release.

Actually, it will work, but there may be a few things that need to be manually updated. I wrote the migration tool, and I don't remember all of the things that it does. I would need to go and read the code (it is done with DrDialog, which is REXX), and the last change was in January of 2015.

I did file a request for a new ID on the bugtracker, but it's been a couple of hours now and I still have not received anything in my email. I'll give it a bit more time.

Hmmm. I am not sure who is doing that now. If it is who I think it is, it may take a day or two, but I will rattle his chain. I am not sure if it would be worth while to make a bug report, or not. I am the one who would need to look after it, and all I can do is write it off as a bad file in the original PMMail. This is definitely not the first time something like that has happened. Then again, it probably wouldn't hurt to document what happened, but I don't think there is anything to do to fix the problem, short of completely rewriting the tool, and that isn't likely to happen. It isn't perfect, but it does the job (sometimes with a few glitches).


Mail-News / Re: PMMail: 2.00.xx to 3.22 migration...what to do?
« on: October 14, 2017, 12:24:38 am »
Are you suggesting that I put NEW child folders into the account specific default SENT parent folder? I thought of doing this before but I always assumed that it was a bad idea to mess with this folder. It certainly makes a lot of sense, and for starters I would be able to do a search in the SENT folders, which today causes my PMMail to simply crash.

Yes. Child folders in Sent are okay, but they should all be sent files, or you might get some strange entries in the list. That is, don't try to put both sent, and received, files in the same folder. The display is a little different.

OK, so a specific issue I have is that I only have about 1.5Gig left on my application drive (also happens to be my boot drive, but that's the legacy of the original install I did). So the option I have is to move my current pmmail directory structure to a different drive, where I have a bunch of space, wipe it off of my boot drive and then do the WarpIn based install. Will the installer itself attempt to migrate the old PMMail stuff during the install, or is this a separate process one does later once the NEW PMMail install is completed?

It is really a separate process, but the migration tool is started after the WarpIn install is done, and before it terminates. In this case, I would suggest installing to the new location, and just let the tool do the copy. That is supposed to work, and it should give you the default setup, with all of your accounts, and files. Don't touch your old install, at this point. It should still work.

The 2nd question is: does the migration tool/process simply need to find a disk directory structure of the old PMMail, or is it looking for some application specific install/config data?

It actually looks for the INI entry that the old PMMail puts in one of the INI files (USER.INI, I think). That should point to the old PMMail, but many users have managed to lose that entry over the years, so i would be surprised if it is there, and correct. Just point the migration tool to the old base PMMail directory, and it should do the job.

Basically I am wondering if my plan to move the current install to the spare drive has a chance of working?

I think it should work, but I don't remember doing a copy to a different drive. Let's see what happens.

UHOH! something has come up. I will have to follow up later...

Mail-News / Re: PMMail: 2.00.xx to 3.22 migration...what to do?
« on: October 13, 2017, 08:30:23 am »
First BACK UP what you have, just in case something goes wrong (and it could, simply because the version you are using is very old).

You may want to join the mail list. See That is the best place to ask questions, and find answers to problems, but you need a working mail program to use it.

Next, be sure to READ the information that is presented by the installer, and it would probably be a good idea to look through the FAQ Setting up secure server support is explained in the FAQ, in a different way than it is in the Help. Some people find one, or the other, to be confusing, but they usually figure it out by using both.

I would suggest that you think about reducing the number of messages in the primary folders (Inbox, Sent, and any that you filter messages to). I usually put old messages into sub folders, by year, or month, depending on the amount of activity. Sub folders of the Sent folder take on the characteristics of the Sent folder. You will get much better performance by doing that, and migration will probably be better too.

Then, Re-Index the important folders, to be sure that they don't have surprises in them. The new PMMail can Re-Index whole accounts, but the old one can't (I assume that your version can do folders, but it may not).

Okay, now that you have done some preparation, try it. It will ask for a new location, and basically copy all of your mail etc. to the new location (it is a new directory structure, and some files are modified to match), so be sure that you have enough space. The old PMMail will remain operational, until you decide that the new one is working. Again, READ the instructions, and remember that any mail that you SEND with one, will not be in the other. The new accounts are set to NOT delete mail from the POP server, until you set it to do so, so Incoming mail can end up in both places, as long as you process it with the new program first. If something goes wrong, you can ask what to do about it, and, worst case, erase what was done, and start over.

Another thing, is that the "Migration Tool" is badly named. It does the migration, but it also does a couple of other things, like make PMMail the default mail program, and remove the old PMMail (it actually ZIPs it up), when you select those options. It should never try to do a new migration, when the source is the new PMMail, However, if you don't have a standard setup, odd things can happen. Please ASK what to do if something goes wrong.

Oh yeah, the new spell checker needs to have the appropriate files beside the main installer, when you do the install. Page down on the PMMail home page to get the ASpell packages that you need. They are used by the main installer.

Be especially careful with existing filters. Some fairly serious problems were fixed, and that means that some filters now actually do what they are supposed to do. A few people got caught using incorrect filter operation, which now doesn't do what it did before.

You mention SPAM. PMMail now uses the BogoFilter program, so you will probably want to use that, and get rid of your own SPAM filters. I guarantee that BogoFilter will do a better job, after you properly train it (usually takes a few days, but it is not difficult to do).

That should cover most of it, but I may have forgotten something. Try it, and see what happens.

Mail-News / Re: PMMail 3.22 and SMTP authentication...can it do that?
« on: October 12, 2017, 07:12:41 am »
[quoteI do not have a problem paying for a sir, happy to pay for my 3.x PMMail upgrade. What I do not understand is this requirement to purchase a VOICE membership and then pay once again for the product. If I have no desire to be a VOICE member then why am I being forced to pay for it?][/quote]

That whole procedure was changed. You will need to read the new instructions (which I, admit to not doing).

The reason why it was done like that, was that those who were members when VOICE bought the rights were the ones that paid for those rights, so they were grandfathered into getting PMMail. Those who joined after the purchase were charged for the program. Since VOICE tries to keep the costs down, they decided to just have the user pay twice for a membership, rather than having to pay the banks (or, whoever) for a whole new method to collect money for PMMail. They already had to pay to collect memberships. Now that the whole operation has moved to the Netherlands, the rules have changed, and so has qualifying for PMMail, but you still need to be a sponsor of VOICE. PMMail is, after all, a bonus for supporting VOICE (which you really do want to support, since they support OS/2).

It really is THAT simple...nothing more to it...let me pay for the product I purchase, that's all I'm asking.

Well, no it isn't that simple. When VOICE bought the rights to PMMail, the board decided that it would be a bonus for those who support VOICE. After all, they own it, so they can say how they will use it, and if you want PMMail, you become a supporter of VOICE (at least for one year). The PMMail license doesn't end, if you decide not to support VOICE, but it does make it that much harder for VOICE to support OS/2.

Pages: 1 2 [3] 4 5 ... 64