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 - DougB

Pages: 1 [2] 3 4 ... 28
Networking / Re: Wake on LAN
« on: 2012.09.10, 23:00:14 »
More information:

With my A8N-SLI motherboard, using the driver from nveth-0.1.10.wpi, I went to windows XP, and enabled the magic packets option in the driver. Now it will wake up, even after running eCS. This happens to be the one that I want to be able to wake up, so that is good.

On my IBM ThinkPad T43 (1871-W8M), I can't seem to convince it to work. I suspect that I may not have found the right BIOS, and/or, windows settings, yet.

On my antique IBM ThinkPad A22e, turning on the setting in the BIOS did the trick.

It appears that the eCS drivers may not mess with the magic packets feature, but it also appears that my Lenovo T510, using the Multimac Intel driver from e1000e-0.2.3.wpi, does turn off the feature, unless it is specifically enabled by the driver at shutdown. This is probably a "security" feature. So, the driver needs to enable magic packets at shutdown for Magic.CMD to be able to turn it back on. Not important for what I want to do, but it may help others.

I suspect that it is NOT a good idea to enable laptops to power on with a magic packet anyway. If it gets one at an unexpected time, it may cause system damage.

Now, the next question that I have, is how can one tell a remote computer to shut down (cleanly, of course), from a program? I can see this being useful to power on the machine that I want to backup to, do the backup, then tell it to shut down. Of course, the shutdown is really an indication that "this" machine is finished. some other machine may also be doing a backup, and it would not be good to pull the plug on that.

Networking / Re: Wake on LAN
« on: 2012.09.10, 17:55:18 »
Yes, you need to enable magic packets in the windows drivers. Then, the machines will turn on. However, if you run eCS, the driver seems to know nothing about enabling magic packet support, and the machine will not power on after running eCS. I tried this with my Lenovo ThinkPad T510, using the Multimac Intel driver from e1000e-0.2.3.wpi. Some other eCS drivers may work.

Networking / Re: Wake on LAN
« on: 2012.09.10, 17:05:14 »
I have tried it on the four of the five computers, that I have, where it should work. Only one will power on. Of course, it isn't the one that I would like to use it on. I suspect that the problem is that windows turns off the feature by default, and the eCS drivers (Multimac for Intel, Multimac for NVIDIA, and GENMAC for Broadcom) doesn't enable it at shutdown. The one that does work, is a Realtek 8139, using the RTSND driver. I need to find more time to play with this, but it does look like it does what it is supposed to do.  Thanks...   :)

Utilities / Re: Burning CD/DVD on AHCI system?
« on: 2012.09.05, 16:31:20 »
is there a way of burning the CD/DVD media on AHCI system?


If you look up the parameters (\ecs\DOC\OS2AHCI\README), you will find that /S gives you the SCSI interface that CD/DVD writing needs. You also need ASPIROUT, or ASPINKK, and OS2ASPI.DMD (same as when using IDE).

Trying 184 on my Asus M3A78-EM motherboard (2 EHCI, and 5 OHCI, adapters). I find that no USB 1.1 device can connect when using the USBOHCD.SYS driver from 184. If I back level only USBOHCD.SYS to the 183 version, it all works properly.

It appears that USBOHCD.SYS (184) has a problem, but backing that out to 183, while leaving USBEHCD.SYS at the 184 level causes a repeating TRAP0008 (I think - it is hard to tell).

Hmmm. I just realized, that the system where this happened has an OHCI adapter (AMD 756 chipset) on the motherboard, that has been disabled forever (it causes very serious problems when the original IBM drivers find it). Somehow, that has managed to get itself enabled. After adding another USBOHCD.SYS entry, in CONFIG.SYS, the 184 drivers are working, even with the previously unusable adapter. So, I guess I had better go back and see if the other system has a similar problem (I am pretty sure that it doesn't - but).

So, this:
One has 2 OHCI and 1 EHCI adapters - doesn't operate my Logitech wired USB mouse.
has changed to this:
One has 1 OHCI adapter on the motherboard, and  2 OHCI and 1 EHCI adapters on an add in card - works.

An interesting observation is that it seems that when there is one driver short, the adapters that get enabled are not always the same ones. I think that the motherboard adapter was enabled sometimes, but not always, while one of the adapters on the add in card was enabled only when the on board adapter was not enabled, and the other was dead. It is entirely possible, that the adapter where the mouse was connected was the one that didn't get a driver.

I have 5 systems. Three work good, two don't seem to recognize the USB mouse.

One system has only one UHCI adapter - works.
One system has 4 UHCI and 1 EHCI adapters - works.
One system has 2 EHCI adapters - works.
One has 2 OHCI and 1 EHCI adapters - doesn't operate my Logitech wired USB mouse.
One has 5 OHCI and 2 EHCI adapters - doesn't operate my Logitech wired USB mouse.

Going back to 183 works fine.

I also tried my wireless USB mouse on the two failing systems. It doesn't work either. It does work on the other three. A very quick test shows that USB 2.0 devices are working.

It appears that USBOHCD.SYS (184) has a problem, but backing that out to 183, while leaving USBEHCD.SYS at the 184 level causes a repeating TRAP0008 (I think - it is hard to tell).

Incident #22 at the bug tracker.

It makes me thinks somebody has gone to some effort to make Ecs look a little more modern and I appreciate that effort.

I seem to recall, that WPS Wizard existed before eCS did, as did XWorkPlace (which morphed into eWorkPlace). WPS Wizard  did not gain much popularity because of many problems, and because the author was pretty picky about what he acknowledged as a problem. Basically, if he couldn't make something fail, it didn't get fixed. I can understand that, because I too find it difficult to fix something that isn't broken. However, some attempt to understand a problem, and fix it, needs to be made anyway. I also remember that the author didn't much like anybody claiming that his software was less than perfect, so he "packed up his toys, and went home". Sorry, but I can't think of a nicer way to put it, and that has happened more than once.

The reason for my post to was to see if anybody knew how I could capture information (like logs or other debugging information) that the developer might find useful

There are many ways to help software developers improve their products. Unfortunately, there is no good set of instructions about how to go about it, and far too many developers seem to think they don't have the time to coach those who want to help, but have no idea how to go about it (I suspect that you fall into that category). Of course, those who don't know what to do should take some effort to learn, before they start bothering a developer. If you follow the entries in the bug report areas, for a while, to see what the developers want, and then learn how to reproduce reported problems, with supporting documentation, you should pick up the basics. You should also see what they tend to ignore  ;D

I think you would be better off to pick a more current project, with more "user friendly" developers., and follow the project for a while to see how you can help, and how to go about it. Trying to help with a project that is apparently abandoned by the developer is probably not going to do anybody any good. It is sort of like offering to help Ford motor company improve on the 1976 Thunderbird.

There are more important projects that seem to need help. A couple that come to mind are eCUPS, and SAMBA. User testing, and problem report feedback, is needed. Printer, and networking, support, would seem to be a little more important than "eye candy" in the overall picture. Some would disagree, but if a system can't support the basics, it really doesn't matter how good it looks. Nobody is going to use it.

As the old saying goes: "If you can't make it work, make it look good". I would rather make it work.

Above all, keep it civil. Making demands of a developer (especially one who is voluntarily doing the work), is not going to make them feel wanted. Of course, that is a two way street.

"The developer" is just Chris, that person who created the NOM thing.

Reference to "NOM"?? I don't recall that.

Chris also did AudioCDCreator, which works reasonably well. When you install the last version of ACDC, it complains that WPS Wizard is not installed, but it still installs, and works okay, without it. Apparently, there are some menu items that are missing, but it is obvious that they are not required.

So, either it works for you or not.

Unfortunately, that seems to be what happens when you have a program from a single developer, and it is closed source. If you have a problem, you are often ignored, unless the developer can, easily, reproduce the problem (even then, they can decide that it isn't worth the effort to fix it, or, they can just walk away). I suspect that this sort of thing is the main reason why Martin insists that all projects need to be open source.

Meanwhile, it seems that WPS Wizard works for some, and if it doesn't, the only option is to remove it, and find another way to do what you want. I would suggest that the OP should uninstall WPS Wizard, and find another way to do whatever it is that they want it to do.

These days Mozilla and OOo can't be run simultaneously on any of my installation

I don't have trouble with running Firefox 10.0.5 and OOo 3.2 (Text document) together. I also have lots of shared memory space left over (shown by Above512). The secret seems to be to abandon HPFS, and use only JFS (as shipped with eCS 2.1). I also use FAT32 for compatibility with windows (I do NOT use cachef32.exe with it), but HPFS seems to use up a lot of shared memory space that can be used elsewhere. Today, the big shared memory space hog is ClamD (ClamAV), but it seems to use the more plentiful upper shared memory space, so it hasn't been a problem, yet.

I have got to ask: Why do you want to use WPS Wizard?

I tried it years ago, and got it off my machine as quickly as I could. I would never use it again, simply because it does all of the bad things that you are describing. I can't say that I have ever missed it.

So far, everything seems to work on my T510, except suspend/resume, and the Realtek WiFi adapter (which is probably a GENMAC problem). I think that suspend is working, but resume fails to turn on the backlight in the screen, so it is difficult to tell if resume actually works. Since Ctrl-Alt-Del (twice, or more) fails to cause a reboot, I suspect that resume didn't complete.

Try REMing the "RUN=E:\OS2\EXTENDFS.EXE *" line in CONFIG.SYS. That line is not, normally, needed anyway, and if that is what is causing the problem, it should then work (or, perhaps give you some other indication). You can also REM the "CALL=E:\IBMCOM\PROTOCOL\NETBIND.EXE" line, but your networking won't work.

I doubt that either one will let it boot. It will probably just stop at the next RUN or CALL statement. I expect that this is related to a problem, that I have seen more than once, where the boot stops after executing the last DEVICE statement, and before it starts to run the RUN and CALL statements.

Three other things to try:

1) Add the line "DEVICE=STOP.SYS" at the end of your CONFIG.SYS. There is no STOP.SYS, so the system will stop, and complain that it is missing, with the option to use ENTER to continue. That should allow whatever causes the blockage to finish, and when it continues, it should work. If that works, you can use other methods to cause a timed delay.

2) Try sorting the CONFIG.SYS with my Logical Config.SYS Sort (LCSS) program:

Be sure to READ the instructions.

3) If you use ACPI, and have a Software Subscription, get the latest available version of ACPI (3.20.03 at this time). Of course, you will need to get the machine booted to install it using the installer.

Networking / Re: ****solved***Network card help.
« on: 2012.07.19, 16:49:19 »
Thank you for explaining the issue to me.  That was easy and it's now working.

Great! Unfortunately, doing that doesn't always work. More recent devices seem to need something else that GENMAC is missing. Eventually, the Multimac project should produce a driver for more modern devices, but I think that GENMAC will still be required for some of the older devices that GENMAC supports. Watch for announcements of new support by Multimac, and use that, if it supports your device, and if it works. If it is supposed to support your device, but doesn't work, be sure to let the developers know about the problems so they can fix them.


Coming back to the computer half an hour later it was hanging in the pop up window with the text: Releasing file systems and showing 100 % done. It didn't respond to any action and I just had to switch it of (power off).

I saw that once. I had to press the reset button (which would be equivalent to power off, then on).

it came up with the blue background and the ePager, and there it stopped

I have seen that a couple of times (it seems to be unrelated to the first problem). It happened after a system crash, but Ctrl-Alt-Del (twice) has always caused a clean reboot.

I tried to start with pressing Alt+F2 and select an earlier config file.

I think you mean Alt+F1 to get to the menu.

I wonder if I can copy a file from 2.0 or do I have to reinstall 2.1.

Re-install, or copying files, probably won't help. I think you have run into a problem that can happen just as the WPS is starting up. What you probably need to do, is change the boot timing somehow. Try adding a file AltF2on.$$$ to the root of the boot drive. It doesn't matter what is in it, the system simply looks to see if that file exists, and if it does, it acts as if you had done Alt-F2 immediately after the boot starts. That will slow the boot slightly (probably not really noticeable) because it will display the startup information. If you are lucky, that should change the timing of the problem enough that it won't affect you any more.

Networking / Re: Network card help.
« on: 2012.07.19, 04:07:50 »
However, it doesn't seem to be enabled or fully recognized.

That is true. If you load a GENMAC driver in UNSUPPORTED mode, it apparently doesn't load something that XWLAN needs to make it work.

Checking the log I find a particular file is not found during loading:

True again, but those files are not needed.

What's puzzling to me is the eCS installer recognizes the wireless card, naming it Atheros AR5007EG/AR42X, and suggests a driver.

There is a problem with the Atheros drivers in eCS 2.1. Apparently, Mensys could not get clearance to include the windows drivers for Atheros devices, so they removed the windows drivers from all of them. GENMAC still installs okay, but the windows driver is missing (it probably wouldn't work anyway <see below>).

Those instructions referred to downloading a program from an archive and editing a similar file, but they lost me.

What you need to do, is modify an entry for a supported device, in the GENMAC driver, to make it match the device that you have. This cannot be done, and then distributed, because that has been specifically forbidden by the author of GENMAC (who also refuses to release his work, or do anything more with it). All we can do is tell you how to do the modification (which is actually quite easy). I will add a few more lines to the note from the GENMU package.

NOTE: It seems that GENMAC does not enable wireless device support when it is used in UNSUPPORTED mode.
To get around that limitation, you will need to edit a similar device in
(other copies of this file are not used). There is a tool called EGENM32W that is designed to make
changes to that file. It is at:

Unzip that, and run the program EGENM32W.EXE. Click the OPEN button, and navigate to <boot drive>:\IBMCOM\macs, then scroll down until you find genm32w.os2. Click Open. Now, you will see all of the SUPPORTED devices that are in GENMAC.

Look up a similar device (try $168C $0012), and change the ID, and file names (if required).
Change $0012 to $001C
Change AR5211.SYS to ATHW.SYS
Change AR5211.INF to NETATHW.INF
Click SAVE and EXIT.

Then, edit <boot drive>:\IBMCOM\PROTOCOL.INI to change the word "UNSUPPORTED" to "NONE"

Reboot, and see what happens. Of course, you also need XWLAN to be able to actually use the wireless device.

READ the instructions carefully.

Pages: 1 [2] 3 4 ... 28