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 ... 97 98 [99] 100 101 ... 107
1471
Networking / Re: OS/2, Realtek and NIC drivers
« on: October 09, 2013, 09:47:05 pm »
Quote
r8169-0.3.1.wpi

Which doesn't work.

I guess it is time to ask the tough question. What, exactly, do you mean by "Which doesn't work"???

If you report that "it doesn't work", nobody is going to bother to ask you "What doesn't work"? They also won't bother trying to figure it out. They need to know, exactly, what it is that they are trying to fix, and how to reproduce the problem.

It is also possible, that you have something else that is causing the problem. With more information, we might be able to spot the problem, without bothering the developer, who is overloaded with work already.

NETBIOS *might* be the missing link. As I said, I haven't used that, for years. It was causing problems when I quit using it, and I am sure that it hasn't changed. The last time I tried NETBIOS over TCPIP, it was causing more problems than SAMBA (which is certainly not perfect), but it worked better than NETBIOS, for me, when I was using it.

1472
Article Discussions / Re: ecs 2.2
« on: October 09, 2013, 06:38:17 pm »
Does any one have any thoughts as to what is going on with
ECS 2.2 GA or another beta

regards Phil

Hopefully, they are working hard to get it right, this time. The last attempt was not done well.

1473
Networking / Re: OS/2, Realtek and NIC drivers
« on: October 08, 2013, 08:40:04 pm »
Quote
"Found Realtek NIC at bus 3:1:0: 10EC:8169 version 3 (RTL8169sb/8110sb)"

Interesting... That is the same one that always worked with Multimac, for me, but mine is on a PCI plug in card. It also worked with GENMAC, but only at 100 Mbs.

Quote
Samba won't install under Ubuntu and needs to be beat over the head a few times.

Odd. SAMBA comes with Linux Mint (which is Ubuntu under the covers). All it needed was to be configured.

1474
Networking / Re: OS/2, Realtek and NIC drivers
« on: October 08, 2013, 04:44:04 pm »
Quote
Years ago I installed my system with it and got sporadic traps

When I was using RTGNDA, nothing else would work, at all, so I figured that potential traps were better than no networking. FWIW, I used it for a couple of months, and never had a problem with it, other than I couldn't use it with VBox (which didn't matter anyway). I haven't used NETBIOS (not over TCP/IP) for many years. I have an Asus WL-330g that will not work with it. If anybody is interested, rtgnda13.zip comes with source code.

I did take the steps necessary to report the Realtek problem, and work with those who know about such things, to get it fixed. Sitting back, waiting for somebody else to do it, is not an option, although it took a second report to get enough interest to get it done. Apparently, the Linux crowd has been having similar problems with Realtek devices, but there are a lot more of them working on the problem.

1475
Networking / Re: OS/2, Realtek and NIC drivers
« on: October 08, 2013, 06:12:10 am »
Quote
Device 8168h RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller

Unfortunately, that does NOT tell you what the chip is. Realtek seems to have about 40 different chip versions that PCI will identify as the same thing. They are not the same. You need the RtlChipId.exe program, which is found along side of the "working" driver, in the betazone. Without that information, everybody is guessing about what chip you have. There is a clue, that you have something different, because of the "/8411" entry.

Quote
less one day...

Okay, I just checked, and what is in the non SS betazone is what I have. RtlChipId.exe is also there. That means that you should collect the relevant information, and report the problem.

Quote
Doug, I do not have access to Subscription Services though I have in the past; I do not consider it to be a valid expenditure...

As for Software Subscription being a "valid expenditure", that depends on your point of view. If you want (some of) the latest stuff, before it becomes available in the "next" release, you pay for Software Subscription. However, you must also look at it as a way to support moving eCS (OS/2) forward. IMO, I can't afford NOT to have SS, it is a way to support the work that is being done, and, you get the "next" release, when it becomes available. Not a bad deal, although it would be better if "next" releases were better managed, and more frequent.

To correct what I wrote earlier (About the "third device"):
Code: [Select]
10EC:8169 version ?? (RTL8169a/8111a)
(or something similar). It is on a PCI plug in card.
should read:
Code: [Select]
10EC:8169 version 3 (RTL8169sb/8111sb)
It is on a PCI plug in card.

Quote
At any rate, I'll see how that GenMAC driver does now...

I couldn't get that one to work with the 10EC:8168 version 33 (RTL8168evl/8111evl) device. It did work with the 10EC:8169 version 3 (RTL8169sb/8111sb) device, but only at 100 Mbs. When I tried it at 1000 Mbs, it would trap in GENMAC. You could try updating to the windows driver that comes with it, but that may not work at all. GENMAC is definitely limited, and most newer windows drivers won't work.

BTW, which RTGNDA driver do you have? The one that I was using is v1.13. BLDLEVEL shows:
Code: [Select]
Signature:       @#chagrin:1.13#@Realtek RTL8169 OS/2 NDIS 2.0.1 MAC Driver
Vendor:          chagrin
Revision:        1.13
File Version:    1.13
Description:     Realtek RTL8169 OS/2 NDIS 2.0.1 MAC Driver
on the rtgnda.os2 file. I also had to use some parameters to make it use IRQs above 15, and to add the MAC address.

1476
Networking / Re: Remote file browsing and management OS/2 -> Linux
« on: October 07, 2013, 05:27:41 am »
As I noted earlier, you don't need to use SAMBA server. All you need is the SAMBA client, which will co-exist with the older, OS/2, network support, and allow you to log onto the Linux SAMBA server. You probably do need the latest version, with supporting software, so it will actually work reasonably well. Google "netlabs samba" to get the latest information.

You will probably run into user ID, and password, problems when trying to get the eCS SAMBA client to log on to Linux SAMBA. It seems to work more like the Win 7 (and probably win 8) networking. I have not found a reliable way to get it to connect, but it seems that "Authenticate for browsing" is the key, meaning you need to add the user ID, and password, BEFORE you attempt to log on to Linux (or even display that a share exists). It does work, but I don't, yet (and probably never will), have deep layers of sub-directories to play with, in Linux. I do in an eCS, home built, NAS box, and that seems to work okay, but large file transfers, using the SAMBA server, seem to die after a while (99% CPU on the server). RSync seems to be the most reliable way to do mass file transfers (Linux, and eCS). Poking around in Linux, with the few directories that I do have access to, from the SAMBA client in eCS, seems to work okay (once I get it to connect, and it is much faster than with a SAMBA server, in eCS).

The bottom line is, that the SAMBA client should do what you want, and it should co-exist with what you use now.

1477
Networking / Re: OS/2, Realtek and NIC drivers
« on: October 07, 2013, 04:11:39 am »
You need to go to the eComStation Software Subscription site. If you do not have that, you do not have access to anything that has been released after your subscription ran out. It must be renewed after one year (the site becomes static, as you describe, if you don't).

The ONLY version of the Multimac Realtek driver that will work with the chipset that you have, is the one from that source. It was, unfortunately released as r8169-0.3.1.wpi, which is the same name, and version, used for an earlier, defective, version of the driver. The one that works, for me, is dated 5/17/2013 (m/d/y). Bldlevel reports:
Code: [Select]
Signature:       @#D Azarewicz:0.3.1#@##1## 17 May 2013 08:46:29     DAZAR1
:::1::SVN253@@Realtek 8169/1Gb PCIe MAC Driver
Vendor:          D Azarewicz
Revision:        0.03.1
Date/Time:       17 May 2013 08:46:29
Build Machine:   DAZAR1
FixPak Version:  SVN253
File Version:    0.3.1
Description:     Realtek 8169/1Gb PCIe MAC Driver
on the r8169.os2 file. If that is what you have, please report that it doesn't work, with as much information as you can supply, at the Multimac bug tracker.

I have three Realtek Gigabit devices. PCI.EXE describes one, on board device, as:
Device 8168h RTL8111/8168B PCI Express Gigabit Ethernet controller
it is, in fact a:
10EC:8168 version 21 (RTL8168c/8111c)
(from RtlChipId.exe, that is available in the Software Subscription betazone).
A second, on board device, is described as:
Device 8168h RTL8111/8168B PCI Express Gigabit Ethernet controller
It is, in fact:
10EC:8168 version 33 (RTL8168evl/8111evl)
which is probably the same as yours.
I don't have the other one installed, but I think it is
10EC:8169 version ?? (RTL8169a/8111a)
(or something similar). It is on a PCI plug in card.

As you can see, Ivan's question is valid, you need to find out which Realtek chip it is, and the only tool, that I know about, that actually tells you that, is RtlChipId.exe, which is found in the betazone under Software Subscription (which is NOT the same as the betazone in the eCS web site).

The third one always worked with the various versions of the Multimac Realtek driver.

The first one started working, before the second one did.

The second one is working properly, with the above mentioned driver, but did some nasty things before the latest driver was available. One of those nasty things is that it disabled the ethernet interface, and the ONLY way to get it turned back on, is to turn off all power to the machine (pull the plug, - and remove the battery if it is a laptop - for a minute, or so). Even windows (and the working Multimac driver) wouldn't re-enable it, before the power was removed. The only other driver, that came close to working, was the old RTGNDA driver.

1478
Networking / Re: Remote file browsing and management OS/2 -> Linux
« on: October 06, 2013, 09:28:52 pm »
Quote
Samba is not really an option because my home LAN uses LAN Services a fair bit. It could be replaced with Samba again, (I tried it once before), but Samba has a problem in dealing the EAs; I had to dump it a couple of years back; I won't try again.

Ideas?

If you haven't tried SAMBA for a couple of years, I would suggest trying it again. It still has problems, but it is working much better now than it was even 6 months ago. FWIW, I have never had trouble with EA support, although I never tried it with Linux at the other end of the wire (I assume that Linux supports EAs, but I never checked that out. It may need to be enabled, somehow). EAs, other than in the desktop stuff, are mostly redundant anyway. Any program that thinks you need them, will recreate them.

Of course, SAMBA, the server, is quite different from the SAMBA client. You can use the client (EVFSGUI, that comes with eCS, but the updates at netlabs improve the reliability a lot), along side of the NETBIOS over TCPIP stuff. The SAMBA server does not get along with NETBIOS over TCPIP, because they both want to use the same ports. From what you say, the client should do what you want. You would need the server, if you want to use Linux to browse the eCS machine, although it might work with NETBIOS over TCPIP (I never tried it).

1479
Utilities / Re: PMVNC & Linux?
« on: October 06, 2013, 12:07:27 am »
Quote
I vaguely remember it being a non step forward or contained some trivial change. Do you, (or anyone), recall if there is any point in "upgrading"?

FWIW, I am using the 1.04 version from pmvnc104_ow.zip (at HOBBES). The updates seem to be minimal, but it is probably worth updating, especially if you have an SMP machine.

1480
Utilities / Re: PMVNC & Linux?
« on: October 02, 2013, 09:26:27 pm »
It is PM VNC, in eCS, that contains a JAVA thing to communicate with a JAVA enabled browser. Apparently VINO, in Linux, doesn't have that feature. I find that VNC Viewer in eCS works much better than Firefox anyway.

I expect that you are right about negotiating a common protocol. The delay is only a couple of seconds, so it is not a problem.

1481
Utilities / Re: PMVNC & Linux?
« on: October 02, 2013, 01:32:15 am »
Is there a version, (or an equivalent), of/to PMVNC for OS/2 that works with OS/2 and Linux... with Linux acting as the host?

I know that the version for OS/2 is ancient and it is highly unlikely to be compatible with modern versions, but there must be someone out there that has a solution and can save me some time duplicating their research.

HobLink/2 no longer works, (even though I have added the eCSreg*.ini files), so that is not an option.

Any help would be appreciated...
Thanks.


I just tried this, and it works. In eCS (OS/2) you need the PM VNC package installed (the server part), and configured (just add a password).

Then, use Firefox in Linux, with the URL "192.168.0.100:5800" (without the quotes, and use the address of the target machine). It will ask for the password. Enter that, and the eCS desktop will open in Firefox.

I am using Linux Mint 15 Cinnamon 64, and it comes with a program called VINO, which shows in the menu as "Desktop Sharing". You need to configure that to allow others to view, and control, your desktop. I turn off confirming a connection, and add a password. Set the rest as you like. Then, in eCS, I tried using Firefox, but it doesn't seem to work. Using VNCViewer from: http://hobbes.nmsu.edu/download/pub/os2/apps/internet/misc/pmvnc104_ow.zip works. Just connect to the URL (192.168.0.100:0), and enter the password. I notice that the connection takes a few seconds, where connecting to another eCS machine is almost instant. I suspect that is something that needs to be set, but it figures it out.

1482
General Discussion / Re: Backgroud celebrating 25 years old of OS/2 Warp
« on: October 01, 2013, 07:38:36 pm »
Quote
So, the zip.zip file will be automatically deleted, hope.

You will need to e-mail the archiver to get it deleted. The address is at the bottom of the incoming web page. If you just let it stay there, it will, eventually end up in the DELAYED folder, where it will, eventually, be removed when somebody gets around to trying to figure out what it is (could be years from now).

1483
Utilities / Re: SyncBackup & ssh-askpass
« on: September 30, 2013, 04:47:09 am »
Quote
      gid             = *insert your password here*

According to what I read, "gid" stands for "Group ID". That would seem to have nothing to do with passwords. In fact, I suspect that it is probably ignored, since it doesn't seem to matter what I put in that setting.

The RSync docs indicate that RSync (client) gets the password from the environment variable, which can be set just before opening RSync, or it could be set globally in CONFIG.SYS (with the associated security concerns). It seems that Linux (server) associates the uid (User ID) with the password that is assigned to that user. In eCS, or OS/2, it seems to always use "root" for both uid, and gid, which makes sense because eCS doesn't have the user ID association to passwords support.

1484
Utilities / Re: SyncBackup & ssh-askpass
« on: September 21, 2013, 05:18:54 pm »
Don't forget that the module name is case sensitive. It must match, exactly, on both ends.

1485
Utilities / Re: SyncBackup & ssh-askpass
« on: September 18, 2013, 11:22:11 pm »
Quote
Working with the commandline here, I noticed in your example;
Quote

    192.168.0.101::backups/

... called "backups/". I first I thought it to be a directory, but the "::" defines it as a module.

How does that apply... or is it not related/necessary?

The module is "backups". The directory to use, in that module, is "/", or the root of the module (/home/dougb/RSyncData). In this case, it is probably not necessary, however, if you wanted to store the U:\ACPI data in /home/dougb/RSyncData/ACPI you would use the command:
Code: [Select]
W:\UTILITY\RSYNC\BIN\RSYNC.EXE -a --delete --log-file=logs/RsyncTest.log U:/acpi/ 192.168.0.101::backups/ACPI/Note that Linux is case sensitive, so it will create, and use, the upper case directory name (in this case), while eCS doesn't care about that.

The trailing slash (on both source, and target), gives you a little more control over what RSync will work with. Look up "trailing slash" in the RSync docs.

Pages: 1 ... 97 98 [99] 100 101 ... 107